On Google Play, unpublishing and deleting are different actions, and which one you can do depends on whether the app was ever published. Unpublishing removes the app from the store so new users cannot install it, keeps existing users' copies working, and leaves the app record in your Play Console, and it is reversible. Deleting permanently removes the app record, but you can generally only delete an app that was never published to production; once published, you can unpublish but not truly delete, which is why lingering, undeletable listings are called ghost apps. The application ID cannot be reused for a new app afterward.
Short answer
To remove an app from Google Play, you either unpublish it or, in limited cases, delete it. Per Google's app management guidance, unpublishing takes the app off the store while keeping the record in your Console and leaving existing installs working, and it is reversible. Deleting the app record is only possible for apps that were never published to production; once an app has been published, you can unpublish but not delete it, so its record remains as a ghost app. In all cases the application ID, the package name, is retired and cannot be reused for a new app. Choose unpublish if there is any chance you will bring it back.
Unpublishing versus deleting
Unpublishing and deleting solve different problems. Unpublishing makes the app unavailable to new users by removing it from the store, but the app record stays in your Play Console, existing users keep their installed copy, and you can republish later. It is the reversible option, and it is what most people actually want when they say they want to remove an app.
Deleting is permanent and removes the app record itself from your Console. Its catch is eligibility: you can generally only delete an app that has never been published to a production track. If your app reached production at any point, deletion is not offered, and unpublishing is as far as you can go. So the first thing to establish is whether your app was ever production-published, because that decides which options you even have.
Can you permanently delete a published app?
For a published app, generally no. Once an app has been published to production, Google does not let you delete the record; the permanent option you have is to unpublish it, which removes it from the store but leaves the record in your Console indefinitely. This surprises developers who expect a delete button, but it follows from how Google retains published app records.
The practical result is that a published app cannot be fully erased from your account. You can make it unavailable, remove its store presence, and stop distributing it, but the entry remains. If your goal is simply that no one can find or install the app anymore, unpublishing achieves that; if your goal is a completely clean account with no trace, that is not something Google offers for an app that was once live.
What happens to existing users
Neither unpublishing nor deleting removes the app from the devices of users who already installed it. Unpublishing stops new installs and hides the store listing, but current users keep the app and can continue using it, though they will not receive updates once you stop publishing them. Your backend, if any, still receives their traffic until you shut it down.
This matters if you are removing the app to end a service. Taking the app off the store does not turn off the app in users' hands, so if you need to stop it working, you handle that separately, for example by retiring the backend it depends on or shipping a final update that communicates the shutdown. Plan for existing users explicitly rather than assuming removal reaches them.
The application ID cannot be reused
A key consequence of removing an app is that its application ID, the package name like com.yourcompany.app, is retired for good. Once an app has been published under an application ID, Google associates that ID permanently, and you cannot publish a new app under the same one, even after unpublishing or deleting. The namespace is one-time.
Plan around this before you remove anything. If you might relaunch under the same identity, unpublishing preserves your ability to republish the same app, whereas starting a genuinely new app will require a new application ID regardless. Choosing a fresh, well-considered ID for any replacement app is part of the removal decision, because you will not get the old one back.
Ghost apps explained
Ghost apps are the app records that remain in your Play Console after you can no longer publish or delete them. Because a published app cannot be deleted, unpublishing it leaves a permanent, inactive entry, a listing that is off the store but still present in your account. Developers call these ghost apps because they linger without being live.
They are not a bug or a problem to fix; they are the expected result of Google's retention model. You can leave a ghost app unpublished indefinitely, and it does not affect your other apps. The only real implication is cosmetic, an extra entry in your Console, plus the retired application ID. Accepting that a published app becomes a ghost rather than disappearing sets the right expectation for what removal actually does.
Options compared
The available actions differ in effect and reversibility. The table below compares them.
| Action | Effect | Reversible? |
|---|---|---|
| Unpublish | Removed from the store, record stays in Console | Yes, republish |
| Delete | App record removed, only if never production-published | No |
| Stop a specific track | Ends distribution on that track | Often yes |
| Existing installs | Unaffected by unpublishing or deleting | Not applicable |
Read the table against your situation. If the app was ever published to production, your real choice is unpublish, and if it never was, delete is available but permanent, so be sure before you use it.
Removal checklist
A short sequence avoids surprises when removing an app. The checklist below covers it.
| Check | Action | Done? |
|---|---|---|
| Decide intent | Choose unpublish (reversible) or delete (permanent) | [ ] |
| Back up first | Export any data, keys, or assets you may need | [ ] |
| Remove it | Set app availability to unpublished, or delete if eligible | [ ] |
| Note the ID | Accept the application ID is retired for good | [ ] |
| Handle users | Plan for existing installs and any backend shutdown | [ ] |
The step people regret skipping is backing up first, since a deleted app record and its assets are not recoverable, and even an unpublished app is easier to revisit if you kept your data and keys. Decide unpublish versus delete deliberately, because only one of them can be undone.
If you are removing over a security issue
Sometimes an app is removed because of a security or privacy problem, and in that case the removal is only half the job. If a released version exposed data or shipped a secret, taking the app off the store does not fix the exposure for users who still have it, so you also rotate any leaked credentials and address the underlying issue in whatever you ship next.
A scanner like PTKD.com analyzes an app build and reports findings ordered by severity and mapped to OWASP MASVS, so a replacement or a final update does not repeat the same problem. To be clear about the boundary: PTKD does not unpublish or delete an app or touch your Play Console. It helps ensure the build you keep distributing, or the one that replaces a removed app, is free of the issues that prompted the removal.
What to take away
- Unpublishing removes an app from the store but keeps the record and existing installs, and it is reversible; deleting is permanent.
- You can generally only delete an app that was never published to production; a published app can be unpublished but not deleted.
- Neither action removes the app from devices of users who already installed it, so plan for existing users separately.
- The application ID is retired for good after removal and cannot be reused, so a replacement app needs a new one.
- A published app that is unpublished becomes a ghost app in your Console; if you removed it over a security issue, verify the next build with PTKD.com.
