How to Export Google Play Reviews to CSV & Excel

Pull every public review from a Google Play app listing into a clean spreadsheet — complete with the app version, device model, and developer replies that make Android feedback so analytically rich.

Google Play is one of the few review sources that tells you not just what a user thought, but which build of your app they were running when they thought it. That single detail turns a pile of star ratings into a release-by-release diagnostic tool. The trouble is that the Play Console only shows you reviews a screen at a time, and the public store page offers no export button at all. Copy-pasting hundreds of localized reviews by hand is a non-starter.

This guide walks through exporting any public Google Play app's reviews to CSV or Excel in three steps using the Google Play Reviews Exporter Chrome extension. It auto-paginates through long review lists, preserves the version and device metadata Google attaches, and hands you a spreadsheet you can pivot, filter, and feed into an LLM the same afternoon.

What gets exported from Google Play

Each review on the store page becomes one row. The exporter captures these fields:

• rating — the 1–5 star score the reviewer gave.
• review_text — the full written review, exactly as the user typed it.
• review_date — when the review was posted.
• app_version — the build the review was written against, when Google exposes it.
• device — the hardware model the reviewer used.
• developer_reply — the developer's public response, if one exists.
• thumbs_up — the “was this helpful?” count that ranks a review's resonance.

Sample CSV header

The export opens with a single header row, so it imports cleanly into Excel, Google Sheets, or pandas with no reshaping:

Export Google Play reviews in 3 steps

1. Install the extension

Open the Add to Chrome listing in the Chrome Web Store and confirm the install. The exporter runs entirely in your browser — no account, no API key, and no review data leaves your machine.

2. Navigate to the app listing

Go to the Google Play store page for the app you want, which follows the pattern play.google.com/store/apps/details?id=[package-name]. Open the “Ratings and reviews” section so the reviews are visible. This works on any public app page, including your competitors'.

3. Run the export

Click the extension icon and hit export. It auto-scrolls and paginates through the review list — even for high-volume apps with thousands of entries — then downloads a CSV. Open it directly in Excel or import it into Google Sheets and you're ready to analyze.

Google Play-specific tips and quirks

The app_version field is your release diagnostic

Google tags many reviews with the exact app_version they were written on. No other major review platform gives you this. It means you can correlate a rating drop to a specific release and do genuine regression analysis — pinpointing the build where things went wrong rather than guessing.

The device field exposes hardware-specific bugs

Because Android spans thousands of device models, the device column often reveals that a crash or layout bug only hits certain hardware or OS combinations. Filtering negative reviews by device frequently turns “the app is buggy” into a concrete, reproducible target.

thumbs_up ranks the most-felt complaints

The helpful count tells you which complaints other users co-signed. Sorting by thumbs_up floats the issues felt by the most people to the top, so you triage by real impact instead of recency.

Reviews are localized — and that is fine

Play reviews are shown in the reviewer's language, so a single export can mix English, Spanish, Portuguese, and more. They come through exactly as written. Run them through a translation step or a multilingual LLM before topic-clustering if your audience is global.

review_text is an ASO goldmine

The exact phrasing users employ in review_text is free keyword research. The words real people use to describe your app are the words they search the store with — mine them for your title, short description, and listing copy.

Turn Google Play reviews into insights

Recipe 1 — Find the release that tanked your score

Build a pivot table with app_version as rows and average of rating as the value. The version where the average falls off a cliff is your culprit. Add a count of reviews per version to confirm the dip is statistically meaningful and not one angry user.

Recipe 2 — Isolate hardware and OS bugs

Count negative reviews grouped by device with a formula like:

Repeat per device, or pivot device against a rating ≤ 2 flag. A cluster of one-star reviews on a single device family points straight at a hardware- or OS-specific defect.

Recipe 3 — Triage by impact and feed the roadmap

Sort the sheet by thumbs_up descending to surface the highest-impact complaints first. Tag the recurring feature requests with a label column, then pivot the tags to rank what the roadmap should tackle next based on how many people asked.

Who uses exported Google Play reviews

Frequently Asked Questions

Does it capture which app version a review was for?

Yes. When Google shows the build a review was written on, it lands in the app_version column — the field that makes release-regression analysis possible.

Can I export competitor app reviews?

Yes. The exporter works on any public app page, so you can pull a competitor's reviews the same way you pull your own.

Does it handle thousands of reviews?

Yes. The extension auto-paginates through long review lists, so high-volume apps export in a single pass without manual scrolling.

Are non-English reviews included?

Yes. Localized reviews are exported exactly as written, so a global app's feedback comes through in every language users left it in.

Does it capture developer replies?

Yes. Public developer responses are exported in the developer_reply column, so you can audit support engagement alongside the original feedback.

Related guides