HTML-in-Canvas vs. rasterizing DOM into Canvas textures: a visual comparison (side-by-side below, with average capture time comparison) The existing methods for extracting web content into Canvas are both slow and lossy: - Animations stutter or fail to play entirely - CSS replication is inaccurate - Blocks the main thread, causing other animations to lag HTML-in-Canvas (texElementImage2D) allows the browser's own compositor to precisely map CSS layouts, animations, and transitions onto Canvas/WebGL textures — with just one native call instead of thousands of JS style reads. This feature is currently available via Chrome's experimental flag. Super cool, and I can’t wait to see it go mainstream!