Re:Show HN: I created snapDOM to capture DOM nodes as images...
by streptomycin on Sunday April 27, 2025 @01:30PM
(#43813611)
I've been using html2canvas for a long time in https://play.basketball-gm.com/ so I gave your library a try. It was much slower (I know your README has benchmarks saying the opposite so idk) and the result looked a lot worse.
Also I recommend putting the npm package name clearly in your README. I guess I don't really know what other people are doing these days, but I think most people are like me and consume packages like this from npm rather than a <script> tag.
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by tinchox6 on Sunday April 27, 2025 @01:44PM
(#43813761)
Thank you for testing it out and sharing the screenshots!
I’ve run some performance tests using Vitest Bench, and SnapDOM was faster. I also created a few manual demos, and SnapDOM won in both speed and accuracy.
That said, I still need to run more real-world tests. So, thanks again for your help!
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by kaoD on Sunday April 27, 2025 @03:41PM
(#43814538)
You can embed HTML in an SVG via foreignObject. Seems like that's exactly what the library is doing[0].
Whether that's faster or more reliable, I don't know. Seems likely to render different depending on where you view the SVG (especially out of browsers).
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by tinchox6 on Sunday April 27, 2025 @04:23PM
(#43814820)
It is pretty the same idea. There are many good solutions like dom-to-imge-more: the battle tested html2canvas, dom-to-image, modern-screenshot, etc. SnapDom is focused on avoiding long-taks whenever is possible because was designed to a zoomble UI engine that needs the capture doesnt affect the transition. But this is the first public version and there many things to adjust.
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by jdiff on Sunday April 27, 2025 @01:41PM
(#43813740)
Capturing HTML as scalable SVGs is huge, how do you manage condensing all of CSS and its quirks into an SVG? Do you only support a subset of styling properties and rely on the browser to calculate layouts for you?
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by tinchox6 on Sunday April 27, 2025 @01:47PM
(#43813788)
I was upset about the size of generated svg file because at first all styles were inlined in each element. So I created a function to make mini css classes (.c1, c2, c3,...) So the final size is quite small.
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by darrenf on Sunday April 27, 2025 @03:40PM
(#43814523)
I’ve been writing a browser extension recently, and part of the functionality I want is to export part of a view as an image, shareable for the socials. I wanted to use html2canvas, but the docs explicitly advise against using it in a browser extension. Would snapDOM be suitable for inclusion in an extension?
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by genewitch on Monday April 28, 2025 @04:30AM
(#43818938)
Firefox has screenshot that auto-picks elements, or you can click and drag a crop, or you can save the whole page. That and ad nauseam are the reason I use firefox; that singlefile also works is great (single html file dump of a web page, somehow).
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by ashishact on Sunday April 27, 2025 @03:20PM
(#43814405)
Image in the readme would really be helpful.
In fact anytime there is a visual output it makes sense to put an image.
Thanks for creating this though - Will give it a try for an upcoming project.
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by maxloh on Sunday April 27, 2025 @02:42PM
(#43814143)
Maybe add a function to convert to PDF? I've always dreamed of converting an element or the document body to a long-scrolling PDF. I tried to implement it with Playwright Python, but I had no luck. The resulting PDF height is messed up.
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by krebby on Sunday April 27, 2025 @01:36PM
(#43813674)
How does this compare to something like the the Media Capture API? Looks like this uses `canvas.toDataURL()` which can be slow to serialize compared to `toBlob` or `canvas.captureStream(0).getVideoTracks()`
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by tinchox6 on Sunday April 27, 2025 @02:25PM
(#43814029)
Hi! Insaw this API when I was starting to work on snapDOM but I thought it was not ok for my needs so I discarded it. Regarding other API it would be great if View Transitions API could exposed the old view in a future
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by streptomycin on Sunday April 27, 2025 @01:58PM
(#43813858)
Looks cool, somebody should make a package that puts a nice API around it. However seems that those APIs are only in Chrome now, not Firefox or Safari.
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by Eduard on Sunday April 27, 2025 @02:08PM
(#43813910)
Not only screenshots, but also actual results. As I understand the short description, this tool allows to transform a website's current visual state into an SVG.
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by simonw on Sunday April 27, 2025 @08:38PM
(#43816417)
Tiny feature request: snapdom.toJpg(el) appears to return a JPEG image where the background color for any transparent areas is set to black - it would be useful to be able to set that to another color (I needed it to be white).
Re:Show HN: I created snapDOM to capture DOM nodes as images...
by Sephr on Monday April 28, 2025 @10:57AM
(#43822199)
Awesome! I was making exactly this library 13 years ago but only made it as far as creating CSS and other asset inlining+normalization tools before I ran into a few major roadblocks.
The most significant roadblock was that drawing SVG <foreignObject> with inline subresources (data: and blob: URIs) tainted canvases in Chrome and Safari, and this was partially resolved in 2019[1].
Notably, some issues still remain but apparently it's now workable. As is apparent from snapDOM, completely accurate CSS normalization is still an unsolved problem.
While I'm excited to see the HTML-in-foreignObject use case mature, it is also important to point out that the Media Capture API now has the ability to capture individual elements natively in Chrome[2].
html2canvas: https://i.imgur.com/zfSwNR1.png
snapdom: https://i.imgur.com/FxowTzp.png
Also I recommend putting the npm package name clearly in your README. I guess I don't really know what other people are doing these days, but I think most people are like me and consume packages like this from npm rather than a <script> tag.
I’ve run some performance tests using Vitest Bench, and SnapDOM was faster. I also created a few manual demos, and SnapDOM won in both speed and accuracy.
That said, I still need to run more real-world tests. So, thanks again for your help!
Whether that's faster or more reliable, I don't know. Seems likely to render different depending on where you view the SVG (especially out of browsers).
[0]: https://github.com/search?q=repo%3Azumerlab%2Fsnapdom%20fore...
https://github.com/zumerlab/snapdom/issues/1
https://github.com/zumerlab/snapdom/issues/3
I've been using CropTarget.fromElement with a CaptureController: https://gist.github.com/akre54/e93ab2ce27999aecb109e38085f2e...
For most cases, the Element Capture or Region Capture API should be sufficient: https://developer.mozilla.org/en-US/docs/Web/API/Screen_Capt...
Demos: https://mdn.github.io/dom-examples/screen-capture-api/elemen... https://mdn.github.io/dom-examples/screen-capture-api/region...
If you need cross-browser compatibility (and can't just use a canvas) then yeah html2canvas is the way to go
Plus it just struck at pending promise dont work
Plus css is messed up, i cant call it a snapshot, if it dont look same
domtoimage lib works for me and is fast whole html body node captured within second
The most significant roadblock was that drawing SVG <foreignObject> with inline subresources (data: and blob: URIs) tainted canvases in Chrome and Safari, and this was partially resolved in 2019[1].
Notably, some issues still remain but apparently it's now workable. As is apparent from snapDOM, completely accurate CSS normalization is still an unsolved problem.
While I'm excited to see the HTML-in-foreignObject use case mature, it is also important to point out that the Media Capture API now has the ability to capture individual elements natively in Chrome[2].
1. https://issues.chromium.org/issues/41054640#comment49
2. https://developer.mozilla.org/en-US/docs/Web/API/CropTarget/...