How to Publish a Chrome Extension to the Chrome Web Store
Photo by Caio on Pexels

9 min read

From the studio

We build apps people actually keep.

Tinkrd is a small indie studio making focused, high-quality apps for everyday life. See what we're working on.

View our apps

Publishing a Chrome extension is not complicated, but the process has enough specific steps that it is easy to get stuck or miss something before submitting. This guide covers the whole path from packaging your files to getting listed in the Chrome Web Store, including the parts most tutorials skip.

What You Need Before You Can Publish a Chrome Extension

Before you can publish a Chrome extension, you need three things: a finished, working extension directory, a Google developer account, and a one-time $5 registration fee. That is the full entry cost. There are no monthly fees just to be listed.

Your extension directory must include a valid manifest.json at its root. Chrome Web Store requires Manifest V3 for all new submissions. If you built your extension using the older Manifest V2 format, you will need to migrate before submitting.

A minimal working directory looks like this:

my-extension/
  manifest.json
  popup.html
  popup.js
  icon128.png
  icon48.png
  icon16.png

Your manifest.json needs at minimum a name, version, and manifest version field. Here is a simple example:

{
  "manifest_version": 3,
  "name": "My Extension",
  "version": "1.0",
  "description": "A short, accurate description.",
  "action": {
    "default_popup": "popup.html",
    "default_icon": "icon128.png"
  },
  "icons": {
    "16": "icon16.png",
    "48": "icon48.png",
    "128": "icon128.png"
  }
}

If you are still figuring out the build side, Chrome extension development: what it actually takes covers the full technical picture before you get to submission.

How to Package Your Extension for Submission

Packaging a Chrome extension means zipping your project directory into a single .zip file, with the manifest.json at the top level inside that zip, not inside a subfolder.

This is the most common packaging mistake. If your zip contains a folder called my-extension/ with everything inside it, the Web Store will reject the upload or fail to parse the manifest. The manifest must be at the root of the archive.

How to zip correctly on Mac or Linux

Navigate into your project directory and run:

cd my-extension
zip -r ../my-extension.zip .

The . at the end tells zip to include everything in the current directory, so manifest.json ends up at the archive root.

How to zip correctly on Windows

Open your project folder, select all files inside it (not the folder itself), right-click, and choose “Send to Compressed folder.” Alternatively, use the same pattern in PowerShell:

Compress-Archive -Path my-extension\* -DestinationPath my-extension.zip

Before you zip, remove any local development files that should not be in production: node_modules/, .git/, .env files, source maps if you do not want them public, and any test files. Keep the zip clean.

Setting Up Your Chrome Web Store Developer Account

The Chrome Web Store developer registration is a one-time $5 payment tied to a Google account. You pay once, and that account can publish unlimited extensions. The payment is non-refundable, but five dollars is a low bar.

Go to the Chrome Web Store Developer Dashboard and sign in with the Google account you want to associate with your publisher identity. You will be prompted to pay the $5 fee before you can submit anything.

A few things worth noting at account setup:

At Tinkrd, when we were evaluating the browser extension distribution path alongside our iOS work, the low cost of entry was genuinely appealing compared to the $99 per year Apple charges for developer access.

How to Submit Your Extension to the Chrome Web Store

Submitting your extension involves uploading the zip file, filling in your store listing details, setting visibility and distribution options, and then hitting submit for review. The process takes about 15 to 20 minutes if you have your assets ready.

Store listing details you will need

Prepare these before you open the dashboard. Having them ready prevents you from leaving the form half-finished.

Asset Requirement Notes
Short description 132 characters max Appears in search results, make it clear and specific
Long description No strict limit Plain text only, no HTML formatting rendered
Store icon 128×128 PNG Displays on your listing page
Screenshots 1280×800 or 640×400 PNG/JPG, at least one required Up to 5, show real UI
Promotional tile (optional) 440×280 PNG/JPG Used if Google features your extension
Privacy policy URL Required if you request any permissions Must be a live, accessible URL

Permissions and the single purpose policy

Chrome Web Store enforces a single purpose policy: your extension must have one clearly defined purpose, and every permission it requests must be necessary for that purpose. Reviewers look at this closely.

