Nearly Picked Makefiles


    2.15.0 • Public • Published

    DOM to Image

    Build Status

    What is it

    dom-to-image-more is a library which can turn arbitrary DOM node, including same origin and blob iframes, into a vector (SVG) or raster (PNG or JPEG) image, written in JavaScript.

    This fork of dom-to-image by Anatolii Saienko (tsayen) with some important fixes merged. We are eternally grateful for his starting point.

    Anatolii's version was based on domvas by Paul Bakaus and has been completely rewritten, with some bugs fixed and some new features (like web font and image support) added.

    Moved to 1904labs organization from my repositories 2019-02-06 as of version 2.7.3



    npm install dom-to-image-more

    Then load

    /* in ES 6 */
    import domtoimage from "dom-to-image-more";
    /* in ES 5 */
    var domtoimage = require("dom-to-image-more");




    All the top level functions accept DOM node and rendering options, and return promises, which are fulfilled with corresponding data URLs.
    Get a PNG image base64-encoded data URL and display right away:

    var node = document.getElementById("my-node");
      .then(function (dataUrl) {
        var img = new Image();
        img.src = dataUrl;
      .catch(function (error) {
        console.error("oops, something went wrong!", error);

    Get a PNG image blob and download it (using FileSaver, for example):

    domtoimage.toBlob(document.getElementById("my-node")).then(function (blob) {
      window.saveAs(blob, "my-node.png");

    Save and download a compressed JPEG image:

      .toJpeg(document.getElementById("my-node"), { quality: 0.95 })
      .then(function (dataUrl) {
        var link = document.createElement("a"); = "my-image-name.jpeg";
        link.href = dataUrl;;

    Get an SVG data URL, but filter out all the <i> elements:

    function filter(node) {
      return node.tagName !== "i";
      .toSvg(document.getElementById("my-node"), { filter: filter })
      .then(function (dataUrl) {
        /* do something */

    Get the raw pixel data as a Uint8Array with every 4 array elements representing the RGBA data of a pixel:

    var node = document.getElementById("my-node");
    domtoimage.toPixelData(node).then(function (pixels) {
      for (var y = 0; y < node.scrollHeight; ++y) {
        for (var x = 0; x < node.scrollWidth; ++x) {
          pixelAtXYOffset = 4 * y * node.scrollHeight + 4 * x;
          /* pixelAtXY is a Uint8Array[4] containing RGBA values of the pixel at (x, y) in the range 0..255 */
          pixelAtXY = pixels.slice(pixelAtXYOffset, pixelAtXYOffset + 4);

    Get a canvas object:

    domtoimage.toCanvas(document.getElementById("my-node")).then(function (canvas) {
      console.log("canvas", canvas.width, canvas.height);

    All the functions under impl are not public API and are exposed only for unit testing.

    Rendering options


    A function taking DOM node as argument. Should return true if passed node should be included in the output (excluding node means excluding it's children as well). Not called on the root node.


    A string value for the background color, any valid CSS color value.

    height, width

    Height and width in pixels to be applied to node before rendering.


    An object whose properties to be copied to node's style before rendering. You might want to check this reference for JavaScript names of CSS properties.


    A number between 0 and 1 indicating image quality (e.g. 0.92 => 92%) of the JPEG image. Defaults to 1.0 (100%)


    Set to true to append the current time as a query string to URL requests to enable cache busting. Defaults to false


    A data URL for a placeholder image that will be used when fetching an image fails. Defaults to undefined and will throw an error on failed images


    It's tested on latest Chrome and Firefox (49 and 45 respectively at the time of writing), with Chrome performing significantly better on big DOM trees, possibly due to it's more performant SVG support, and the fact that it supports CSSStyleDeclaration.cssText property.

    Internet Explorer is not (and will not be) supported, as it does not support SVG <foreignObject> tag

    Safari is not supported, as it uses a stricter security model on <foreignObject> tag. Suggested workaround is to use toSvg and render on the server.`



    Only standard lib is currently used, but make sure your browser supports:


    Most importantly, tests depend on:

    • ocrad.js, for the parts when you can't compare images (due to the browser rendering differences) and just have to test whether the text is rendered

    How it works

    There might some day exist (or maybe already exists?) a simple and standard way of exporting parts of the HTML to image (and then this script can only serve as an evidence of all the hoops I had to jump through in order to get such obvious thing done) but I haven't found one so far.

    This library uses a feature of SVG that allows having arbitrary HTML content inside of the <foreignObject> tag. So, in order to render that DOM node for you, following steps are taken:

    1. Clone the original DOM node recursively

    2. Compute the style for the node and each sub-node and copy it to corresponding clone

      • and don't forget to recreate pseudo-elements, as they are not cloned in any way, of course
    3. Embed web fonts

      • find all the @font-face declarations that might represent web fonts

      • parse file URLs, download corresponding files

      • base64-encode and inline content as data: URLs

      • concatenate all the processed CSS rules and put them into one <style> element, then attach it to the clone

    4. Embed images

      • embed image URLs in <img> elements

      • inline images used in background CSS property, in a fashion similar to fonts

    5. Serialize the cloned node to XML

    6. Wrap XML into the <foreignObject> tag, then into the SVG, then make it a data URL

    7. Optionally, to get PNG content or raw pixel data as a Uint8Array, create an Image element with the SVG as a source, and render it on an off-screen canvas, that you have also created, then read the content from the canvas

    8. Done!

    Using Typescript

    1. Use original dom-to-image type definition npm install @types/dom-to-image --save-dev

    2. Create dom-to-image-more type definition (dom-to-image-more.d.ts)

      declare module 'dom-to-image-more' {
       import domToImage = require('dom-to-image');
       export = domToImage;

    Things to watch out for

    • if the DOM node you want to render includes a <canvas> element with something drawn on it, it should be handled fine, unless the canvas is tainted - in this case rendering will rather not succeed.

    • at the time of writing, Firefox has a problem with some external stylesheets (see issue #13). In such case, the error will be caught and logged.


    Marc Brooks, Anatolii Saienko (original dom-to-image), Paul Bakaus (original idea), Aidas Klimas (fixes), Edgardo Di Gesto (fixes), 樊冬 Fan Dong (fixes), Shrijan Tripathi (docs), SNDST00M (optimize), Joseph White (performance CSS), Phani Rithvij (test), David DOLCIMASCOLO (packaging), @meche-gh (node copy cleaning)




    npm i dom-to-image-more

    DownloadsWeekly Downloads






    Unpacked Size

    318 kB

    Total Files


    Last publish


    • idisposable