Four steps.
About five minutes.
Every template is readable source you install yourself. There is no installer, no build step and no account — you unzip a folder and point Chrome at it. Here is the whole process.
4 steps · about 5 minutes · nothing to install first
- 1
Download the template
Pick the one that does the job you need. Every template downloads as a ZIP of readable source — a manifest, a popup, the logic, and its own documentation.
Copy Clean Link is free, no email required. It is the same package a buyer gets, so you can read real code before deciding.
No installer, no account, no build tools. The ZIP is the product.
- 2
Unzip it somewhere permanent
Unzip it to a folder you intend to keep — Documents, a projects folder, anywhere stable.
Chrome reads an unpacked extension from that folder every time it starts. Unzip into Downloads and empty Downloads, and the extension disappears.
Inside you will find manifest.json, the popup files, and a README explaining what it does.
- 3
Load it in Chrome
Type
chrome://extensionsinto the address bar. A link cannot open it — Chrome only allows that address to be typed.Turn on Developer mode (top right), click Load unpacked, and choose the folder holding
manifest.json.Developer mode is Chrome's normal way to run an extension you have the source for. It is not a hack or a workaround.
- 4
Pin it and use it
Click the puzzle-piece icon in the toolbar and pin your extension so it stays visible.
Open an ordinary web page and click it. Most templates ask only for
activeTab, which means they can act on the tab you clicked and nothing else.Extensions cannot run on chrome:// pages, the Web Store, or a blank tab. Try a normal site.
Then it is yours
Rename and re-brand it
Change the name in manifest.json, swap the three icons, edit the popup. It is plain HTML, CSS and JavaScript with no build step, so an editor and a browser refresh is the whole toolchain.
Read every line first
A template is a handful of short files. No minified bundle, no dependency tree, no remote code. An automated check enforces that no template makes a network call, on every release.
Publish it under your name
Each ZIP includes a store-listing draft with permission justifications, privacy guidance, and a testing checklist. The licence lets you publish derivatives commercially. Chrome Web Store acceptance is always Google's decision.
Common questions
Do I need to know how to code?
To install and use one, no — the four steps above are the whole process. To change what it does, you need to be comfortable editing HTML, CSS and JavaScript. These are starting points for developers, not no-code apps.
Is Developer mode safe?
It is how Chrome runs an extension from source, and it is what every extension developer uses. The risk is running code you have not read. That is exactly why these ship as readable source rather than a packaged blob.
Will the extension update itself?
No. An unpacked extension is a folder on your machine and it changes only when you change it. Nothing phones home, and there is no update channel to trust.
Can I put it in the Chrome Web Store?
Yes, and the licence allows publishing derivatives under your own name. Each package includes a store-listing draft and permission justifications to make the submission easier. Acceptance is determined by Google's review, never by us.
What if it does not load?
Chrome names the problem. Click Errors next to the extension on chrome://extensions and read the message — it is usually exact about the file and line. The most common cause is choosing the wrong folder: pick the one with manifest.json directly inside it.
What data do the templates collect?
None. No template makes a network call — no fetch, no beacons, no remote scripts — and an automated check enforces that on every release. Whatever a template reads from a page is processed on your machine and shown in the popup.
See what is in the vault
Browse the catalogue, open a template to read its code before you buy, and download the free one to judge the quality for yourself.
Browse the templates