Developer Chrome extensions are the category most over-supplied by the Web Store and most under-customized to the individual developer. Every developer uses a JSON formatter; everyone's preferred JSON formatter looks slightly different. Every developer uses a color picker; everyone wants slightly different output formats. Every developer uses a regex tester; everyone has a slightly different mental model for how the input and output should be laid out.
The result: most developers have a folder of installed extensions, each one approximately right and exactly wrong in some small way. PlugThis solves this by letting you build the version that matches your workflow. Color picker that outputs in tailwind classes by default. JSON formatter that mirrors your team's exact style guide. Regex tester that supports the specific dialect your codebase uses.
You're also in the ideal user position to build these — you understand what you want at a precision other users can't articulate. PlugThis output is real Manifest V3 code you can edit and extend.
Scan any webpage for broken links in seconds. Get status codes, export to CSV.
Highlight typos and grammar issues on any webpage with AI-powered detection.
See file counts, line counts, and language breakdown on every GitHub repo page.
JSON, YAML, XML formatters; URL parsers; base64 decoders
Regex testers, API request inspectors, cookie viewers
Color pickers, font inspectors, rulers and grids, viewport switchers
Quick-access bookmarklets, devtools enhancements, snippet runners
Partially. Chrome extensions can't talk directly to local IDEs, but they can write to localhost servers, push to APIs (Linear, GitHub, Notion), or copy formatted output to the clipboard for paste-in. PlugThis can wire any of these.
More answers below.
Two reasons developers do it anyway: customization (default outputs match their codebase), and trust (no telemetry, no surprise feature additions, no ownership change when the original developer sells the extension).
Yes. Three options: (1) publish to the Chrome Web Store privately (only people with the link can install), (2) share the .crx file directly, (3) share the source folder and have teammates load it as an unpacked extension. Each option has tradeoffs — PlugThis output supports all three.
More answers below.
Rarely. Chrome's extension API is stable across versions. Major breaking changes (like the Manifest V2 → V3 transition) come with multi-year deprecation periods. PlugThis output uses Manifest V3, which is the current stable spec.
More answers below.
Tab managers, focus tools, note capturers, and time trackers that make your browser work harder for you.
AI-powered summarizers, writers, readers, and assistants — built on your own API keys, owned outright.
On-page SEO auditors, keyword research helpers, SERP analyzers, and marketing tools — built around your specific workflow.
Describe what you want in one sentence. PlugThis generates a working Manifest V3 Chrome extension in under two minutes.
Open the builder