The Thread, Opened
Top-level comments plus the replies TikTok collapses behind a link, expanded and kept in order, as far down the section as the page will keep loading.
A TikTok comment section isn't a list you scroll to the end of. AllyHub keeps opening it, and tells you what it got.
The app hands you a few hundred comments, hides the replies behind a link, and does it in an order that changes while you read. AllyHub works down the section instead — opening the threads, keeping only the comments you asked for, stamping each one so it can be found again, and sorting what comes back.
Top-level comments plus the replies TikTok collapses behind a link, expanded and kept in order, as far down the section as the page will keep loading.
Point it at a single URL, at everything a creator has posted, or at the videos where your product keeps coming up, and the comments land in one table.
Say the filter up front and it applies while fetching: comments that name a term, comments shaped like a question, comments above a like count you set.
Each row carries the video it came from, the comment's own ID, the reply it sits under, and the moment you pulled it, so a quote you cite can be traced back.
The same question asked ninety times is one finding, not ninety rows. AllyHub sorts the pull into the things people keep repeating, and gives you that list instead.
The TikTok comments exporter is part of the same job: take the table as CSV, JSON, or Excel, or stay in the run and ask for a sentiment read or the brand mentions.
Name the videos, say which comments you want, and get the section back as rows.
Paste a video link, a list of them, or a creator's handle, then say in a sentence which comments matter and how deep to go.
It records each comment's text, the handle behind it, its like and reply counts, the time it was posted, its place in the thread, and pinned or creator-liked marks.
Take the file, or carry on in the same run with follow-up questions. Save the video set as a Playbook and run it again after the next drop.
Every tool in this category implies it got all of them. A TikTok comment section does not work that way.
TikTok feeds the section in as you scroll, hides replies behind a link, and reorders between loads. AllyHub keeps going until the page stops giving, then reports the number it captured and the moment it ran. You get a dated sample you can describe, not a total somebody implied.
.jpeg&w=1920&q=75)
TikTok's only official comments endpoint sits inside a research program: a non-profit project, an approved institution, one of a short list of countries, a proposal and an ethics review. Everyone else is reading the public page. AllyHub reads the public page too, just faster and into a table.
.jpeg&w=1920&q=75)
The app rounds engagement for display, which is fine to look at and useless to sort by. What comes back are the counts themselves, so you can rank comments by likes or replies and get an order that means something.
.jpeg&w=1920&q=75)
Friday's comment section under a video is not Tuesday's, so this is a job you do more than once. Keep the video set as a Playbook, re-run it after each drop, and because your AllyHub never starts from scratch again, setting it up is a one-time cost.
.jpeg&w=1920&q=75)
Creators, brand and community teams, product researchers, and agencies who need what the comment section says without living in it.
The video that finally works is the one whose comment section becomes unreadable, and the comment that is next week's whole video is sitting somewhere past number three thousand. Pull the section, read the repeats, and the next video gets chosen from what they said instead of from a hunch.
Your product turns up in somebody else's video, and the conversation about it happens in a comment section you do not own and cannot search. Collect the sections from every video where you are named, and that conversation becomes something you can actually sit down and read.
The objection that kills a purchase never makes it into a survey, because nobody fills in a survey to complain about a zip. It goes into a comment under a review video. Pull those and you are reading research nobody had to be recruited for.
The campaign report is a folder of screenshots and a sentence starting "people seemed to like it". Bring back the comments with their counts and their dates, and the read-out has something underneath it the client can check.
Explore more AI-powered tools across research, content, and data.

Amazon Bestsellers Scraper — pull any ranking list with rank position, ASIN, price, and rating. No code, no Amazon API, all marketplaces. Try AllyHub free.

Amazon Product Scraper — pull structured product data from any Amazon domain without code or the Amazon API. Export JSON or CSV. Try AllyHub free.

Amazon Niche Finder — start from your interests, a category, or a rival, and get underserved niches scored on demand vs competition. Try AllyHub free.
Guides on what a comment section can prove, where the real objections sit, and keeping comment research honest.

Struggling to scrape Amazon product data without getting blocked? Learn safe, effective Amazon scraper methods using APIs, no-code tools, and Python.

Discover the 10 best Amazon competitor analysis tools used to track competitors, uncover keyword gaps, and understand why top listings outperform yours.

Discover the best Amazon SEO tools to boost your rankings, find high-converting keywords, and outpace competitors. Reviewed and ranked for e-commerce marketers.
The questions that come up before a comment pull is worth running: what comes back, how much of it, and what you may do with it.
It turns a video's comment section into rows instead of a scroll: the text, who wrote it, what it earned, and where it sits in the thread. Tell AllyHub which videos in a sentence or two, and it works through several of them, or a creator's whole library, opening the reply threads as it goes.
Yes. A single video with the standard comment fields runs free. What the paid plans carry is the bigger shape of the work: many videos in one job, deeper reply expansion, filtering at fetch, scheduled re-pulls, and the analysis pass on top.
No tool can promise that, and the ones implying otherwise are not describing how TikTok behaves. The section loads as you scroll, replies sit behind a link, and the order shifts between loads. AllyHub goes as far as the page will go and then tells you the number it returned and when it ran, so what you hold is a sample with a date on it rather than an unqualified total.
Yes, and that is the usual shape of the job. Give it a handle, a list of links, or the videos where a term shows up, and every row comes back tagged with the video it belongs to, so you can read one section or compare across all of them.
No. TikTok's official comments endpoint is part of a research program with an eligibility bar most people cannot clear, and it is not what this uses. AllyHub reads the public page the way a person would, so there is no developer account, no application, and nothing to write.
It reads only what a visitor sees without signing in, and it does not go behind a login or build profiles of the people commenting. Comments are still written by real people, so treat the output as personal data: keep what the research question needs, and check your own obligations before you store or publish it.
Scrolling gives you an impression and no way to show your work. This gives you the comments, their counts, their dates, and the repeats grouped together, kept as a Playbook that compounds with every task — so the next video's section is one sentence away instead of another hour.
That is the same job under another name, and for most people the export is the whole point of the pull. One row per comment, carrying the columns you asked for rather than every field it holds — the system waiting downstream usually has opinions about that. It is written as UTF-8 with separators escaped, so a comma inside a comment stays in its own cell and emoji survive the trip instead of arriving as boxes, and posting times come out as real dates rather than ten-digit numbers. When several videos go into one job, rows are deduplicated by comment, so a thread quoted under two of them does not land twice.