Vivliostyle

Vivliostyle is an open-source publishing toolkit that turns standards-based HTML and CSS into paginated digital publications and PDFs. It suits developers, technical publishers, and production teams comfortable with web technologies who need browser previewing and scriptable output. Its strongest case is flexible, self-hosted typesetting; readers seeking a guided commercial book-production workflow should look elsewhere.

Overview

Founded in 2018 and maintained by the Vivliostyle Foundation in Saitama, Japan, the project focuses on web-standard typesetting for digital and web publishing. The browser-based Viewer renders HTML with CSS, and can also display EPUB files and web publications. Vivliostyle Pub adds an editing workspace for text, Markdown, or HTML with live typesetting preview, although its newer version is still in alpha and is therefore better suited to experimentation than a mission-critical editorial pipeline.

The project separates presentation from production: authors can preview in a browser, then run the CLI to typeset HTML and export finished files. Publications created with Vivliostyle do not have to publish their HTML or CSS source, which makes the tool practical for releasing compiled books while keeping source materials private.

Key features

Browser and command-line workflows

Vivliostyle Viewer is useful for checking pagination and CSS results without installing a desktop layout suite. It can load HTML hosted on GitHub or Gist, or be copied into a public web-server directory for use on a website. The CLI is the production engine: it accepts HTML and EPUB-related inputs, generates PDF, and can create PDFs from EPUB files. That division suits teams that want a shareable review link and a repeatable build command.

Formats, themes, and print output

Supported imports include HTML, Markdown, EPUB, EPUB OPF, publication manifests, and WebBook, while EPUB and PDF are available as exports. Themes are npm packages configured through vivliostyle.config.js, giving web developers a reusable way to standardize typography and page design across titles. For print workflows, the CLI supports PDF/X-1a through its PRESS-READY option. That option requires Ghostscript and Xpdf, adding setup and dependency management that less technical users may find inconvenient.

Standards-oriented licensing

Vivliostyle is released under AGPLv3. Modification and commercial use are allowed, but the reciprocal license obligations matter when you distribute modified software or integrate it into a service. This is a strong fit for organizations able to manage open-source compliance, and a poor fit for teams that require permissive licensing without copyleft conditions.

Pricing

There is no subscription, seat charge, or published quota. The cost advantage is substantial for self-hosted projects and automated publishing pipelines, but users take responsibility for installing Node.js, optional print-PDF dependencies, and maintaining their own workflow rather than receiving a packaged commercial service.

Platforms

Vivliostyle supports Linux, macOS, Windows, web use, and self-hosted deployment. The CLI requires Node.js, and its installation guidance covers macOS, Windows, and Linux. Viewer and Pub run in the browser, while self-hosting lets organizations place the viewer in their own web infrastructure.

Who it's for

Choose Vivliostyle if you publish books or web publications from HTML, Markdown, or EPUB, need CSS-driven control over page layout, or want reproducible PDF builds in scripts and CI systems. It is particularly well matched to developers, documentation teams, and publishers already using npm-based tooling. The alpha status of the newer Pub editor and the Node.js and Ghostscript/Xpdf requirements make it less suitable for nontechnical authors who expect a turnkey visual editor and managed exports.

Pros and cons

Pros

• Free and open source: there is no paid tier or stated usage ceiling, making large or repeated publishing runs economical.
• Web-standard control: HTML and CSS, npm themes, and browser previewing fit modern content pipelines.
• Broad publication output: EPUB and PDF export, including PDF/X-1a for print-oriented work.
• Flexible deployment: the viewer can be embedded on a web server or used with hosted GitHub and Gist files.

Cons

• Technical setup: CLI users need Node.js, and PRESS-READY PDF/X-1a output adds Ghostscript and Xpdf dependencies.
• Alpha editor: the new Pub version is not the safest choice for a mature editorial production line.
• AGPLv3 obligations: reciprocal licensing terms require careful compliance for modified or integrated deployments.

Alternatives

For a wider comparison, see Book Layout Software and eBook Creation Software.

• Kotobee Author is a freemium, cross-platform ebook tool with Android and iOS support; pick it when interactive ebook production and a broader app-device footprint matter more than Vivliostyle's code-first workflow.
• Coverfairy offers free and paid cover-generation plans; choose it when the immediate need is cover design rather than full typesetting.
• Folio Studio provides a free project-based plan with templates, EPUB, and watermark-free PDF; it is a better fit for guided template work.
• Koberger has a free formatting and preview account but requires Pro to export finished files; choose it for an account-based design workflow if paid exporting is acceptable.
• Storyloft combines manuscript limits, image credits, and AI conversations in its free tier; pick it when assisted writing and worldbuilding are central.
• Blurb BookWright is a desktop book-design application with templates and offline editing; choose it for conventional desktop photo-book layout.
• Bookmint offers web templates, print PDF, and EPUB in beta, with watermarked free exports; it suits browser-first template publishing.
• BookSetter provides a free beta package for one eligible book with limited corrective exports; choose it for a one-off guided edition.

Verdict

Vivliostyle is the right choice for technically capable publishers who want standards-based CSS layout, browser review, and repeatable EPUB/PDF generation without licensing fees. Its main reason to look elsewhere is the engineering overhead: Node.js, optional print dependencies, alpha editor status, and AGPLv3 compliance make a managed commercial layout platform more practical for teams that prioritize turnkey production.