SOMETHING IS WRONG / 7 MIN READ
How many comments a video can hold — and where every limit really sits.
There is no published cap on how many comments a video collects. The limits people actually run into live somewhere else: in what a page loads, what the counter counts, and what any tool can carry. This page walks the four layers.
“How many comments can a video have” sounds like a question with a number for an answer. It is really a question about four different ceilings — and the one you are hitting depends on where you are reading from.
Is there a cap?
Not one anybody hits. The first video ever posted to YouTube now carries more than ten million comments, and busy uploads cross hundreds of thousands as a matter of course. There is a hard limit in the other direction, though — one commentcan be at most 10,000 characters, top-level and replies alike. That is why unusually long comments usually end with a pointer elsewhere: the text did not fit.
So the popular question is the wrong one. The useful question is how much of a thread any given reader — a page, a counter, a tool — will actually hand you. Those are the four layers below.
The four limits that actually bite
Each layer below is a deliberate design choice somewhere between the platform and your screen. None of them is a bug, and each has its own way around — or its own reason there is no way around.
- The page loads in batchesThe comment section on the watch page starts with a first batch and adds more only when you ask. Switching the sort discards what is loaded and starts again. This is a reading interface with a floor, not a window onto the whole thread.What to do: For a quick read, keep pressing Load more. For the real thing, load the thread in a tool — the see-all page walks through both paths.
- The counter is a tally, not an inventoryThe number under the video includes replies, refreshes on its own schedule, and never shrinks in step with deletions. It counts everything the platform considers part of the thread — including things that will never load on a page, like comments held for review.What to do: Treat the number as context, not as a target the page should reach. A mismatch between the count and what loads is normal — it is not a signal that something is broken.
- Tools fetch in pages, tooAny tool that reads comments — including this site's — fetches them in batches, follows the cursor from batch to batch, and has to stop somewhere: on very large threads no tool receives every comment the platform has ever seen. Big threads are served as large samples.What to do: Check what a tool reports about coverage before trusting an export at face value. A labelled sample is worth more than a file with an unspoken gap.
- Some comments are out of reach by designComments that are held for review, deleted, filtered by the channel's rules, or restricted to members never appear in the public thread. No viewer, extension or export can read them back — every tool reads the same public data, so a limit for one is a limit for all.What to do: Save what is public while it is public. If a comment matters, an export you made while it was live is the only version that survives its removal.
When the numbers don’t match
The most common worry this page answers is a comparison: the counter says one number and the loaded thread shows another. As the second layer explains, that mismatch is the normal state of affairs — the count includes replies, lags, and never shrinks on cue. It is not evidence that comments are missing, hidden or deleted.
If the thread is absent rather than short, that is a different problem on the not-showing page: the section never appeared at all, and the fix is on the settings side. If it appears and never finishes loading, the request is being dropped somewhere between you and the page — that one is covered by the not-loading page. And if comments were there before and are gone now, nothing on this page applies — that is a removal, and the where-did-they-go pageworks through the five ways it happens.
When coverage matters, the number that serves you is not the counter — it is what a tool reports about how much of the thread it actually reached. Look for that figure before treating any export as complete.
Saving what is public
Every layer above has the same practical consequence: what is reachable today is worth more than what might be reachable later. The thread you can read now is the one worth exporting now — and the tools below each handle it differently.
- Export everything public — CSV or JSON of the thread as far as it can be reached — with a coverage check before you trust it.
- Running this across many videos — When the limits matter at scale — a whole channel, a campaign, a back catalogue.
- Read the thread in one view — The full public thread outside the watch page — loaded in one pass, sortable five ways.
Want to read the whole thread anyway?
Loading everything from first comment to last has its own page — including the parts that stay out of reach.