snapdom.dev valid

SnapDOM

SnapDOM is a high-performance engine for capturing, modifying, and converting DOM elements into any format. It is fast, pixel-faithful, extensible through plugins and continuously maintained.

For agents: SnapDOM: JavaScript engine for capturing and converting DOM elements to images, PDF, HTML and other formats, with API docs, options, plugins and framework guide

dom-capturehtml-to-imagejavascript-librarypluginspdf-export

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T05:23:49.257Z. Cached copy · Source on snapdom.dev

# SnapDOM

Last updated: 2026-10-05.

> SnapDOM is a high-performance engine for capturing, modifying, and converting DOM elements into any format. It is fast, pixel-faithful, extensible through plugins and continuously maintained.

SnapDOM (`@zumer/snapdom`) captures a DOM subtree, its styles and its assets into a reusable result. The core exports SVG, PNG, JPG, WebP, canvas and blobs, and reports capture geometry. Plugins add HTML, text or JSON context, annotated element maps, searchable, paginated PDFs and editable vector artwork and recordings.

Two integrated engines render the same finished clone: `svg` (default) serializes it, while experimental `html-in-canvas` paints it through the browser's native API. The second engine still needs the browser feature flag or applicable origin trial (supported Chrome builds: `chrome://flags/#canvas-draw-element`) and a build compiled with `SNAPDOM_CANVAS_ENGINE=1 npm run compile`; the default build currently omits it. Unsupported captures fall back to SVG.

This reference describes SnapDOM v3.x.x. See the [installation notes](https://github.com/zumerlab/snapdom#installation). Older projects can use the [preserved v2 branch](https://github.com/zumerlab/snapdom/tree/v2).

## Quick start

```bash
npm install @zumer/snapdom@latest
```

```js
import { snapdom } from '@zumer/snapdom';

const capture = await snapdom(document.querySelector('#card'));
const image = await capture.toPng({ width: 1200, dpr: 1 });
const svg = await capture.toBlob();
document.body.appendChild(image);
```

Image exports reuse the captured state. Capture the element again to read later page changes. Recording plugins are different: they take new frames when the recording export starts.

The package entry is ESM. The browser IIFE build exposes `window.snapdom`; there is no CommonJS build. The core has no runtime dependencies. Plugins are a separate package.

## Documentation

- [Full reference for LLMs](https://snapdom.dev/llms-full.txt): API, options, plugins, examples and limits
- [Documentation](https://snapdom.dev/docs/): start here
- [API](https://snapdom.dev/docs/api/): capture and export methods
- [Options](https://snapdom.dev/docs/options/): geometry, assets, fonts and exclusions
- [Plugins](https://snapdom.dev/docs/plugins/): hooks and custom exports
- [Cache and preCapture](https://snapdom.dev/docs/cache/): resource reuse, repeat captures and intent events
- [How-to](https://snapdom.dev/how-to/): capture recipes and framework guides (React, Vue, Next.js, Svelte, Angular, Lit)
- [Compare](https://snapdom.dev/compare/): capture approaches and alternatives
- [Plugins](https://snapdom.dev/showcase/#plugins): what a capture can become (images, PDF, HTML, GIF/video, ASCII, agent context) and who provides each, core or plugin
- [Ecosystem](https://snapdom.dev/ecosystem/): official and community plugins, PDF, Vector, SnapEye, SnapSurf and SnapDIFF; differences and combined workflows
- [Blog](https://snapdom.dev/blog/): capture archite
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=snapdom.dev · GET /v1/domain/snapdom.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for snapdom.dev:
1. POST https://agentwebmap.com/v1/sites/snapdom.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://snapdom.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/snapdom.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/snapdom.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.