Convert a GitHub README to PDF
Convert a GitHub README to PDF by pasting its raw Markdown and saving a clean PDF with tables and highlighted code intact, all in your browser. Your README never leaves your device, and the tool keeps working offline.
Your README is processed on your device only.
How it works
- Open your README on GitHub, click Raw, and copy the Markdown.
- Paste it here, then choose page size and a light or dark theme.
- Click Print or Save as PDF to download the rendered document.
Why you paste the Markdown instead of a URL
The site is built so it cannot upload or download anything: its content security policy allows network connections only back to itself, which is how the privacy guarantee is enforced rather than merely promised. The trade-off is that it cannot fetch a file from github.com for you, so you paste the raw README source. It is one extra copy, and in return nothing about your project touches a third-party server.
If you already have the file locally, the Markdown to PDF converter takes the .md file directly. See how browser-side rendering works.
GFM, code, and what does not render
A README converts with GitHub Flavored Markdown: tables, task list checkboxes, strikethrough, fenced code with syntax highlighting, and fenced mermaid diagrams. What does not appear are assets that would need a network fetch, namely external badge images and images linked by a relative repo path, since the tool loads nothing from the network.
For a README that is mostly code samples, the code to PDF converter focuses on a single highlighted snippet instead of a full document.
Frequently asked questions
- Why can't it pull my README straight from a GitHub URL?
- By design the tool makes no network requests: nothing is fetched and nothing is uploaded, which is what keeps it private and offline-capable. That same rule means it cannot reach github.com to download a file, so you paste the raw Markdown instead. Open the README, copy its source, and paste it in.
- Do badges and images show up?
- External badge images (like shields.io) and images referenced by a relative repo path are not loaded, because the tool fetches nothing from the network. Text, GFM tables, task lists, and highlighted code all render, and mermaid diagrams are drawn in the browser. Inline base64 images embedded in the Markdown do appear.
- Does it support GitHub Flavored Markdown?
- Yes. GFM tables, task list checkboxes, strikethrough, and autolinks are supported, fenced code blocks are syntax highlighted, and fenced mermaid blocks are rendered as diagrams, so a typical project README converts faithfully.
- Is my README uploaded anywhere?
- No. Parsing, highlighting, and rendering all happen in your browser on your device. The Markdown never leaves the machine, there is no account, and the converter keeps working with the network disconnected.