Sign in
Pricing
How it worksThe docs visuals workflow from CI capture to permanent URLs.Visual DiffReview changed docs visuals before they publish.CI/CD CaptureCapture docs visuals in the pipeline you already run.CDN URLsPermanent URLs that stay current when you ship.IntegrationsCI runners and docs platforms that fit the same workflow.
BlogWriting on docs visuals, CI/CD capture, and visual debt.Visual DebtUnderstand the cost of stale docs visuals.AboutWhy we built Reshot and how we think about the problem.Docs-as-Code GuidePractical guidance for versioned docs workflows.
Sign in

[02] CI/CD Capture

Run screenshots where your code already builds.

Define capture scenarios in a YAML config alongside your code. One CLI command in any CI runner. Reshot launches a browser, navigates, captures, and uploads. No manual steps.

Start capturing freeSee all integrations

[01] The capture model

Declare what to capture. CI handles the rest.

Your reshot.config.json file lives in the repo, right next to the code that changes the UI. Pages, viewports, themes, wait conditions, interaction sequences, and auth states.

01

Declare in YAML

A reshot.config.json file in your repo defines every page, viewport, theme, and interaction sequence to capture.

02

Trigger from CI

Add one line to your CI pipeline. Reshot runs as a CLI step, no custom Docker images or browser management required.

03

Browser-based rendering

Reshot launches headless Chrome, navigates to each URL, executes configured actions, waits for the page to settle, and captures.

[03] Full workflow example

GitHub Actions in four lines.

This is the complete GitHub Actions workflow. One step. Reshot reads your reshot.config.json, launches headless Chrome, and uploads the results.

.github/workflows/reshot.yml
name: Reshot Capture
on: [push]
jobs:
  capture:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npx /screenshot run
        env:
          RESHOT_TOKEN: ${{ secrets.RESHOT_TOKEN }}

[04] Capture configuration

Everything in one YAML file.

Define URLs, viewports, themes, wait conditions, interaction sequences, and authentication. All version-controlled alongside your code.

reshot.config.json
project: meridian-app

scenarios:
  - name: Dashboard
    url: /dashboard
    viewports: [1280x800, 768x1024, 375x812]
    themes: [light, dark]
    wait: networkidle

  - name: Settings
    url: /settings
    viewports: [1280x800]
    themes: [light]
    auth:
      email: test@example.com
      password: ${RESHOT_TEST_PASSWORD}

  - name: Analytics
    url: /dashboard/analytics
    viewports: [1280x800]
    actions:
      - click: '[data-tab="weekly"]'
      - wait: 500

Get started

Start with one docs visual workflow.

Free tier. No credit card. Connect your repo, capture one real docs scenario in CI/CD, and keep the same URL current after every ship.

Start capturing freeSee how it works