Free App Store Reviews Review Analyzer

Find top complaints and praise in App Store reviews. Export from Apple's tools, then analyze the file here.

Analyze a file

Drop your reviews file here

Supports CSV and Excel (XLSX) files

Try with sample data

Privacy First

Everything runs in your browser. Your review data never leaves your device and is not uploaded to any server.

How to analyze app store reviews

App Store reviews are written by iPhone, iPad, and Mac users against a specific app version. They are short, emotional, and often dated to the last release. A 1-star week after a forced login or a broken checkout is a support queue you can see from outside the building.

We do not have an App Store Chrome extension. Apple already gives developers official paths. In App Store Connect, open Ratings and Reviews for the app. You can read reviews there, filter by version and territory, and reply. For a file, use the App Store Connect API reviews endpoints if you already have API access, or export from the internal report your team already runs. Apple also publishes a public customer reviews RSS/JSON feed per app ID, which many teams convert into CSV for research. That feed is Apple's, not ours, and it is paginated, so it is not a complete lifetime archive.

If you only need a recent slice, the public feed or a Connect export is enough. If you need history, keep a monthly CSV so you are not reconstructing 2019 from memory. Do not use unofficial "app store scraper" extensions we did not build. They break when Apple changes markup, and they are not required for this analyzer.

Columns that help: rating, review title, review text, date, app version, territory, and author. Rating and text are required. Version is the column that makes App Store analysis worth doing. A crash theme on version 3.4.1 that disappears on 3.4.2 is a ship decision, not a brand crisis. Territory explains language and payment complaints that are really storefront issues.

Look for crashes on launch, login loops, Sign in with Apple failures, paywall confusion, restore purchases, notification spam, battery, and "update ruined it." Consumer apps should watch onboarding. B2B apps should watch SSO and offline use. Games should watch ads, energy, and save loss. Praise like "widgets actually work" or "offline mode saved me" is specific enough to protect in the next sprint.

Pair the file with your release calendar. Tag the CSV with version before you upload, or keep version in the sheet. Then check whether 1-star volume moved after the release, not just whether the average rating moved. Averages lag. Themes show up in days.

Upload the CSV or Excel on this page. Nothing is sent to our servers. We cannot reply to App Store reviewers for you. Use App Store Connect for replies, and use this tool to decide which reply and which fix come first.

Columns to include

  • Rating (required)
  • Review text (required)
  • Review title
  • Date
  • App version
  • Territory / country
  • Author

Open the generic Review Analyzer

Already have an App Store reviews CSV? You can also run the same tool on the main analyzer page.

Open the generic Review Analyzer

Frequently asked questions

Do you have an App Store reviews exporter?

No. Use App Store Connect, the App Store Connect API, or Apple's public customer reviews feed, then save CSV or Excel and upload it here.

Is Apple's public reviews feed complete?

No. It is a recent window, not the full lifetime of the app. Use it for current themes, and keep your own archive if you need history.

Why map the version column?

Most App Store fires are version-specific. Without version, a crash from last week looks the same as a three-year-old UI complaint.

Does this tool submit replies to Apple?

No. It only analyzes a file in your browser. Reply in App Store Connect.

Can I analyze a competitor app?

You can study public reviews for research. Do not impersonate that developer or republish reviews as your own social proof.