Home / How to name a browser extension

How to name a browser extension

An extension name has to work in three places at once: the toolbar tooltip, the store listing, and a trademark database. This guide walks through a process that covers all three.

Step 1 — Brainstorm broadly

Generate fifty candidates before judging any of them. Feed a seed word — what the extension actually does — into the generator, try each style, and download the lists. Then do one manual round: write the ten words your target users would type into store search, and force combinations with them. The manual round catches obvious, searchable names that feel too plain to invent but perform well in stores.

Step 2 — Filter ruthlessly

• Say it once. If a friend cannot spell it after hearing it, drop it.
• Tooltip test. Keep it under about 20 characters — long names get truncated in toolbar tooltips and look broken.
• No borrowed authority. Drop anything containing a browser brand name or words like "official".
• Distinctive spelling. One unusual spelling is memorable; two is a support burden.

Step 3 — Check the stores

Search each surviving name in the major extension stores — Chrome Web Store, Firefox Add-ons and Edge Add-ons. Extension names collide constantly because the vocabulary is small (tab, boost, shield, saver). A collision is not just a branding problem — users will install the wrong extension and blame you in the reviews. Also run a trademark search in your country's database and check domain availability for your finalists.

Step 4 — Commit

Pick one, then use it everywhere consistently: manifest name, store listing title, repo, docs and support email. Write a one-line naming note in your README explaining what the name means — future contributors naming features and settings will follow its lead.

Testing names with real users

Before you commit, test your top three names with five people who match your target users. You do not need a formal study — a hallway test works:

• Say it once, ask them to spell it. If two of five fail, the name is too clever.
• Show the name next to two competitors' names. Ask which one they would click. You are testing distinctiveness, not beauty.
• Ask what it does. If nobody guesses correctly and the name is meant to be descriptive, it failed at its job.

Run the same test on your store listing title, not just the bare name — "Tabcharm" and "Tabcharm — Tab Manager" test very differently.

What if you need to rename later?

Renaming a published extension costs reviews, search ranking and user trust — the store treats it as a significant listing change. The common triggers are trademark complaints and collisions discovered too late. Both are preventable with the checks in step 3. If a rename becomes unavoidable, keep the old name in the listing description for a transition period ("formerly X") so existing users and links still find you, and announce it in your release notes and support channels.

Key takeaways

• Brainstorm fifty candidates with a seed word before judging any of them.
• Filter for spelling-after-hearing, tooltip length, no borrowed authority.
• Search every major extension store plus the trademark database — collisions are the top killer.
• Test the top three with five real users before you commit.
• Write the winner down in a one-page naming doc so future features and spin-offs follow the same pattern.