How to Use PlugThis

From a one-line idea to a working Chrome extension installed in your browser — in under two minutes. Here's how every part of PlugThis works.

Getting Started

You have an idea for a Chrome extension. You don't have a developer, six weeks, or $5,000. PlugThis closes that gap — describe the extension in plain English and ship a working Manifest V3 build before your coffee gets cold.

Quick Start in 3 Steps

1

Sign in

Sign in with Google or with your email. Free to try — no card needed.

2

Describe your extension

On the home page, under "What should we build?", say what you want in plain English. For example: "Save every article I read for more than 2 minutes to a Notion database." Leave the Build tab selected and send.

3

Try it, then install it

Click around in the live preview, then open Test & Download: Install writes it straight into a folder (or Download gives you a ZIP). Load that folder at chrome://extensions with Developer mode on.

💡 Stuck for an idea? Browse the extensions catalog for ready-to-build prompts, or paste a problem into the Idea Generator to get three tailored builds.

🔧 Free tools. Need a one-off manifest.json without running a full build? Use the Manifest V3 Generator. Want to understand what a permission does before requesting it? See the Permissions Explainer.

Chat with AI

The chat is where every build starts and where every change happens. Describe the extension in plain words and PlugThis writes the whole Manifest V3 project: manifest, popup or side panel, content scripts, background worker, icons. Want a change? Say what to change.

The PlugThis home page with a request typed in

Ask, Plan or Build

Pick a tab above the message box before you send:

  • Ask (free): questions about your extension or about Chrome extensions. Nothing is built.
  • Plan (free): PlugThis writes a plan you can change in the chat. Nothing is charged until you click “Build this plan”.
  • Build (1 credit): writes or changes the extension. The credit is used only if the build passes its checks.

Fast suits most changes; Deep thinks longer, for harder logic.

How to write good prompts

  • ✓Be specific: "Add a Summarize button under every YouTube video that pulls the transcript and asks Claude for 5 bullets" beats "make a YouTube summarizer."
  • ✓Name the trigger: What starts the extension? A button click, a right-click menu, a keyboard shortcut, page load?
  • ✓Mention the site: If the extension only runs on certain sites (gmail.com, github.com, your CMS), list them. Scoped extensions ask for fewer permissions and pass review more easily. Not sure what a permission does? See the Permissions Explainer.

Making changes

  • • Ask in plain words: “Change the button colour to blue”, “Add a settings page”, “Make it work on YouTube only”.
  • • Every reply lists the files it changed. Undo on that reply puts the code back the way it was.
  • • What next? under a reply offers follow-ups you can run with one click.
  • • While a build runs, keep typing: your next change waits in a queue and sends when this one finishes.
  • • Fix an error: paste a Chrome console error, or describe what does nothing, and PlugThis fixes it in place.
  • • Files: point the AI at the exact files you mean.

Images

Add up to 5 images per message (or paste them into the box) to share a mockup, a screenshot of a similar extension, or the part of a page you want changed.

Code

You never have to touch code. If you want to, open Code next to Preview.

The code view

Every file, grouped

The file list groups your project (source, pages, icons, config). Open a file and it gets its own tab.

Edit and Save

Edit any file and press Save. Saving your own edits uses no generation.

New file

Add a file exactly as you paste it. Nothing is rewritten.

Send code to the chat

Select some code and ask about it or change it in the chat.

Live Preview

Try your extension before installing it. The preview runs its pages in a safe frame, so you can click and type without loading anything into Chrome.

Live Preview

What you can do

  • • Switch views: Popup, Side Panel, Options, New Tab, or “On a page” for extensions that add something to websites.
  • • Pick Element: click any part of the preview and PlugThis finds its code, so you can say “make this bigger” about exactly that part.
  • • Watch it build: the preview updates while PlugThis writes the files.

The preview is simulated. Content scripts and the background worker don't run there, and storage and tabs won't behave exactly as installed. To test on real websites, install it in Chrome (see Test & Download).

Set up

The Set up menu above the preview holds what an extension may need before it works.

Setup steps

What still stands between this build and a working extension (for example a database table to create), with the schema if it has one. Tick steps off as you do them.

Keys

Your API keys and Supabase project. Save them once in Settings, or give one extension its own. Keys are stored encrypted and never put into the AI’s prompt.

Bot

An assistant inside your extension that runs its actions for the people who use it, with routines on a schedule and an optional team of bots.

Test & Download

Open Test & Download at the top right of a project. Each download is a complete Manifest V3 folder, with your source code in its source/ folder.

Install

Writes the built extension straight into a folder on your computer: no zip to unpack. PlugThis remembers the folder, so the next version takes one click. Works in Chrome, Edge and Opera; in Brave, turn on folder access first.

Download

A ZIP to unpack and load yourself. “Download clean copy” leaves out all of PlugThis’s test tools.

GitHub

Push the project’s files to a repository on your GitHub account.

Legal

Write a privacy policy and terms for your extension, from what its code actually does. Copy them or download them.

Load it in Chrome

1

Install to a folder, or unzip your download

2

Open chrome://extensions in Chrome

3

Turn on Developer mode (top-right corner)

4

Click “Load unpacked” and pick the folder

5

Click the puzzle icon in the toolbar and pin your extension

Keeping your installed copy up to date

When the copy installed in Chrome is behind your project, the project header shows Update Chrome to v…. One click writes the new files into its folder and reloads it.

