Guide
Google Play Reply Character Limit: 350 (and How to Fit It)
Google Play caps developer replies at 350 characters; the App Store allows 5,970. What happens when you go over, and how to write a reply that fits without sounding curt.
Quick answer: Google Play developer replies are limited to 350 characters. The Apple App Store allows 5,970. Play doesn’t trim an over-long reply — it refuses it.
The limits at a glance
| Store | Developer reply limit | Over the limit? |
|---|---|---|
| Google Play | 350 characters | Rejected — the Console blocks submission and the API errors |
| Apple App Store | 5,970 characters | Rejected by App Store Connect |
Because Play’s limit is the strict one, anything written to fit Google Play works on both stores — which is how our reply template library is written.
Writing a reply that fits 350 characters
- Cut the greeting, keep the empathy. “Hi, thank you so much for taking the time to leave feedback” is 55 characters that say nothing. “Sorry — that crash is on us” is 27 that say everything.
- One issue per reply. If the review raises three problems, answer the one that made them angry and move the rest to email.
- Move detail to your support channel. A support email costs ~25 characters and replaces a paragraph of troubleshooting.
- Skip the signature. The reply is already labeled as the developer’s response — “— The [App] Team” is spent budget.
Before and after
Over the limit (about 430 characters): “Hello, thank you so much for taking the time to share your valuable feedback with us. We are very sorry to hear that you have experienced crashes with the application after the most recent update. Our development team takes these reports very seriously and is currently investigating the root cause of the problem. We would kindly ask you to contact our customer support team so that we can gather further information about your device…”
Fits with room to spare (about 250 characters): “So sorry about the crash — that’s on us. A fix is rolling out in 2.4.1; please update in a day or two. Still crashing after that? Email support@example.com with your device model and we’ll dig in. We’d love to earn those stars back.”
Why the short limit is actually good for you
The reply renders directly under the review on a phone screen, and every future visitor reads it as part of your store listing. A tight limit forces the shape a good reply has anyway: acknowledge, answer, and offer a next step. Reviewers respond to it — the published numbers on ratings after developer replies come almost entirely from short, specific answers.
If you automate drafting, the limit becomes an engineering constraint: generated replies must be measured after translation into the reviewer’s language, not before. StoreReplies drafts to fit, shortens overruns automatically, and counts down as you edit — so the limit is something you stop thinking about.