Home / How to name a Chrome extension

How to name a Chrome extension

A Chrome extension name has to work in the toolbar tooltip, the Web Store listing, and a trademark database — while steering clear of Google's branding policies. This guide covers all four.

Step 1 — Brainstorm broadly

Generate fifty candidates before judging any of them. Feed a seed word — what the extension does — into the generator, try each style and tone, and download the lists. Then do a manual round with the ten words your users would type into Web Store search; forcing combinations with search words catches obvious, discoverable names that feel too plain to invent.

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 truncate in the toolbar and look broken.
• The "Chrome" question. Decide deliberately whether the name uses "Chrome". "X for Chrome" describes compatibility; "Chrome X" can read as Google-made. When in doubt, leave the brand word out of the name and put it in the listing description instead.
• No borrowed authority. Drop "official", "pro" implying endorsement, and any Google product names.

Step 3 — Check the Web Store

Search each surviving name on the Chrome Web Store. Names collide constantly in a small vocabulary (tab, boost, shield, saver), and a collision means users install the wrong extension and blame you in reviews. Then run a trademark search in your country's database and check domain availability for the finalists.

Step 4 — Commit

Use the name consistently everywhere: manifest name, store listing title, repo, docs and support contact. Write a one-line naming note in your README so future contributors naming features follow the same tone.

The manifest name field

Your extension's manifest.json has a "name" field, and it should match your store listing title exactly. Mismatches confuse users ("I installed Tabcharm but the toolbar says Tab Manager?") and look unprofessional in reviews. Decide the final name before you write the manifest, and treat any later change as a rename with all the costs described in the testing section.

Testing with real users

Test your top three names with five people who match your target users:

• Say it once, ask them to spell it. If two of five fail, the name is too clever.
• Show it beside two competitors' names and ask which they would click — you are testing distinctiveness.
• Ask what it does. If the name is meant to be descriptive and nobody guesses right, it failed its job.

A note on other languages

The Web Store is global. Check that your candidate does not mean something unfortunate in the languages of your largest user bases — a quick search plus asking a native speaker takes an hour and prevents permanent embarrassment. Also check how the name sounds in major languages: a name that is awkward to pronounce will be awkward to recommend.

Key takeaways

• Decide the "Chrome" question deliberately — describe compatibility, do not claim identity.
• Keep the manifest name and listing title identical, under ~20 characters.
• Search the Web Store and trademark database before you commit; test with five users.