Got an idea for a Chrome extension? Describe it in plain English and PlugThis builds it. Real code, a real backend, ready for the Chrome Web Store. Refine it just by chatting. Connect Supabase for login and a database. Every change is saved as a version, so nothing is ever lost. When you're ready, we generate the icons, screenshots, and listing copy the store asks for. Everyone else builds web apps. We build Chrome extensions. That is the one thing we do.
Free Options
Launch Team / Built With
Dropbox SignSimple, secure eSignatures for the way your team works.
Promoted
Do the plugins stop working if you stop paying for the subscription? Or you just can’t modify them further?
@jasonrdunn Great question, and the answer is the good kind: your extensions keep working.
What you build is a real, standalone Chrome extension. The code is yours to download, and once it's installed or published to the store it runs on its own with no dependency on PlugThis servers. So if you stop paying, nothing you already shipped breaks.
The subscription is about building and modifying, generating new extensions and iterating on existing ones inside the tool. Pause it and your live extensions keep running exactly as they are, you just wouldn't be creating or changing more until you're back.
So it's full ownership, no kill switch. Your extension, your code, yours to keep.
@saurabh_dey1 great, thanks, that is great to hear!
The permission-scoping and service-worker answers here are more honest than I expected. One thing I didn't see asked: what happens when the extension someone describes needs a third-party API key. We shipped an internal extension that called an LLM endpoint and I pulled the key back out of the packed CRX in about a minute, because encrypting it at rest doesn't help when the decryption key ships in the same bundle. We ended up proxying every call through our own backend. Does PlugThis push people toward a proxy when the prompt implies a keyed API, or does it inline the key and leave that to the user?
@nefer_ai Tested it today and it's genuinely fun to use. I expected to spend time fixing boilerplate, but it got me to a usable extension much faster than I thought. If you keep improving the generation quality, this could become a go-to tool for anyone building Chrome extensions. Congrats! 👏
@neerajkanoi Thank you, glad you found it to be useful. If there is any feature you wan to see in the app, please let us know.
@hamza_afzal_butt Thank you, the types of extension being created are wide spread from scrapers to AI powered extensions that do customer research.
But my favourite so far was an interactive digital wellness BFF someone had created that acts as your buddy reminding you to do exercise, drink water every 20 minutes.
One other thing I have observed is people re-creating extensions that already exist and adding features they want on top of them.
The version history baked in is such a thoughtful touch, makes iterating with the chat feel safe instead of nerve-wracking. Glad someone finally focused on Chrome extensions instead of yet another web app builder.
@hamidesevg79879 Thank you version history was born out of pain we faced not having it :) And we wanted to be super focussed from day 1 and be the best platform to build chrome extensions.
Solid product. I've used this to create a few of my Chrome extensions to make my day to day work easier.
Although people with AI dev tools can create their own, I think everyone (even non-devs) needs to make their own chrome extensions to make their workflows easier, that's where this just works.
@soumitrasen Thank you for your kind words! Very happy to have you as a user from the earliest days of plugthis.
Super excited to check this out and will be trying it for our current web app 'dot.' as we could definitely expand our offerings with a chrome extension!
@munimur_ashrafy Thank you, great idea. A lot of our early customers create extensions to offer along side their main product. Please reach out to me if you have any challenges.