Frequently asked questions
Straight answers about extension naming and the AddonAtlas generator — no invented statistics, no marketing fluff.
What makes a good browser extension name? +
Short, pronounceable, clear about the job, distinctive enough to find in a crowded store, honest about what it does, and ownable across stores and trademarks. Our five-traits breakdown explains each with tests.
Can I use a browser brand name in my extension name? +
Risky. Names implying official status or affiliation with a browser maker can get listings rejected or removed and may raise trademark issues. Describe what the extension does instead of borrowing the browser's brand.
Are generated names safe to use commercially? +
Not automatically. The tool performs no trademark or store-listing checks. Search the major extension stores for collisions, check your country's trademark database, and verify domain availability before committing.
Descriptive or brandable — which is better for a new extension? +
Descriptive names match store search queries, which helps new extensions get discovered. Brandable blends are more memorable and ownable long-term. Many extensions start descriptive and rebrand once they have users.
How long should an extension name be? +
Aim for one or two words, under about 20 characters. Longer names get truncated in toolbar tooltips and look broken in store cards.
Is the generator really private? +
Yes. It runs entirely in your browser using crypto.getRandomValues(). Seed words and generated names never leave your device. See the privacy page.
What does the category bias do? +
It leans the generator's word pool toward vocabulary that category's users recognize — Shield and Vault for privacy, Focus and Flow for productivity, and so on. It does not restrict output; it just makes relevant pairings more likely.
Can two extensions have the same name? +
Different stores sometimes allow it, but it is a bad idea: users install the wrong extension and leave angry reviews on yours. Treat any exact store collision as a disqualifier.
Should the name match my domain? +
Ideally, yes. Owning the matching domain makes the project look legitimate and gives you a home for docs and support. Check domain availability alongside the trademark search — if the exact .com is taken by an unrelated business, a clean .io or .dev works for developer tools.
How do I handle a name collision I find late? +
Rename before launch, not after. Before launch a rename costs an afternoon; after launch it costs reviews, ranking and user trust. If you discover a collision late, treat it as a disqualifier and pick your runner-up — that is what the shortlist is for.
Do I need a logo before choosing a name? +
No — name first, logo second. A distinctive name constrains the logo in a useful way (Tab Vault suggests a vault icon), while designing the logo first often produces a generic mark. Pick the name, then brief the icon around it.
Should I include keywords in the extension name? +
Sparingly. One descriptive word that users search for (Tab, Cookie, Password) helps discoverability; stuffing three keywords into the title looks spammy and gets truncated. Put the keywords in the title once and the rest in the listing description, where they belong.
What if my favorite name is taken in one store but free in another? +
Pick a different name. Publishing under the same name as an existing extension in another store still confuses users and search engines, and the other developer may expand to your store later. A name should be ownable everywhere you might ever publish.
Still deciding?
Generate a fresh shortlist and run it through the five traits.