Build your first Chrome extension
Extensions are small web apps that live in the browser toolbar. You will pick a pattern, generate a working Manifest V3 extension, read every file, load it in Chrome yourself and change one behaviour — the fastest way to understand how extensions work.
You will practise
- How manifest.json, popup and permissions fit together
- Loading an unpacked extension for testing
- Asking for the minimum permissions
1Brief
Answer a few questions. The generator writes the code; you will read and change it.
2Make
Generate the project, then open every file. Comments explain each part. You can edit files right here.
3Check
Automatic checks for the mistakes that break real projects: invalid config, leaked keys, missing security steps.
4Improve
- Run the check first.
Your change: Change one behaviour yourself: e.g. in page-notes, make the status say “Saved at 14:32” with the current time. Reload the extension and test.5Ship
Load it unpacked in Chrome or Edge (steps in README.md). Publishing to the Chrome Web Store needs a developer account with a one-time fee; sharing the ZIP with friends is free. Step-by-step instructions are inside
README.md.✓ Added to your tool record on this device. See all 39 tools →
Questions people ask
Do I need to know JavaScript?
No to start. The generated code is short and commented; reading it and making one small change is the lesson.
What is Manifest V3?
The current format Chrome requires for extensions. It forbids remote code and encourages minimal permissions.
Do I need an AI key to use this?
No. The guided template teaches the same skill with no AI at all. If you add your own free key (Groq, Google Gemini, OpenRouter, Mistral or Cerebras), the tool can also draft and revise. The key stays in your browser and requests go straight to that provider.
Where is my work saved?
In this browser only (local storage), until you copy or download it. Nothing you type is sent to Open Practice.