Using pixmoat

pixmoat helps your team answer one question before a change is merged: did the interface change in an expected way?

The normal workflow is short:

1. Connect a project to your Playwright tests.
2. Run the tests in CI.
3. Open the build in pixmoat and review anything that changed.
4. Approve expected changes or reject regressions.
5. Finish the review so the approved screenshots become the next baseline.

Start with a project

From Projects, open an existing project or create a new one. A project keeps the screenshots, builds, branches, and review history for one application or interface.

To connect the project to Playwright, create a project access token in Project settings → Tokens and add it to your CI variables. The Playwright integration guide shows the complete connection.

Run a build

When your Playwright suite runs, pixmoat groups the uploaded screenshots into a build. Each screenshot is compared with the approved baseline for its branch.

The build can contain:

• New — there is no approved baseline yet.
• Changed — the current screenshot differs from its baseline.
• Unchanged — the current screenshot matches its baseline.
• Removed — a screenshot that existed before was not uploaded in this build.

Open a build from the project to see the screenshots and their review status.

Review a build

Select a new or changed screenshot to compare the baseline with the current capture. Use the visual modes to inspect the change, then choose:

• Approve when the change is intentional and should become part of the product.
• Reject when the change is unexpected or needs a code fix.

Decisions are staged while you work. They are applied to the baseline only after you select Finish review. This means you can change a decision before finishing.

For a more detailed walkthrough, see Review visual changes.

After the review

If every required change is approved, the build passes and the approved screenshots become the baseline for future comparisons. If a change is rejected, fix the code and run the build again.

If nothing changed, pixmoat finalizes the build automatically because there is nothing to review.

Find the right place

• Projects — choose an application and open its builds.
• Usage & capacity — see how much of the organization’s project, seat, and screenshot capacity is in use.
• Billing & usage — manage the plan and additional capacity.
• Organization settings — manage members and their access.
• Project settings — manage tokens, review behavior, integrations, and project-specific settings.

The shortest path for a new teammate

1. Open the project linked to the work you are changing.
2. Open the latest build for your branch.
3. Review screenshots marked New or Changed.
4. Approve expected changes, reject regressions, and finish the review.