Skip to content
All guides

Best Screenshot Tools for Docs-as-Code Teams

Options for keeping screenshots current when your documentation lives in a git repo, from free CLIs to managed services.

Docs-as-code teams have an advantage: CI already runs on every change. The question is whether screenshots should live in the repo as files or be referenced by URL.

The short answer

If engineers own the docs and you want screenshots committed to the repo, Heroshot is the best starting point. It is free, picks elements visually, and opens a pull request with updated images. Choose ScreenshotAgent when writers or support staff also manage screenshots, when the same images are used outside the repo, or when you would rather reference a hosted URL than commit binaries. Playwright scripts are the fallback when you need full control.

What we looked for

  • Fits a git-based review flow.
  • Works with Docusaurus, Mintlify, VitePress, MkDocs, or Next.js docs.
  • Handles logged-in screens.
  • Who can maintain it: only engineers, or writers too.

Our picks

  1. 1. Heroshot

    Best free option for repo-based docs

    An open-source CLI that saves screenshot definitions as config and recaptures them in CI. It also has an MCP server for coding assistants.

    Pricing: Free, MIT licensed, no paid tiers.

    • Visual picker writes the config for you.
    • Light/dark and viewport variants from one config.
    • GitHub Actions workflow commits new screenshots and opens a pull request.
    • Made for developers; writers will need help to set up.
    • Screenshots live in the repo, so there are no hosted embed URLs for a CMS or help center.

  2. 2. ScreenshotAgent

    Best when non-engineers share the work

    Reference /s/{uuid}.png URLs in Markdown instead of committing image files. Trigger recapture from CI with POST /api/v1/recapture, or from a coding agent over MCP.

    Pricing: Pro $199/mo (400 captures, 2,000 AI annotations), Business $499/mo (1,200 captures, 6,000 AI annotations), Enterprise from $1,499/mo. Unlimited users, Recapture API, MCP server, and search API on every plan. 14-day trial with 5 captures and 10 AI annotations, or 30 captures and 100 AI annotations with a card.

    • No image binaries in the repo.
    • Writers manage screenshots in a web app.
    • Same URLs work in your CMS and help center.
    • Paid, and costs much more than a free CLI.
    • Images are not reviewed in your pull requests.

  3. 3. Playwright scripts

    Best for full control

    Write capture scripts with Playwright and run them in CI. Every detail is yours to set, from seeded data to timing.

    Pricing: Free and open source.

    • Complete control.
    • No vendor.
    • Scripts break when selectors change and need upkeep.

  4. 4. ScreenshotOne

    Best hosted API to call from CI

    Call an API from your build to render pages, with hide selectors and cookie support.

    Pricing: Free 100/mo. Basic $17/mo (2,000). Growth $79/mo (10,000). Scale $259/mo (50,000).

    • No browsers to run yourself.
    • Cheap per shot.
    • Logins and multi-step states need custom scripts.
    ScreenshotAgent vs ScreenshotOne

Pricing checked on October 2, 2026 from each vendor’s public website. Confirm current prices before buying.

FAQ

Should screenshots be committed to the docs repo?
Committing them gives you review in pull requests and versioned history with the docs. Hosted URLs keep the repo small and let the same image appear in other tools. Both are reasonable.
Does ScreenshotAgent work with Docusaurus and Mintlify?
Yes. Any Markdown renderer that loads remote images works with ScreenshotAgent URLs.

Sources

Run this guide in ScreenshotAgent

Start with one project and apply this workflow to keep screenshots accurate with less effort.

Start free trial14-day trial · 5 captures free · No card required