Instagram Comment Export Tools for CSV, Excel, and Replies
Compare six extension, hosted, official API, and developer workflows by reply hierarchy, output format, access, and recovery behavior.
The useful comparison is not which product promises the most comments. It is whether the workflow preserves the rows, fields, reply relationships, terminal state, and file shape required by the handoff. This guide compares six distinct methods: two focused browser-extension paths, one preview-first Web service, one managed dataset service, Meta’s official API route, and a developer library.
Disclosure: Web Tidy publishes this comparison and develops one unpublished local candidate below. Its code, fixtures, package, and writer were reviewed locally, but its current Instagram request templates were not tested against a real account in this run. Competing facts come from publisher-controlled sources opened August 17, 2026. No competitor was installed, purchased, or run. The title deliberately omits “best,” a year, a count modifier, and Free/Paid because evidence is not uniform enough for those claims.
Quick picks
- Choose Web Tidy for local evaluation when a fixed flat parent schema, durable task state, and partial artifacts matter more than immediate Store availability.
- Choose Comment Exporter when a documented top-level CSV baseline and public Store listing are sufficient.
- Choose exporter24 when a masked preview before sign-in and CSV export fits the decision process, but verify replies first.
- Choose Apify when a managed multi-URL dataset, documented reply objects, API access, and multiple export formats matter.
- Choose the Meta API for authorized professional-account media and maintained application workflows.
- Choose Instaloader for Python-controlled normalization when you accept maintenance and session handling.
How the methods were compared
Every included method has a current publisher or project source and a direct route to comment data. The shared dimensions are target scope, reply evidence, file or dataset format, field clarity, task continuity, access model, and evidence state. Giveaway pickers, sentiment-only dashboards, follower exporters, media downloaders, and products supported only by third-party roundups were excluded.
1. Web Tidy Instagram Comments Exporter
Web Tidy’s local 1.0.0 candidate accepts one supported Instagram post or Reel URL and offers Comments or Comments + replies, a row limit, pacing, CSV/XLSX, pause, resume, stop, partial results, and History. Its writer order is User Id, Username, Comment Id, Parent Comment Id, Comment Type, Comment Text, Profile URL, Profile Pic URL, Date, and Like Count.
Top-level and per-parent reply cursors are persisted separately, duplicate Comment Id values are removed, and History keeps up to 20 terminal tasks. Stop keeps confirmed rows. Reply parsing and fixtures exist, but the live request template is still a user-operated gate; an unavailable reply source yields Attention/partial rather than a false zero-reply success.
The UI shows 100–10,000 row options, while the current local free entitlement normalizes runs to 100. There is no public checkout or verified Store URL. This makes it a local evaluation candidate, not a live installation recommendation. See the product page and documentation.
2. Comment Exporter
The Chrome Web Store listing currently shows version 1.0.18, 10,000 users, CSV output, and seven fields: comment ID, text, username, username ID, profile URL, profile picture URL, and date. Its publisher FAQ says the user must log in to Instagram, free mode exports 100 comments at a time, paid mode reaches 10,000, and a user may pause and wait after a platform limit.
That evidence supports a focused top-level CSV baseline. The reviewed pages do not establish a Parent Comment Id, reply object, native XLSX, or durable artifact/history contract. Use a small authorized sample with known replies before treating the file as a threaded export.
3. exporter24 Instagram Comment Exporter
exporter24’s current product page accepts a public post URL, shows masked rows, and asks the user to sign in for a full CSV export. The page names commenter details, text, likes, date, and source-post fields. Its pricing page describes Local and Boost modes, credits, subscriptions, and local history.
This is useful when previewing fit before committing to a run. The reviewed product page talks about conversations and organizing replies, but it does not establish a Parent Comment Id or nested reply contract. Recovery and credit treatment after a failed comment run are also not clear enough to claim. Recheck current pricing before purchase.
4. Meta Instagram API
Meta’s official Get Comments request documents a GET request to the media /comments endpoint for authorized Instagram professional-account workflows. It returns API data containing comment IDs, text, and publication time; the collection documents app authorization, permissions, and account scope.
This is the right category for an organization that manages the professional account and needs an authorized application pipeline. It is not a general arbitrary-post URL tool and does not generate CSV/XLSX. The application owns paging, reply modeling, persistence, de-duplication, retry policy, storage, and transformation.
5. Apify Instagram Comments Scraper
Apify’s official Actor page accepts one or more Instagram post or Reel URLs. It documents an includeReplies option, reply arrays, IDs, text, timestamps, owner information, likes, reply counts, datasets, scheduling, API access, and downloads in JSON, CSV, Excel, XML, and HTML.
This is the strongest documented managed-dataset option in the group for replies and multiple formats. It still needs a file-shape check: nested reply JSON may not automatically become the flat parent-ID table required by an analyst. Pricing and accessible counts are volatile, and the hosted provider’s current account, processing, and retention model should be reviewed for the actual project.
6. Instaloader
Instaloader’s project documentation says Post.get_comments() yields comments with IDs, text, owners, creation time, likes, and answers; each answer exposes its own ID, time, text, owner, and like count. A Python pipeline can write the parent comment first and then one row per answer carrying the parent ID.
The benefit is deterministic normalization and file creation under your control. The cost is maintenance: no finished task UI, workbook, retry policy, or partial artifact is provided. The developer must handle access context, rate limits, checkpoints, duplicates, encoding, session storage, version changes, and safe stopping.
Choose by job
For one interactive top-level CSV, Comment Exporter is the clearest public baseline. For a preview-before-export workflow, exporter24 is relevant. For a managed multi-URL dataset with documented replies, choose Apify. For authorized professional media and an application team, choose Meta’s API. For bespoke Python normalization, choose Instaloader. For a local task model with flat parent IDs and recoverable partial artifacts, evaluate Web Tidy while preserving its Store and real-site gates.
Choose by delivery type
Extensions keep the workflow close to a browser tab but depend on current page access and extension lifecycle. Hosted services move runs and datasets into a provider account and may make scheduling easier. Official APIs use formal application authorization but require engineering. Libraries maximize control while making the user responsible for access, storage, updates, and error recovery.
CSV, XLSX, and JSON are different decisions
CSV is portable and easy to inspect, but it is flat. Native XLSX is useful for workbook handoff and a stable sheet name. JSON is best for preserving nested replies before flattening. “Excel” in marketing copy does not prove native .xlsx; “replies supported” does not prove Parent Comment Id; and a completed file does not prove every visible row was accessible.
For a flat thread, write one row per comment or reply, leave Parent Comment Id blank for a top-level row, and copy the parent ID into every reply row. Store top and reply paging separately. Generate all formats from the same persisted normalized rows so CSV and XLSX cannot drift.
Frequently asked questions
Which option has the clearest public reply evidence?
Apify documents reply objects and includeReplies; Instaloader documents an answers iterator. Web Tidy has local reply code but a real-site request-template gate.
Which option is already available in the Chrome Web Store?
Comment Exporter has a public listing. Web Tidy does not yet have a confirmed Store item ID or URL.
Can an “Excel” export still be CSV?
Yes. Verify the downloaded extension and worksheet structure before promising native XLSX.
What should a partial result contain?
Confirmed rows, immutable settings, target, terminal reason, and enough cursor/state provenance to avoid calling it complete.
Does the official API work for any public post?
No. The reviewed collection is for authorized professional-account workflows and managed media.
Should pricing decide the ranking?
Not here. Price evidence is mixed and volatile, so price and Free/Paid were omitted from the title and ranking logic.
Where are Web Tidy’s exact controls documented?
See the product page and Docs.