Screenshots with JavaScript
Go to file
Niklas von Hertzen 6020386bbe
examples: fix duplication (#2813)
2022-01-23 00:27:44 +08:00
.github ci: add ios 15.0 testing (#2780) 2021-12-29 21:02:16 +08:00
configs test: include reftests previewer with docs website (#1799) 2019-04-12 23:17:23 -07:00
docs feat: add support for webkit-text-stroke and paint-order (#2591) 2021-07-15 18:19:26 +08:00
examples examples: fix duplication (#2813) 2022-01-23 00:27:44 +08:00
scripts deps: update dependencies with lint fixes (#2565) 2021-07-11 20:25:22 +08:00
src fix: Properties x and y of BoundingRect is undefined in old browser (#2797) 2022-01-23 00:18:49 +08:00
tests feat: add support for <video> elements (#2788) 2022-01-02 16:14:27 +08:00
www ci: add ios 15.0 testing (#2780) 2021-12-29 21:02:16 +08:00
.babelrc build: update webpack and babel (#1793) 2019-04-07 14:24:17 -07:00
.editorconfig ci: build docs (#2305) 2020-07-31 19:21:02 +08:00
.eslintrc deps: update dependencies with lint fixes (#2565) 2021-07-11 20:25:22 +08:00
.gitignore Typescript conversion (#1828) 2019-05-25 15:54:41 -07:00
.npmignore update npm build (#2316) 2020-08-08 16:00:41 +08:00
.prettierrc Typescript conversion (#1828) 2019-05-25 15:54:41 -07:00 Update 2022-01-23 00:24:05 +08:00
LICENSE updated license formatting 2012-12-28 19:46:23 +02:00 docs: update README to github discussion Q/A 2021-07-17 17:24:15 +08:00
jest.config.js fix: correctly respect logging option (#2013) 2019-09-25 03:37:59 -07:00
karma.conf.js ci: add ios 15.0 testing (#2780) 2021-12-29 21:02:16 +08:00
package-lock.json chore(release): 1.4.1 2022-01-22 16:19:57 +00:00
package.json chore(release): 1.4.1 2022-01-22 16:19:57 +00:00
rollup.config.ts fix: source maps (#2787) 2022-01-02 16:08:10 +08:00
tsconfig.json deps: update dependencies with lint fixes (#2565) 2021-07-11 20:25:22 +08:00


Homepage | Downloads | Questions

Gitter CI NPM Downloads NPM Version

JavaScript HTML renderer

The script allows you to take "screenshots" of webpages or parts of it, directly on the users browser. The screenshot is based on the DOM and as such may not be 100% accurate to the real representation as it does not make an actual screenshot, but builds the screenshot based on the information available on the page.

How does it work?

The script renders the current page as a canvas image, by reading the DOM and the different styles applied to the elements.

It does not require any rendering from the server, as the whole image is created on the client's browser. However, as it is heavily dependent on the browser, this library is not suitable to be used in nodejs. It doesn't magically circumvent any browser content policy restrictions either, so rendering cross-origin content will require a proxy to get the content to the same origin.

The script is still in a very experimental state, so I don't recommend using it in a production environment nor start building applications with it yet, as there will be still major changes made.

Browser compatibility

The library should work fine on the following browsers (with Promise polyfill):

  • Firefox 3.5+
  • Google Chrome
  • Opera 12+
  • IE9+
  • Safari 6+

As each CSS property needs to be manually built to be supported, there are a number of properties that are not yet supported.


The html2canvas library utilizes Promises and expects them to be available in the global context. If you wish to support older browsers that do not natively support Promises, please include a polyfill such as es6-promise before including html2canvas.

To render an element with html2canvas, simply call: html2canvas(element[, options]);

The function returns a Promise containing the <canvas> element. Simply add a promise fulfillment handler to the promise using then:

html2canvas(document.body).then(function(canvas) {


You can download ready builds here.

Clone git repository:

$ git clone git://

Install dependencies:

$ npm install

Build browser bundle

$ npm run build


For more information and examples, please visit the homepage or try the test console.


If you wish to contribute to the project, please send the pull requests to the develop branch. Before submitting any changes, try and test that the changes work with all the support browsers. If some CSS property isn't supported or is incomplete, please create appropriate tests for it as well before submitting any code changes.