Plugins and tools built on SnapDOM.
Extend a capture with official or community plugins. Export documents with PDF, reconstruct editable artwork with Vector, or use the tools for agents and visual testing.
Choose by the job
| Job | Use |
|---|---|
| Export an element as an image or file | SnapDOM core + plugins |
| Check that nothing changed visually | SnapDIFF |
| Give a coding agent before/after evidence | SnapEye |
| Let an agent reach a state and verify it | SnapSurf (experimental) |
One settings panel, three kinds of checks
1 · Reach the state
SnapSurf opens the page and clicks Settings. Verify that the panel appeared and the controls are available.
2 · Inspect the edit
SnapEye captures the open panel before and after the code change. Compare its appearance or record the transition.
3 · Keep it checked
SnapDIFF adds the panel to a repeatable visual suite. Review the baseline and check future changes against it.
Your agent or test harness connects these steps. For an already-open panel, call SnapEye’s in-page API: its URL trigger reloads the page. Keep viewport, data and state consistent, and manage each tool’s baselines separately.
Official plugins
Prepare captured content with filters, timestamps, text replacement, private-field masking and tint. Add HTML snapshots, ASCII art, GIF, video, text or JSON context and annotated element maps. PDF belongs to this package too.
Turn captured HTML into paginated documents with selectable text, links, bookmarks and optional form fields. This is the exporter previously offered as PDF Pro.
Vector
Reconstruct text and supported shapes as editable SVG artwork or Figma content. Core SVG preserves HTML through foreignObject; Vector converts supported content into vector elements.
Community plugins
Build a plugin in your own repository and submit it to the directory. Community extensions are maintained by their authors, alongside the official package.
SnapDIFF
Compare captures against baselines, inspect changed pixels and use the result in a browser test suite or CI.
Try it here
Take a baseline of the card, change its title, then compare. Changed pixels turn red, the rest fades.
What it does
- Mark elements with
data-snapfor in-page checks. - Review split, slider and diff views; approve intended changes.
- Use a Vitest browser suite with disk baselines to fail CI on visual drift.
SnapEye and SnapDIFF both compare pixels. Choose SnapEye for an agent’s capture-and-inspect task; choose SnapDIFF for a maintained set of visual tests and baseline reviews.
SnapEye
Capture, compare and record a local app through a CLI or page API. Give a coding agent artifacts and change regions.
Try it here
Take a baseline, change the card, then compare to get the before/after pair an agent would receive.
What it does
- Capture an element before a change, then compare it afterward.
- Locate changed regions and inspect the current and diff images.
- Record a transition and review its frames, GIF or video.
SnapEye does not navigate or click. A browser driver reaches interactive states; SnapEye measures their appearance. Its visual comparison uses SnapDIFF’s diff engine.
SnapSurf
Navigate, locate controls, act and verify what changed. SnapSurf adds browser interaction around capture evidence.
What it does
- Open a page, find a control, click or type, then verify.
- Check changes to content, state, layout and clickability.
- Assert expected changes and the absence of unwanted ones.
A semantic diff answers whether the observed page changed. It does not replace a pixel comparison against a saved visual baseline. Its managed browser has its own cookies and storage, separate from your everyday browser.