# 📘 EPUB to PDF CLI – Node.js EPUB to PDF Converter using Calibre

epub-to-pdf-cli is a fast and reliable Node.js command-line tool to convert EPUB files to PDF using Calibre.

It supports CLI usage, automation scripts, CI pipelines, and programmatic Node.js integration.

This tool is ideal for:

• Developers
• Automation pipelines
• Ebook processing
• Batch EPUB to PDF conversion

✨ Features

• Convert EPUB to PDF using Calibre
• Simple CLI (epub2pdf)
• Programmatic Node.js API
• Cross-platform (Linux, macOS, Windows)
• No bundled binaries (uses system Calibre)
• Lightweight and fast
• Clear error handling

📦 Installation

Global install (CLI)

npm install -g epub-to-pdf-cli

After installation, the epub2pdf command will be available globally.

Or run without installing

npx epub-to-pdf-cli book.epub

🖥 CLI Usage

epub2pdf <input.epub> [output.pdf]

Examples
epub2pdf mybook.epub
epub2pdf mybook.epub mybook.pdf

This converts an EPUB ebook file into a PDF document using Calibre.

📚 Programmatic Usage

bash

npm install epub-to-pdf-cli

js

import { convertEpubToPdf } from 'epub-to-pdf-cli';

await convertEpubToPdf('book.epub', 'book.pdf');

This makes the package suitable for Node.js scripts, backend services, and automation workflows.

⚙ Requirements

This package requires Calibre to be installed.

Verify installation:

bash

ebook-convert --version

Install Calibre

Ubuntu/Debian

sudo apt install calibre

macOS

brew install calibre

Windows

Download from: https://calibre-ebook.com/download

❌ Common Errors & Solutions

ebook-convert not found

→ Install Calibre and ensure it is in PATH.

Cause: Calibre is not installed or not in PATH

Solution: Install Calibre and restart your terminal

→ Input EPUB file does not exist

Cause: Invalid file path

Solution: Check the EPUB file path and permissions

🔖 Versioning & Breaking Changes

This project follows Semantic Versioning using Conventional Commits.

Commit Types

• fix: → Patch release
• feat: → Minor release
• feat!: → Major release (breaking change)

Breaking Changes

Any change that breaks existing usage must be marked as a breaking change.

Example:

git commit -m "feat!: change CLI input format"

📄 License

MIT © Suraj Sutar