Chrome Extension Publish Checklist

MV2 is no longer accepted for new submissions.

Only request permissions your extension actually uses. Excessive permissions trigger manual review.

Ensure your service worker handles lifecycle events (install, activate) correctly.

Define CSP in manifest.json if your extension loads external resources.

MV3 prohibits executing remote code. All logic must be bundled in the extension.

Test all pages and features. Check the background script console for errors too.

Your main icon. Design at 128px, test at 16px for legibility.

Up to 5 screenshots. The first is the most important — it shows in search results.

Optional but increases chance of being featured.

Optional. Used for larger featured placements.

Optional. The hero banner for top-level featuring.

Clear, descriptive name. Avoid keyword stuffing.

Appears in search results. Make it compelling and keyword-rich.

Explain features, use cases, and how to get started.

Choose the most relevant category for discoverability.

Link to your landing page or homepage.

Required if your extension collects any user data. Must be publicly accessible.

Declare what data you collect and how it's used in the Privacy tab.

Explain why each permission is needed. Vague justifications cause rejections.

Google requires each extension to have one clearly defined purpose.

Test on the latest stable Chrome release.

Ensure your extension works (or gracefully degrades) in private browsing.

Uninstall and reinstall. Verify onboarding, default settings, and first-run experience.

No orphaned data, workers, or alarms after uninstall.