GETTING THE DATA OUT / 7 MIN READ
How to download YouTube comments without losing context.
A clean export is more than copied text. Keep the source, timing and conversation structure close enough that someone else can trust what they are reading.
You do not need every comment to answer every question. You need a reproducible slice of the conversation, with enough context to understand who said what, when they said it and how other viewers responded.
Before you export
Start with a public video and write down the question your export should answer. Are you collecting product objections? Looking for repeated questions? Checking how a launch landed? The question determines which filters are useful and keeps a large thread from turning into an undirected dataset.
Paste a video link, preview the thread and carry your search or date filters into a CSV or JSON export.
Open the downloaderThree practical steps
- Load and verify the source.Check the title, channel and video ID before you collect anything. A copied URL can point to a different upload than the one in your brief.What to do: Paste the link into the downloader, confirm the title, channel and video ID match what you meant to collect, then open the thread preview.
- Filter before you download.Use a phrase, date range, likes or reply count to define the slice. Filtering first makes the export easier to review and easier to explain.What to do: Set the phrase, date range or engagement filters while previewing — the export inherits exactly the slice you see.
- Keep a traceable file.Choose CSV for a human review pass or JSON for a script. The video ID is written into the file name, so an export never drifts away from the video it came from.What to do: Choose CSV for a review pass or JSON for a script — both write the video ID into the file name for you.
What the export contains
Every export carries the same five columns — the words, who wrote them and how the thread answered. Nothing else, so the file stays readable in a spreadsheet:
- text_plain — the comment body, as written.
- author_name — who said it.
- like_count — how many viewers backed it.
- reply_count — how much of a conversation it started.
- published_at — when it was posted.
The video ID travels in the file name, youtube-comments-<video_id>.csv, so every file still points back to its source video without dragging a long identifier column through your data. CSV and JSON carry exactly the same five fields — pick the format your next tool reads, not the columns. If that tool is Excel, the file needs one setting before it opens cleanly: why the encoding breaks and which dialog fixes it.
Check the limits
YouTube does not expose every possible comment in every situation. Deleted, held, members-only or disabled comments may not be returned, and API quotas can affect how much a job can fetch. Treat coverage as part of the result. A smaller, labelled sample is more useful than a large file with an unspoken gap.
Putting the file to work
Run one, read the thread it came from, and know what “all” means before you quote a number from a big thread.
- Run your export — Paste the link, preview the thread and carry your filters straight into CSV or JSON.
- Read the thread it came from — The whole public thread in one view — useful before choosing the slice, and after.
- The reading side of the same job — How to see the whole thread outside the watch page — and when "all" really is all.
Ready to search the thread?
Open a public video and find the language behind the headline.