Skip to content
Tutorials Center
My learning

Topics

Lesson 30 of 36 ยท Publishing

Preparing Your Extension for the Chrome Web Store

Get a Chrome extension ready to publish: a clean manifest, required icons and screenshots, a clear single purpose, a privacy policy, a production build and a zip package that passes review.

Your extension works on your machine. Before strangers can install it, it must clear the Chrome Web Store's checks: a clean package, honest metadata and a clear purpose. Most rejections come from small, avoidable things, so a careful preparation pass saves days. This lesson is the pre-flight checklist.

The single purpose rule

The store requires every extension to have a single, narrow purpose that is easy to describe in one sentence: "Highlights prices on shopping pages" or "Saves notes about the current tab". Features must serve that purpose. A pack of unrelated tools ("also changes your new tab page and the search engine") will be rejected. If you have two ideas, publish two extensions.

Manifest quality

Review each key before packaging:

JSON
{
  "manifest_version": 3,
  "name": "Price Marker",
  "version": "1.0.0",
  "description": "Highlights prices on shopping pages so you can scan them fast.",
  "icons": {
    "16": "icons/16.png",
    "32": "icons/32.png",
    "48": "icons/48.png",
    "128": "icons/128.png"
  },
  "action": { "default_title": "Price Marker", "default_popup": "popup.html" },
  "permissions": ["activeTab", "storage"],
  "minimum_chrome_version": "114"
}
  • name: 75 characters at most, matches the listing, no keyword stuffing or other brand names.
  • description: up to 132 characters, plain and accurate. It becomes the short description in the store.
  • version: one to four dot-separated integers (1.0.0, 1.2.3.4). Each upload must be higher than the last.
  • icons: 128x128 is required for the store; add 16, 32 and 48 for the toolbar and the extensions page. PNG with a transparent background looks best.
  • permissions: only what you use; see The permissions model.
  • Remove the "key" field before publishing (the store assigns the id), and any localhost match patterns used for tests.
A manifest checker

Edit the JSON and press Check to see which kinds of issues reviewers look for.

Store assets

Prepare these before you open the dashboard:

Store listing assets

Icon 128 x 128 PNG
Screenshots 1 to 5, 1280x800 or 640x400
Promo tile Small 440x280 (optional)
Video YouTube link (optional)

At least one screenshot is required.

1 / 2

Screenshots should show the real extension doing its real job; add short captions in the image if it helps, but never fake features, other brands or misleading claims. Use the same name and icon everywhere.

The listing text

  • Title matches the manifest name.
  • Short summary comes from description.
  • Detailed description: explain what it does, how to use it, which permissions it asks for and why. Plain text, no keyword spam, no reviews or ratings pasted in.
  • Category and language: choose honestly; add translations later with _locales (see Updates and versioning).

Privacy and data

Before you submit, prepare:

  • A privacy policy URL, if you handle any user data (see Least privilege and data).
  • Your data disclosures: tick the categories you handle.
  • A permission justification for each sensitive permission, written in one or two sentences.
  • A test account and instructions, if the extension needs sign-in. Reviewers must be able to see it work.

Build and package

Ship production code, not your working folder:

  1. Bundle and minify if you use a build tool, but keep code readable enough to review (do not obfuscate; obfuscated code is prohibited). Minification is allowed.
  2. Remove source maps, tests, node_modules, .git, secrets, .env files and unused libraries.
  3. Make sure no remote code is loaded (see CSP).
  4. Zip the contents of the folder, so manifest.json is at the zip's root, not inside a subfolder.
Text
# from the build folder
cd dist
zip -r ../price-marker-1.0.0.zip .

Then load the unzipped result with Load unpacked one more time and test it, because a build bug often hides in the package and not in the source.

Pre-submission checklist

  • Single purpose is clear.
  • Manifest valid, icons present, version bumped.
  • Only needed permissions; justifications written.
  • Privacy policy and disclosures ready.
  • Screenshots and descriptions truthful.
  • Package tested, no remote code, no secrets.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does the single purpose policy require?

    Bundling unrelated features is a common reason for rejection.
  2. 2. Where must manifest.json be inside the zip you upload?

    Zip the contents of the build folder so manifest.json sits at the top level.
  3. 3. Which is allowed in the submitted code?

    Minification is fine. Obfuscation, remote code and hidden behaviour violate policy.
  4. 4. Which icon size is required for the store?

    A 128x128 icon is required; smaller sizes are used in the toolbar and extension page.

Summary

  • Give the extension one clear purpose and a manifest that matches the listing.
  • Provide icons, screenshots, a truthful description, a privacy policy and data disclosures.
  • Ship a clean, minified (not obfuscated) package with manifest.json at the zip root and no remote code.
  • Test the final zip before you upload it.

Next: Submitting to the Web Store and Passing Review