Does the App Store Translate Reviews for Developers? (And What to Do Instead)

No — the App Store does not translate reviews or your replies for you. App Store Connect shows every review in the exact language the reviewer wrote it, with no translate button anywhere on the screen, and it posts your response precisely as you typed it, in whatever language you typed. If a user in São Paulo leaves a two-star review in Portuguese, you see Portuguese, and if you answer in English, that English is what publishes on the Brazilian storefront.

This surprises people because Google Play works differently: Play Console will machine-translate a review so you can *read* it in your own language. But even there, the store never writes your reply for you. So on Apple you own the translation on both ends, and on Google you own it on the reply. Either way, the language of the response is your job. Here's exactly what each store does, why it matters for your rating, and the workflow that lets you answer a Japanese review without speaking Japanese.

Apple presents reviews per storefront, in the reviewer's original language, and stops there. Open the Ratings and Reviews section for your app and you'll find a country filter and a language that follows the storefront, but no inline translation, no 'view in English' toggle, and nothing that converts the review text for you. What the user typed is what you get. If your app is live in 40 markets, that means you're reading feedback in a couple dozen languages with zero help from the console.

The reply side is just as literal. Apple gives you one developer response per review, and it publishes verbatim on the storefront where the review lives. There's no step where Apple detects the reviewer's language and localizes your answer. Type English, English ships, even on the Japanese, German, or Arabic store. That's not a bug; Apple simply doesn't offer translation as a feature to developers, so the responsibility sits entirely with you.

Worth naming while we're here: Apple publishes no official character limit for developer replies. Community testing over the years has landed on numbers as low as roughly 5,970 and as high as 10,240, but Apple documents none of it, so treat any hard figure as folklore rather than fact. In practice you have room for a real, complete answer, which matters because a good reply usually needs it. The exact caps and rules differ by store — we keep a current cheat sheet in [reply rules for every app store](/blog/reply-rules-for-every-app-store).

Google Play Console does give you a reading aid Apple doesn't: it will show a machine-translated version of a review so you can understand a comment written in a language you don't read. That's genuinely useful for triage: you can tell an angry crash report from a feature request without pasting anything into a separate translator. The two stores diverge on a handful of these mechanics, and we map the full set in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

But notice the ceiling on that help: Play translates the review *for you to read*. It does not translate the reply *you write* into the reviewer's language. You still compose the response yourself, and whatever language you write in is what posts. So even with Play's translation, the reply you send a French user is your French. If you didn't write it in French, it's your English landing under their French complaint. Reading is assisted; answering is not.

Play also enforces a hard limit Apple doesn't: developer replies max out at 350 characters, full stop. Anything longer won't save. If you draft for both stores, that Play cap is the tighter constraint to design around: lead with the fix, cut the throat-clearing, and a tight answer fits every time.

It's tempting to answer everything in English and move on. The reviewer can machine-translate your reply if they care, right? Sometimes. But a reply is rarely written for the one person who left it — it's written for the next hundred shoppers reading your review section before they decide to install. When those readers are Japanese and your responses are all in English, the signal is loud: this developer isn't really here for us.

There's a rating case too. When Google announced recency-weighted ratings at I/O 2019, it also reported that developers who respond to reviews see an average lift of 0.7 stars. Independent research points the same direction — Hassan et al., studying 4.5 million reviews, found users were roughly six times more likely to raise their rating after a developer replied (4.4% versus 0.7% with no response). A reply the reviewer can actually read, in their own language, is the version most likely to earn that change. We dig into the mechanism in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating).

That reply is in the reviewer's own language, names the exact device and version, points to the fix, and leaves a door open. Neither Apple nor Google produced a word of it. A person or a tool did, and then it published verbatim. That's the whole point of this article in one example: the store is a delivery pipe, not a translator. The quality and the language of what goes through it are on you.

You don't need to be multilingual to do this well — you need a repeatable loop. Here's the manual version, which works for a handful of reviews a week.

That loop is fine at low volume. It falls apart the moment you're getting fifty reviews a week across a dozen languages, because every one becomes a copy-paste-translate-trim errand, and the reviews you skip are usually the foreign-language ones you can't quickly read. That's exactly the point where a tool earns its keep. [ReplyArgus](/features) watches your Apple App Store and Google Play reviews in one inbox and drafts a reply for each in the reviewer's own language (over 100 languages, in both directions), grounded in your past approved replies and your store listing, and already fitted to each store's character limits. You read the review in English, approve a native-language reply in a click, and the console never becomes a translation chore. The mechanics of doing this cleanly across every locale are covered in [reply to app reviews in any language](/blog/reply-to-app-reviews-in-any-language).

So the short answer holds: the App Store translates nothing, and Google Play translates only what you read, never what you write. The language of every reply is yours to own — which is a burden at scale and an advantage if you get it right, because a fluent native answer is the one that turns a frustrated reviewer, and the market watching them, back toward you. [Start free with ReplyArgus](/signup), no card required, and Argus drafts your first reply in the reviewer's own language in minutes, already sized for each store.