Moving from Lost Pixel
Lost Pixel’s team is joining Figma, and the product is being sunset. Its open-source engine still runs from npm and Docker, so you don’t have to rewrite how you capture screenshots: keep Lost Pixel for capture and let PixelCI compare and review them.
Lost Pixel’s notice: “Lost Pixel is joining Figma. We are sunsetting the product and building what’s next.” The repository was archived on 22 April 2026.
Capture stays. Review moves.
Let Lost Pixel only capture.
In
lostpixel.config.ts, setgenerateOnly: trueand removefailOnDifference; PixelCI decides whether the job passes. If you used the Lost Pixel Platform, removelostPixelProjectIdandapiKey. Your Storybook, Ladle, Histoire and page shots, breakpoints andmaskselectors all keep working, because they apply while the screenshots are taken.Upload
.lostpixel/current.Add the PixelCI CLI after the Lost Pixel step.
# the job needs permissions: id-token: write - uses: lost-pixel/[email protected] - uses: docker://ghcr.io/zyno-io/pixelci/cli:latest env: PIXELCI_API_URL: https://pixelci.example.com PIXELCI_APP_ID: <your-app-id> PIXELCI_IMAGES_PATH: ./.lostpixel/current
Screens keep Lost Pixel’s file names:
button--primary.pngbecomes the screenbutton--primary.Using
customShots? Lost Pixel reads those straight from yourcurrentShotsPathand doesn’t copy them into.lostpixel/current. PointPIXELCI_IMAGES_PATHat that folder instead; if custom shots are all you use, you can drop the Lost Pixel step.On GitLab CI, capture in one job and keep
.lostpixel/currentas an artifact, then upload it in a job that uses the PixelCI CLI image, set up as in the GitLab setup guide. Runnpx lost-pixelin an image that has Playwright’s browsers installed;npx lost-pixel dockerneeds a Docker daemon in the job.Approve your first build.
The first build on your default branch has no baselines, so every screen shows as new. Review them once and approve; from then on PixelCI compares each branch against the right baseline.
Retire the baseline folder.
PixelCI keeps approved baselines itself, so
.lostpixel/baselineand the update-baselines pull request workflow (LOST_PIXEL_MODE=update) are no longer needed.
What maps to what
| In Lost Pixel | In PixelCI |
|---|---|
Baseline PNGs committed in .lostpixel/baseline | Approved baselines stored in PixelCI, per branch, outside Git |
LOST_PIXEL_MODE=update and the update pull request | Approve the screen in the review screen |
| Platform approve or reject per image | Approve or reject each screen, with a comment |
threshold | Comparison tolerances per app or per screen: colour, sub-pixel shift, changed pixels allowed |
mask selectors | Keep them in your Lost Pixel config; they’re applied at capture |
| Documented for GitHub Actions | GitHub Actions and GitLab CI, including self-managed GitLab |
If you used the Lost Pixel Platform
Lost Pixel hasn’t published a shutdown date or a data export for its hosted platform, so check their announcement for timing. Your current screenshots are produced in CI either way, so moving doesn’t depend on exporting anything.
Keep the capture. Move the review.
Start with one app and one build; your Lost Pixel setup stays as it is.