Browser extension store naming rules you must follow
You can build the best extension in the world and still get rejected at the store door over the name. Both major stores — the Chrome Web Store and Firefox Add-ons (AMO) — enforce naming policies, and reviewers apply them by hand. Here is what the rules actually require, so you can pick a name that sails through review the first time.
The universal rules (both stores)
- No trademark misuse. Your name cannot imply endorsement by or affiliation with another company. "YouTube Downloader Pro" will be rejected; a descriptive-but-original name will not. This is the single most common rejection reason.
- No keyword stuffing. "Ad Blocker - Block Ads, Popup Blocker, Adblock Plus Alternative" is not a name; it is a search query wearing a trench coat. One clear name, no keyword lists.
- No misleading claims. "Official", "Pro", or "Best" in the name must be defensible. Do not call it "Official" anything unless you are the official party.
- No impersonation. Names that copy or closely mimic existing popular extensions get rejected — even if the original is abandoned.
- Match the listing. The name in the store listing must match the name in the extension manifest. Mismatches trigger reviews and rejections.
Chrome Web Store specifics
Chrome's policies add a few sharp edges. The store prohibits "excessive" use of keywords not just in the name but across the listing — title, description, and promotional images are reviewed together. Repetitive or irrelevant metadata can sink an otherwise fine name. Chrome also enforces its brand guidelines around the words "Chrome" and "Google": you may describe compatibility ("for Chrome") but may not brand the extension as Google. When in doubt, keep the tech giant's trademarks out of your name entirely.
Firefox Add-ons (AMO) specifics
Mozilla's reviewers are known for thorough manual review, and naming gets real scrutiny. AMO's policies emphasize that the name must accurately represent the add-on's functionality — cutesy-but-opaque names can draw questions. Mozilla is also strict about the "Firefox" trademark: community extensions should not present themselves as Mozilla products. The upside of AMO's human review is that you can explain your reasoning in reviewer notes — use them if your name choice is unusual but legitimate.
Compliant vs rejected
| Pattern | Example | Verdict |
|---|---|---|
| Original, descriptive | TabTidy — Tab Manager | Compliant |
| Trademark-adjacent | Gmail Power Tools | Rejected (implies Google affiliation) |
| Keyword-stuffed | Dark Mode - Night Mode, Dark Theme, Eye Care | Rejected (keyword stuffing) |
| Misleading authority | Official VPN Shield | Rejected ("Official" without standing) |
| Copycat | AdBlocker Ultimate (mimicking AdBlock) | Rejected (impersonation) |
Picking a review-proof name
- Invent, do not describe-and-stuff. A distinctive coined name with one honest descriptor ("TabTidy — Tab Manager") passes everywhere. Generate candidates with the browser extension name generator, then filter against the rules above.
- Search both stores first. Check the exact name and close variants on the Chrome Web Store and AMO before you commit — collisions with existing listings are rejections waiting to happen.
- Keep one name everywhere. Manifest, store listing, website, and support pages should all show the identical name. Consistency is both a policy requirement and good branding.
- Document your reasoning. If the name is unusual, add a sentence in the reviewer notes explaining the choice. Reviewers are human; context helps.
- Plan the rename path. If your current name violates policy, rename before you build a user base around it — store renames confuse existing users and reset some listing signals.
Key takeaway: original, honest, and consistent. Avoid trademarks, keyword lists, and authority claims you cannot back up — and your name will clear review on both stores.
FAQ
Can I use the word "Chrome" or "Firefox" in my extension name?
Describing compatibility is generally fine ("Tab Manager for Chrome"); presenting your extension as the browser maker's product is not. When unsure, leave the trademark out of the name and mention compatibility in the description.
What happens if my name is rejected?
You will get a rejection notice with the policy cited. Rename the extension, update the manifest to match, and resubmit. Repeated violations can lead to account strikes, so fix it properly the first time. For the full rename playbook, see our guide on rebranding a Chrome extension.
Can two extensions share a similar name?
Similar names invite impersonation flags, especially if one is established. Pick something clearly distinct — it is better branding anyway.
Do the rules apply to the short description too?
Yes — reviewers evaluate the name, description, and screenshots as a package. A compliant name with a keyword-stuffed description still gets rejected.
Should I trademark my extension name?
If the extension becomes a real product with users and revenue, yes — a trademark both protects you and strengthens your position if someone copies your name later.