Convert Figma logo to code with AI

tsayen logodom-to-image

Generates an image from a DOM node using HTML5 canvas

10,307
1,685
10,307
324

Top Related Projects

Screenshots with JavaScript

✂️ Generates an image from a DOM node using HTML5 canvas and SVG.

An HTML5 saveAs() FileSaver implementation

file downloading using client-side javascript

5,251

Native Linux App for UI and UX Design built in Vala and GTK

Quick Overview

dom-to-image is a JavaScript library that allows you to convert HTML DOM nodes into vector (SVG) or raster (PNG/JPEG) images directly in the browser. It uses HTML5 canvas and SVG to create high-quality images, making it useful for generating screenshots, thumbnails, or exporting web content as images.

Pros

  • Works entirely in the browser without server-side processing
  • Supports various output formats (PNG, JPEG, SVG)
  • Preserves CSS styles and layout of the original DOM
  • Handles complex DOM structures, including nested elements and pseudo-elements

Cons

  • May have performance issues with very large or complex DOM structures
  • Limited support for certain CSS properties and external resources
  • Potential cross-origin resource issues when dealing with images or fonts from different domains
  • Not actively maintained (last commit was in 2017)

Code Examples

Converting a DOM node to a PNG image:

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

Generating a JPEG image with custom quality:

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

Creating an SVG image:

domtoimage.toSvg(document.getElementById('my-node'))
    .then(function (dataUrl) {
        console.log(dataUrl);
        // Use the SVG data URL as needed
    });

Getting Started

  1. Install dom-to-image using npm:

    npm install dom-to-image
    
  2. Include the library in your project:

    import domtoimage from 'dom-to-image';
    
  3. Use the library to convert a DOM node to an image:

    const node = document.getElementById('my-node');
    domtoimage.toPng(node)
        .then(function (dataUrl) {
            // Use the generated image data URL
        })
        .catch(function (error) {
            console.error('Error:', error);
        });
    

Competitor Comparisons

Screenshots with JavaScript

Pros of html2canvas

  • More actively maintained with frequent updates
  • Larger community and better documentation
  • Supports a wider range of CSS properties and rendering scenarios

Cons of html2canvas

  • Slower rendering performance for complex layouts
  • Larger file size and more dependencies
  • May produce less accurate results in some edge cases

Code Comparison

html2canvas:

html2canvas(document.body).then(function(canvas) {
    document.body.appendChild(canvas);
});

dom-to-image:

domtoimage.toPng(document.getElementById('my-node'))
    .then(function (dataUrl) {
        var img = new Image();
        img.src = dataUrl;
        document.body.appendChild(img);
    });

Both libraries aim to convert HTML content to images, but they differ in implementation and usage. html2canvas focuses on rendering the entire page or specific elements using canvas, while dom-to-image uses SVG and XML serialization for conversion. html2canvas offers more options for customization and handling complex layouts, but dom-to-image may provide better performance for simpler use cases. The choice between the two depends on specific project requirements, desired output quality, and performance considerations.

✂️ Generates an image from a DOM node using HTML5 canvas and SVG.

Pros of html-to-image

  • More actively maintained with recent updates and bug fixes
  • Supports a wider range of CSS properties and complex layouts
  • Better handling of external resources like fonts and images

Cons of html-to-image

  • Slightly larger bundle size
  • May have slower performance for simpler DOM structures

Code Comparison

dom-to-image:

domtoimage.toPng(node)
    .then(function (dataUrl) {
        var img = new Image();
        img.src = dataUrl;
        document.body.appendChild(img);
    })
    .catch(function (error) {
        console.error('oops, something went wrong!', error);
    });

html-to-image:

htmlToImage.toPng(node)
    .then(function (dataUrl) {
        var img = new Image();
        img.src = dataUrl;
        document.body.appendChild(img);
    })
    .catch(function (error) {
        console.error('oops, something went wrong!', error);
    });

Both libraries have similar APIs, making it easy to switch between them. The main differences lie in their internal implementations and handling of various HTML and CSS features.

An HTML5 saveAs() FileSaver implementation

Pros of FileSaver.js

  • Focused on saving files, providing a simple and efficient solution for file downloads
  • Supports a wide range of browsers and file types
  • Lightweight and easy to integrate into existing projects

Cons of FileSaver.js

  • Limited to file saving functionality, lacks image generation capabilities
  • Requires additional libraries or code for creating content to save

Code Comparison

FileSaver.js:

