Skip to content
install

TWO BUILDS9 browsers

Chromelisting in reviewFirefoxlisting in reviewBravelisting in reviewOperalisting in reviewEdgelisting in review4 moreChromium browsers: Arc, Vivaldi, Chromium, Opera GXthe Chrome build

comparison · LoupeKit vs ColorZilla

LoupeKit vs ColorZilla: which one should you install?

ColorZilla has been the answer to "what colour is that" for longer than most of this category has existed - four million users, free, on both Chrome and Firefox, with a Photoshop-style picker, a colour history, stored palettes and the CSS gradient generator half the web has used at some point. Both extensions pick from anywhere on screen; the difference is what happens to the colour afterwards.

Picking one colour: ColorZilla. Taking the whole palette out as tokens: LoupeKit. Both are free to try and they do not conflict.

ColorZilla

Free · 4M+ users · Chromium and Firefox

An eyedropper and a set of colour tools around it: pick any pixel on the page or beyond it, an advanced picker, a page colour analyser that locates the elements using a colour, seven bundled palettes, a history of what you have picked, and a gradient generator that outputs CSS.

LoupeKit

Free tier · nine surfaces · Chromium and Firefox

Colour as part of a reading rather than as the product: the palette as painted rather than as declared, each swatch with its contrast against the first opaque ancestor behind it, a contrast checker with suggested fixes, a vision simulator, and the palette exportable as a theme or token file.

section#matrix

Feature by feature

CAPABILITY
ColorZilla
LoupeKit
Eyedropper on the page
Picking outside the browser window
Colour history and stored palettes
CSS gradient generator
Editing a gradient the page already has
Palette read from what is painted
-
Contrast against the real backdrop
-
Colour-vision simulation
-
Palette export as theme or tokens
-
Technology detection
-
section#gaps

Where LoupeKit stops, and why

Editing a gradient the page already has
The gradient tool composes a new one from the colours the page paints most, and every live edit LoupeKit makes is DOM-only and undoable - nothing it changes survives a reload. Editing the page’s own gradient in place would be the first edit that had to be written back.
section#jobs

The same jobs, side by side

Pick a colour from anywhere on screen

COLORZILLA Including outside the browser window, on both browsers.

LOUPEKIT Also outside the window, through the browser’s own screen-wide eyedropper - which Firefox does not yet have, so there it is the page only.

Get the page’s palette

COLORZILLA The analyser lists DOM element colours and finds what uses them.

LOUPEKIT The palette as painted, each swatch carrying its contrast and where it is used.

Check a pair for contrast

COLORZILLA Not its job.

LOUPEKIT Against the first opaque ancestor, with suggested passing values.

Build a CSS gradient

COLORZILLA Its gradient generator, which is a small institution.

LOUPEKIT A builder seeded from the two colours the page paints most, up to six stops, copied as CSS or as a Tailwind class - but it cannot take an existing gradient apart.

See the page as a colour-blind visitor

COLORZILLA Not offered.

LOUPEKIT A vision simulator across the common deficiencies.

Take the palette away as a file

COLORZILLA Copy values one at a time.

LOUPEKIT A Tailwind theme, a CSS custom-property sheet or a W3C token file.

Pick ColorZilla if

If picking is the job and you want the tools built around it. We have the history, the stored palettes and a gradient generator now, and theirs are older and deeper - the gradient editor in particular takes an existing CSS gradient apart, which ours does not. It is also free, it is on Firefox with its screen-wide picking intact where ours falls back to the page, and it has been dependable for well over a decade.

Pick LoupeKit if

If the colour question is about the page rather than about a pixel: what the palette actually is once everything is painted, whether those pairs pass contrast, what they look like to somebody who sees colour differently, and getting the set out as a file.

Run both

The common arrangement, and free on both sides. Pick with one, judge the palette with the other.

Add LoupeKit- opens the list of browsers it can be installed in

TWO BUILDS9 browsers

Chromelisting in reviewFirefoxlisting in reviewBravelisting in reviewOperalisting in reviewEdgelisting in review4 moreChromium browsers: Arc, Vivaldi, Chromium, Opera GXthe Chrome build
free to read · no sign-up · both extensions can be installed side by side

CHECKED 17 AUGUST 2026

Every figure about ColorZilla on this page was checked on that day against its Chrome Web Store and Firefox add-on listings, and colorzilla.com, and nothing here is quoted from a review. Where a fact is not published anywhere we can point at, the table says so rather than estimating it. Products change; if something above is out of date, write to [email protected] and it will be corrected.

ColorZilla and every other product name on this site are the trademarks of their own owners. LoupeKit is not affiliated with, endorsed by or sponsored by any of them.