Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time
November 1, 2018 14:53
March 15, 2023 17:12
July 3, 2018 17:38
March 31, 2020 15:01
March 15, 2023 17:12
January 28, 2023 13:55
May 2, 2023 14:16
May 2, 2023 14:16

Paged.js logo - pagination in the browser

Paged.js - Paged Media Tools

Paged.js is an open-source library to display paginated content in the browser and to generate print books using web technology.

It contains a set of handlers for CSS transformations and fragmented layout which polyfill the Paged Media and Generated Content CSS modules, along with hooks to create new handlers for custom properties.

The currently supported properties can be found on the pagedjs website.

A quick overview to getting started with Paged Media CSS and Paged.js is available on

NPM Module

$ npm install pagedjs
import { Previewer } from 'pagedjs';

let paged = new Previewer();
let flow = paged.preview(DOMContent, ["path/to/css/file.css"], document.body).then((flow) => {
	console.log("Rendered",, "pages.");


Add the the paged.polyfill.js script to replace all @page css and render the html page with the Paged Media styles applied:

<script src=""></script>

Try the polyfill with Aurorae.

By default the polyfill will run automatically as soon as the DOM is ready. However, you can add an async before function or return a Promise to delay the polyfill starting.

	window.PagedConfig = {
		before: () => {
			return new Promise((resolve, reject) => {
				setTimeout(() => { resolve() }, 1000);
		after: (flow) => { console.log("after", flow) },

Otherwise you can disable auto running the previewer and call window.PagedPolyfill.preview(); whenever you want to start.

	window.PagedConfig = {
		auto: false,
		after: (flow) => { console.log("after", flow) },

	setTimeout(() => {
	}, 1000);


Chunks up a document into paged media flows and applies print classes.



Converts @page css to classes, and applies counters and content.



Command line interface to render out PDFs of HTML files using Puppeteer:


Modules are groups of handlers for that apply the layout and styles of a CSS module, such as Generated Content.

New handlers can be registered from import { registerHandlers } from 'pagedjs' or by calling Paged.registerHandlers on an html page.

<script src=""></script>
	class MyHandler extends Paged.Handler {
		constructor(chunker, polisher, caller) {
			super(chunker, polisher, caller);

		afterPageLayout(pageFragment, page) {

Handlers have methods that correspond to the hooks for the parsing, layout and rendering of the Chunker and Polisher. Returning a promise or async function from a method in a handler will complete that task before continuing with the other registered methods for that hook.

// Previewer
beforePreview(content, renderTo)

// Chunker
afterPageLayout(pageElement, page, breakToken)
finalizePage(pageElement, page, breakToken)

// Polisher
beforeTreeParse(text, sheet)
afterTreeWalk(ast, sheet)
onDeclaration(declarationNode, ruleNode)
onContent(contentNode, declarationNode, ruleNode)

// Layout
renderNode(node, sourceNode, layout)
onOverflow(overflow, rendered, bounds)
onBreakToken(breakToken, overflow, rendered)
afterOverflowRemoved(removed, rendered)


Install dependencies

$ npm install


Run the local dev-server with livereload and autocompile on http://localhost:9090/

$ npm start


Build the dist output

$ npm run build

Compile the lib output

$ npm run compile

Generate legacy builds with polyfills included

$ npm run legacy


Testing for Paged.js uses Jest but is split into Tests and Specs.


Unit tests for Chunker and Polisher methods are run in node using JSDOM.

npm test


Specs run a html file in Chrome (using puppeteer) to test against CSS specifications.

They can also output a pdf and compare pages (one at a time) in that PDF with samples PDFs (saved as images).

The PDF comparison tests depend on the ghostscript and the ghostscript4js package.

It is recomend to run these in the Docker container below via:

npm run docker-specs

However if you'd like to run the specs outside of Docker, you'll need to install a local version of Ghostscript for your system according to

For Mac you can install it with

brew install ghostscript

For Debian you can install it with

sudo apt-get install ghostscript
sudo apt-get install libgs-dev

Now you can install the ghostscript4js library. For Linux you can optionally pass the location ghostscript was installed to in GS4JS_HOME.

GS4JS_HOME="/usr/lib/$(gcc -dumpmachine)" npm install ghostscript4js

To test the pdf output of specs, you'll need to build the library locally.

npm run build

Then run the jest tests in puppeteer.

npm run specs

To debug the results of a test in a browser you can add NODE_ENV=debug

NODE_ENV=debug npm run specs

To update the stored pdf images you can run

npm run specs -- --updateSnapshot


A pagedmedia/pagedjs docker image contains all the dependencies needed to run the pagedjs development server, as well as the pdf comparison tests.

To build the image run

docker build -t pagedmedia/pagedjs .

By default the container will run the development server with npm start

docker run -it -p 9090:9090 pagedmedia/pagedjs

The tests and specs can be run within the container by passing a seccomp file for Chrome and running npm test

docker run -it --security-opt 'seccomp=seccomp.json' pagedmedia/pagedjs npm test && npm run specs


Core team

The core team behind paged.js includes Adam Hyde, Julie Blanc, Fred Chasen & Julien Taquet.


MIT License (MIT), which you can read here