var blob = new Blob(["Hello, world!"], {type: "text/plain;charset=utf-8"});
saveAs(blob, "hello world.txt");

dom-to-image:

domtoimage.toPng(node)
    .then(function (dataUrl) {
        var link = document.createElement('a');
        link.download = 'my-image-name.png';
        link.href = dataUrl;
        link.click();
    });

Summary

FileSaver.js is a specialized library for saving files in the browser, while dom-to-image focuses on converting DOM nodes to images. FileSaver.js excels in file saving across various browsers but lacks image generation capabilities. dom-to-image, on the other hand, provides powerful DOM-to-image conversion but may require additional code for saving the generated images. The choice between these libraries depends on the specific requirements of your project, whether it's primarily file saving or image generation from DOM elements.

file downloading using client-side javascript

Pros of download

  • Lightweight and simple to use, with a focus on file downloading
  • Supports a wide range of file types and data formats
  • Can generate downloads from various sources (URLs, Blobs, data URIs)

Cons of download

  • Limited to file downloading functionality
  • Lacks image manipulation and DOM-to-image conversion features
  • May require additional libraries for complex use cases

Code Comparison

dom-to-image:

domtoimage.toPng(node)
    .then(function (dataUrl) {
        var img = new Image();
        img.src = dataUrl;
        document.body.appendChild(img);
    })
    .catch(function (error) {
        console.error('oops, something went wrong!', error);
    });

download:

download("hello world", "dlText.txt", "text/plain");
download(canvas.toDataURL(), "dlCanvas.png", "image/png");
download("/path/to/file", "dlFile.pdf");

Summary

dom-to-image specializes in converting DOM elements to images, offering advanced features for capturing and manipulating web content. It's ideal for creating screenshots or exporting complex layouts as images.

download, on the other hand, focuses solely on file downloading functionality. It provides a simple and versatile way to trigger downloads for various file types and data sources, making it useful for basic file handling tasks in web applications.

Choose dom-to-image for DOM-to-image conversion and advanced image manipulation, or download for straightforward file downloading capabilities.

5,251

Native Linux App for UI and UX Design built in Vala and GTK

Pros of Akira

  • Full-featured vector graphics editor with a modern UI
  • Supports complex design workflows and prototyping
  • Actively maintained with regular updates and new features

Cons of Akira

  • Larger project scope, potentially more complex to use
  • Focused on vector graphics, not specifically for DOM-to-image conversion
  • May have a steeper learning curve for basic image conversion tasks

Code Comparison

While a direct code comparison isn't relevant due to the different nature of these projects, here's a brief example of how they might be used:

dom-to-image:

domtoimage.toPng(document.getElementById('my-node'))
  .then(function (dataUrl) {
    var img = new Image();
    img.src = dataUrl;
    document.body.appendChild(img);
  });

Akira (hypothetical usage):

var design = new Akira.Design();
design.add_rectangle(100, 100, 200, 200);
design.export_as_png("output.png");

dom-to-image is a focused library for converting DOM elements to images, while Akira is a comprehensive vector graphics editor. dom-to-image is better suited for quick, programmatic image generation from web content, whereas Akira excels in creating and editing complex vector graphics designs.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

DOM to Image

Build Status

What is it

dom-to-image is a library which can turn arbitrary DOM node into a vector (SVG) or raster (PNG or JPEG) image, written in JavaScript. It's 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.

Installation

NPM

npm install dom-to-image

Then load

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

Bower

bower install dom-to-image

Include either src/dom-to-image.js or dist/dom-to-image.min.js in your page and it will make the domtoimage variable available in the global scope.

<script src="path/to/dom-to-image.min.js" />
<script>
  domtoimage.toPng(node)
  //...
</script>

Usage

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');

domtoimage.toPng(node)
    .then(function (dataUrl) {
        var img = new Image();
        img.src = dataUrl;
        document.body.appendChild(img);
    })
    .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:

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

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

function filter (node) {
    return (node.tagName !== 'i');
}

domtoimage.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);
          }
        }
    });

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


Rendering options

filter

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.

bgcolor

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.

style

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.

quality

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

cacheBust

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

imagePlaceholder

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

Browsers

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.`

Dependencies

Source

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

Tests

Most importantly, tests depend on:

  • js-imagediff, to compare rendered and control images

  • 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!

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.

Authors

Anatolii Saienko, Paul Bakaus (original idea)

License

MIT

NPM DownloadsLast 30 Days