How to Remove an iOS App from the App Store

Two different things people mean by "remove"

App Store Connect draws a hard line between two actions that both feel like "taking my app down":

• Remove from sale. Your app disappears from App Store search and browsing — no new downloads. Anyone who already has it installed keeps it, can keep using it, and can still redownload it from their purchase history. Reversible at any time.
• Delete the app record. The entire app — every version, every piece of metadata, every review — is permanently removed from App Store Connect. This is not reversible, and Apple is explicit that this should only be used for records created by mistake, not for retiring a real, published app.

For almost every real-world reason people search for this ("sunsetting a product," "rebranding," "consolidating apps," "app didn't work out"), the right move is remove from sale, not delete.

How to remove an app from sale

1. Sign in to App Store Connect and open your app.
2. Go to the Pricing and Availability section.
3. Under Availability, click Remove from Sale (wording may appear as "Remove App from Sale," depending on the current App Store Connect UI).
4. Confirm. The app stops appearing in App Store search and browsing, typically within a few hours.

What stays intact: your app record, all past versions, all reviews and ratings, and your App Store Connect analytics history. Existing users keep the app and can still redownload it. If you change your mind, you can put it back on sale from the same screen — no new submission or review required, since the app and metadata haven't changed.

What actually happens to existing users

This is the part people worry about most, and the answer is reassuring: removing from sale doesn't uninstall anything or break the app for people who already have it. Specifically:

• The app keeps working exactly as it did before, unless the app itself depends on a backend you're also shutting down (that's a separate decision from the App Store listing).
• Users who deleted the app can still redownload it from their Purchased tab in the App Store, as long as it's tied to their Apple ID purchase history.
• New users searching the App Store will not find it and cannot install it for the first time.
• You can still push app updates to the removed app if needed (for a critical bug fix, for instance) — removal from sale doesn't block updates to existing installs.

When to actually delete the app record

Deleting is the nuclear option and Apple treats it that way. Use it only when:

• You created a duplicate app record by mistake and it was never submitted or approved.
• A test/placeholder app record needs to be cleaned up and has zero version history.

If your app has ever gone through review and been approved, deleting the record throws away your review history, ratings, and analytics permanently — information you might want later even for a retired product. Removing from sale keeps all of that intact while accomplishing the same practical goal (no new downloads).

Rebranding or consolidating apps: a common reason people search this

If you're retiring App A because you're launching App B as a rebrand or replacement, the cleanest approach is usually:

1. Keep App A's listing live briefly with an updated description pointing users to App B (or push one final update with an in-app message).
2. Remove App A from sale once existing users have had a reasonable window to migrate.
3. Leave App A's record in Remove-from-Sale state rather than deleting it — this preserves your developer account's history and avoids losing the app name/bundle ID unnecessarily.

Bundle IDs, once used, generally can't be reused by a different app record even after removal — another reason to remove from sale rather than delete and hope to reclaim the identifier later.

Google Play equivalent

Google Play Console has the analogous distinction: unpublish (equivalent to remove from sale — stops new installs, existing users unaffected) versus deleting the app entirely from your developer account. The same logic applies — unpublish for a real retirement, delete only for mistaken/test entries.

If you're relaunching under a new listing instead

Sometimes "removing" an app is really the first step of a relaunch — new branding, new screenshots, sometimes a new bundle ID entirely. If that's your situation, once the old listing is handled, getting the new one submission-ready is the next task. ezscreenshots makes that fast: drop your new screenshots, pick the correct preset for each required device size, add captions, and export the full set in minutes — no account, no export limit, all in the browser.

Summary

• Remove from sale (Pricing and Availability → Remove from Sale) — stops new downloads, existing users keep the app and can redownload it, fully reversible, keeps your app record intact
• Delete the app record — permanently erases everything (versions, reviews, analytics); only for mistaken/test records that never had a real published version
• For almost every real retirement reason (sunsetting, rebranding, consolidating), remove from sale is the right move
• Bundle IDs generally can't be reclaimed once used, even after removal — another reason not to delete unnecessarily
• Google Play equivalent: unpublish vs delete, same logic applies