What is the Threads Comment Scraper?
The InsightSocial Threads comment scraper is a free Chrome extension that exports the whole conversation under a Threads post — every reply, the replies underneath those replies, and the ones Threads has filed away out of sight — to CSV, Excel, or JSON. Each row carries the commenter, the reply text, likes, timestamp, and the parent comment id that says where it sits in the thread. No Meta developer account, no app review, no API key.
The part that decides whether an export is worth anything is depth. A Threads post page serves you the trunk of the conversation and stops: the first level of replies, and a "hidden replies" bucket you have to open separately. Take only what the page hands over and a post with 843 replies exports as roughly 230 comments — you keep the opening remarks and lose the argument. This extension replays the request Threads itself uses for each sub-thread, then makes a second pass for the hidden bucket, so what lands in your spreadsheet is the conversation rather than its first paragraph.
Both of those passes are on by default, and both are switchable. They are the reason a one-minute run can turn into several minutes on a heavily discussed post — the work is proportional to how many separate reply threads exist, not to the raw comment count. If you only need the top-level responses, turn them off and the run is quick.
Who is it for?
- Brand and social teams reading how an audience actually answered a campaign post, not just how many liked it
- Market researchers collecting unprompted opinion on a product, a price, or a competitor from public discussion
- Content strategists studying which posts pull real conversation rather than passive engagement
- Founders and indie builders validating positioning against what people say back to accounts in their niche
- Community managers tracking sentiment under their own posts and finding replies worth answering
- Analysts and journalists building a structured record of a public conversation before it scrolls away
Key Benefits
- Reply threads followed all the way down — replies to replies are collected, not just the first level the page shows
- Hidden replies retrieved and flagged — the bucket Threads keeps behind a separate view is fetched and marked in its own column
- Conversation shape survives the export — parent comment id, reply depth, an is-reply flag, and the reply-to author on every row
- Post context travels with the replies — the originating post's URL, author, text, likes, and timestamp sit alongside its conversation
- Many posts in one run — point it at a profile, a keyword search, or your feed and it collects the posts first, then walks each conversation
- No Meta app review — nothing to register, no access request to wait on, no quota to budget
How to Use the Threads Comment Scraper
Step 1: Install the Extension
Add InsightSocial from the Chrome Web Store. The icon appears in your browser toolbar.
Step 2: Open the Post — or a Profile, Search, or Feed
Go to the Threads post whose replies you want. If you want conversations from many posts at once, open a profile, a keyword search, or your home feed instead. You need to be logged into Threads in your normal browser; Threads shows signed-out visitors very little, and the extension only ever reads what your own session already displays.
Step 3: Choose Post + Comments
Click the InsightSocial icon. The sidebar recognises which Threads surface you are on and offers Post + Comments. On a profile, search, or feed it also asks how many posts to work through — 5, 10, and 25 are the presets, deliberately small, because every post in the list means opening its conversation separately.
Step 4: Check the Two Depth Options
Under the scrape type sit Full reply threads and Replies Threads hides. Both are on by default and both are worth leaving on for research work — they are the difference between 230 rows and the full 843-reply conversation described above. Switch them off when you want a fast pass over top-level replies only.
Step 5: Start the Run
Click "Start Scraping". A counter tracks posts and captured comments as the run proceeds. Deep conversations take longer than wide ones: a post with 40 separate reply threads costs 40 follow-up requests, while a post with 200 flat replies costs almost none.
Step 6: Export
Click "Export" and pick CSV for spreadsheet work, .xlsx for Excel, or JSON for a script or an NLP pipeline. Every comment is one row, already flattened, with its post attached. Sessions also sync to your private InsightSocial portal, where you can re-open or re-export them later.
Frequently Asked Questions
Why does my export have fewer comments than the post's reply count?
Two ordinary reasons before you suspect a defect. First, the depth options: with Full reply threads off, only the first level is collected, which on a busy post can be a quarter of the total. Second, Threads' own counter includes replies that have since been deleted by their authors or removed by the poster — those no longer exist to be returned, by any tool. With both depth options on, what you get back is what a person could reach by opening every thread by hand.
What are hidden replies, and why are they separate?
Threads filters some replies out of the main conversation and puts them behind a separate view — the equivalent of a low-quality or flagged bucket. They are still public, they are just one click further away. The scraper fetches that view as a second pass and marks each of those rows with a hidden flag, so you can include them in an analysis, exclude them, or study the filtering itself.
How do I rebuild the nested conversation from a flat CSV?
Match each row's parent comment id against the comment id column. Rows with an empty parent are top-level replies to the post; the rest answer another comment. The reply depth column tells you how far down a row sits, and the reply-to author column names who was being addressed when Threads records it. In a spreadsheet that is one VLOOKUP; in pandas, one self-join.
How long does a full thread take?
Longer than a post scrape, and the reason is structural rather than a throttle on our side. Threads' post endpoint serves the reply trunk only; every deeper thread costs one replayed request, and the hidden bucket costs another on top. A conversation with many separate branches therefore takes minutes rather than seconds. If speed matters more than completeness, turning off the two depth options makes the run about as fast as a normal post scrape.
Can I export replies to posts I don't own?
Yes — that is the point, and it is where the official route stops. Meta's Threads API returns replies for posts on accounts you have authorized, and reaching even that requires passing app review. Anything on someone else's post — a competitor's launch, a journalist's thread, a discussion about your category — is out of scope for it. The extension sidesteps the question by reading the conversation your own logged-in browser is already rendering.
Will this get my Threads account restricted?
The extension behaves like an attentive reader. It requests the same conversations your session would load if you opened each thread yourself, inside your own browser, and it never posts, likes, follows, or messages on your behalf. Keeping volumes sensible keeps the activity indistinguishable from ordinary use.
Can I run sentiment or LLM analysis on the export?
Yes, and the structure helps. Because each row carries its parent and its depth, you can separate reactions to the post from arguments between commenters — two very different signals that a flat comment dump collapses into one. Comment text keeps its emoji and line breaks. The CSV drops straight into ChatGPT or Claude; the JSON suits a transformer pipeline.
How many comments can I export?
Scraping is unlimited on every plan, and a scrape you decide not to export costs nothing. The monthly quota is export credits, one per exported row, so a thread with 12 replies costs 12 and one with 800 costs 800:
- Free plan: 500 export credits per month
- Pro Monthly: 10,000 export credits per month for $9.99/mo
- Pro Yearly: 10,000 export credits per month for $95.88/year ($7.99/mo)
Working out which conversations are worth the credits? Run the Threads Post Scraper over a profile or a search first, sort the file by comment count, and export the conversations under the outliers. Comparing tools across platforms, the best ExportComments alternatives covers bulk comment export without per-link caps.