The details people forget
Many product issues depend on environment: screen width, browser, route, scroll position, user role, or staging environment. Screenshots rarely include that information, and reporters often do not know which details matter.
SnapState collects the basics automatically so the recipient can start with a more complete artifact.
- URL, title, timestamp, and viewport dimensions.
- Browser and extension version for reproducibility.
- Optional project or environment labels when a workspace configures them.
Useful across teams
Designers can confirm the viewport where a layout issue appears. QA can identify the environment where a test failed. Support can show engineering which route and customer-facing state caused confusion.
The same metadata also helps later when teams search old snapshots. Instead of remembering a Slack thread, they can filter by project, route, or issue type.
Do not over-collect
Metadata helps explain a captured state without becoming surveillance. SnapState makes captured fields visible and keeps site-level diagnostics optional.
This reinforces the product's core privacy position: SnapState captures the moment a user chooses to share, not a hidden stream of everything they do.