Chrome Extension

Design-to-Build QA
for Figma + Chrome

Catch every pixel that drifted from the design — before your client does.

Free forever · No sign-up · Works on any live or staging URL

  • Click any element — instantly finds the Figma match
  • Compares padding, color, typography, radius and more
  • Pass/fail report — export to HTML in one click
  • No Figma plugin — works on any live build

Stop eyeballing design QA.
Measure it.

Visual-overlay tools let you squint at two layers. QAPixel reads the real values from both the design and the DOM and tells you exactly what's off — down to the pixel and the font weight.

Element-first matching

Click the button or card on your page and QAPixel ranks the Figma layers that match by text and size — no hunting through an unlabeled layer tree.

Property-level report

Padding, color, border-radius, opacity, font-size, weight, line-height and letter-spacing — each row is green (ok), magenta (fail) or amber (warning).

Export & attach to tickets

One click writes a standalone HTML report you can save or drop straight into a bug ticket. Every pairing is saved per page URL for re-audits.

No Figma plugin

Runs in Chrome and reads your design through the Figma API with a read-only token. Works on any live, staging, or local build.

Re-audit on every deploy

Pairings persist per URL. After a deploy, hit “Re-audit all” and QAPixel re-checks every element against the live DOM instantly.

🛈

Honest about limits

Rate-limit aware with a 15-minute Figma cache, and it flags where a comparison can only be approximate rather than pretending it's exact.

A full audit in under a minute

Load a Figma frame, pick an element, confirm the matched layer, read the report.

Trouble playing here? Watch the demo on YouTube →

Four steps, zero setup in Figma

1

Load a frame

Paste a Figma frame's “Copy link to selection” URL into the panel.

2

Pick an element

Click the button or card on your live page you want to check.

3

Confirm the layer

QAPixel suggests the best-matching Figma layer — click to pair.

4

Read & export

Get a pass/fail table and export it as an HTML report.

Start free. Upgrade when it earns its keep.

Free

$0
  • Full spec comparison engine
  • 1 pairing per page
  • Element-first smart matching
  • Export report
  • Unlimited pairings
Download free

Pro PRO

One-time · see price on Gumroad
  • Everything in Free
  • Unlimited pairings
  • One-click HTML report export
  • Re-audit all on every deploy
  • Priority email support
Get Pro on Gumroad →

Install QAPixel Free

Download the extension, load it unpacked in Chrome, and start auditing. Upgrade to Pro anytime by pasting a license key — no reinstall.

Chrome → chrome://extensions → Developer mode → Load unpacked → select the unzipped folder.

Questions, answered

Does QAPixel need a Figma plugin?
No. QAPixel runs entirely in Chrome and reads your design through the Figma API using a read-only personal access token. Nothing is installed in Figma, and it works on any live, staging, or local build.
What exactly does it compare?
Reliably (as pass/fail): padding, background & text color, border color and width, border-radius, opacity, font-size, font-weight, line-height and letter-spacing. As softer warnings: width, height, font-family and box-shadow, since those can differ legitimately with real content and responsive layout.
Is my Figma token safe?
Your token is stored locally in your browser and sent only to api.figma.com. We recommend a token scoped to “File content: Read-only.” QAPixel has no server and never sees your token or your designs.
What's the difference between Free and Pro?
Free allows one pairing per page and no export — enough to try the full comparison engine. Pro unlocks unlimited pairings and one-click HTML export. Pro is a license key purchased on Gumroad and pasted into the extension's Options; the same install upgrades in place.
How do I activate Pro?
Buy on Gumroad, then right-click the QAPixel icon → Options, paste your license key, and click Activate. The badge flips to PRO and everything unlocks. A refund or chargeback automatically returns the extension to Free.
I get a “Too Many Requests” (HTTP 429) error — what's wrong?
That error comes from Figma's API, not from QAPixel. Figma rate-limits requests per account, and how many you get depends on your Figma plan/subscription level. To minimise calls, QAPixel caches each fetched frame for about 15 minutes — reloading the same frame while you iterate costs zero API calls — and while a 429 is active it stops calling Figma and serves the cached copy, because retrying during a lockout only extends it. If you hit a 429, simply wait for the countdown shown in the panel to clear. Please note: QAPixel is an independent tool and is not affiliated with, endorsed by, or sponsored by Figma, Inc. — “Figma” is a trademark of its respective owner.

QAPixel is an independent product by BS WebPortali and is not affiliated with, endorsed by, or sponsored by Figma, Inc. or Google LLC. “Figma” and “Chrome” are trademarks of their respective owners.