Visual regression testing for GitHub Actions and GitLab CI

Review each visual change once.

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.

Storefront
feat/checkout-redesigna1f9c3e0Tighten the order summaryNeeds Review
checkout
Needs Review
Reference build approved baselineNew build
fernhill
Checkout
Order summary
Linen shirt$68.00
Canvas tote$24.00
Shipping$6.00
Total$98.00
Place order
fernhill
Checkout
Order summary
Linen shirt$68.00
Canvas tote$24.00
ShippingFree
Total$92.00
Place order
product-card
New
Reference build approved baselineNew build No diff: this screen is new
New screen. There's no reference yet; approving makes this the baseline.
New
Linen shirt
Add to bag · $68

0 of 2 reviewed · 2 unreviewed will be approved on submit

J/K next/previousA approveR rejectD diff

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).

How it works

Screenshots in. One decision out.

  1. 1

    Your tests take screenshots

    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.

  2. 2

    One CI step uploads them

    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.

  3. 3

    PixelCI picks the right baseline

    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.

  4. 4

    Only real changes reach a person

    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
visual-regression · job logfailed
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.

Something changed. The job fails and links to the build for review.

Cross-branch approvals

Approve it on one branch. Every branch knows.

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.

One change, three builds1 review for 3 builds
  1. feat/button-refresh7be20d14 · You review itDraftProcessingNeeds ReviewChanges Approved
  2. feat/gift-cards3c91fa02 · Same pixels, already approvedDraftProcessingNeeds ReviewChanges Approved
  3. maine04d6b29 · Merged. Nothing to re-reviewDraftProcessingNeeds ReviewChanges Approved
Built for the reviewer

Fast for the developer who hit a red build. Thorough for the person who reviews fifty.

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.

Closes the CI loop

Approving a build re-runs the failed job and takes you to the pipeline. Nobody hunts for a retry button.

Self-managed GitLab, on every plan

GitHub, GitLab.com and your own GitLab instance, including on Free. You don’t need an enterprise contract to use your own GitLab.

Unlimited seats

Designers, QA and product leads review for free. You pay for screenshots, never for the people who check them.

Exact pixels

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.

Keyboard-first review

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.

MCP server

Your AI assistant can read the review.

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.

  • Four tools: list_apps, list_builds, get_build and get_screen_image
  • Read-only: it can’t approve, reject or comment
  • Signs in with your own GitHub or GitLab token and sees only the projects you can
  • Built into PixelCI at /api/mcp: nothing to install or run
AI assistantpixelci MCP · read-only

Why did the visual job fail on feat/checkout-redesign?

  • list_apps
  • list_buildsStorefront
  • get_buildfeat/checkout-redesign · a1f9c3e0
  • get_screen_imagecheckout · kind=diff

The reviewer rejected checkout. product-card is new and was approved.

Maya R.Rejected
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?

Two ways to run it

The same PixelCI, hosted or on your own servers.

PixelCI Cloud

Early access

We run it, scale the diff workers and keep the history. You add one CI step.

  • Sign in with GitHub, GitLab, Google, Microsoft or an email code
  • CI signs in with OIDC: no tokens to store
  • Free up to 5,000 screenshots a month
  • 14-day Business trial, no card

Self-hosted

Available now

One Docker image on your own infrastructure. Screenshots never leave it.

  • Source-available, free for internal use
  • Your database, your Redis, your S3 bucket
  • GitHub Actions and GitLab CI
  • The same review screen and approval engine

Stop approving the same change twice.

Tell us about your pipeline and we’ll get you into the early-access cloud, or help you run it yourself today.