Lost Pixel, the open-source visual regression engine with a hosted review platform, is being sunset: its team announced in April 2026 that they are joining Figma. If your pull requests still run the Lost Pixel GitHub Action, it is time to choose where your screenshots, baselines and approvals go next.
The closest like-for-like replacement is another visual testing tool, and the best one depends on what you fed Lost Pixel. Argos is the nearest match for an open-source, bring-your-own-screenshots setup. Chromatic suits Storybook-first teams. Percy, Happo and Applitools cover broader browser or platform needs, and Meticulous replaces written tests with recorded sessions. Design Bug Bot, from 21st, is not a pixel-regression replacement; the last section explains the narrower gap it covers.
Disclosure: This guide is published by 21st, which makes Design Bug Bot. It is based on each product's official pages, checked on September 14, 2026. We have not benchmarked these tools against each other, and the order below is not a ranking.
What happened to Lost Pixel
On April 22, 2026, the co-founders published The Lost Pixel Team Is Joining Figma. The post states it plainly: "We're sunsetting Lost Pixel." The team will work on the next generation of developer tools at Figma.
The post gives no shutdown date, no timeline for the hosted platform, and no migration or data-export instructions. As of September 14, 2026, the pricing page still lists plans beneath a sunsetting notice. With no deadline to plan against, moving on your own schedule beats waiting for one.
The lost-pixel repository was archived by its owner the same day and is read-only. The code remains available under the MIT license, but an archived repository takes no new commits, so the engine and the GitHub Action it provides will not receive upstream fixes.
Lost Pixel alternatives at a glance
| Tool | How your UI gets captured | Closest fit for Lost Pixel users |
|---|---|---|
| Argos | Screenshots from your own Playwright, Cypress, Vitest, Storybook, WebdriverIO or Puppeteer runs, or a CLI upload | Custom shots and page shots; teams that want to stay open source |
| Chromatic | Cloud-rendered snapshots from Storybook, plus archives from Vitest, Playwright and Cypress tests | Storybook shots |
| Percy | The SDK captures DOM and assets; Percy re-renders them across browsers and widths | One capture checked in several browsers and widths |
| Happo | Storybook, Cypress, Playwright or a custom integration, across Chrome, Firefox, Safari and Edge | Component libraries that need wide browser coverage |
| Applitools Eyes | Visual AI checkpoints from test SDKs, including Storybook | Programs that also test native mobile apps or documents |
| Meticulous | Recorded sessions turned into generated visual end-to-end tests | Page-shot users who would rather not maintain a page list |
What to carry over from your Lost Pixel setup
Start with lostpixel.config.ts. Its README lists five inputs, each moving differently.
- Storybook shots. Look for a native Storybook integration that supports your Storybook version.
- Ladle or Histoire shots. The integration lists we checked for Argos, Chromatic, Percy and Happo do not name Ladle or Histoire, so plan to screenshot the built explorer's story URLs with Playwright or a custom integration.
- Page shots. A list of paths maps to a URL loop in your test runner; Argos documents one for Playwright, Cypress and Puppeteer.
- Custom shots. The easiest move: pick a tool that accepts screenshots from your own Playwright or Cypress runs.
- Baselines. In open-source mode, Lost Pixel baselines are committed to your Git repository. Expect the new tool's first build to become your reference, and review it before accepting it.
Also carry over the settings that shaped your diffs: viewports, browsers, sensitivity thresholds, masked regions and flaky-test retries. Then find the lost-pixel step in your GitHub workflow and any required status check in branch protection, so pull requests do not wait on a check that no longer reports.
The alternatives in detail
Argos
Argos is the closest match to Lost Pixel's open-source model: its overview says the whole platform, comparison engine included, is MIT-licensed. SDKs for Playwright, Cypress, Vitest, Storybook, WebdriverIO and Puppeteer, plus a CLI for any other pipeline, let custom shots move with little rework. It picks baselines from your Git history rather than committed images. Argos has also published its own Lost Pixel migration guide, worth reading as a vendor's view.
Chromatic
Chromatic, from the Storybook maintainers, is the natural home if most of your config was Storybook shots. UI Tests run visual, interaction and accessibility checks on stories and can also use Vitest, Playwright and Cypress tests, though the Playwright docs note that those runs still include a build Storybook step. Budget by billed snapshot, because each browser and mode counts separately.
Percy
Percy, part of BrowserStack, captures the DOM and assets in your test browser, then re-renders each snapshot across browsers and widths in its own infrastructure. SDKs cover Storybook, Playwright, Cypress, Puppeteer, Selenium and more, and a CLI path needs no automation script. Because rendering happens outside your test suite, test authentication and asset loading during the trial.
Happo
Happo runs screenshot tests from Storybook, Cypress, Playwright or your own integration and covers Chrome, Firefox, Safari and Edge. Its pricing page includes accessibility testing on every plan and adds iOS Safari on the Pro plan. It suits component libraries where cross-browser differences matter most.
Applitools Eyes
Applitools Eyes uses Visual AI to validate interfaces and covers websites, web apps, native mobile apps and documents. Its Storybook SDK discovers stories and creates one baseline per story and environment on the first run. It fits teams whose visual testing reaches beyond a single web app.
Meticulous
Meticulous takes a different route: a recorder script on local, staging and preview environments records sessions, and Meticulous generates and maintains visual end-to-end tests from them, replaying recorded backend responses. Its setup covers Next.js, React, Vue, Angular, Nuxt and SvelteKit. Tests come from recordings rather than your config, so treat it as a change of approach, not a migration.
Free tiers to trial with
Check your recent monthly screenshot count first: Lost Pixel's pricing page lists 7,000 on its free plan. As listed on September 14, 2026, Argos pricing offers up to 5,000 screenshots a month on Hobby, Chromatic pricing 5,000 billed snapshots on Free with Chrome only, and Happo pricing 5,000 snapshots on Free with Chrome.
Where Design Bug Bot fits after the move
Design Bug Bot does not replace Lost Pixel: it keeps no approved baselines, runs no cross-browser pixel regression and does not block merges. Swap Lost Pixel for it alone and you lose the job Lost Pixel did.
What it adds is the review a baseline cannot give. A baseline answers whether a screen changed, not whether a new button duplicates the shared one or a heading sits outside your type scale. Design Bug Bot reviews changed UI code in GitHub pull requests against your repository's components, tokens, spacing and type scale, plus layout risks such as horizontal overflow and actions hidden on mobile. Findings point to the file and line when available and include suggested fix code.
When its isolated render succeeds, the review can include desktop and mobile screenshots; otherwise findings are labeled code-backed recommendations. It is advisory and React-focused, and new accounts get 5 successful reviews free (details).
Make the switch in four steps
- Inventory lostpixel.config.ts and your monthly screenshot count.
- Trial two candidates on one branch with the same inputs: Chromatic if you are Storybook-heavy, Argos if you mostly send custom or page shots.
- Review the first baseline as a design check before accepting it, because an accepted baseline can preserve an existing mistake.
- Require the new tool's status check in branch protection, then remove the Lost Pixel step and its old required check.
For deeper side-by-side pages, see Argos, Chromatic, Percy, Happo, Applitools and Meticulous compared with Design Bug Bot.
Frequently asked
- Is Lost Pixel shutting down?
- Its team announced on April 22, 2026 that they are sunsetting Lost Pixel and joining Figma. The announcement gives no shutdown date or timeline for the hosted platform, and the GitHub repository was archived the same day, which makes it read-only.
- What is the closest replacement for Lost Pixel?
- It depends on your inputs. For screenshots from your own Playwright or Cypress tests and an open-source codebase, Argos is the nearest match. For Storybook-centered setups, consider Chromatic; for wide browser coverage, Percy or Happo; for native mobile or document testing, Applitools; for tests generated from recorded sessions, Meticulous.
- Can I keep using the open-source Lost Pixel engine?
- The code remains available under the MIT license, and you can fork it. The repository is archived, though, so it takes no new commits and will not receive upstream fixes for browsers or dependencies. Forking means taking on that maintenance yourself.
- Is Design Bug Bot a Lost Pixel alternative?
- Not for pixel regression. Design Bug Bot keeps no baselines and runs no cross-browser comparisons. It reviews changed UI code in GitHub pull requests against your repository's components, tokens, spacing and type scale, so it can sit beside whichever visual testing tool replaces Lost Pixel.