Shipped
Indexly Vault & Reddit Responder
He started building it himself, then found PlugThis. It worked in 2–3 prompts and shipped the same day.

Chetan Giridhar
Founder, Indexly
Build the ones you need.
Watch the Merlin rebuild on YouTube (opens in a new tab)
Watch the CSS Peeper rebuild on YouTube (opens in a new tab)
Watch the Wiz Write rebuild on YouTube (opens in a new tab)
Watch the Writeseed rebuild on YouTube (opens in a new tab)
Watch the Pretty Prompt rebuild on YouTube (opens in a new tab)
Watch the BlurWeb App rebuild on YouTube (opens in a new tab)Shipped
Indexly Vault & Reddit Responder
He started building it himself, then found PlugThis. It worked in 2–3 prompts and shipped the same day.

Chetan Giridhar
Founder, Indexly
Shipped
Bank Statement Importer
“It was so fast and worked like a charm. I thought for sure I’d spend hours, days, and grey hairs on this.”

Crystal Harrison
CEO, SnapTax
Raison d’être



We used to think about where PlugThis fits next to the big builders.
Lovable, v0, Bolt and Emergent will take a sentence and hand you back a working app by the afternoon. They remind us of McDonald’s, Wendy’s and Burger King. Enormous menus, same quality every time, at prices you can’t argue with.
But you can’t get a hot dog at McDonald’s. None of them were built for Chrome extensions. Ask for one and you’ll usually get something extension-like that doesn’t quite load.
PlugThis is the hot dog cart down the street. One thing on the menu. Chrome extensions, nothing else.
And we make the best hot dogs. Period.
Team PlugThis
You've paid enough for extensions that do 80% of what you need. Build the one you actually want, and keep the code.
A Chrome extension builder generates the code, the manifest and the packaging a browser extension needs, without you writing any of it by hand. PlugThis is built only for Chrome, so it works with the platform’s architecture instead of pasting in generic web app code that won’t run inside a browser.
Describe what you want in plain English and PlugThis generates the full Manifest v3 package: a manifest.json with the right permissions, content scripts scoped to the right URLs, a popup interface, a background service worker, and a Supabase backend when the extension needs one. It takes about two minutes.
You don’t need to know JavaScript, the Chrome extension APIs or the Manifest v3 spec. Say what the extension should do, which sites it runs on, and what it should remember. Permissions, file structure, message passing and packaging are handled for you, and the source code is yours to keep.
People build page summarisers, focus blockers, autofill tools, price trackers, AI writing assistants, meeting transcribers, tab managers, scrapers and translators. Anything Chrome’s extension APIs allow. Every build is Manifest v3 compliant and ready for the Chrome Web Store.
Everything from manifest to Web Store publish. The reference Chrome’s docs should be.
Every Manifest V3 field documented with examples, valid values, and common mistakes.
Every chrome.* API with code samples, use cases, and when not to use each one.
Skip the boilerplate. Describe what you want in plain English.
How AI generates a working Manifest v3 extension in minutes.
Stuck for an idea? Browse a curated list with ready-to-use prompts.
Step-by-step walkthrough from prompt to Chrome Web Store.
A tutorial for builders who've never shipped an extension before.