How to Delete or Edit Your Developer Reply on Google Play

Yes — you can delete or edit a developer reply on Google Play, and it takes about thirty seconds. In Play Console, open your app, go to Ratings and reviews → Reviews, click the review, and use the controls on your existing reply: edit the text and re-send to overwrite it, or delete the reply to remove it entirely. A new reply always overwrites the old one. There's no version history and no thread, so editing and re-sending is really just deleting-and-replacing in one step.

The reason this question fills community threads instead of a clean help doc is that Google buries the delete control and never quite spells out the overwrite behavior. So here's the part the two-line answer skips: exactly where the buttons live, when to edit versus delete, the one thing deleting your reply does *not* do (spoiler: it can't touch the review), and why the Play Developer API can change your reply but flat-out refuses to delete it.

There are three separate operations people mix up, and Google labels none of them clearly. Editing your reply overwrites the old text with new text. Deleting your reply removes your response so the review shows no developer answer at all. And deleting the review itself — that one you simply cannot do, ever, by any means. Keep those straight and the rest is clicks.

The catch is that the delete option is easy to miss. On the Reviews page your posted reply sits under the reviewer's text with an edit control right there; the delete action is tucked into the reply's options rather than shown as a big red button. That layout is exactly why searchers land on forum threads convinced the feature doesn't exist. It does — you're just looking for a pencil when you want the overflow.

Most of the time you don't want a blank space where your reply was — you want a *better* reply. A deleted response leaves a low-star review sitting there with no answer, which reads worse to the next shopper than an imperfect reply would. So before you delete, ask whether an edit fixes it instead.

The classic case is a promise that aged badly. You told a furious reviewer the crash was "fixed in 2.3," then the fix actually shipped in 2.3.1. Don't delete — correct it. Reopen the review, edit the reply to name the version that's really live, and re-send. The reviewer who's still hitting the bug reads an accurate promise, and anyone browsing your listing sees a developer who keeps their word current.

That's the edited version of what might have started as a rushed "we're looking into it." It fits the 350-character cap, names the exact build, and makes one keepable promise — the reply you'd rather have live than a deleted blank. Delete only when the original reply is genuinely wrong or embarrassing and no edit rescues it. For the full craft of these, see [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews).

This is where most of the frustration in those forum threads lives, because people delete a reply expecting it to fix something it can't.

Deleting your reply does not delete the review. No Console setting, API, or third-party tool lets a developer remove or hide a user's rating and text — your only lever on a bad review is a good reply, never a delete. It also can't un-ring the bell: Google emailed the reviewer your reply the moment you first sent it, so deleting it later doesn't recall your original words from their inbox. And it won't move your star average, because a deleted reply changes nothing about the ratings feeding your recency-weighted score. If you want a higher rating, answer more reviews well — Google reported roughly a +0.7-star average lift for developers who respond (I/O 2019) — don't scrub the ones you already handled.

If you script your replies, here's the sharp catch: the Google Play Developer API can *change* a reply but it cannot *delete* one. There is a single `reviews.reply` method that sets the reply text, and calling it again on the same review overwrites the previous reply. That covers editing perfectly. There is no `reviews.delete`-reply endpoint at all — none exists in the v3 reference. To truly remove a reply, you have to open Play Console and delete it by hand.

One more constraint the docs mention only in passing: the Reviews API surfaces reviews from roughly the last seven days. A review that aged out of that window is unreachable programmatically — miss it for eight days and the API can't edit your reply on it either.

Deleting one bad reply is easy. The hard version is the one that actually eats your week — a reply that promised the wrong version number across forty reviews after a hotfix, or a tone that landed badly in a language you don't read, sitting live on your listing until someone notices. At that point you're not deleting a reply; you're auditing a backlog, one overwrite at a time, inside the same Console UI that hides the button.

That's the seam [ReplyArgus](/features) is built for. It watches Google Play and the App Store in one inbox and drafts each reply in the reviewer's own language (100+ languages, both directions), grounded in your past approved replies and an auto-ingested knowledge base of your store listing, so a draft already knows your product, your voice, and which version actually shipped. Every draft fits the 350-character cap, nothing publishes until you approve it (or until a rule you set does, by rating, keyword, language, or store), and edits go back out the same way. If you'd rather do it hands-on first, the full walkthrough is [how to reply to reviews in Google Play Console](/blog/how-to-reply-to-reviews-in-google-play-console).