How to rename and rebrand a Chrome extension
Extension names age. The clever pun from 2021 now confuses new users; the product outgrew its original scope; or the name you picked in an afternoon is holding back a real business. Renaming a Chrome extension is entirely doable — but the store, your users, and your reviews all need handling. Here is the playbook.
When a rename is worth it
- Scope changed. "Tab Counter" now manages tab groups, workspaces, and sessions — the name undersells it.
- Trademark trouble. A cease-and-desist (or a looming one) makes renaming urgent, not optional.
- Going pro. The hobby name ("Dave's Cool Tabs") undermines the paid tier you are launching.
- Confusion. Users consistently misunderstand what the extension does from the name alone.
Not worth it: mild boredom with the name, or a founder's whim. Renames cost attention and trust — spend them on real problems. If you are still choosing, our naming guide and store naming tips cover getting it right the first time.
Step 1: Pick the new name properly
Do not repeat the rushed process that created the problem. Run the new name through the full gauntlet: trademark search, Chrome Web Store search for collisions, domain and social availability, and the store's naming policies (no keyword stuffing, no misleading claims). Generate a proper shortlist with the Chrome extension name generator and sit with the finalists for a week before committing. Run the new name against the store rules before you commit — see our guide on extension store naming policies.
Step 2: Update the listing and the code together
The store requires the listing name and the manifest name to match. Plan the change as a single release:
- Update the
nameinmanifest.json— this is what appears in the browser toolbar and extension pages. - Update the store listing title, and rewrite the description's first lines so new visitors meet the new brand immediately.
- Refresh screenshots and the store icon if they carry the old name or old visual identity.
- Update your website, support pages, and any documentation in the same release — a half-renamed product looks abandoned.
- Keep the extension ID unchanged. The ID is the identity; the name is the label. Changing the ID would orphan your entire user base.
Step 3: Tell your users before the store does
Users notice renames and assume the worst — hijacked extension, sold to a sketchy buyer, malware. Get ahead of it: publish a changelog entry and an in-extension notice ("New name, same extension, same developer") a version before the rename ships. After the rename, keep a "formerly X" note in the store description for several months. Transparency here is not marketing; it is security hygiene, because extension hijackings are a real thing users have learned to fear.
Step 4: Mind the review queue
A renamed listing can trigger additional review scrutiny — reviewers check that the new name complies with policy and that the extension is what it claims to be. Submit the rename as its own update, not bundled with major permission changes or code overhauls, so reviewers evaluate one thing at a time. If the old name had policy issues (trademark-adjacent, keyword-stuffed), the rename is also your chance to get fully compliant.
What happens to reviews and rankings
| Asset | What happens on rename | What to do |
|---|---|---|
| User base | Unchanged (tied to extension ID) | Nothing — but communicate |
| Reviews & ratings | Stay with the listing | Expect a few confused reviews; reply to them |
| Search ranking | May dip while the new name gains history | Keep old keywords in the description temporarily |
| External links | Keep working (store URL is ID-based) | Update the important ones anyway |
| Brand searches | Old name searches fade over months | "Formerly X" in description bridges the gap |
Key takeaway: rename for real reasons, keep the extension ID, ship the name change as its own clean update, and tell users before the store does. The name is the label — the ID is the identity.
FAQ
Will I lose my users if I rename?
No — users are tied to the extension ID, not the name. You will confuse some of them, which is why communication matters more than the rename mechanics.
Can I rename just the store listing and not the manifest?
You should not — mismatched names trigger policy issues and confuse users. Update both in the same release.
How long does a rename review take?
It varies with the review queue; renames sometimes get extra scrutiny. Submit it unbundled from other major changes to keep the review focused.
Should I keep the old name in the description?
Yes, as "formerly X" for several months. It catches old-name searches and reassures users who go looking for what happened.
What if I want a completely new extension ID too?
Then you are launching a new product, not renaming. Publish it as a separate listing and migrate users deliberately — do not try to pass it off as the same extension.