Test tools and error reports

  • • Test copies (Download, Install, Update) carry PlugThis test tools while loaded unpacked. Clean copies and Web Store ZIPs never carry any of our code.
  • • Test error reports are off until you turn them on. When on, your test copy sends its errors (the error, the file and line, and the site's address, never page content) so you can fix them in one click.
  • • Your saved key is not in the download unless you choose “Put my saved key in this copy”. Without it, the extension asks for the key once, in its own settings.
  • • Want to open it from anywhere? “Add it” gives the extension a keyboard shortcut, a pop-out button and an “Add to desktop” page.

Publish

The Publish menu above the preview takes your extension outside PlugThis.

Store assets

Generate the screenshots and promo images the Chrome Web Store listing needs.

Chrome Web Store

A readiness checklist: icon, descriptions, single purpose, permission reasons, privacy answers and category, written for you and ready to copy into your submission.

Share a preview link

A public read-only link to try your extension’s UI. Your .env files are never shared, and you can revoke the link any time.

Publishing to the Chrome Web Store needs a Google developer account ($5 one-time fee). You can also publish to Discover, where others can download your extension or clone it and change it.

Your extensions & workspaces

Every extension you build is saved to your account. The sidebar on the left lists them, with your unbuilt plans below. The home page shows where you left off.

Versions

Every change is saved as a version. Compare any two, add a note, or restore an older one. Restoring adds it back as a new version, so nothing is lost.

Duplicate, move, favourite

The arrow next to an extension in the sidebar opens its actions: favourite, publish, versions, keys, move to another workspace, duplicate, delete.

Workspaces

Build together. Create a workspace, invite people as admins or members, and share keys across its extensions.

Unbuilt plans

Plans and chats that never became an extension stay in the sidebar, so you can pick them up later.

Billing & Plans

Simple, transparent monthly pricing. Cancel anytime. No per-seat fees, no surprise add-ons. Every plan includes ZIP export and full code ownership.

Popular
Starter
$9.99/mo
Monthly • Cancel Anytime
  • ✓
    1 extension
  • ✓
    Unlimited chats to build and refine it
  • ✓
    Build & ship to the Chrome Web Store
  • ✓
    Own all code — no lock-in
  • ✓
    Cancel anytime

For builders shipping their first extension.

Builder
$29.99/mo
Monthly • Cancel Anytime
  • ✓
    3 extensions
  • ✓
    Unlimited chats to build and refine them
  • ✓
    Full-stack (Supabase + LLM)
  • ✓
    Priority support
  • ✓
    Cancel anytime

For active builders shipping multiple extensions.

What does “Front-end only” vs “Full-stack” mean?

Front-end only (Starter): manifest, popup, content scripts, options page, icons. Everything that runs in the browser. Full-stack (Builder): everything in Front-end plus auto-wired Supabase backend (auth, database, edge functions) and LLM integration (OpenAI, Anthropic, Gemini) — useful when the extension needs persistent storage across users or AI features beyond the user's own API key.

Payment & billing

  • • Payments are processed by Dodo Payments. We never store card details.
  • • Plans are monthly — cancel anytime from your account settings, no exit fees.
  • • Extensions you've already built stay on your machine and keep working forever, even after you cancel.

Managing your plan

Open Plan and credits to see your current plan, remaining monthly builds, and upgrade options. See the full plan comparison on the Pricing page.

Analytics & Performance

Open Analytics from the account menu to see what you've built, and whether it's working, over the last 7, 30 or 90 days, or all time.

Analytics Dashboard

Your numbers

Extensions, how many you published, how many packaged cleanly, and how long a typical build takes.

Generations

How many builds started, finished, failed or stopped early.

What happened

A list of every build and package, newest first, and the projects to pick up where you left off.

Frequently Asked Questions

Do I need to know how to code?

No. Describe the extension in plain English and PlugThis returns a working Manifest V3 bundle. You only touch code if you want to.

Is the output a real extension or a prototype?

A real extension. The output is Manifest V3 compliant, uses native Chrome APIs, and ships as a folder you can load into Chrome immediately or publish to the Chrome Web Store.

Can I edit the generated code?

Yes. Open Code next to Preview, edit any file and press Save (your own edits use no generation). Or ask for the change in the chat.

Who owns the code?

You do. Every download includes your source code. Test copies carry PlugThis test tools while loaded unpacked; a clean copy or a Web Store ZIP carries none of our code. It's yours to keep, modify, ship, or sell.

How does this compare to building it myself or paying a developer?

A custom Chrome extension typically takes a developer 1–6 weeks and costs $2,000–$10,000+. PlugThis returns a working build in under two minutes. We rebuild popular paid extensions on video in our /rebuilds series so you can see the process end-to-end.

Will my extension use AI? Do I need to pay for an AI API?

Only if you want it to. If your extension needs AI (summarizing, writing, translating), you bring your own key (OpenAI, Anthropic, Gemini, Groq or OpenRouter). Keys you save in Settings are stored encrypted and never put into the AI's prompt. They are not in your download unless you choose to put your key in a copy; otherwise the extension asks for it once, in its own settings.

Is my data private?

Your prompts and generated code are not used to train AI models. A clean copy or Web Store ZIP of your extension carries none of our code. A test copy sends its errors to PlugThis only if you turn Test error reports on, and then only the error, the file and line, and the site's address, never page content.

Can I publish my extension to the Chrome Web Store?

Yes. Publish → Chrome Web Store walks you through everything the submission asks for. You'll need a Google Developer account ($5 one-time fee) to submit it.

What if I run out of monthly builds?

Builds reset at the start of each billing cycle. If you hit your cap before then, upgrade from Starter ($9.99/mo) to Builder ($29.99/mo) and you'll get more extensions and capacity. Cancel anytime from your account.

Can I get a refund?

Fees are generally non-refundable except as required by law. If you hit an issue, email support@plugthis.ai — we read and respond to every message.

Ready to build?

Skip the rest of the docs. Describe what you want and ship a Chrome extension in under two minutes.