markdown2pdf
markdown2pdf is a versatile command-line tool and library designed to convert Markdown content into pre-styled PDF documents. It uses a lexical analyzer to parse the Markdown and a PDF module to generate PDF documents based on the parsed tokens.
The library employs a pipeline that first tokenizes Markdown text into semantic elements (like headings, emphasis, code blocks, and lists), then processes these tokens through a styling module that applies configurable visual formatting. The styling engine supports extensive customization of fonts, colors, spacing, and other typographic properties through a TOML configuration file. For more information on how to configure the styling rules, please refer to the Configuration section down below.
This project includes both a binary and a library:
- Binary (cli): A command-line interface that provides an easy way to convert Markdown files, URLs, or direct string input into styled PDF documents. Supports custom styling through configuration files.
- Library (lib): A robust Rust library that can be integrated into your projects for programmatic Markdown parsing and PDF generation. Offers fine-grained control over the conversion process, styling rules, and document formatting.
Note: This project is under active development and welcomes community contributions! We're continuously adding new features and improvements. If you have suggestions, find bugs, or want to contribute:
- Open an issue for bugs or feature requests
- Submit a pull request to help improve the project
- Check our CONTRIBUTING.md guide for development guidelines
Install
You can install the markdown2pdf binary globally using cargo by running:
If you want to install the latest git version:
Install as library
Run the following Cargo command in your project directory:
Or add the following line to your Cargo.toml:
= "0.1.3"
Usage
To use the markdown2pdf tool, you can either specify a Markdown file path, provide Markdown content directly, or set the output PDF path.
Options
-p,--path: Specify the path to the Markdown file to convert.-s,--string: Provide Markdown content directly as a string.-u,--url: Specify a URL to fetch Markdown content from.-o,--output: Specify the output file path for the generated PDF.
Examples
-
Convert a Markdown file to a PDF:
Convert the 'resume.md' file in the 'docs' folder to 'resume.pdf'.
-
Convert Markdown content provided as a string:
Convert the provided Markdown string to 'output.pdf'.
-
Convert Markdown from a URL:
Convert the Markdown content from the URL to 'readme.pdf'.
Notes
- If multiple input options (-p, -s, -u) are provided, only one will be used in this order: path > url > string
- If no output file is specified with
-o, the default output file will be 'output.pdf'.
Using as Library
The library exposes a high-level parse() function that orchestrates the entire conversion process. This function accepts raw Markdown text and an output path, handling all intermediate processing steps internally. Under the hood, it leverages the lexer to build an abstract syntax tree, applies styling rules from configuration, and renders the final PDF output. For basic usage, simply pass your Markdown content as a string to parse().
For more advanced usage, you can work directly with the lexer and PDF generation components. First, create a lexer instance to parse your Markdown content into tokens
let mut lexer = new;
let tokens = lexer.parse.unwrap; // handle errors
Next, you'll need to create a PDF renderer to transform the tokens into a formatted document. Before initializing the renderer, you'll need to define styling rules through a StyleMatch instance. See the Configuration section below for details on customizing the styling rules.
let style = load_config;
let pdf = new;
let document = pdf.render_into_document;
Finally, the Document object can be rendered to a PDF file using the Pdf::render() function. This function handles the actual PDF generation, applying all the styling rules and formatting defined earlier. It takes the output path as a parameter and returns a Result indicating success or any errors that occurred during rendering:
Configuration
The markdown2pdf tool supports customization through a TOML configuration file. You can configure various styling options for the generated PDFs by creating a markdown2pdfrc.toml file in your home directory, or by specifying a custom configuration file path.
Under the hood the file is translated to the StyleMatch instance which determines how different Markdown elements will be rendered in the final PDF. When using the library, you can load custom styling configurations using config::load_config() or create a custom StyleMatch implementation. For direct binary usage, the tool automatically looks for a configuration file in your home directory.
The configuration file supports customization of fonts, colors, spacing, and other visual properties for all Markdown elements. When using the library, you can also programmatically override these settings by modifying the StyleMatch instance before passing it to the PDF renderer.
Custom Configuration Path
When using markdown2pdf as a library, you can specify a custom configuration file path. This is particularly useful for library usage, project-specific configurations, or when you want to maintain multiple configuration files:
Use custom config path - supports both relative and absolute paths
parse?;
parse?;
Use default config (~/markdown2pdfrc.toml or ./markdown2pdfrc.toml)
parse?;
Error Handling: If the specified configuration file cannot be found or contains invalid syntax, the library will gracefully fall back to default styling without crashing. This ensures that PDF generation always succeeds, even with configuration issues.
Getting Started with Configuration for binary
-
Create the config file:
-
Copy the example configuration:
- View the example config at markdown2pdfrc.example.toml
- Copy the contents to your
~/markdown2pdfrc.tomlfile - Modify the values according to your preferences
Contributing
For information regarding contributions, please refer to CONTRIBUTING.md file.