How to Export App Store and Google Play Reviews to CSV

Straight answer: the App Store has no one-click "export reviews to CSV" button. App Store Connect will show you every rating and review in its dashboard, but it won't hand you a spreadsheet. To get App Store reviews into a CSV you have three real routes — Apple's public customer-reviews RSS feed (free, no code, roughly the last 500 reviews per country), the App Store Connect API (JSON you convert yourself), or a third-party tool that does the conversion for you. Google Play is the friendlier store here: it actually generates downloadable CSV review reports for you, monthly, in a storage bucket.

This page walks every method honestly, including the gotcha each one hides — the RSS cap, the API's auth, Google's UTF-16 encoding, the third-party price tag. Then the part nobody selling you an exporter mentions: a CSV is a dead snapshot the second it downloads. If you're exporting reviews to actually answer them, the export is step one of the wrong job.

No. This is the first thing worth saying plainly, because most people land on this search after hunting for an export button that doesn't exist. Open App Store Connect, go to your app, click Ratings and Reviews, and you get a browsable list you can filter by territory — but there is no "Download CSV" anywhere on that screen. The reports you *can* download (Sales, Finance, App Analytics) contain numbers and metadata, not the text of customer reviews.

So when you need App Store review content in a spreadsheet, you're building or borrowing a pipeline. There are exactly three: the RSS feed for a quick free pull, the API for completeness, or a paid tool that wraps both. Google Play is the outlier that gives you a genuine file, and we'll get to it.

Apple publishes a public RSS feed of customer reviews for any app on the store, no developer credentials required. It's the fastest way to get reviews out without writing auth code — paste a URL, get JSON (or XML) back, convert it to CSV with any converter or a five-line script. The catch: it's per-country and it only reaches the most recent reviews.

You point the feed at your app's numeric ID and a storefront country, and it returns the newest reviews for that storefront. Apple doesn't formally document the feed's limits, but in practice it pages 50 reviews at a time up to 10 pages, so you get roughly 500 most recent reviews per country and repeat per storefront if your app is global. It does not include your developer replies, only the customer's rating and text.

When the RSS window isn't enough — you want the full history, filtered by rating, or your own responses alongside the reviews — you use the App Store Connect API. It returns JSON, not CSV, so you're still writing the flatten-and-save step, but unlike Google's API it doesn't expire reviews out of a short window, so you can page back through everything.

Practically that means: mint a JWT from your App Store Connect key, call the customer reviews endpoint for your app, follow the pagination cursor to the end, and (optionally) pull the matching responses to include a "your reply" column. The full field list, auth shape, and rate limits live in the [App Store Connect reviews API reference](/blog/app-store-connect-reviews-api-reference).

Google Play is the store that actually generates a spreadsheet for you. In Play Console, open Download reports, choose Reviews, and Google drops monthly CSV files into a Google Cloud Storage bucket tied to your developer account (the bucket name starts with `pubsite_prod_rev_`). Each file is one app for one month, with columns for the review text, star rating, language, device, app version, and, usefully, your developer reply and the date you posted it.

Two honest caveats. First, these reports only include reviews that have written text; star-only ratings with no comment don't appear. Second, the coverage is the recent past, not your entire lifetime. Google keeps a rolling set of monthly files, not an all-time archive. For anything newer than the current month, or for programmatic access, the Play Developer API is the route, and it carries the store's sharpest gotcha — see the [Google Play reviews API reference](/blog/google-play-reviews-api-reference) for the field detail.

Plenty of tools will do the pipeline for you: reputation and ASO platforms such as AppFollow and Appbot pull both stores into one place and export to CSV, Excel, or Google Sheets, usually with sentiment tags and filtering bolted on. What you're buying is the aggregation you'd otherwise script — both stores, every country, replies included, deduped, plus a UI. What you're paying for it is a recurring subscription, and review export typically sits on a paid tier rather than a free one, so price it against how often you actually need the file.

If you're weighing those specifically, we keep dated, honest breakdowns at [ReplyArgus vs AppFollow](/vs/appfollow) and [ReplyArgus vs Appbot](/vs/appbot). *AppFollow and Appbot are trademarks of their respective owners; ReplyArgus is not affiliated with either.* The trade-off is the usual build-versus-buy: the RSS feed and reports bucket cost nothing but your time, a tool costs money but no maintenance.

Here's the thing every exporter guide skips: almost nobody exports reviews to admire them. You export to read, triage, and respond — and the second you do, the CSV is stale, because a new one-star landed while you were opening the file. A spreadsheet is a photograph of a river. Treating review management as "export, then act" means you're always acting on yesterday's water.

And responding is what actually moves the number you care about. Google reported roughly a +0.7-star average lift for developers who reply to reviews (I/O 2019), and Hassan et al., studying 4.5 million reviews, found people who got a response were about 6x more likely to raise their rating (4.4% versus 0.7%). None of that comes from the download — it comes from the reply. If you're going through the trouble of exporting, [replying is what earns the rating back](/blog/does-replying-to-app-reviews-raise-your-rating).

That's the seam [ReplyArgus](/features) is built for. It watches both stores in one live inbox — no RSS pagination, no UTF-16 file to un-mangle, no 7-day window to miss — and drafts each reply in the reviewer's own language, grounded in your store listing and your past approved replies, so nothing publishes until you approve it (or until a rule you set does). You still get exports when you need them: reviews cluster into a product roadmap board you can push to Google Sheets, Jira, or Notion. The difference is the data stays live instead of dying in a download folder, and you [never miss a new review to answer](/blog/get-notified-of-new-app-store-reviews).