Branch-aware baselines
Each build is checked against its branch’s last approved build as well as the default branch, so screens you already approved on a branch pass straight through.
PixelCI compares every screenshot your CI takes against the right baseline and asks a person only about what actually changed. Approve a change on one branch and every other branch already knows.
PixelCI Cloud is in early access. The self-hosted edition is available now and free for internal use.
A working copy of the review screen. Scroll the list, approve or reject each screen, leave a comment, then submit. The keyboard works too: J K A R, and hold D to flash the diff (Shift+click a screenshot toggles it).
Playwright, Cypress, Storybook, a shell script: anything that writes PNGs. PixelCI doesn’t run browsers for you, so it never disagrees with the ones you already trust.
Add the PixelCI step to GitHub Actions or GitLab CI. It authenticates with the CI job’s own identity, so there is no API key to store or rotate.
Each screen is compared with the last approved build on its branch, then the default branch, and checked against changes already approved elsewhere. Differences under your threshold are ignored.
If something changed, the job fails with a link to the build. Approve it and PixelCI re-runs the job and sends you back to the pipeline.
# .github/workflows/ci.yml (permissions: id-token: write) - uses: docker://ghcr.io/zyno-io/pixelci/cli:latest env: PIXELCI_API_URL: https://app.pixelci.dev PIXELCI_APP_ID: 019a1f3c-8d2e-7b41-9f60-2c5e8a7d4b13 PIXELCI_IMAGES_PATH: ./screenshots
# .gitlab-ci.yml (signs in with CI_JOB_TOKEN) visual-regression: image: ghcr.io/zyno-io/pixelci/cli:latest variables: PIXELCI_API_URL: https://app.pixelci.dev PIXELCI_APP_ID: 019a1f3c-8d2e-7b41-9f60-2c5e8a7d4b13 PIXELCI_IMAGES_PATH: ./screenshots script: - pixelci
Creating build... Build 019a7c3e-4f21-7b8d-9c2e-5a1f0d3b6e47 created. Uploading screen "checkout"... Screen "checkout" uploaded. Uploading screen "product-card"... Screen "product-card" uploaded. Uploading screen "site-header"... Screen "site-header" uploaded. Finalizing build... Checking build status... Build is still processing. Checking build status... Build status: needs review See details at: https://app.pixelci.dev/apps/019a1f3c-8d2e-7b41-9f60-2c5e8a7d4b13/builds/019a7c3e-4f21-7b8d-9c2e-5a1f0d3b6e47 Error: Visual changes require review. (status: needs review). See https://app.pixelci.dev/apps/019a1f3c-8d2e-7b41-9f60-2c5e8a7d4b13/builds/019a7c3e-4f21-7b8d-9c2e-5a1f0d3b6e47 Visual changes require review. Error: Process completed with exit code 1.
Creating build... Another job uploaded this commit's screenshots; waiting for its result. Build status: changes approved See details at: https://app.pixelci.dev/apps/019a1f3c-8d2e-7b41-9f60-2c5e8a7d4b13/builds/019a7c3e-4f21-7b8d-9c2e-5a1f0d3b6e47 Visual changes were approved.
Creating build... Build 019a7c52-0b9e-7d13-8e4a-61c7f2a9d035 created. Uploading screen "checkout"... Screen "checkout" uploaded. Uploading screen "product-card"... Screen "product-card" uploaded. Uploading screen "site-header"... Screen "site-header" uploaded. Finalizing build... Checking build status... Build is still processing. Checking build status... Build status: no changes See details at: https://app.pixelci.dev/apps/019a1f3c-8d2e-7b41-9f60-2c5e8a7d4b13/builds/019a7c52-0b9e-7d13-8e4a-61c7f2a9d035 No visual changes.
$ pixelci Creating build... Build 019a7c3e-4f21-7b8d-9c2e-5a1f0d3b6e47 created. Uploading screen "checkout"... Screen "checkout" uploaded. Uploading screen "product-card"... Screen "product-card" uploaded. Uploading screen "site-header"... Screen "site-header" uploaded. Finalizing build... Checking build status... Build is still processing. Checking build status... Build status: needs review See details at: https://app.pixelci.dev/apps/019a1f3c-8d2e-7b41-9f60-2c5e8a7d4b13/builds/019a7c3e-4f21-7b8d-9c2e-5a1f0d3b6e47 Visual changes require review. Cleaning up project directory and file based variables ERROR: Job failed: exit code 1
$ pixelci Creating build... Another job uploaded this commit's screenshots; waiting for its result. Build status: changes approved See details at: https://app.pixelci.dev/apps/019a1f3c-8d2e-7b41-9f60-2c5e8a7d4b13/builds/019a7c3e-4f21-7b8d-9c2e-5a1f0d3b6e47 Visual changes were approved. Cleaning up project directory and file based variables Job succeeded
$ pixelci Creating build... Build 019a7c52-0b9e-7d13-8e4a-61c7f2a9d035 created. Uploading screen "checkout"... Screen "checkout" uploaded. Uploading screen "product-card"... Screen "product-card" uploaded. Uploading screen "site-header"... Screen "site-header" uploaded. Finalizing build... Checking build status... Build is still processing. Checking build status... Build status: no changes See details at: https://app.pixelci.dev/apps/019a1f3c-8d2e-7b41-9f60-2c5e8a7d4b13/builds/019a7c52-0b9e-7d13-8e4a-61c7f2a9d035 No visual changes. Cleaning up project directory and file based variables Job succeeded
Something changed. The job fails and links to the build for review.
After a reviewer approves, PixelCI re-runs the job. The commit already has a build, so nothing is uploaded again.
Every screen matches its baseline, so the job passes without anyone looking.
A new button shouldn’t need approving on every branch that carries it, and again after the merge. PixelCI remembers what was approved, pixel for pixel, and recognises it wherever it turns up next.
The result is one review per change instead of one per branch, and a main branch that goes green on merge.
7be20d14 · You review itDraftProcessingNeeds ReviewChanges Approved3c91fa02 · Same pixels, already approvedDraftProcessingNeeds ReviewChanges Approvede04d6b29 · Merged. Nothing to re-reviewDraftProcessingNeeds ReviewChanges ApprovedEach build is checked against its branch’s last approved build as well as the default branch, so screens you already approved on a branch pass straight through.
Approving a build re-runs the failed job and takes you to the pipeline. Nobody hunts for a retry button.
GitHub, GitLab.com and your own GitLab instance, including on Free. You don’t need an enterprise contract to use your own GitLab.
Designers, QA and product leads review for free. You pay for screenshots, never for the people who check them.
Screenshots are stored losslessly and compared pixel by pixel. A sub-pixel shift tolerance and a changed-pixel threshold keep anti-aliasing noise out of your reviews.
J and K step through screens, A and R approve or reject, and holding D flashes the diff. Reviewers can work through a whole build from the keyboard.
Reviewers can leave a comment with every approval or rejection. PixelCI’s MCP server lets Claude and other MCP clients read builds, decisions, those comments and the diff images, so the assistant fixing a red build knows what the reviewer asked for.
list_apps, list_builds, get_build and get_screen_image/api/mcp: nothing to install or runWhy did the visual job fail on feat/checkout-redesign?
list_appslist_buildsStorefrontget_buildfeat/checkout-redesign · a1f9c3e0get_screen_imagecheckout · kind=diffThe reviewer rejected checkout. product-card is new and was approved.
Free shipping is right, but the button lost its dark fill. Keep it like the other CTAs.
The diff marks three changes in the order summary: the shipping line, the total and the Place order button. Want me to put the button’s dark fill back?
We run it, scale the diff workers and keep the history. You add one CI step.
One Docker image on your own infrastructure. Screenshots never leave it.
Unlimited seats on every plan. Early-access plans: limits and prices may change before launch.Compare plans
Tell us about your pipeline and we’ll get you into the early-access cloud, or help you run it yourself today.