High fidelity
Web fonts, pseudo-elements, SVG references, backgrounds and open shadow roots travel with the capture.
Open source · zero dependencies · browser native
SnapDOM captures any element as SVG, PNG, JPG, WebP. Plugins add GIF, video, standalone HTML and custom formats.
Subject: Mr. SnapDOM
AF · locked
Live DOM: not a screenshot
Fig. 01: moments before capture
SnapDOM starts from the element the browser rendered. It preserves the parts that usually make DOM capture difficult without rebuilding the page in a second rendering engine.
Web fonts, pseudo-elements, SVG references, backgrounds and open shadow roots travel with the capture.
A linear capture pipeline, bounded caches and lazy exporters keep repeated captures responsive.
Capture once, then export to PNG, SVG, canvas, blob, JPG or WebP from the same result.
Ship one focused browser library without pulling a second DOM or rendering stack into your app.
Add formats and capture behavior without making the core library larger for everyone.
The core remains MIT licensed, inspectable and usable in personal and commercial projects.
Use the DOM as the design surface, then capture the result for downloads, generated assets, automation or tests.
Export charts, KPI cards, legends and surrounding interface as one image.
FrontendTurn a rendered React component or web UI into a downloadable asset.
ContentDesign in HTML and CSS, then generate shareable images in the browser.
TestingProduce deterministic component captures for visual regression workflows.
Paid plugins for production workflows built on top of SnapDOM.
SnapDOM Pro will add focused, production-ready capabilities without changing the free core. Plugin sales fund ongoing SnapDOM maintenance and help keep the library current, independent and open source.
Start with the small API, then go deeper only where your capture needs it.

21 live demos
Run SnapDOM against canvas, video, fonts, masks, transforms, Shadow DOM, iframes and plugin exporters. Every example uses the real library.
Open the showcase