New: Monthly plans available. Ask in chat

Guide

Export Threads Replies for Brands — Save Campaign Feedback to CSV, Excel & JSON (2026)

By Sarayut L., Founder, ZocialCommentNovember 16, 20269 min read
Export Threads Replies for Brands — Save Campaign Feedback to CSV, Excel & JSON (2026)

Export Threads replies now

Free — first 100 comments of any post, no signup. CSV, Excel & JSON.

To export Threads replies as a brand, paste the link of your campaign or launch post into a Threads reply exporter and download the replies as CSV, Excel or JSON, one row per reply with the username, text, likes and timestamp. Threads has no export button for replies, Meta's data download only covers what you wrote yourself, and the official Threads API needs a developer app and only reads your own posts. For a weekly report or a campaign review, an exporter is the shortest route; for a permanent pipeline on your own profile, the API is.

This guide is for social media managers, community teams and creators who need the replies in a file they can tag, count and hand to someone else. We run the Threads exporter described here, so the column details below are what the file actually contains.

Why brand teams end up needing the replies in a file

Replies on Threads are where customers ask the questions your FAQ missed, where a launch gets its first honest reaction, and where complaints surface before they reach support. Reading them in the app works for one post on one afternoon. It stops working when you need to:

  • Report on a campaign. A manager wants to know what people said, not just how many interactions there were.
  • Route customer questions. Shipping, sizing and pricing questions belong with support or sales, and they need a list, not a screenshot.
  • Compare launches. Was the reaction to this drop warmer than the last one? You can only answer that with two files side by side.
  • Keep a record. Replies get deleted. A dated file is the only copy you control.

Five routes compared side by side

There are five realistic ways to get Threads replies, or numbers about them, out of the app. They differ mainly in whose posts they cover and whether the reply text survives.

MethodSetupWhose postsReply text keptOutputBest for
Meta "Download your information"Request in Accounts Center, wait for the fileYour own activity onlyOnly replies you wroteHTML or JSON archiveBacking up your own posts
Threads InsightsNone, built into the appYour own profileNo, numbers onlyOn-screen chartsReach and interaction trends
Manual copyingNoneAny public postYes, by handWhatever you paste intoUnder ~20 replies
Official Threads APIMeta developer app, reply permissions, app review, codeYour own posts onlyYes, full conversationJSON via your codeDaily automated pipelines
ZocialComment exporterPaste the post linkAny public postYes, one row per replyCSV, Excel, JSONCampaign reviews and weekly reports

A few details behind the table. Meta's Download your information tool, reached through Accounts Center, bundles your Threads posts and the replies you left on other people's posts. Replies written by others under your posts are not part of it. Threads Insights reports views, likes, replies, reposts and follower numbers, which tells you a post got 340 replies but not what any of them said.

The Threads API is the one Meta-built route that returns reply text. Its reply management endpoints list the replies and the whole conversation under a post, but only with an access token from the profile that published it, and only once your app has the reply permissions approved.

Which route to use when

The decision usually comes down to two questions: do you own every post you need, and do you need this once or every day?

  • You want a backup of what your brand posted: use Meta's data download. It is the only route that captures your own posts in bulk.
  • You only need reach and engagement numbers: Threads Insights is enough. No file needed.
  • A post has a dozen replies: copy them by hand into a doc. Any tool is overkill.
  • You need replies from your own profile every day, inside your own systems, and have a developer: build on the Threads API. It is official and it scales.
  • You need replies from campaign posts this week, from posts on a creator's or partner's profile, or from a competitor's launch: use an exporter. It is the only route that covers posts you do not own, and it takes a minute rather than an app review.

Most brand teams land on a mix: the API, if they have one, for their own always-on monitoring, and an exporter for everything ad hoc, especially collaboration posts that live on someone else's profile.

What lands in each reply row

Each row of a Threads export is one reply. These are the columns, with what a brand team does with each:

  • author and username: the display name and handle. Use the handle to spot repeat repliers across posts.
  • text: the full reply, emoji included.
  • likes: how many people liked the reply. This is your best quick signal of how many people agree with it.
  • replies: how many direct replies the reply has received. A customer question with replies at 0 has not been answered by anyone.
  • created_at: when the reply was posted, as an ISO 8601 timestamp in UTC.
  • id, code and canonical_url: the reply's identifiers and its permalink, so anyone reading the report can click straight to the reply and answer it.
  • user_pk and user_is_verified: the replier's numeric account ID and whether the account is verified. Verified replies from press or partner accounts are worth flagging.
  • avatar_url: the profile picture link, useful for slides.

