The calendar, honestly
How Long Does It Take to Build a Chrome Extension? The Stages, Who Holds Each One, and Why Nobody Can Promise a Date
Ask a developer for a launch date and watch where their eyes go. The honest ones glance toward the store. Most of an extension's calendar is ordinary work you can plan, and one stage belongs to a reviewer you will never meet.
November 17, 2026 · 9 min read
- PassDeveloper account registered to a company address
- Pass2-Step Verification turned on
- WarnPrivacy policy approved by counselWith counsel
- FailListing icons and screenshotsNot started
- PassReviewer test login in Test instructions
- PassA justification written for each permission
- PassBuild tested in a clean browser profile
The short answer
A Chrome extension takes as long as its stages: scope, a permission plan, an estimate, the build, testing, developer account setup, the listing and store review. Build time depends on complexity, so DataCram quotes a fixed price rather than a date. As of November 2026, Chrome says most reviews finish within a few days but can take up to a few weeks. Connections to your own systems go live the same day.
On this page
- The question with two answers: the work, and the wait
- Eight stages, and whose desk each one sits on
- Five jobs on your side of the table, best started on day one
- What each store says about review, in its own words
- Why some reviews run long, and which causes a build can remove
- Every update waits in the same queue as the launch
- Ways to reach a working extension sooner, without a promised date
The question with two answers: the work, and the wait
Every extension schedule has two halves. The first half is work: deciding the job, writing the code, testing it, filling in the store's forms. A developer can scope that work, and so can you, because most of it depends on choices made in the first conversation. The second half is a wait. After submission, the package sits in a queue run by Google, Microsoft, Mozilla or Apple, each with its own wording about how long that takes and none promising anything.
So we quote a price and not a launch date. DataCram builds custom extensions from $1,500, depending on complexity, with a fixed written estimate before work starts. A date would mean promising something about a reviewer's inbox, and the stores decline to make that promise themselves. Our development service page shows the full process, and the browser extensions hub lists every kind we build.
A developer who promises a launch date is promising something about a stranger's inbox.
Eight stages, and whose desk each one sits on
| Stage | Who holds it | What tends to stall it |
|---|---|---|
| Scope and single purpose | You and us | A feature list that turns out to be two extensions |
| Permission plan | Us, approved by you | A feature that needs broad site access, which changes both the plan and the review |
| Written estimate | Us | Open questions about which systems and browsers are in scope |
| Build | Us | Scope changes mid-build, or a target site that redesigns its pages |
| Connections to your systems | Us, with your API access | Waiting on credentials; once we have access, connections go live the same day |
| Testing | Us, with your staff | Test accounts nobody has created yet |
| Developer account and listing | You, with our help | Registration, 2-Step Verification, the privacy policy, screenshots |
| Store review | The store | Nothing either of us can hurry, beyond a clean submission |
Read the middle column again. Several stages wait on you, and they are where calendars slip. None of them is hard. All of them are easy to start late, because they look like paperwork next to the exciting part. The next section lists them so they can begin on the first day, in parallel with the build, instead of after it.
Five jobs on your side of the table, best started on day one
- 1
Register the developer account
Google requires registration and a one-time fee before you publish: $5 as of November 2026, per an April 30, 2026 entry on Chrome's What's new page. Use a company address you will keep, since the account's email cannot be changed later.
- 2
Turn on 2-Step Verification
Chrome's two-step policy requires it on every developer account before publishing or updating an extension. Chrome's security guidance suggests a security key.
- 3
Get the privacy policy approved
If the extension handles any user data, the store requires an accurate privacy policy linked in the dashboard. We draft the data disclosures from the permission plan; your counsel approves the policy.
- 4
Gather the listing material
The store needs icons and a description of at most 132 characters. Google's troubleshooting page lists a missing icon, title, screenshot or description as a rejection it labels Yellow Zinc.
- 5
Prepare reviewer access
If the extension needs a login, the dashboard's Test instructions tab takes credentials for the reviewer. A ready test account keeps the reviewer from stopping at a sign-in screen, which matters most for a SaaS companion extension.

