Google ChromeOne extension, four stores: publish on Chrome, Edge, Firefox, and Safari from the same code
Team at AiToolsForAppsWritten with AI assistance16 min readIn summary
- Since Chrome 148, all extension APIs are available under the
browsernamespace, in addition to the classicchrome, according to the guide Transition to browser namespace from Chrome for Developers. The recap of I/O 2026 for web extensions (November 2026) summarizes it this way: the shared global "reduces the need for compatibility aliases". - Extensions with
devtools_pagewere initially left out: support forbrowserin that case arrived in Chrome 152. - What is not unified is the card: Chrome requires screenshots of 1280x800, Edge accepts 640x480 or 1280x800, Apple demands 16:10 without alpha channel (1280x800, 1440x900, 2560x1600, or 2880x1800) and AMO recommends 1280x800 or 1.6:1 ratio.
- The text limits also do not match:
descriptionof the manifest 132 characters in Chrome, store description of 250 to 10,000 in Edge, summary of 250 in AMO, and app name of 30 in App Store Connect. - And privacy is declared four times: Privacy tab in Chrome, Privacy page in Partner Center,
data_collection_permissionsin the manifest for AMO, and privacy policy in App Store Connect.

For years, porting a Chrome extension to Firefox, Edge, and Safari started with the same ugly line in the header of each file: an alias that decided whether to use chrome.* or browser.*. In 2026 that line is unnecessary. What continues to be a burden are the hours spent redoing the store card four times, and that’s where aiChrome comes in, the tool from AiToolsForApps for those who create, sell, or compete in Chrome extensions: it has the catalog of measurements and limits of the Chrome Web Store card with a verification seal, and what does not fit the specification is not delivered. This article explains what is no longer needed in the code and what remains manual work store by store.
What exactly changed in 2026 with the browser namespace?
Chrome adopted the browser global that Firefox and Safari were already using. According to the official documentation of transition to the browser namespace, "since Chrome 148, all Chrome extension APIs are available under the browser namespace, in addition to the existing chrome". The chrome namespace is not being retired: both coexist, so there’s nothing to break.
The practical effect is that an extension targeting only modern browsers can be written once, with browser.* and promises, and work in all four engines without an intermediate layer. Two important details:
runtime.onMessageaccepts promises. In Chrome 148, a listener can directly return aPromiseto respond asynchronously, instead of the classicreturn trueto keep the channel open.- The polyfill becomes unnecessary. Chrome's documentation states that webextension-polyfill "does nothing in Chrome 148 and later", because the browser already has native support.

Can I use browser without breaking users with old Chrome?
Yes, and Chrome's own documentation provides two routes. If your audience is already on Chrome 148 or higher, declare "minimum_chrome_version": "148" in the manifest and use browser unconditionally. If you need to support earlier versions, put a guard at the beginning of the startup:
if (!globalThis.browser) {
globalThis.browser = chrome;
}
The case that causes the most surprises is DevTools. In earlier versions, declaring devtools_page disabled the browser namespace for the entire extension, not just on the DevTools page. That limitation disappeared in Chrome 152, which now covers any extension. The onMessage listeners that return promises are still not available in DevTools page contexts.
What still remains ununified in the code
That the namespace is the same does not mean that the manifest is. According to the MDN guide on building a cross-browser extension:
| Point | Chrome / Edge | Firefox | Safari |
|---|---|---|---|
| Namespace | chrome and browser (148+) | browser (and chrome for compatibility) | browser |
| Background in MV3 | extension service worker | background pages | supports both |
browser_specific_settings | not supported | required (gecko block) | — |
| Packaging | ZIP with manifest.json at the root | ZIP | app-type packaging |
That is: the namespace is no longer a variable, but the background block and browser_specific_settings still require a manifest per target. The reasonable approach is to maintain a base manifest and generate the variants in the build, rather than keeping four files manually.
What else did Chrome announce in the I/O 2026 recap?
In addition to the namespace, the I/O 2026 recap from Chrome for Developers brings two changes that affect how it is published, not how it is programmed: team roles in the Developer Dashboard and private publishing for businesses.
The three new roles are:
- Admin: general management and adding new members.
- Item Manager: allows "uploading and submitting updates to the extension", without giving control of the account.
- Viewer: for those who only need to view performance metrics.
And additional members can be invited without each having to go through the developer registration. For an agency that publishes on behalf of a client, this is exactly the gap that needed to be filled: before, uploading an update meant sharing the account.
The private publishing for businesses allows deploying an extension to external organizations that approve it directly from the Chrome Web Store. The same recap adds a couple of contextual data about the ecosystem: developer registrations have doubled in the last year, 17% of new extensions in the Chrome Web Store incorporate AI, and the developer registration is expanding to more than 120 additional countries.
Image requirements differ in each store: comparative table
Here is the work that does not disappear. Each store asks for the same screenshot in a different crop, and one of the four directly rejects transparency. This is the comparison based on the official documentation of each:
| Active | Chrome Web Store | Microsoft Edge Add-ons | AMO (Firefox) | App Store Connect (Safari) |
|---|---|---|---|---|
| Icon / logo of the card | 128x128 PNG (96x96 of art + 16 px of transparent margin) | 1:1, recommended 300x300, minimum 128x128 | 32x32 and 64x64, PNG or JPEG | icon of the container app |
| Screenshots | 1280x800 (preferred) or 640x400, square corners and bleed | 640x480 or 1280x800, maximum 6 | 1280x800 recommended, or 1.6:1 ratio | 16:10: 1280x800, 1440x900, 2560x1600 or 2880x1800 |
| No. of screenshots | at least 1, up to 5 | up to 6 | at least those of key features | from 1 to 10 per size |
| Small tile | 440x280 (optional) | 440x280 (optional) | — | — |
| Large tile / marquee | 1400x560 (optional) | 1400x560 PNG (optional) | — | — |
| Transparency | the icon needs it in the margin | — | — | prohibited: no alpha channel or transparencies |
Sources: images of the Chrome Web Store card, publish an extension for Microsoft Edge (document updated in 2026), create an appealing listing in AMO and App Store Connect screenshot specifications.

