Opening soon
Building Chrome Extensions & Automations
Build a Chrome extension, from the manifest and content scripts to popup and options pages, with AI help.
5 chapters · 22 lessons
Get an email when this course opens
What you'll cover
The chapters
The plan for the full course. Lessons open when the course does.
- 01How Chrome extensions are structured4 lessons
- 02The manifest file and permissions4 lessons
- 03Content scripts and changing web pages5 lessons
- 04Building popup and options pages4 lessons
- 05Using AI to build and debug extensions5 lessons
Self-check
How much do you already know?
5 quick questions. Pick an answer to see why it's right or wrong. Nothing is saved.
Question 1 of 5
What replaced background pages in Manifest V3 for running background scripts?
Question 2 of 5
A user installs an extension that saves their custom settings. They log into Chrome on a new laptop. What happens to those settings if the extension uses chrome.storage.sync?
Question 3 of 5
What does the 'permissions' field in manifest.json do?
Question 4 of 5
What does the 'activeTab' permission grant a Chrome extension?
Question 5 of 5
Which file tells Chrome which components an extension has, what permissions they need, and where each one runs?
Key terms
Words you'll meet in this course
- Manifest V3
- The current version of Chrome's extension platform, which replaces background pages with service workers and limits remotely hosted code.
- Content script
- JavaScript an extension injects into matching web pages so it can read and change their content.
- Isolated world
- The separate JavaScript environment a content script runs in: it shares the page's DOM but not the page's own variables or functions.
- Service worker
- An extension's event-driven background script, which Chrome starts when an event needs handling and stops when it is idle.
- Host permissions
- The list of sites an extension asks to access, declared in the manifest and shown to users before they grant it.
- Match patterns
- URL patterns, such as https://example.com/*, that tell Chrome which pages a content script or permission applies to.
- Message passing
- How an extension's separate parts, such as content scripts and the service worker, send data to each other through Chrome's messaging APIs.
Help us choose
Which course should open next?
Pick the one you'd take first. Your vote helps us decide what to finish next.