Source · .md
Drop a .md file or images here
Paste Markdown, drop a .md file, or open one
Proof
A4 · page breaks follow the downloaded PDF
Live
Drop a CLAUDE.md, an AGENTS.md or any Markdown file your coding agent wrote, and download a clean PDF to review, annotate or share. Nothing is uploaded.
Paste Markdown, drop a .md file, or open one
CLAUDE.md is the file Claude Code reads at the start of every session: how to build and test the project, the conventions to follow, the things never to do. AGENTS.md is the same idea in a vendor-neutral file that several coding agents read. As these files grow, they become policy, and policy gets reviewed: by a tech lead, by security, by a new team member on their first day.
A PDF is the easy way to do that review. Drop the file here and it is typeset as a document: headings with bookmarks, commands in highlighted code blocks, tables, nested rules and Mermaid diagrams, ready to annotate on a tablet, attach to a ticket or print for a meeting. The same works for the plans, specs and reports Claude Code writes as .md files.
Instruction files are dense: nested lists of rules, commands in backticks, blocks of shell and config. In the PDF, commands stay in a monospaced face with syntax highlighting, lists keep their nesting, and tables keep their columns, so a reviewer can read the file the way the agent does, only more comfortably.
Ask Claude Code for a design plan, a migration checklist or a review summary and it writes Markdown, often with a Mermaid diagram of the architecture. Drop that file here to share it with people who do not live in a terminal. The diagrams become vector graphics, and a long plan gets a table of contents and page numbers.
Instruction files tend to mention internal hostnames, directory layouts and deployment steps. This page typesets them in your browser and cannot send them anywhere: its Content Security Policy forbids connections to other servers.
A project’s file is CLAUDE.md (or .claude/CLAUDE.md) in the repository root; personal instructions for every project are in ~/.claude/CLAUDE.md. Folders that start with a dot are hidden on macOS: press ⌘⇧. in a Finder window to show them.
Yes. They are all Markdown, so any of them converts the same way. Front matter at the top of a file is read for the options it knows, such as title, and anything else in it is ignored.
No. A line such as @docs/testing.md tells Claude Code to read another file; here it is printed as written. To review the whole set, paste the imported files below the main one, each under its own heading.
It can, by writing and running a conversion script with a tool such as pandoc or a PDF library, which has to be installed and sets the look. Here there is nothing to install, the layout is a proper typeset document, and the conversion never goes through the model or anyone’s server.
No. It is converted in this browser tab. If you edit it here, the text is kept as a draft in this browser only, until you press New.
save a ChatGPT answer as a clean PDF with its tables, code and formulas
export DeepSeek answers, formulas included, as a PDF
turn Claude answers and Markdown artifacts, Mermaid diagrams included, into a PDF
save Google Gemini responses as a typeset PDF
diagrams that render as vectors, with selectable text, in the PDF
a GitHub README.md as a PDF, with tables, code and diagrams
print a .md file with proper page breaks, diagrams and fonts