No, you can’t change the package name of an Android app after publishing it on Google Play. The package name (also called the application ID) is the app’s permanent identity, so a build with a new one is treated as a completely different app. If you must change package name after publishing, you publish a second app and move your users to it.
Why you can’t change package name after publishing
The package name is fixed because Google Play and every Android phone use it to decide which app an update belongs to. Android’s app module guide says every app has a unique application ID, such as com.example.myapp, that identifies it on the device and in the Google Play Store.
The same guide is blunt: “Once you publish your app, you should never change the application ID.” If you do, Play “treats the upload as a completely different app.” Play Console Help says the same thing from the store side: package names are unique and permanent and “can’t be deleted or re-used.”
An update must match the original release on two things: the application ID and the signing certificate.
Android’s Sign your app guide explains the device side. When an update installs, the system compares its certificate with the installed one and only allows the update if they match. Get either one wrong and the phone sees a stranger, not an update. That’s also why a mismatched build often fails with an App not installed error.
What you can still change on a published app
Most things people want to rename can be changed without touching the package name. The package name is an internal ID; users rarely see it.
| What you want to change | Can you change it after publishing? | How |
|---|---|---|
| Store listing app name | Yes | Edit the listing (30 characters max) |
| Name under the icon | Yes | Ship an update with the new label |
| Icon, colours, screenshots | Yes | Update or edit the listing |
| Code folder or namespace | Yes, carefully | Keep applicationId fixed |
| Package name (application ID) | No | Publish a new app |
| App signing key | Only through Play’s key upgrade rules | See Play App Signing |
Play Console Help lists the app name as a store listing field with a 30 character limit, and you can add one localized name per language. So if your brand changed from “Bob’s Bakes” to “Oven Club”, you can rename everything users see and leave com.bobsbakes.app alone.
My take: an outdated package name is almost never worth a new listing. Nobody browses Play by package name.
The namespace trap that changes your package name by accident
Changing the namespace in your Gradle file can silently change the application ID if you never set applicationId explicitly. Android’s guide notes that a missing applicationId “automatically takes on the same value as the namespace,” so renaming the namespace renames the app.
You refactor com.oldname to com.newname in Android Studio, build, upload, and Play refuses the bundle because the package name doesn’t match the existing app. Play’s update rules require the updated bundle to have the same package name as the current version and a higher version code.
The fix: write applicationId = "com.oldname.app" in build.gradle.kts before you rename folders. Android notes that some older APIs still say “package name” when they mean the application ID.
How to move to a new package name if you really must
Moving to a new package name means running two apps for a while and asking users to switch. Plan it like a migration, not a rename.
- Pick the final name once. It needs at least two segments with a dot, each segment starting with a letter, using only letters, numbers and underscores.
- Create a new app in Play Console with the new package name and a new store listing.
- Build and release the new app with its own version history, starting at version code 1 if you like.
- Update the old app with a screen or banner that links to the new listing. This is your only way to reach existing users, because they won’t get the new app automatically.
- Move user data through your backend or an account sign-in. On-device data stays with the old package and is lost if users uninstall it.
- Unpublish the old app once most users have moved. Per Play Console Help, existing users can still use it and get updates, but new users won’t find it on Google Play.
Expect to lose some things for good: your install count, ratings and reviews stay with the old listing. Firebase, Google sign-in and Maps keys tied to the old package name also need new entries.
Can you delete the old app and reuse its package name?
You can reuse a package name only if the deleted app never had a single install. Google’s Delete an app page says a deleted app with zero lifetime installs frees its package name for anyone. With any lifetime installs, the name “can’t be reused by any other app,” including apps from the same account.
Deletion has its own rules. Only the account owner can delete an app, it must be installed on fewer than 1000 active devices, and monetized apps with installs need Google support instead. You can recover a deleted app within seven days.
How Web2Apk handles package names
Web2Apk treats the package name as the app’s identity, just as Android does. Our signing and updates guide says a different package name creates a separate app, and a different signing key with the same package name does not normally update the installed app.
In the builder:
- Version codes are tracked per package name in your browser, so a renamed project starts a separate version history.
- Project backups keep the package name, so restoring a backup on a new device continues the same app.
- Uninstalling can remove the app’s saved data, which matters if you ask testers to swap apps.
The limitation: Web2Apk can’t migrate users between two package names for you. Change it and you’re running two apps, with the hand-off message in the old app left to you. Set the package name before your first release, and keep the key backup next to it. If you ever lose that key, see what to do when you lose your signing key.
Which option should you pick?
Keep your current package name unless you’re forced to move. A new listing restarts your reviews and installs, and many users of the old app will never switch.
Move only when the old package is unusable: you lost the original signing key, a trademark issue forces the change, or the app never had installs and you can delete and reuse cleanly. If your app is still in testing with no public installs, now is the cheapest moment to fix the name. Check what publishing costs before you plan a second listing.
FAQ
Can Google Play support change my package name for me?
No. Play Console Help says package names are unique and permanent and can’t be deleted or re-used. A different package name always means a separate app listing.
Can I change the app name without changing the package name?
Yes. The app name on Google Play is a store listing field with a 30 character limit, separate from the package name. You can also change the name shown under the icon in a normal update.
If I delete my old app, can I reuse its package name?
Only if it never had an install. Google frees the package name of a deleted app with zero lifetime installs; with any lifetime installs, nobody can reuse it, including you.
Will users of the old app get the new one automatically?
No. Android only updates an app with the same package name and signing certificate, so users must install the new app themselves. Tell them inside the old app.