Two of those jobs, the account and the privacy policy, have nothing to do with code and can start before the estimate is even signed. Our page on extension permissions and privacy explains what the disclosures cover, so your counsel knows what is coming.
What each store says about review, in its own words
| Store | What it says | Source |
|---|---|---|
| Chrome Web Store | "For most extensions, review is completed within a few days, but it can take up to a few weeks." Past three weeks pending, Google suggests contacting developer support. | Google's review process page |
| Microsoft Edge Add-ons | "The certification process can take up to seven business days after you submit the extension." | Microsoft's publishing guide |
| Firefox add-ons | Signing and publishing can take up to 24 hours, "or longer if your submission is selected for manual review." | Mozilla's signing overview |
| Safari, through the App Store | Apple says it reviews all extensions and updates. We have no stated review time from Apple to quote. | Apple's Safari extensions page |
Note what those sentences are: descriptions, not commitments. Each store keeps the right to take longer. Google adds that every submission goes through the same system "regardless of the tenure of the developer or number of active users," so there is no fast lane for famous names. Mozilla adds that any add-on can get a manual code review at any time after submission. Our page on Chrome Web Store review goes deeper on the process.
Why some reviews run long, and which causes a build can remove
Google's review page names the signals that draw closer review: new developers, new extensions, dangerous permission requests and significant code changes. It adds that reviews may take longer for extensions requesting broad host permissions, such as <all_urls>, or carrying a lot of code or hard-to-review code. Some of that is fixed by circumstance. Some is a choice.
- New developer, new extension. Unavoidable the first time. A company's first extension is, by Google's own list, the kind that draws a closer look.
- Broad host permissions. Avoidable in most builds. GatorCrawl Keywords, our own extension, runs its content script on one address pattern and has host access only to its own app, as the GatorCrawl case study shows.
- Hard-to-read code. Avoidable. Google allows minification and forbids obfuscation, so we minify where useful and never obfuscate.
- A rejection and resubmission. The most avoidable delay. Google's troubleshooting page lists a permission requested but never used (Purple Potassium) and files named in the manifest but missing from the package (Yellow Magnesium) among the common causes.
Every update waits in the same queue as the launch
Launch is not the last review. Google's documentation says all submissions, "whether for a new item or an update to an existing one," go through the same review process. A bug fix waits in line the way a first release does, which is one more reason to test thoroughly before each submission rather than after.
The exceptions are narrow. Updates that change only Declarative Net Request rules and meet Google's criteria can skip review, and Google says they "usually go live within a few minutes." Partial rollout, sending an update to a share of users first, is open only to items with over 10,000 seven-day active users, as of November 2026. Neither helps a brand-new business extension much: one covers only rule changes, the other needs an audience first.
A new permission costs time of a different kind. When an update adds a permission that triggers a warning, Chrome disables the extension for each user until they accept it. Planning permissions in the first build, or making later ones optional, avoids that. Our page on extension maintenance covers the release routine, and Manifest V3 covers platform changes that force updates.
Ways to reach a working extension sooner, without a promised date
Start with Chrome
Ship one browser first. Microsoft says a Chromium extension can then go to Edge without a rewrite, and Firefox and Safari can follow. See cross-browser extensions.
Let staff use it first
Google says domain-published extensions on a Workspace organization's private store usually clear review more quickly. Internal team extensions explains the setup.
Cut to one job
Every feature outside the single purpose is a second extension, a second review and a second set of permissions. Trim it before the build, not after a rejection.
Have API access ready
Connections to your CRM, web app or AI provider go live the same day once we have credentials. API integrations explains what we need.
If the calendar matters because the extension is one piece of a launch plan, a fractional CTO can sequence the pieces so the store review is not the last thing anyone thinks about. For the money side, our extension pricing guide explains what sets the estimate. Or call (210) 346-0848 and tell us what the extension should do.
Questions owners ask about custom browser extensions
No, and be careful with anyone who does. The build is work we can scope and price, but store review belongs to Google, Microsoft, Mozilla or Apple, and none of them promises a time. We quote a fixed price from $1,500, depending on complexity, and remove the causes of avoidable delay: broad permissions, missing listing material and unclear disclosures.
As of November 2026, Google's review page says most extensions are reviewed within a few days, but some take up to a few weeks, and it suggests contacting developer support after three weeks pending. New developers, new extensions and broad host permissions are among the signals Google names for closer review, so a first submission may take longer.
Each store words it differently. As of November 2026, Microsoft says Edge certification can take up to seven business days. Mozilla says Firefox signing can take up to 24 hours, or longer if a submission is picked for manual review. Apple says it reviews all Safari extensions and updates; we have no stated time from Apple to quote.
Connections to your own systems, whether a CRM, your web app, an AI provider or a payment processor, go live the same day once we have API access. The extension talks to your server, and your server talks to those systems, so the connection does not wait on a store review.
Yes. Google says new items and updates go through the same review process. A narrow exception covers updates that change only Declarative Net Request rules and meet Google's criteria. An update that adds a warning-bearing permission also disables the extension for each user until they accept it, so plan permissions early.
The parts easiest to start late are the client-side jobs that look like paperwork: registering the developer account, turning on 2-Step Verification, getting the privacy policy approved, gathering listing images and preparing a reviewer login. Start them on the first day, alongside the build, and the only wait left is the store's.
Keep reading
- The store, read closelyChrome Web Store Review Process: Why Extensions Get Rejected and How to Stay Out of the Resubmission LoopHow Chrome Web Store review works as Google documents it, what the color-and-element rejection codes mean, and how to submit once instead of five times.
- The price, line by lineHow Much Does It Cost to Build a Chrome Extension? Five Decisions, the Store Fees and Our FloorWhat a custom Chrome extension costs to build: the five drivers, store fees as of November 2026, the costs after launch, and when not to spend at all.
- The offer, part by partCustom Chrome Extension Development Services: Discovery, a Permission Plan, the Build and a Listing in Your NameHire a Chrome extension developer for discovery, a written permission plan, a Manifest V3 build, store submission and a handover under your account.
- Your app, one tab closerSaaS Browser Extensions That Carry Your App's Login, Plan and Credits Into the Tab Your Users Already Have OpenA companion Chrome extension that signs in with your SaaS account, spends the same plan credits and bills on your own site. From $1,500, owned by you.
- Your data, on their pageCustom SEO Chrome Extensions That Paint Your Own Numbers Onto Google's Results PageBuild an SEO extension that shows your own keyword, rank or client data on Google results, on one site, with two permissions. From $1,500, yours to own.
- Capture, minus the clipboardCRM Chrome Extensions That Save a Contact in One Click, Straight Through Your CRM's APIA Chrome extension that saves the contact on your screen to your CRM in one click, through the CRM's API, with no copy and paste. From $1,500.
- Everything in Custom Browser ExtensionsSee the section
From the Insights desk
- The Web Agency on CNBC vs. the One That Picks Up Your CallThere's a national web agency running ads on CNBC — 500 people, Fortune 500 clients. It's a capable shop, but a national cable ad is aimed at enterprise budgets, not the plumber in Boerne. The case for a local partner you can actually reach.
- Twelve Questions to Ask Before You Sign With Any Web CompanyBuying a website means judging work you cannot inspect, in a vocabulary chosen to keep you from inspecting it. Twelve questions that sort the field faster than any proposal — ask them of us, too.
Plan the calendar you can control
Tell us what the extension should do and when it matters to you. We reply with the stages, the jobs on your side, and a fixed written estimate from $1,500, with no launch date we cannot keep.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.