Where does The Fork get its Pitchfork review scores?

Updated

The Fork (the-fork.vercel.app) draws its scores from Pitchfork's own album reviews. The site describes itself as "Rotten Tomatoes for albums" and states that it aggregates "every critic review score," filterable by genre, decade, score, country, and year. So the underlying ratings are Pitchfork's review scores, not a separate or independent scoring system.

What the site says about its data

The Fork's own description is the clearest statement of scope:

  • Source: Pitchfork album reviews
  • Coverage: "every critic review score" — i.e., it aims to include all of them, not a curated subset
  • Aggregation: scores are collected and displayed together in one browsable, filterable list
  • Filters: genre, decade, score, country, and year

The "Rotten Tomatoes for albums" framing is useful for understanding the model: Pitchfork supplies the individual review scores, and The Fork is the layer that gathers them into one place and makes them sortable.

How the data loads

The page evidence shows the interface rendering as "Loading reviews… Load more." That tells you two things about how the data reaches you:

  1. Reviews are fetched dynamically rather than baked into a single static page.
  2. Results are paginated — you see an initial batch, then pull in more with "Load more."

In practice, if the list looks empty or incomplete at first, it's likely still loading or waiting for you to request the next batch, not a sign that the dataset is missing.

What this means for using the scores

Because the scores originate from Pitchfork, The Fork is best understood as an index and filter tool rather than a new rating authority. If you want to know how a given album was received, the score you see traces back to Pitchfork's review. If you want to browse by genre, decade, score range, country, or year, that's the value The Fork adds on top.

One caveat worth keeping in mind: the site's description states the coverage goal ("every critic review score"), but the page itself only shows a loading state and a "Load more" control in the available evidence. Whether the collection is truly complete, and how current it is, isn't something the visible page content confirms — so treat the "every" claim as the site's stated intent rather than a verified count.