Add to Chrome
Compare

The 6 best CSS inspector Chrome extensions

Every one of these puts an element's styles in front of you without opening DevTools. What separates them is how much of the design they actually read — and that is where the list stops being interchangeable.

The short answer

CSS Peeper if you want colors, fonts and assets in a clean panel. VisBug if you want to edit the page as well as read it. CSSViewer if you want the smallest possible hover readout. Design Toolkit if you need the parts the others leave out — spacing between elements, hover and focus states, animation timings, and a whole section copied as code.

A CSS inspector readout over a live web page showing size, spacing, font and color
What a design readout looks like in practice: size, spacing, type and color answered in one place, on the page.

How to judge a CSS inspector

They all show you a font and a color. The differences that matter in practice:

ToolMeasures gapsHover statesMotionCode exportPrice
Design ToolkitYesYesYesCSS, Tailwind, React, plus whole sections as HTML, Vue or Elementor7-day trial, then one-time
CSS PeeperNoNoNoColors, fonts, assetsFree
VisBugYesNoNoEdits live, no exportFree, open source
CSSViewerNoNoNoNoFree
Chrome DevToolsManualForce stateAnimations panelCopy ruleFree, built in
Screen RulerYesPartlyNoCSS, TailwindFree tier, paid tiers

1. Design Toolkit

Design Toolkit Ours

Chrome, Edge, Brave, Opera, Arc, Vivaldi · 7-day free trial, then one payment

Built for the question a designer actually asks, which is rarely "what is this element's padding" and usually "why does mine not look like that". It reads the box model, the layout, the type with its real rendered font, the colors with their contrast ratio, and — the part that separates it — the distance between any two elements, the hover and focus changes with the timing that carries them, and the animations, including ones created in JavaScript, with their keyframes.

  • Hover anything for size, spacing, type, color and contrast; click to pin and compare two elements
  • Click two elements for the exact gap, the way you would in Figma
  • Reads hover, focus-visible and active states, with the transition that runs them
  • Reads motion: durations, easing curves, keyframes, and JavaScript animations
  • Exports an element as CSS, Tailwind classes or a React style object
  • Copies a whole section as exact code — Tailwind, HTML, React, Vue or Elementor — to paste into ChatGPT, Claude, Gemini or Cursor
  • Pulls the colors out of any image, video frame or canvas, and copies them for Figma
  • Responsive mode with several screens side by side, a page audit, an eyedropper and asset downloads

Weak spot: it is not free after the trial, and it is deliberately not a live editor — it reads and measures, it does not let you drag things around the page.

2. CSS Peeper

CSS Peeper

Chrome · Free

The designer-first inspector, and the one most people meet first. It shows a clean panel of the styles that matter to a designer — colors, typography, border radius — instead of the cascade mess, and it collects the page's color palette and downloadable assets in one place.

  • Clean panel: font, size, color, radius, without the code
  • Page-wide color palette and asset list
  • Genuinely free

Weak spot: it reads one element at a time and nothing about relationships between them — no distance measurement, no states, no motion.

3. VisBug

VisBug

Chrome · Free, open source

Different in kind from the rest: an open-source design-tools overlay from Google that lets you edit a live page the way you would edit a design file. Move padding, change text, swap colors, drag things around — all on top of someone else's site, all thrown away on refresh.

  • Edit a live page visually: spacing, type, color, position
  • Inspect and measure while you are in there
  • Free and open source

Weak spot: it is a sandbox, not a reader. There is no export, and nothing survives a reload. Reach for it to try an idea, not to record one.

4. CSSViewer

CSSViewer

Chrome · Free

The oldest idea on this list and still the simplest: click the toolbar icon, hover anything, read its CSS properties in a small floating box. No panel, no settings, no account.

  • Instant hover readout of the main CSS properties
  • Tiny and fast

Weak spot: it shows properties, not answers. No measurement, no copy, no states, and a readout that has not really changed in a decade.

5. Chrome DevTools

Chrome DevTools

Every Chromium browser · Free, already installed

Worth naming, because for some jobs nothing beats it. DevTools is the only tool here that tells you why a value is what it is: which rule won, what it overrode, where the specificity went wrong. It can force :hover on an element, and its Animations panel can slow a transition down and scrub through it.

  • The full cascade, with the rules that lost
  • Force element state to inspect hover and focus
  • Animations panel for slowing down and inspecting motion
  • Computed tab shows resolved values including the rendered font

Weak spot: it is built for debugging, not for reading a design. Half your screen goes to a panel, the answer is spread across three tabs, and measuring the distance between two elements means doing arithmetic on two bounding boxes.

6. Screen Ruler

Screen Ruler

Chrome · Free tier, paid tiers

The closest thing to a direct competitor for us, and a capable one. It measures, inspects, reads CSS, and its paid tier adds live editing and an MCP bridge for coding agents.

  • Measurement and element inspection
  • CSS and Tailwind output
  • Live editing and an agent bridge on the paid tiers

Weak spot: no animation inspection — durations, easing and keyframes are not part of what it reads. Its Chrome Web Store listing also discloses collecting personally identifiable information, user activity and website content, which is worth reading before you install anything that sees every page you visit.

Which one to install

Read a design, not a stylesheet

Size, spacing, type, color, contrast, states and motion — in one readout, on any page. Free for 7 days.

Add to Chrome

No accountRuns locally14-day refund

Common questions

Why use an extension when DevTools is already built in?

DevTools is a debugging tool: it answers one property at a time and takes half your screen. An inspector extension answers the design question — size, spacing, type, color, hover — in one readout while you stay on the page. Use DevTools when you need to know why a rule won; use an extension when you need to read a design.

Do these extensions work on any website?

On ordinary pages, yes. All of them are blocked on browser pages such as the Chrome Web Store and settings, because Chrome does not allow extensions to run there. A stylesheet served from another domain without CORS headers cannot be read as source by any of them either, though computed values still work.

Which one gives me code I can paste?

CSS Peeper and Design Toolkit both export. What differs is the scope: CSS Peeper is built around colors, fonts and assets; Design Toolkit exports the box model, layout, type and effects as CSS, Tailwind or a style object, and can copy a whole section as Tailwind, HTML, React, Vue or Elementor. How to copy a section as code.

Can any of them read an animation?

Most read static styles only. DevTools has an Animations panel for inspecting one by hand. Reading motion properly means reporting the transition properties, durations and easing curves, the animations that are running including ones created in JavaScript, and the keyframes behind them — a different job from reading a computed style. How to copy an animation from a website walks through it.

Read next