Three practical consequences of that table:
- 1280x800 is the common denominator. It works in Chrome, Edge, and AMO, and is one of the four valid sizes from Apple. If you are only going to produce one set of screenshots, make it that.
- Apple forces you to flatten. App Store Connect does not accept alpha or transparencies, so a PNG exported with a transparent background is rejected even if it "looks good". You need to flatten and re-measure the binary, do not rely on the viewer.
- The Chrome icon is not a filled square. It is 128x128 canvas with 96x96 art and 16 px of transparent margin on each side. This is the most common mistake when reusing the icon from another store.
Character limits do not match either
Each store truncates the text at a different point, and in two of them, the text is not written in the store: it comes from the manifest. This is what the official documentation says:
| Field | Limit | Source |
|---|---|---|
name from the manifest | maximum 75 characters | Chrome name key |
description from the manifest | no more than 132 characters, plain text without HTML | Chrome description key |
| Tab description in Edge | minimum 250, maximum 10,000 characters | publish on Edge Add-ons |
| Search terms in Edge | up to 7 terms, 21 words in total, 30 characters per term | publish on Edge Add-ons |
| Summary in AMO | 250 characters | listing in AMO |
| App name in App Store | 2 to 30 characters | app information in App Store Connect |
| Subtitle in App Store | 30 characters | app information in App Store Connect |
Two details that save a review cycle:
- In Edge, the name of the extension and the short description are read-only in Partner Center: they come from the manifest. To change them, you must edit the
manifest.json, repackage, and resubmit. So those 132 characters ofdescriptionare not just a Chrome thing: they travel with you. - In Edge, if the package declares multiple languages but only one locale appears in Partner Center, it is usually because the manifest has fixed strings instead of placeholders
__MSG_extensionName__withdefault_localeand_locales. Partner Center detects the languages based on those i18n references. - In Safari, the name and subtitle are those of the container app, not those of the extension: 30 characters are very few if you came from a 75-character name.
The privacy declaration is made four times, and in Firefox, it goes in the manifest
None of the four reviews accepts the declaration from another, and since late 2025, Firefox has stopped requesting it on a form to request it within the manifest. This is the part of the process that is most undervalued when planning a multi-browser launch.
Chrome Web Store. The privacy tab of the dashboard requires a single purpose, justification for each permission declared in the manifest, declaration of remote code usage, certification of data usage practices, and privacy policy URL.
Microsoft Edge Add-ons. The Privacy page of Partner Center asks for the same in five sections: Single Purpose, justification per permission, remote code usage, data usage, and privacy policy. The documentation warns that any incomplete or misleading declaration "may be considered a violation of developer policies" and result in additional review, delay, or rejection. And remember that remote code is not allowed in Manifest V3.
AMO (Firefox). As of November 3, 2025, every new extension must declare what data it collects or transmits using the browser_specific_settings.gecko.data_collection_permissions key, according to Mozilla's announcement about the data collection consent changes (October 23, 2025). If you collect nothing, it must be explicitly stated:
{
"browser_specific_settings": {
"gecko": {
"data_collection_permissions": { "required": ["none"] }
}
}
}
The Firefox built-in data consent documentation details the accepted values (personallyIdentifyingInfo, healthInfo, financialAndPaymentInfo, authenticationInfo, personalCommunications, locationInfo, browsingActivity, websiteContent, websiteActivity, searchTerms, bookmarksInfo, plus technicalAndInteraction only as optional) and the coverage: Firefox 140 on desktop and 142 on Android. Without the key properly set, the extension cannot be submitted for signing. For extensions that already existed before that date, Mozilla says they will have to adopt it "later", without a specific date published.
App Store Connect (Safari). The privacy policy URL is mandatory for iOS and macOS apps, and the privacy declaration is made at the container app level, with the App Store Connect specifications as a reference.
Packaging: three ZIPs and an Xcode project
Three of the four stores are fed by the same artifact; the fourth one is not. Chrome, Edge, Firefox, and Opera consume a ZIP with the manifest.json at the root. Safari requires an app-style package: the extension travels within a native app that is distributed through the App Store.

