A developer builds a genuinely useful Chrome extension. It cleans up your Gmail inbox or adds missing features to Google Docs, and it works well. Naming it feels obvious, something like “Chrome Inbox Helper” or “Google Docs Toolkit,” because that is exactly what it does and exactly what people will search for. Then the submission gets flagged. Not for a bug. For the name itself. Google's own branding guidelines explicitly restrict using its trademarks, including the word “Chrome” or “Google,” in an extension's name without written permission, and most developers have never read that document before naming their extension.
The rule almost nobody reads before naming an extension
Google's own Chrome for Developers documentation lays this out plainly, even though almost nobody reads it before choosing a name. The branding guidelines for Chrome extensions explicitly instruct developers not to use Google trademarks, or any confusingly similar marks, as the name of an extension or company without written permission from Google. This means a name like “Chrome Password Manager” or “Google Sheets Exporter” is a real risk, not a stylistic choice, even if the extension genuinely works with Chrome or integrates with a Google product. The guidelines do provide an approved pattern for referencing compatibility, though. Instead of putting the trademark directly in the name, developers are instructed to use phrasing like “for Google Chrome” or “for use with,” alongside the proper trademark symbol, with the reference text kept visibly smaller than the extension's own branding. This is a specific, checkable rule, not a vague suggestion, and it is the single most common naming mistake among first time extension developers who assume mentioning the platform their tool works with is always fine, and always allowed.
What you can and cannot do with the name
Cannot use the trademark as the core of your name
Names like “Chrome Extension Manager” or “Google Tab Organizer” place the trademark directly inside the product identity, which the guidelines prohibit without written permission. This is true even when the extension is free, non-commercial, and genuinely built to work with that specific browser or product. The reviewer is not evaluating whether your claim is accurate. Google's guidelines treat the trademark itself as the issue, regardless of how well the extension actually performs the function its name describes. A developer who builds something excellent still faces this exact restriction, since usefulness has no bearing on trademark placement, and a working extension gets flagged just as fast as a broken one if the name itself is the problem.
Can reference compatibility with the approved phrasing
The guidelines provide a specific, sanctioned pattern for exactly this situation. A name like “Tab Organizer for Google Chrome,” using the proper trademark symbol and smaller reference text, is compliant, because the trademark is clearly a compatibility reference rather than the core brand identity. This distinction, trademark as descriptor versus trademark as identity, is the entire rule in practice. The product name itself, “Tab Organizer,” carries the branding weight, while “for Google Chrome” simply confirms where it runs. Developers who structure their naming decision this way from the start rarely run into a rejection over the name alone, since the reviewer can see immediately which part of the name is the brand and which part is the compatibility note.
Cannot use a confusingly similar mark either
The restriction extends beyond exact matches of the word Chrome or Google. A name that is a close variation of an existing Google product name, even without using either trademarked word directly, can still be flagged as confusingly similar during review. This is a judgment call made by a human reviewer, not a simple keyword filter, which means a cautious developer should lean toward a name that is clearly distinct rather than one that merely avoids the literal trademarked word while still echoing an existing product's identity in structure, sound, or intent. A name that sounds like it could be Google's own naming convention deserves a second look before submission, not after a rejection.
The manifest name and the store listing name are the same field, unlike other platforms
This is a genuine point of difference from other developer tool ecosystems worth naming directly. Unlike a VS Code extension, which has a separate technical identifier and a human facing displayName field, a Chrome extension's name in manifest.json is generally the same string users see in the Chrome Web Store listing. There is no separate lowercase machine identifier absorbing the branding risk. This means the naming decision has to satisfy the trademark restriction, general readability, and Chrome Web Store search relevance, all in a single field, with no second field to compensate. This two field split does exist in other developer tool contexts, including the two name split covered in NameKit's VS Code extension guide, since Chrome extensions do not get that same separation. Any developer tool with only one name field, rather than a split between a technical identifier and a display name, carries more naming risk in that single field, which is the same single identifier problem developers run into elsewhere.
A pre-submission naming check
- 01Read the specific phrase you are considering against Google's branding guidelines directly, checking whether "Chrome" or "Google" appears as the core of the name rather than as a smaller compatibility reference.
- 02If referencing compatibility, use the sanctioned pattern, the product name followed by "for Google Chrome" with proper trademark symbol usage, rather than embedding the trademark earlier in the name.
- 03Search the Chrome Web Store directly for your candidate name and close variants, checking both for existing extensions and for anything that could be read as confusingly similar to an existing Google product.
- 04Confirm the manifest.json name field and the intended store listing name match exactly, since Chrome extensions do not have the separate technical identifier some other platforms provide.
- 05If in doubt about whether a name is a compatibility reference or a trademark violation, choose the more conservative option, since Google's review process treats this as a real compliance issue, not a stylistic preference.
Name it clearly, name it compliant
Chrome extension naming carries a genuine legal and policy constraint that most naming guides never mention, and getting it wrong causes real submission delays, not just aesthetic problems. A name that reads clearly to a user can still fail review if it treats a Google trademark as its own brand identity instead of a smaller compatibility note. NameKit's App Name Generator is a reasonable place to start for generating a pool of compliant candidate names before checking each one against the guidelines directly.
Frequently asked questions
Can I use the word Chrome in my extension's name?
Only as a smaller compatibility reference, using phrasing like "for Google Chrome" alongside the proper trademark symbol, not as the core identity of the name. Google's branding guidelines explicitly restrict using its trademarks as the primary name without written permission, regardless of how accurately the name describes what the extension does.
What happens if my extension name violates Google's branding guidelines?
Google may request that you modify or cease use of the name, and in some cases this can delay or block your Chrome Web Store listing. The guidelines apply to naming, descriptions, and logos, so a compliant name alone does not guarantee approval if other branding elements also reference the trademark improperly.
Does a Chrome extension have a separate technical name and display name?
No, unlike some other developer tool platforms. The name in manifest.json is generally the same string shown in the Chrome Web Store listing, so the naming decision has to satisfy branding compliance and readability in a single field, with no second, more technical field available to absorb any of that risk.
Is "confusingly similar" to a trademark clearly defined?
Not with a precise technical test. It is a judgment call applied during review, which means a name that merely avoids the literal trademarked word is not automatically safe if it closely resembles an existing Google product name in spirit or structure.
Can I mention that my extension works with Google Docs or Gmail in the name?
Yes, but through the same sanctioned compatibility pattern, referencing the product name as a smaller, secondary element rather than embedding it as the core of your extension's identity, and using the appropriate trademark symbol when doing so, consistently, throughout your listing.