The Chrome extensions worth installing for web development in 2026 are the devtools for your framework (React, Vue, Angular or Redux), Web Developer and VisBug for poking at pages, WhatFont, ColorZilla and CSS Peeper for design details, Requestly for network rules, axe DevTools and WAVE for accessibility, and Responsive Viewer for layouts. Every extension on this list was live in the Chrome Web Store when we checked on 20 November 2026.
That last part matters more than it used to.
Chrome now only runs extensions built on its newer extension platform, called Manifest V3. The older ones were switched off through 2025, and in August 2026 Google removed the last of them from the Chrome Web Store. A few extensions that still top other lists, like uBlock Origin and ModHeader, are gone. We cover what to use instead further down.
One more thing, so you can weigh what we say: we make Huddlekit, a website feedback tool. It isn't a Chrome extension, so nothing of ours is on this list, and nobody paid to be on it.
At a glance
| Extension | Best for | Last updated |
|---|---|---|
| React Developer Tools | React components, props, state and renders | Sep 2026 |
| Vue.js devtools | Vue components, Pinia stores and routes | Nov 2026 |
| Angular DevTools | Angular component trees and change detection | Nov 2026 |
| Redux DevTools | Replaying actions and state changes | Oct 2026 |
| Web Developer | A toolbar of quick page checks | Jun 2024 |
| VisBug | Nudging layout and text on the live page | Nov 2024 |
| CSS Peeper | Reading styles and assets without DevTools | Nov 2026 |
| WhatFont | Identifying fonts by hovering | Oct 2026 |
| ColorZilla | Picking colors and building gradients | May 2024 |
| Requestly | Redirects, header changes and API mocks | Sep 2026 |
| axe DevTools | Automated accessibility testing | Oct 2026 |
| WAVE Evaluation Tool | Seeing accessibility issues on the page | May 2026 |
| Lighthouse | One-click performance and SEO audits | Jun 2026 |
| Responsive Viewer | Several screen sizes in one view | Aug 2026 |
| Window Resizer | Exact window or viewport sizes | Jul 2024 |
| PerfectPixel | Laying the design over the build | Nov 2026 |
| Fake Filler | Filling forms with test data | Aug 2024 |
| Cookie-Editor | Viewing and editing cookies | Feb 2024 |
| Wappalyzer | Seeing what a site is built with | Oct 2026 |
| Detailed SEO Extension | Checking titles, canonicals and headings | Jun 2026 |
| Tampermonkey | Running your own scripts on any site | Oct 2026 |
| Jam | Bug reports with console and network logs | Nov 2026 |
| Marker.io | Bug reports sent to your issue tracker | May 2026 |
| BugHerd | Feedback pinned to the page, on a task board | Nov 2026 |
"Last updated" is what the Chrome Web Store showed on 20 November 2026. An old date isn't a red flag on its own. Web Developer and ColorZilla each do one job well and haven't needed much change.
Framework devtools
If you write React, Vue or Angular, the official devtools extension is the first thing to install. Each one adds tabs to Chrome DevTools that understand your components, which the Elements panel never will.
1. React Developer Tools
Adds Components and Profiler tabs to DevTools. You can walk the component tree, read and edit props, state and hooks, and record which components re-rendered and how long each render took. It's published by Meta and open source.
It only lights up on pages running React. Profiling a production build needs React's profiling build, so most people profile in development.
2. Vue.js devtools
The same idea for Vue: inspect components and their state, Pinia stores, routes and a timeline of events. It's maintained by the Vue team and open source.
3. Angular DevTools
The official Angular extension shows the component tree with each component's inputs and properties, plus a profiler for change detection. It only works on apps running in development mode, so it won't help you poke at someone else's production site.
4. Redux DevTools
If your state lives in Redux or Redux Toolkit, this shows every action with the state before and after it, and lets you step backward and forward through them. Other state tools speak its protocol too, such as NgRx and Zustand's devtools middleware.
Inspecting and editing pages
5. Web Developer
Chris Pederick's toolbar is one of the oldest developer extensions around, first on Firefox and then on Chrome, and it's still the fastest way to do dozens of small checks. Disable JavaScript or CSS, outline block elements, show image sizes and alt text, view form details or resize the window. Each one is a click instead of a trip through DevTools.
6. VisBug
A design tool from Google Chrome Labs that lets you click any element and move it, change its spacing, edit its text or swap an image, right on the live page. It's great for trying a layout change with a designer before anyone touches code. Nothing is saved: reload and the page is back to normal.
It's open source, and its last update was in November 2024, so think of it as finished rather than actively developed.
7. CSS Peeper
Click an element and CSS Peeper shows its styles in a clean panel: colors, fonts, spacing and dimensions, plus the colors and assets the whole page uses. It's handy when you want a component's styles without digging through the Styles pane, or when you're helping a designer who doesn't live in DevTools.
Fonts and colors
8. WhatFont
Hover over text and WhatFont tells you the font family, size, weight, line height and color, and whether it comes from a font service like Google Fonts. It was updated in October 2026, so it's very much alive.
If you only need the font for one element, DevTools can tell you too. Select it, open the Computed tab and scroll down to Rendered Fonts.
9. ColorZilla
An eyedropper for any pixel on the page, a color history, a palette of every color a page uses and a CSS gradient generator. DevTools has its own color picker in the Styles pane, but ColorZilla's page palette is still the quickest way to see which colors a site actually uses.
Network requests and APIs
10. Requestly
Requestly lets you set rules for the requests a page makes. Redirect a production script to your local build, add or change headers, mock an API response, or slow a request down to test a loading state. It's open source, and when BrowserStack bought it in May 2025 it said Requestly would stay free and open source.
It's also the natural replacement for ModHeader, which was pulled from the store in July 2026 (more on that below). For a quick one-off, DevTools' local overrides can change a response's headers and content too.
Accessibility and performance
11. axe DevTools
Deque's extension runs automated accessibility checks in a DevTools tab and explains each issue with the element, the rule it breaks and how to fix it. The free version covers the automated scan, and guided tests and team features are part of the paid Pro plan.
Automated tools catch a share of accessibility problems, not all of them, so treat a clean result as a starting point rather than a pass.
12. WAVE Evaluation Tool
WebAIM's WAVE draws its findings onto the page itself, with icons next to missing alt text, empty links, low contrast and heading problems. It's free, and a marked-up page is often easier to show a designer or a client than a list of rule IDs.
13. Lighthouse
Lighthouse audits performance, accessibility, SEO and best practices. The same engine is built into DevTools as the Lighthouse panel, so the extension is a shortcut more than a new capability. Use whichever you'll actually remember to run.
Responsive layouts
14. Responsive Viewer
Shows your page at several screen sizes in one view, so you can see every breakpoint at once instead of resizing back and forth. DevTools' device mode does one size at a time.
15. Window Resizer
Resizes the browser window, or just the viewport, to exact presets like 1366×768 or 1920×1080, with keyboard shortcuts for the ones you use most. Useful for consistent screenshots, or for checking a breakpoint in a real window rather than in device mode.
16. PerfectPixel
Lays a semi-transparent image of the design over the live page, so you can line up the build with the mockup. You can scale, move and center the overlay, and the free tier gives you two layers at a time. Paid plans add more.
Test data and cookies
17. Fake Filler
Fills every field in a form with plausible fake data in one click, which beats typing test@test.com for the hundredth time. Like any form filler, it can see what's typed on the pages it runs on, and its store listing says it handles personal and login information. Keep it in a development profile.
18. Cookie-Editor
View, add, edit, delete, import and export the cookies for the site you're on. It's open source, and it's what we'd use now that EditThisCookie is gone. For a quick look, DevTools' Application panel lists cookies too, and you can edit them there.
What a site is built with
19. Wappalyzer
Shows the technologies behind any site you visit: the CMS, frameworks, analytics, hosting and more. The extension is free. Wappalyzer's paid plans are for bulk lookups, lead lists and its API.
20. Detailed SEO Extension
One click shows the SEO basics of the page you're on: the title and meta description, canonical, robots directives, heading outline, links, images and structured data. It's free, and it catches the mistakes that slip into a deploy, like a leftover staging noindex or a canonical pointing at the wrong page.
Scripts
21. Tampermonkey
A userscript manager. Write a few lines of JavaScript and run them on any site you choose, to fix an annoyance, add a button or automate a check. On Chrome 138 and later, scripts only run after you turn on "Allow User Scripts" in the extension's details page: right-click the icon and choose Manage extension.
Bug reports and feedback
22. Jam
Click once and Jam captures a screenshot or recording of the bug together with the console logs, network requests, user actions and device details, then gives you a link to paste into a ticket. For developers reporting to other developers, it removes the "which browser were you on?" round trip.
23. Marker.io
Marker.io's extension lets a reviewer report a bug with a screenshot and technical details, and sends it into Jira or another issue tracker. Marker.io runs from a snippet on the site, a WordPress plugin, or this extension installed by each reviewer. Plans start at $39 a month after a 15-day trial.
24. BugHerd
BugHerd pins feedback to the element it's about and puts each item on a Kanban board. It runs from a script on the site or from this extension. Plans start at $50 a month, with a free trial.
A note on Huddlekit, and on extensions for clients
We said up front we'd be straight about this. Huddlekit isn't an extension, so it isn't one of the 24. It's website feedback by URL, with nothing to install and no extension for reviewers.
That's a different job from the extensions above, not a better one. If you're a developer filing a bug for another developer, an extension like Jam is the shortest path. The calculation changes when the person giving feedback is a client: every install you ask a reviewer for is one more step before their first comment. We compared both kinds, extension and link based, in our guide to visual feedback tools.
Extensions to remove or replace in 2026
Several extensions that still appear in "best of" lists no longer exist in the Chrome Web Store. If you have one installed, here's what happened and what to use instead.
- uBlock Origin. It was built on the old extension platform, so Chrome switched it off, and it's no longer in the store. Its developer makes uBlock Origin Lite, which runs on current Chrome with fewer advanced features. Some of your users block ads, so it's still worth testing your site with one turned on now and then.
- ModHeader. Google and Microsoft pulled it from their stores in July 2026 after security researchers found hidden data-collection code in an update. Uninstall it if Chrome hasn't already. Requestly does the same job, and DevTools' local overrides can change response headers too.
- EditThisCookie. Removed from the store in 2024, and a copycat using its name was later reported for stealing data. Use Cookie-Editor or the Application panel in DevTools.
- Web Vitals. Google ended support for its Web Vitals extension in January 2025 and moved its features into the DevTools Performance panel, which shows live Core Web Vitals for the page you're on.
- Check My Links. The original listing is gone. A different publisher now lists an extension under the same name, which may be fine, but it isn't the one older guides recommend. It's a good reminder to check who publishes an extension before you install it.
What Chrome DevTools now does without an extension
A lot of jobs that used to need an extension are now built in. Before you install something, check whether DevTools already does it:
- Audits. The Lighthouse panel runs the same audits as the Lighthouse extension.
- Core Web Vitals. The Performance panel shows live LCP, CLS and INP as you use the page, and can compare them with real-user data from Chrome's UX Report.
- Responsive testing. Device mode (the phone and tablet icon) emulates screen sizes, touch and network speed, one size at a time.
- Fonts. Select an element, open Computed and scroll to Rendered Fonts to see the font that actually drew the text.
- Colors. Click any color swatch in the Styles pane for a picker with an eyedropper and a contrast ratio.
- Cookies and storage. The Application panel lists cookies, local storage and more, and lets you edit them.
- JSON. The Network panel's Preview tab shows any JSON response as a collapsible tree.
- Overrides. Local overrides let you change a response's content or headers and keep the change across reloads.
- CSS. The CSS overview panel summarizes the colors, fonts and media queries a page uses. We wrote more about this in how to inspect CSS for faster website QA.
How to vet an extension before you install it
Extensions can read and change the pages you visit, and developers spend their days in admin panels, staging sites and dashboards. ModHeader and EditThisCookie are reminders that a trusted extension can change hands or change behavior. A few habits help:
- Check the publisher. The listing links to the developer's website. Make sure it's the project you meant, not a lookalike with the same name.
- Read the permissions. "Read and change all your data on all websites" is normal for some tools, like a header editor. It's a lot for a color picker.
- Look at the last update and the recent reviews. An old date is fine for a simple tool. A sudden run of one-star reviews about ads or redirects is not.
- Use a separate Chrome profile for development. Keep your dev extensions away from the profile you use for email and banking.
- Remove what you don't use. Fewer extensions means fewer things that can go wrong, and a faster browser.
Extensions, add-ons and plugins: what's the difference?
People search for Chrome add-ons, plugins and extensions as if they were different things, but in Chrome they're all extensions now. "Add-on" is Firefox's word, and Microsoft calls its store Edge Add-ons. Chrome's old plugin system, which ran things like Flash, was removed years ago, and Flash itself was retired at the start of 2021.
So when a guide tells you to install a Chrome plugin or add-on, it means an extension from the Chrome Web Store.
Frequently asked questions
Which Chrome extensions does a web developer actually need?
Fewer than most lists suggest. Start with the devtools for your framework, then add one tool for each job you do every week: an accessibility checker like axe DevTools, Requestly if you work with APIs, and something for layouts like Responsive Viewer. DevTools covers a lot of the rest.
Are Chrome extensions safe for development work?
Mostly, if you're picky. Install from the Chrome Web Store, check the publisher, keep dev extensions in their own Chrome profile and remove anything you stop using. Extensions that can read every page you visit deserve the most scrutiny.
Do these extensions work in Edge, Brave and other Chromium browsers?
Most do. Chromium browsers like Microsoft Edge and Brave can install extensions from the Chrome Web Store, although Edge asks you to allow extensions from other stores first.
How did you choose these?
We started from the extensions developers recommend most, dropped the ones that are gone or have had security problems, and checked every remaining listing in the Chrome Web Store on 20 November 2026. We don't make a Chrome extension, and nobody paid to be on this list.
The short version
Start with DevTools. Add the handful of extensions your stack and your week actually need. Then open chrome://extensions every few months and remove what you haven't touched.
The best extension list is a short one.



