Percy "No snapshots found" build in CI

By Daniel Zoghalchali·Latchkey

Percy started and finalized a build but received zero snapshots. The wrapping percy exec ran, but no percySnapshot() call reached the local Percy server, so there is nothing to compare.

What this error means

The Percy step succeeds but the dashboard shows a build with "No snapshots found," or the CLI logs "Build ... finalized" with a snapshot count of 0. Visual review has nothing to approve.

Percy

[percy] Snapshot taken: (none)
[percy] No snapshots found, deleting build

Common causes

The test never calls percySnapshot

The suite runs under percy exec, but the tests do not actually invoke percySnapshot(page, name), so no images are sent.

The SDK cannot reach the local Percy server

Percy runs a local server that the SDK posts to. If the SDK is a mismatched version or the tests run in a separate network namespace, the snapshot calls silently no-op.

How to fix it

Call the snapshot API in the tests

Import the matching SDK and take a named snapshot at each state you want compared.

tests/home.spec.ts

import { percySnapshot } from '@percy/playwright';
await page.goto('/');
await percySnapshot(page, 'Home page');

Verify exec wraps the test command

Ensure the test runner is a child of percy exec so the SDK can reach the local server the CLI starts.

Terminal

npx percy exec -- npx playwright test

How to prevent it

Call percySnapshot at each state you want captured.
Run the test command as a child of percy exec.
Keep the Percy CLI and SDK versions aligned.

Frequently asked questions

What causes ""No snapshots found""?

The suite runs under percy exec, but the tests do not actually invoke percySnapshot(page, name), so no images are sent.

How do I fix "No snapshots found"?