Is Major Cooked? Free AI risk score + roast for your college major
Solo Era solo activities, solo maxxing, sidequests, challenge
Keepsake Project Management, Freelancers, DesignersChrome extension ideas: 12 small builds, each tied to one extension API
A good Chrome extension idea fixes one repeated annoyance inside the browser and needs one extension API: a side panel for note-taking, the omnibox for jumping to tickets, declarativeNetRequest for blocking distractions, or built-in AI for summaries on the device. Ask for the fewest permissions possible. Below are 12 ideas, each with the API behind it, a first version you can finish in a weekend and the permission to watch.
What makes a good Chrome extension idea?
An extension works best when the job happens in the browser, repeats every day and is too small for a whole app. The best ones sit on one page or one habit: renaming downloads, jumping to a ticket, remembering a price. If the job needs a phone, a server farm or ten integrations, it is not an extension.
Chrome's extension platform is Manifest V3, and every capability sits behind a named API with a permission. That gives you a useful design check. Write down the one API and the one permission your idea needs. Chrome's tabs documentation notes that the "tabs" permission gives access to four sensitive properties: url, pendingUrl, title and favIconUrl. If your idea needs those, say why in the listing. If it does not, do not ask for them.
| API | What it does | Used by |
|---|---|---|
| sidePanel | Hosts your UI beside the page (Chrome 114+) | Quote collector |
| declarativeNetRequest | Blocks or modifies requests by rule, without reading them | Work-hours shield |
| omnibox | Registers a keyword in the address bar | Ticket jumper |
| readingList | Reads and changes the Reading List (Chrome 120+) | Reading list expiry |
| tabGroups | Modifies and arranges tab groups | Session saver |
| downloads | Starts, monitors and searches downloads | Download renamer |
| idle | Detects when the machine's idle state changes | Break nudge |
| Prompt API and built-in AI | Runs a model on the device | Tab questions |
You can build most of these with an AI coding tool in a weekend, because an extension is a manifest, a few scripts and an HTML page. The AI coding prompt builder turns an idea into a first brief, and how to build a Chrome extension walks through the files, loading an unpacked extension and publishing. Publishing on the Chrome Web Store requires a developer account with a one-time registration fee, so build for yourself first and publish only if others ask.
Which Chrome extension ideas help with reading and research?
Reading is where the browser holds the most unfinished work: tabs you meant to return to, pages you meant to quote. These ideas turn that pile into something you can use.
01 Was this actually on sale? A price memory
Remembers the price of products you view and tells you, on the product page, whether today's sale price is below what the item cost last month.
- API
- Content script, storage, alarms.
- Good for
- Shoppers who distrust a crossed-out price.
- Time to first version
- A weekend for one shop.
- Hard part
- Finding the price on a page that changes its markup.
A post on the board asks whether a sale was real. The extension answers on the page itself. A content script reads the price using selectors you write for one shop, and saves it with the date in extension storage. The storage API offers local, sync and session areas; local is right for this because the history stays on the device. See the idea.
First version: one shop, a price captured on each visit, and a small badge reading Lowest in 60 days or 12% above last month. Extension: more shops and a chart. Be honest about the limit: the extension only knows prices it saw, so a new product has no history. Say that in the badge text instead of showing a verdict.
Build a Chrome extension (Manifest V3).
User: an online shopper who wants to know if a sale price is real.
Scope: one shop domain I will name. A content script reads the product id and price from the page and saves {id, price, date} in chrome.storage.local, at most one entry per day per product.
UI: a small badge on the product page: Lowest in N days, or X% above the lowest, or No history yet.
Permissions: storage, and host permission for that one domain only.
Do not build: accounts, a server, other shops, notifications.
Done when: after three saved prices of 40, 35 and 38, the badge on a price of 36 reads 3% above the lowest.Read “Was this actually on sale? A price memory” on the board and copy its build prompt →
02 Turn the open tab into three questions for tomorrow
Reads the article in the current tab and produces three questions to answer from memory the next day, using the on-device model.
- API
- Built-in AI (Prompt API), alarms, notifications.
- Good for
- Students and people who read to learn.
- Time to first version
- One week.
- Hard part
- The hardware the on-device model needs.
A post on the board describes this exact habit. Chrome's built-in AI documentation says its Prompt, Summarizer, Writer, Rewriter and Proofreader APIs run a model on the device, that data is not sent to Google or a third party, and that they need desktop Chrome with enough free storage and a capable GPU or CPU. They are not supported on mobile. See the idea.
First version: a button that sends the page text to the model, shows three questions and stores them with the URL. An alarm fires the next day with a notification to open the questions. Extension: spaced repetition on a schedule. Because the model may not be available on every machine, show a clear message when it is not.
Read “Turn the open tab into three questions for tomorrow” on the board and copy its build prompt →
03 Quote collector in the side panel
A side panel that stays open while you read, collects selected passages with their URL and exports them as Markdown with footnotes.
- API
- sidePanel, contextMenus, storage.
- Good for
- Students writing papers and anyone gathering sources.
- Time to first version
- One week.
- Hard part
- Capturing page title and author when sites mark them up differently.
The side panel API lets an extension host content beside the main page, and the panel can persist as the user changes tabs. That is the difference from a popup, which closes the moment you click away.
First version: right-click selected text, Save quote, and see it in the panel with the page title and URL. Export a Markdown list. Extension: tags, a citation style and drag to reorder. Test with a selection that contains a link and a line break, since the Markdown export will break on them first.
04 Reading list that expires
Moves items from Chrome's Reading List to an archive after a set number of days, so the list stays short enough to read.
- API
- readingList, alarms.
- Good for
- People with 200 unread items.
- Time to first version
- A weekend.
- Hard part
- Deciding what archive means so nothing is lost.
The readingList API reads from and changes the Reading List, available from Chrome 120. An alarm runs once a day, checks the added date and moves anything older than your limit into a stored archive, with a search page for the archive.
First version: a 30-day limit and a one-click restore. Extension: a weekly digest page of what expired. Never delete without a copy. A user who loses an article they meant to read will uninstall the extension and tell others.
05 Reading style that follows you from site to site
Saves a font, text size and line spacing per site and applies it on every visit, so long articles are comfortable to read.
- API
- scripting (CSS injection), storage, activeTab.
- Good for
- People with dyslexia or tired eyes, and anyone who zooms every page.
- Time to first version
- A weekend.
- Hard part
- Sites whose styles are applied with high specificity.
The scripting API can inject JavaScript and CSS into a page. Declare the scripting permission, then use either host permissions or activeTab, which gives temporary access to the tab the user is on. The activeTab route means the extension never asks to read every site.
First version: a popup with three sliders and a Save for this site button; the saved values are injected as CSS next time. Extension: a reading mode that hides sidebars on listed sites, and a preset for high contrast. Test on three very different sites, one news site, one forum and one documentation page. Do not claim a medical benefit; say it lets people set the text the way they find comfortable.
Which Chrome extension ideas help with focus, tabs and downloads?
These ideas change how the browser behaves. They use the APIs that most directly change tabs, requests and files, so each has a clear before and after you can test.
01 Work-hours shield for chosen sites
Blocks a list of distracting sites between set hours and shows a plain page that says when they return.
- API
- declarativeNetRequest dynamic rules, alarms.
- Good for
- People who open the same three sites by reflex.
- Time to first version
- A weekend.
- Hard part
- A way out that does not make the extension pointless.
declarativeNetRequest blocks or modifies network requests with declarative rules. The extension never reads the request, which Chrome describes as more private. An alarm adds the block rules at 09:00 and removes them at 17:00, using dynamic rules.
First version: a list of domains, two times and a redirect to a local page. Extension: a five-minute pass that can be used three times a day, and a weekly count of blocked visits. The honest design question is the escape hatch. Too easy and it does nothing; too hard and you remove the extension. Pick a delay, such as a 30-second wait.
02 Ticket jumper in the address bar
Type a keyword and a number in the address bar and land on that ticket in your issue tracker.
- API
- omnibox.
- Good for
- Teams that live in a tracker and share ticket numbers in chat.
- Time to first version
- A few hours.
- Hard part
- Supporting several trackers or projects.
The omnibox API registers a keyword in Chrome's address bar. Once the user types it, each keystroke goes to your extension, which can suggest results. Type t, a space and 482 and the extension opens the tracker's URL for ticket 482.
First version: one URL template with a project prefix stored in options. Extension: suggestions that show the ticket title, using your tracker's API. This is also the smallest useful extension on the page, and a good first build. Add a second keyword for the wiki.
03 Tab group session saver
Saves a set of tab groups as a named project and reopens them later with their colors and titles.
- API
- tabGroups, tabs, storage.
- Good for
- People who juggle three projects in one window.
- Time to first version
- One week.
- Hard part
- Restoring groups without opening 40 tabs at once.
The tabGroups API changes and arranges groups, but grouping and ungrouping tabs is done with the tabs API. You will use both. Groups have a title and one of nine colors, which you can save and restore.
First version: Save current window as a project, Open project. Extension: open tabs lazily so memory stays low, and export a project as a link list to share. Test with a window of 30 tabs in four groups, and check titles and colors match after restoring.
04 Download renamer by rule
Renames and sorts downloads into folders by site and type, so invoices and receipts stop landing as download (7).pdf.
- API
- downloads (onDeterminingFilename).
- Good for
- Anyone who downloads statements, invoices or reports each month.
- Time to first version
- A weekend.
- Hard part
- Rules that stay understandable after ten of them.
The downloads API includes an onDeterminingFilename event that lets an extension suggest a filename after the MIME type and a tentative filename are known. Paths must be relative to the Downloads folder, and absolute paths or back-references cause an error.
First version: a rule list of domain, filename pattern and subfolder, for example a bank domain and a date prefix. Extension: a rule tester that shows what a file name would become before you save. Keep the order of rules visible and let one rule win, or two will fight.
05 Break nudge that follows real activity
Reminds you to stand up after 50 minutes of actual use, and does not fire if you have already been away.
- API
- idle, alarms, notifications.
- Good for
- Desk workers who ignore fixed timers.
- Time to first version
- A weekend.
- Hard part
- Tuning so it is helpful and not nagging.
The idle API detects when the machine's idle state changes. A fixed timer reminds you even if you just returned from lunch. Counting active time and resetting after a few idle minutes is kinder, and the reason to build it.
First version: 50 minutes active, a notification, a Snooze for 10 minutes. Extension: a daily total of active hours and a quiet period during calls. Keep the text neutral and offer a Skip today. This is a wellbeing nudge, not health advice.
Which Chrome extension ideas save time on forms and finding pages?
The last two ideas handle repeated typing and lost pages. They also touch the most personal data, so they are built to keep everything on the device.
01 Monthly form filler for the same admin forms
Fills the same timesheet, expense or report form each month from a saved template you edit once.
- API
- Content script, storage, commands (keyboard shortcut).
- Good for
- Anyone who files the same form every month.
- Time to first version
- One week.
- Hard part
- Form fields that are built by scripts and ignore normal input events.
Saved templates hold field selectors and values you wrote. A keyboard shortcut, set up with the commands API, fills the form on the current page. Never store passwords or payment details. If a field is sensitive, skip it and leave it to the browser's password manager.
First version: one site, one template, a fill button. Extension: increment a date or invoice number automatically. The hard part is not Chrome but the page: many forms use frameworks that ignore a simple value change, so you must dispatch input and change events after filling. Test on a copy of the real form.
02 Search your history by what the page said
Keeps a local text index of pages you visit so you can find that one article by remembering a phrase, not a title.
- API
- history, content script, IndexedDB.
- Good for
- Researchers and people who lose pages.
- Time to first version
- Two weeks.
- Hard part
- Privacy: what you index, and what you never do.
Chrome's history API lets an extension add, remove and query the browser's record of visited pages, but it holds titles and URLs, not page text. The extension saves the visible text of pages in a local database and searches it.
Set rules before code: no incognito windows, a block list for banking and email domains, a clear Delete everything button, and nothing leaves the device. First version: index only pages you star. Extension: index everything except the block list. If you plan to publish, write the privacy statement first and see if you can say it in two sentences.
How do you pick and test a Chrome extension idea?
- Choose an annoyance you hit this week, not an area you find interesting.
- Name the one API and the one permission. If you need more than three permissions, split the idea.
- Write the first version as one sentence with a number in it: badge reads 3% above the lowest.
- Load it unpacked on your own browser and use it for a week before showing anyone.
- Check the other browsers if you care: Safari can package a web extension from an existing Chrome extension using Xcode tools.
To check whether anyone else wants it, use the idea validation guide. To browse more ideas, see the developer tools and shopping categories on the idea board. If you have an idea you will not build, post it and someone else can pick it up with the build prompt attached.
Frequently asked questions
What are good Chrome extension ideas for beginners?
Start with the omnibox ticket jumper, a download renamer or a context-menu tool. Each uses one API, needs a few permissions and shows results in a minute. Avoid anything that reads every page, handles passwords or needs a server for a first project. A weekend of work is the right size.
Can I make money from a Chrome extension?
Some builders do, usually by solving a paid workflow for a small group rather than by selling to everyone. This is general information, not financial advice, and no income is promised. Start by building for yourself, then ask the first ten users whether they would pay, and what for, before adding any billing.
Do Chrome extensions work with AI?
Yes. Chrome documents built-in AI APIs, including the Prompt, Summarizer, Writer, Rewriter and Proofreader APIs, that run a model on the device and are available to extensions. They need desktop Chrome with enough storage and a capable GPU or CPU, and they do not run on mobile, so handle the case where the model is missing.
What permissions should a Chrome extension ask for?
As few as the first version needs. Each API page lists its permission, such as sidePanel, storage or downloads. The tabs permission exposes sensitive tab properties like the URL and title, so ask for it only if you need them. Narrow host permissions to the one site you work on, and explain each in the store listing.
How do I publish a Chrome extension?
Register a Chrome Web Store developer account, which Google says involves a one-time registration fee, then upload a zipped extension with a listing, screenshots and a privacy statement. Test the unpacked build in your own browser first. The how-to-build guide on this site covers the files and the review steps.
Where can I find Chrome extension ideas people want?
Look for repeated browser chores: copying a price into a note, retyping a form, hunting for a ticket. The idea board lists posted problems by category, and several of its shopping and learning ideas are extension-shaped. Each has a build prompt you can adapt into a Manifest V3 brief.
Created with AI assistance and edited for this site. Examples are illustrative and do not represent customer research. About the publisher.