Supported Environments

Reshot is launch-ready on a production-like localhost path:

Run reshot setup
Start your target app with a production-like local server
Run reshot run
Run reshot publish when the capture looks right

Supported for launch

next build && next start
any equivalent production-like local server that renders the same code path you intend to ship
certified targets that declare a deterministic readiness contract and pass reshot doctor target / reshot verify publish

Not supported for launch reliability

next dev
arbitrary hot-reload development servers with non-production rendering behavior
targets that rely only on sleeps instead of app-owned readiness markers

Why production-like localhost

It reduces the three main sources of flaky captures:

dev-only runtime errors
hydration or hot-reload instability
route timing that differs from the shipped app

You can still experiment in development mode while authoring scenarios, but the supported launch path is to verify captures against a production-like local server before you publish.

Recommended commands

For many Next.js apps, this is the right pattern:

Terminal

npm run build
npm run start
reshot run
reshot publish

If your app requires a capture-safe flag or a different production start command, declare that in reshot.config.json so reshot setup can show the recommended command directly.