The file also carries language, is_pinned and reply_to_id so it lines up with exports from other platforms. Threads does not provide those values, so they are empty or false in a Threads file. If you track multiple languages, add your own column.

Saving campaign replies, step by step

  1. Collect the post links. On each post, open the share menu and choose Copy link. Include the launch post, each campaign post and any post on a partner's profile.
  2. Check the size. Paste a link at the Threads exporter. The reply count appears before anything downloads, which tells you whether the post fits within the first 100 replies.
  3. Batch the rest. With a paid export, paste up to 20 links at once, one per line. Each post downloads as its own file.
  4. Pick the format. Excel if the report goes to a manager, CSV for Google Sheets or an AI assistant, JSON for a dashboard.
  5. Stack the files. Paste each file into one sheet and add a post column with a short name ("launch", "teaser 2", "creator collab") so every reply keeps its source.

Building a weekly Threads replies report

A file is not a report. The structure below turns a week of replies into one page that a manager reads in two minutes.

1. Tag every reply

Add a tag column with four values: question, complaint, praise and other. On a few hundred rows, tagging by hand takes about as long as a coffee. On more, paste the CSV into an AI assistant and ask it to suggest a tag per row, then skim the result; it is fast, but it misreads sarcasm, so check the complaints column yourself.

2. Weight by likes

A complaint with 80 likes is not one complaint, it is a lot of people agreeing. Sort each tag by likes descending and report the top three of each. In Excel, =SUMIFS(D:D, L:L, "complaint") (with likes in column D and tags in column L) gives the total weight behind each tag, which is a fairer headline than a raw count.

3. Track open questions with created_at

Filter to tag = question and replies = 0. Those are questions nobody has answered. For each one, report time minus created_at is how long it has waited. If your team logs when it answers (a simple answered_at column), answered_at - created_at is your response time, and its median is a number worth putting on the report every week. Remember that created_at is in UTC; convert it before comparing with your local working hours.

4. Keep the same shape every week

Use the same tags and the same layout each week: replies by tag, top liked in each tag, open questions and their age, and median response time. Consistency is what makes week-over-week changes visible. A spike in complaints after a shipping change shows up immediately when last week's sheet sits next to this week's.

Where each route falls short

  • The data download is slow to arrive and holds your words, not your audience's.
  • Insights cannot tell you why a number moved.
  • Manual copying drops likes and timestamps unless you retype them, and nobody does past the first page.
  • The API needs an app, permissions approval and maintenance, and still cannot see posts on profiles you do not control.
  • An exporter only sees what Threads shows publicly. Replies the author hid, restricted or deleted are not in the file, and a reply count on the post can include them.

How we know this

This guide comes from operating the Threads exporter at ZocialComment, not from reading about it. Three things we see repeatedly:

  • The badge and the row count rarely match exactly. The reply count Threads shows on a post includes replies that were later hidden or deleted. A file a few rows short of the badge is normal, not a failed export.
  • Threads is one of the slower platforms to read. Measured on our production exports from 8 September to 8 October 2026, the median time to a 100-reply file was about 7 seconds on Threads, against about 2 seconds on TikTok and YouTube, and 59% of Threads exports finished in under 10 seconds.
  • The empty columns are deliberate. Threads does not give us a language, a pinned flag or a parent reply ID, so we leave those columns blank rather than guess. Keeping them in place means a Threads file stacks cleanly with an Instagram or TikTok file in the same report.

The column names and limits in this guide are the live product values at the time of writing. For anything about Threads' own rules, Meta's documentation linked above is the authority.

Handling customer replies responsibly

A reply export is a list of real people and what they said. Treat it as customer data: keep it in your team's workspace, collect it for a purpose you can name (answering questions, measuring a campaign), and delete old files when that purpose is done. If any of your audience is in the EU, the GDPR principles of purpose limitation and data minimisation apply. Do not use the usernames to send unsolicited messages in bulk; answer people where they asked, on the post.

The first 100 replies of any public post export with no signup. Bigger posts and batches of up to 20 links are a one-time payment, never a subscription; see pricing for the details.

Export your Threads replies →

Related reading: downloading Threads comments to CSV, Excel and JSON, opening Threads comments in Excel, copying Threads replies.

Export Threads replies now

Paste any Threads post URL — every public reply in CSV or JSON.