Request only the permissions your extension genuinely needs. If your manifest requests tabs, storage, and activeTab, each one should have an obvious reason tied to what the extension actually does. Broad or unexplained permissions are the most common reason extensions get rejected or delayed in review.

If you request host permissions for specific domains, list exactly the domains you need, not a wildcard unless the extension genuinely requires access to all sites.

Visibility settings

You can set your extension to Public (listed in the Web Store), Unlisted (accessible by direct URL only), or Private (restricted to your organization). For most indie developers, the choice is between Public and Unlisted during a soft launch phase. Unlisted is useful for beta testing with a small group before you open it up.

What Happens During Chrome Extension Review

After you submit, Google reviews your extension before it goes live. Review times typically range from a few hours to a few days for straightforward extensions, but can stretch to a week or longer if reviewers flag something for closer inspection.

The review process checks for:

If your extension is rejected, Google sends an email with a reason. Common rejection reasons include overly broad permissions, a missing or broken privacy policy link, or a store description that does not match what the extension actually does. Most rejections are fixable, and you can resubmit after addressing the issue.

One honest tip: write your store description to match what a reviewer will see when they install and test the extension. If the description says the extension does X, and the reviewer installs it and sees something different, that is a rejection. Keep the description grounded in what the first version actually ships.

For a broader look at what goes into building before you even get to this point, how to build and publish a Chrome extension walks through the development side in more detail.

Publishing Updates After Your Extension Is Live

Publishing an update to an existing Chrome extension follows almost the same process as the initial submission: increment the version number in manifest.json, zip the directory, upload the new zip in the developer dashboard, and submit for review.

Version numbers in the manifest must always increase. Chrome uses a four-part version format: major.minor.build.patch. For most small updates, incrementing the patch or build number is enough.

// Before update
"version": "1.0"

// After update
"version": "1.1"

Updates go through the same review pipeline as the original submission. Google notes that existing users receive updates automatically once the new version passes review. You do not need to notify users manually, though a changelog in the description is a good habit.

If you are adding new permissions in an update, users will see a permission prompt and must re-accept before the update installs. This can reduce your update adoption rate, so add permissions carefully and only when necessary. Removing a permission never requires user action.

Frequently asked questions

How long does it take to publish a Chrome extension for the first time?

The actual submission process takes 15 to 30 minutes if you have your assets and store copy ready. Review time after submission is typically one to three business days for new extensions, though complex or permission-heavy extensions can take longer. Budget a full week for the first submission to be safe.

Do I need a privacy policy to publish a Chrome extension?

Yes, if your extension requests any permissions that could touch user data, such as storage, tabs, cookies, or host permissions, you must provide a privacy policy URL in your store listing. The URL must be live and accessible at the time of review. A simple, honest one-page policy hosted on your own site is enough.

Can I publish a Chrome extension for free?

The only required cost is the one-time $5 developer account registration fee. After that, listing extensions in the Chrome Web Store is free. If you want to charge for your extension or offer subscriptions, you will need to set up a Google payments merchant account, which has additional verification steps but no upfront fee.

What is the most common reason Chrome extensions get rejected?

The most common rejection reasons are overly broad permissions, a missing or broken privacy policy link, and a store description that does not accurately match the extension’s actual behavior. Addressing all three before submission significantly reduces back-and-forth with reviewers.

Can I publish an unlisted Chrome extension for private testing?

Yes. The Chrome Web Store developer dashboard lets you set visibility to Unlisted, which means the extension is only accessible via a direct URL you share. Unlisted extensions still go through Google’s review process, but this is a practical way to do limited beta testing before a public launch.

Publishing a Chrome extension has a low cost of entry and a straightforward process once you know the steps. The main things that slow people down are packaging the zip incorrectly, requesting permissions they cannot justify, and skipping the privacy policy. Get those three right and the path from built extension to live listing is genuinely smooth.

We’re building in the open

Tinkrd is a small studio making thoughtful apps for families. Our first app is launching soon.

See what we’re building

T
The Tinkrd Team

We are a small independent app studio in California. We write about what we are learning as we build and ship products, from first commit to first customer.