For the jump to Safari, Apple offers the command line tool xcrun safari-web-extension-converter, which generates the Xcode project from an existing web extension; it is documented in packaging a web extension for Safari. The hard requirement is not technical, it is administrative: publishing on the App Store requires App Store Connect, and that is only available to members of the Apple Developer Program, which costs 99 USD per year of membership (with exemptions for non-profit entities, accredited educational institutions, and government bodies that meet requirements). Chrome Web Store, for its part, asks for a one-time registration fee when creating the developer account, according to its registration page; Edge Add-ons does not charge for registration, as indicated in its developer registration guide.
Review timelines to keep in mind
| Store | What the official documentation says |
|---|---|
| Chrome Web Store | "For most extensions, the review is completed in a few days, but it can take up to a few weeks"; if more than three weeks pass without changes, support must be opened (review process) |
| Microsoft Edge Add-ons | "The certification process can take up to seven business days" after submission (publishing on Edge) |
Chrome adds a nuance worth reading before requesting permissions: reviews take longer for extensions that request broad host permissions or sensitive execution permissions, or that include a lot of code or difficult-to-review code.
Is it worth publishing on all four? What the market share says
It depends on how much each listing costs, because the desktop share distribution is very uneven. According to data from Statcounter Global Stats for October 2026 in the desktop market worldwide:
| Browser | Desktop share (Oct. 2026) |
|---|---|
| Chrome | 66.98 % |
| Edge | 13.24 % |
| Safari | 7.83 % |
| Firefox | 5.72 % |
| Opera | 2.65 % |
Read wisely: Edge is the second market and shares almost the entire specification with Chrome (same ZIP, same screenshots of 1280x800, same 440x280 and 1400x560, same five privacy sections). It offers the best return for time invested: with the package you already have and two new images, you double your potential reach. Firefox costs a different manifest and the data key. Safari is the real cost: Xcode project, annual membership, and a listing with a 30-character name.
Checklist: publish once, list four times
This is the order that generates the least rework, based on everything above:
- Write the code with
browser.*and promises, and add the guardglobalThis.browser = chromeif you cover Chrome prior to 148. - Maintain a base manifest and generate variants in the build:
background.service_workerfor Chrome and Edge,background.scriptsfor Firefox, and thebrowser_specific_settings.geckoblock only in the Firefox variant. - Adjust
nameto 75 characters anddescriptionto 132 before packaging: those two fields feed the Chrome listing and are read-only in Edge. - If you want a multilingual listing in Edge, use
__MSG_extensionName__and__MSG_extensionDescription__withdefault_localeand_locales. - Produce screenshots at 1280x800 and save them without alpha channel from the start: it is the only version that works for all four.
- Prepare the Chrome icon as 128x128 with 96x96 of art and 16 px margin, and the Edge logo as 300x300 at 1:1.
- Generate the 440x280 tile and the 1400x560 banner only once: they work the same in Chrome and Edge.
- Draft a unique purpose and a justification for each permission in the manifest, and reuse that text in Chrome and Edge.
- Add
data_collection_permissionsto the Firefox manifest, even if it is["none"], or you will not be able to submit it for signing. - Leave Safari for last and budget it separately: conversion with
safari-web-extension-converter, Apple Developer Program, and 16:10 screenshots without transparency.
Frequently Asked Questions
Will the chrome namespace be removed in extensions?
No. The official Chrome documentation is explicit: the browser namespace is added "in addition to the existing chrome", and chrome is not being deprecated. You can migrate when it suits you, at your own pace and without breaking anything.
From which version of Chrome can I use browser unconditionally?
From Chrome 148 for regular extensions and from Chrome 152 if your extension declares devtools_page. Before 152, declaring devtools_page disabled the browser namespace throughout the extension, not just on that page.
Will I still need webextension-polyfill in 2026?
Only if you support Chrome 147 or earlier. In Chrome 148 and later, Chrome's own documentation states that the polyfill "does nothing", because support is already native.
Can I upload the same screenshots to Chrome, Edge, Firefox, and Safari?
Almost. If you produce them at 1280x800 without alpha channel, they are valid for all four: it is the preferred size for Chrome, one of the two accepted by Edge, the recommended size by AMO, and one of the four 16:10 sizes for App Store Connect. What changes is the maximum number (5 in Chrome, 6 in Edge, 10 per size in Apple) and the icons and tiles, which do need to be redone.
Why does App Store Connect reject my PNG screenshots?
The most common reason is transparency: Apple's specifications state that images cannot include alpha channels or transparencies. A PNG with alpha, even if the background appears white, will not pass. You need to flatten the image and check the resulting binary, not the viewer.
What happens if I do not declare data_collection_permissions in Firefox?
If it is a new extension, you will not be able to submit it to addons.mozilla.org for signing. It is mandatory from November 3, 2025, for new extensions; if you do not collect or transmit data, it must be declared with {"required": ["none"]}.
How long does the review take in each store?
Chrome mentions "a few days" for most extensions, with cases taking up to several weeks. Edge indicates that certification can take up to seven business days. Chrome also warns that broad host permissions and hard-to-review code extend the process.
Do I need to pay to publish in all four stores?
Chrome Web Store charges a one-time registration fee when opening the developer account. Edge Add-ons does not charge for registration. AMO does not either. Safari requires the Apple Developer Program, at 99 USD per year of membership, because the App Store is the distribution channel.
What is the Item Manager role in the Chrome dashboard?
It is one of the three team roles announced in the I/O 2026 recap: it allows a member to upload and submit updates for the extension without giving them account management, which remains with the Admin role. The third, Viewer, only sees metrics.
One listing per store, but measured only once
The work that the browser namespace has taken on was the most visible, but not the most expensive. The expensive part was, and still is, the listing: four sets of measurements, four character limits, and four privacy statements that are not inherited between stores. The difference between doing it in an afternoon and doing it in three rejection cycles lies in not improvising the measurements and in checking the binary of each image before uploading it.
That is exactly what aiChrome, from AiToolsForApps, automates: the MV3 manifest builder with the literal notice the user will see for each permission, the listing writer with a single purpose and justification permission by permission, the asset generator that delivers the 128x128 icon, the 1280x800 screenshots without alpha, the 440x280 tile, and the 1400x560 marquee, and a validator that measures your images in the browser, detects real transparency pixel by pixel, and offers you the crop to each specification. If you are going for all four stores, start by making the Chrome one impeccable: the verified table of measurements, limits, and privacy listing for Manifest V3 extensions is the starting point, and always distinguishes what is an official requirement and what is a recommendation.
Before duplicating the listing in four stores, have the Chrome listing pixel-perfect: try aiChrome for free and without registration, generate the manifest, the privacy policy, and the image pack, and validate your captures instantly.
Before duplicating the listing in four stores, have the Chrome listing pixel-perfect: try aiChrome for free and without registration, generate the manifest, the privacy policy, and the image pack, and validate your captures instantly.Keep reading
View all articles →
Why Your Extension is Rejected in the Chrome Web Store in 2026 (and How to Avoid It)

Broken Geode in Geometry Dash 2.2091: which mods are not working and how to keep creating

DLS 27 in December 2026: what is confirmed, what is not, and what happens to your club, your squad and your kits when you update
