Free
Watch one site, weekly.
$0forever
Start free
- 1 site
- 5 pages per site
- Weekly scans
- Desktop capture
- 100 captures a month
- 1 schedule per site
- 7 days of history
- Email alerts
Visual regression monitoring for Webflow
Pixelsitter re-captures every page you watch, compares it against the last version you approved, and emails you the moment the layout shifts — with the picture attached. You find out on a Tuesday morning. Not from your client, on a Friday afternoon.
Free forever for one site. No card, no CI pipeline, no Webflow API keys.
Drag to compare
Baseline · Tuesday 09:00 New capture · today 09:00
The gap
They confirm the page returned 200. They can't see that the hero lost its padding, that a pricing card now wraps to two lines, or that the logo is 400px wide on a phone. Webflow gives you no staging diff and no visual publish history, so the first person to notice is whoever loves the site least.
A client pastes a fuller product name. The card grows, the grid falls out of line, and every collection item under it slides down the page.
Someone tidies up in the Designer. A section loses its padding on publish — and only at tablet width, which nobody thinks to open.
A 4:3 photo drops into a 16:9 slot. Desktop looks fine. The phone version has been broken since the shoot.
How it works
01
Paste the address and drop one TXT record into the domain's DNS. Pixelsitter re-checks every 15 minutes and starts the moment it lands. No Webflow login, no API key, no crawler you have to whitelist.
02
Desktop at 1440×900, plus tablet 768×1024 and mobile 390×844 from Agency up. Hourly, daily or weekly — or the second Webflow fires its publish webhook, so a scan lands before your client refreshes.
03
Every capture is compared to the last one you signed off on, pixel by pixel. Anti-aliasing and font-rendering noise are filtered out first, and anything under 0.5% of the page never reaches you. Quiet is the default state.
04
A thumbnail, the percentage that changed, and a link straight to the before/after. Two buttons wait for you there: approve it as the new baseline, or flag it as broken. Slack instead of email, if that's where you live.
The report
Not a pixel-diff dashboard. A run is five numbers and a stack of before/afters, each one waiting on a yes or a no. This is the whole interface.
Fernwood Coffee · Nightly · today 09:00 · 41.6s
Summary
12
Pages scanned2
Changed10
Unchanged0
First captures1.57%
Largest diffHomepage
Changed/ · 1440×900 · 1.57% of pixels changed
Pricing
One site is free forever, so you can watch something that matters before you decide.
Watch one site, weekly.
$0forever
Start free
For a freelancer with a handful of client sites.
$19/month
Start free, upgrade later
Every client site, every breakpoint, scanned on publish.
$59/month
Start free, upgrade later
Hourly scans, unlimited pages, your logo on the report.
$149/month
Start free, upgrade later
One capture is one page at one breakpoint in one run. Quotas reset on the first of the month. Cards, invoices and cancellation live in the Stripe portal.
Questions
No. It works on the published site. You add one TXT record to the domain's DNS to prove it's yours, and that's the only access it needs. Connecting Webflow's publish webhook is optional — it changes when a scan runs, not what Pixelsitter can see.
Only if more than half a percent of the page's pixels move. Anti-aliasing and font-rendering noise are filtered out before anything is counted, so a page that renders a hair differently today stays quiet.
Yes — it captures published URLs, so anything you can open in a browser can be watched. It's built for Webflow because that's where the problem is worst: clients edit the CMS, there's no staging diff, and no visual publish history.
Nothing gets deleted. Sites past your new limit go dormant — the oldest ones keep scanning — and they start again when you upgrade or remove one.
In the Stripe portal, any time. You keep the plan until the period you've already paid for ends, then drop to Free with every site and baseline intact.
On Studio, yes — your logo instead of ours, so a maintenance retainer looks like your work rather than a tool you resell.
Add a URL, approve the first capture, and go back to work. The next time something moves, you'll be the one who noticed.