How to pick a Chrome extension builder (or skip one)
Maksim Norkin (opens in a new tab)Product
· Updated · 6 min read
What an AI Chrome extension builder gives you, how three compare from their own pages, and when the job doesn't need a new extension at all.
Describe it
A Chrome extension builder takes a description of what you want, such as a timer in the toolbar or a button on a site, and makes the extension for you. Many now use AI. This guide compares three AI Chrome extension builders by what you get, how you publish it and who keeps it working, from each one's own pages as of 27 October 2026, and ends with the question worth asking first: does the job need a new extension at all?
An extension is a small set of files: a manifest that tells Chrome what the extension is and what it may do, plus the pages and logic behind its buttons. A builder writes those files from your description, and the differences between builders are in what happens next: whether you get the files, whether you can publish them on the Chrome Web Store, and how you change the extension later.
- manifest.json
- popup.html
chrome://extensions
| PlugThis | Kromio | Manus | |
|---|---|---|---|
| You describe | What the extension should do, in plain English | Your idea, in plain words | What the extension should do, in everyday language |
| You get | The extension's complete files, to download and load into Chrome without PlugThis | The extension's files as a ZIP, which you load in Chrome's developer mode | A working browser tool, mainly for your own use; sharing is planned |
| Publishing | Yes: its page says you can publish, sell or share what you build | Its page describes preparing the files for a store submission | Not described on its page |
| Changing it later | Update or regenerate it in PlugThis | Revise it in Kromio; each revision counts as a generation | Refine the description and build it again |
| Price | Paid plans only | A free plan, with paid plans for more generations | Daily free credits, and subscription plans |
Yes: that is what each builder above does, and a general AI assistant can draft an extension's files too, if you ask. What AI doesn't do is the rest of the job: loading the files into Chrome, testing them on the sites you care about, and fixing what breaks when a site or Chrome changes. If you'd rather understand each step, we wrote a guide to make one yourself, step by step.
- Do you get the files? With the files, you can keep the extension if you stop paying, or ask someone else to change it.
- Can you publish it? A builder that makes a tool for your own use may not give you anything you can put on the Chrome Web Store.
- How do changes work? If every change is a new generation, check how many your plan includes before you start refining.
- What does it ask to reach? An extension can read the sites it is allowed on. Read what the generated extension asks for, the same as you would for one from the store.
First release
- SubmitAfter a one-time developer fee
- ReviewMost finish within a few days
- PublishedOn the Chrome Web Store
Every update
- UpdateAny change you publish
- ReviewThe same review again
- PublishedThe new version
To publish on the Chrome Web Store, you register as a developer and pay a one-time registration fee. Each submission is then reviewed against the store's policies. Chrome's docs say most reviews finish within a few days but can take a few weeks, and that an update goes through the same review as a new extension. So whoever builds it, every change you publish waits for a review, and keeping the extension working is yours to do.
A new extension to own
- A listing
- A review for every update
- A fix whenever the site’s layout changes
Many extensions people describe to a builder are a fix for one site: a button the admin panel doesn't have, an export the dashboard doesn't offer, one view of what's spread across three tabs. For those, a new extension is a lot to own: a listing, a review for every update, and a fix whenever the site's layout changes under it. The same question comes before a new app, too; our guide to a Lovable alternative starts with it.
Tabless isn't an extension builder. It's a browser extension that builds what you ask for from the sites you allow, and what it builds lives inside Tabless: there is no new extension to publish or put through review. Nothing is typed or submitted without your OK. It isn't open yet. We're building it for the jobs above: ask in plain words for the button, the export or the view a site is missing, and it's designed to build that on the site you already use.
It's designed to read through the session your browser already has, so there are no API keys or passwords to hand over, and to ask before it reads each site. You sign in to Tabless with a Wix account.
Yes. To publish on the Chrome Web Store, you register in its developer dashboard, agree to the developer agreement and policies, and pay a one-time registration fee. For an extension only you use, you can load its files into Chrome without publishing it.
PlugThis says you can update or regenerate it there, Kromio counts each revision as a generation, and Manus has you refine the description and build again. Whichever you use, a published update still goes through the Chrome Web Store's review.
No. Tabless isn't an extension builder: what it builds lives inside Tabless, on the sites you already use.
Not yet. Tabless isn't open, and adding a button, an export or a view a site lacks is what we're building it for. Join the waitlist, and we'll let you know when you can try Tabless.