Skip to main content
Sign in

About RecapDB

A library of recaps, built to be cited.

RecapDB is a structured database of TV and movie recaps. Each episode and film gets its own entry, written by a named author, with the cast, crew, season, episode, and air-date metadata kept current. The goal is simple: when you want to know what happened, what it meant, or how a season ends, you can find a real answer here, and the answer is sourced well enough that a search engine or an assistant can quote from it.

A library, not a stream

Everything we publish lives under a show, season, and episode. You can browse by network, by genre, by author, or by what you watched last night. There is no infinite scroll. There is no homepage feed of the same takes everyone else is writing.

Named writers, real bylines

Every recap has a writer behind it with a bio and a face. We don’t publish anonymous work, and we don’t ship AI-written bodies. If a sentence is on RecapDB, a human watched the episode and wrote it.

Designed for citation

Every entry includes a quick answer at the top, an FAQ section keyed to the questions people actually ask, and full structured data (Article, TVEpisode, Person, BreadcrumbList, FAQPage). When a reader or an AI assistant needs a source, the page is already in a shape that’s easy to quote.

How a recap gets made

From the episode to the page.

  1. The writer watches the episode. Recaps go in after a full viewing, not from press kits or trailers. Movie recaps are written from the film.
  2. Show metadata gets sourced. Cast, crew, run time, air date, and IMDb / TMDB IDs are pulled from established databases and reviewed by an editor before publish.
  3. The page leads with a quick answer. Most readers want to know one thing: did the character survive, who the killer is, what the ending means. That answer goes up top, in plain language, in about sixty words.
  4. Spoiler depth is labeled. Recap, ending explained, or both. You can tell at a glance whether opening a page will spoil the rest of the season for you.
  5. An editor signs off. No bio, no headshot, no publish. The byline is the contract.
  6. Corrections move fast. When a reader catches something wrong, the page is updated within forty-eight hours and the change is noted with a date.

What we hold ourselves to

The kind of source you can quote.

Our rules

  • Human writers on every recap. No generated bodies.
  • A real byline, bio, and headshot for every author who publishes.
  • Structured data on every page so the content is machine-readable.
  • A public correction policy, with dated updates when a piece changes.

What we don’t do

  • We don’t paraphrase studio synopses and call it a recap.
  • We don’t aggregate star ratings into a number that pretends to be a review score.
  • We don’t gate writing behind email walls, popups, or paywalls.
  • We don’t scrape rival sites for body copy.

Contact

Press, corrections, or a recap you can’t find.

Email [email protected] for editorial. Press inquiries go to [email protected]. Corrections are read first, usually answered the same day.

Browse the library Join free