Skip to content
Tool

Screenery

Keeps docs, READMEs and marketing screenshots current by publishing them from CI

Platforms
Web, API, CLI
Listing updated
today

Similar tools

About Screenery

Screenery is an AI tool for developer tools. It is available on Web, API and CLI.

The README says screenshots from your existing tests are pushed on each merge to the default branch, so the images embedded in docs, READMEs and landing pages update without anyone retaking them. Each screenshot gets a stable @latest URL that follows the default branch, while pull requests write to their own @pr-n channel and leave the published image alone.

The product can also act as a visual gate. When a baseline folder is configured, the GitHub Action compares each screenshot pixel by pixel before publishing and fails the job if a change exceeds the threshold. Reviewers approve or reject changed screenshots in the console or through an MCP-connected agent, and the result is reported to GitHub as a check.

It suits teams whose docs, website or demo clips go out of date after each release, and who already run Playwright or another test suite that captures screens.

What it does

Automatic screenshot publishing
A CI step uploads PNGs from your test run so embedded images refresh on the next default-branch merge.
Stable @latest URLs
Each screenshot has a fixed address that points at the latest default-branch version, so embeds never need editing.
Pixel-level visual regression gate
A baseline comparison can fail CI and block publishing when a screen changes past a set threshold.
Review and approval workflow
Changed screenshots can be approved or rejected before the merge that moves @latest, reported as a GitHub check.
Keyless GitHub CI setup
GitHub Actions authenticates with OIDC tokens, so no publish secret is stored in the repository.
Playwright golden support
Existing toHaveScreenshot goldens or Argos upload folders can be published as they are.
Public, unlisted or private assets
Screenshots can be served openly, behind signed URLs, or behind read tokens.

Good for

  • Keep README screenshots matching the current app after each release
  • Refresh homepage and pricing page screenshots without manual exports
  • Block visual regressions from reaching docs by failing CI on unexpected pixel changes
  • Publish demo GIFs and MP4s at stable URLs for landing pages
  • Let a coding agent set up self-updating screenshots through MCP

Screenery FAQ

What is Screenery?

Screenery is a package registry for product screenshots. CI pushes screenshots on every build, and each one gets a stable URL ending in @latest.png that follows the default branch.

Do I need a secret in CI?

Not on GitHub Actions. The Action exchanges a GitHub OIDC token for a publish credential that lives five minutes. Other CI systems push with one static publish token.

Does a pull request change the screenshot in my README?

After the first build, no. Pull requests get their own @pr-n channel and do not move @latest. The first build on a new project does move @latest, from whichever branch it came from.

Does it work with Playwright's toHaveScreenshot?

Yes. toHaveScreenshot can remain the pixel gate, and Screenery publishes the goldens it already accepted, or an Argos upload folder, as they are.

What are the best alternatives to Screenery?

The closest alternatives to Screenery are AegisRunner, Kai, Perfectclone, Codecainehq and agentshield.

Where this comes from

  • Description: written from the project's website.