How to Export Instagram Comments to CSV, Excel, or JSON
Updated
Paste the Instagram post URL into a comment exporter such as ZocialComment, pick CSV, Excel, or JSON, and download the file — no signup or API keys required for the paste-and-export flow. This works for public Instagram posts and is the fastest route when you need comment text, usernames, timestamps, and engagement data in a spreadsheet or analysis pipeline. If the post is from a private account, or you need comments from hundreds of posts at once, read the relevant sections below before you start.
What you need before exporting
- A public Instagram post URL (the permalink that opens the post, not a profile link).
- A browser and a destination for the file — a spreadsheet app for CSV/Excel, or a script/notebook for JSON.
- A rough idea of why you're exporting, because that decides your format and mode:
- Client report or quick scan → CSV or Excel, Clean mode.
- Sentiment analysis, NLP, or a data pipeline → JSON, Raw mode.
Step-by-step: export Instagram comments
- Copy the post URL. Open the Instagram post, use the share/menu option to copy the link, or copy it from the address bar. It should look like
instagram.com/p/...orinstagram.com/reel/.... - Paste it into the exporter. On ZocialComment, paste the URL into the input and start the export. The tool fetches the comment thread for that post.
- Choose your output format.
- CSV — opens in Excel, Google Sheets, or any reporting tool.
- Excel — same data, ready-to-use workbook.
- JSON — nested structure for code, sentiment tools, or databases.
- Choose Clean or Raw mode (see the next section).
- Download the file and open it to verify row count and columns before you build anything on top of it.
Expected result: a file where each row (or JSON object) is one comment, with the comment text and associated metadata such as the author and engagement signals.
Clean mode vs. Raw mode
| Mode | What it contains | Best for |
|---|---|---|
| Clean | Readable, report-ready fields — comment text, author, and the essentials | Client reports, spreadsheets, quick review |
| Raw | The fuller payload, including the underlying fields an API would return | Sentiment analysis, custom scripts, data pipelines |
A reviewer quoted on the site describes using Clean for client reports and Raw when they need the full payload for sentiment analysis. Pick Clean unless you're feeding a program.
Exporting many posts at once
If you're working with a campaign, a hashtag set, or a research sample rather than one post, you need bulk export instead of repeating the single-post steps. One researcher cited on the site exported comment data from 200+ videos for a thesis and relied on bulk export plus JSON to feed a data pipeline. The same pattern applies to Instagram: collect your post URLs first, then run them through the exporter in one batch rather than one at a time.
Using the exported file
- Spreadsheets (CSV/Excel): sort by engagement to surface top comments, filter by keyword, or pivot by author to find repeat commenters.
- Sentiment / NLP tools (JSON): load the file directly into your script; the nested structure preserves fields a flat CSV would drop.
- AI assistants: ZocialComment offers an MCP integration so you can export and analyze comments inside Claude or ChatGPT, working on exports up to 100,000 comments. That's useful when you want a summary ("what are people asking?") without manually opening the file.
- Browser extension: if you'd rather not leave the page, the Chrome extension lets you export a post to CSV/JSON directly from Instagram after signing in once.
Common failures and how to handle them
- Private account or restricted post. The exporter can only read comments it can access. If the account is private, the export won't return the thread — you need access to the post first.
- Missing comments. Deleted comments, hidden comments, and replies nested under a parent may not appear the way you expect. Check whether your tool flattens replies into rows or nests them.
- Rate limits or partial exports. Pulling very large threads can be throttled. If a big post returns fewer comments than you see on Instagram, retry, or split the work across sessions.
- Wrong URL type. A profile URL won't export comments — you need a specific post permalink.
- Format mismatch. If your spreadsheet mangles emoji or non-Latin text, re-export as CSV with UTF-8, or switch to JSON and parse it in code.
Choosing a tool: what to check
Use the same criteria across options:
- Formats supported — CSV, Excel, and JSON all matter if you both report and analyze.
- Single vs. bulk export — one post is easy anywhere; bulk is where tools differ.
- Clean vs. raw output — a raw/API-style mode saves you from rebuilding fields later.
- Access requirements — ZocialComment's paste-and-export flow needs no signup or API keys, though the Chrome extension requires signing in once.
- Cost — the site references a free tier and a paid pass (a user mentions a $14 pass for 12,000 comments), but check the current pricing page for up-to-date terms rather than relying on a quoted figure.
If you only need one post's comments for a report, the paste-and-export route with Clean CSV is enough. If you're building a dataset across many posts, prioritize bulk export and JSON.