What the "single purpose" policy actually requires
Your extension must have one clear, narrow purpose — a single function, or a set of features that all serve the same closely related goal. Bundling unrelated tools ("dark mode and a screenshot tool and a password generator") is the classic trigger.
The things that trigger it most:
- Feature grab-bag — several tools that don't share one goal, shipped in one extension.
- Purpose can't be said in one sentence — if describing it needs "and also…", reviewers see more than one purpose.
- Permissions wider than the core feature — extra permissions imply hidden extra features.
- Scope creep over versions — a focused extension that grew unrelated features in updates.
How to fix it and resubmit
- Pick one core feature. Keep the single function users install it for; remove the rest — or split extras into a separate extension.
- Write the purpose in one sentence. "This extension [does one thing] for [who]." Put it at the top of the listing and in the single-purpose field.
- Trim permissions to match. Every permission should serve that one purpose; drop anything that doesn't.
- Make the UI focused. The popup and options should reflect one job, not a toolbox.
Rule of thumb: if you need the word "and" to describe what it does, you probably have two extensions.
Single purpose is one of six rejection families (permissions/Purple Potassium, metadata/Blue Argon, single purpose, privacy, remote code, functionality/Yellow Magnesium). If your email lists more than one, fix them together — a second rejection resets the review clock.
Not sure how to narrow your scope?
Paste your rejection email — get the exact cause in seconds, free. Or we re-scope, fix, and resubmit for you.
Free diagnosis → Metadata rejection? →