Convert Markdown to PDF in your browser
This page turns Markdown text into a clean PDF. Paste your text or open a .md file. The preview updates as you type. When it looks right, press Download PDF. The file never leaves your device (see the privacy policy), there is no watermark, and there is no limit on how many documents you make.
People use a markdown to pdf converter for README files, design docs, meeting notes, reports, résumés, and study notes. Markdown is easy to write and easy to keep in Git. A PDF is easy to share with people who do not use Markdown, such as a manager, a client, or a teacher.
How to convert a Markdown file to PDF
- Paste your Markdown into the editor, or press Open .md file. You can also drag a file onto the box.
- Check the preview. It shows the page at the paper size and margins you chose.
- Pick a theme, the paper size, the margins, and the text size. Turn on page numbers if you want them.
- Press Download PDF. Your browser opens its print dialog.
- Choose Save as PDF as the destination and save the file. The file name comes from your first heading.
On a phone, the Download button stays at the bottom of the screen, and the steps for iPhone and Android are under the tool.
The PDF has real text. You can select it, search it, and copy it. Links stay clickable. This is different from tools that take a picture of the page and put the picture in a PDF.
What Markdown does this converter support?
The converter reads GitHub-flavored Markdown. That covers what most README files and notes use.
| You type | You get |
|---|---|
# Title, ## Section | Headings, from level 1 to level 6 |
**bold**, *italic*, ~~gone~~ | Bold, italic, and strikethrough text |
| a | b | rows with a divider line | A table, with left, center, or right alignment |
- [x] done | A task list with checked and open boxes |
| Three backticks and a language name | A code block with syntax colors |
Text[^1] and [^1]: Note | A footnote that prints at the end |
> quote | A block quote with a bar on the left |
[Install](#install) | A link that jumps to the heading "Install", so a table of contents works |
<details> | A section that opens by itself in the PDF |
A line with only <!-- pagebreak --> or \pagebreak | A new page starts there |
A --- block at the top | Front matter (YAML). Hidden by default. Turn on "Print as a table" to show it |
$E = mc^2$ or $$ on its own lines | A formula, drawn only when your document has one |
A code block that starts with mermaid | A flowchart or another diagram |
> [!NOTE], [!TIP], [!WARNING] | A GitHub alert block with a colored bar |
:rocket: | An emoji |
A worked example
Say you keep a project README and need a PDF for a client. Open the file. The preview shows the title, the install steps, and a table of options. You choose the Technical theme because it fits the code blocks. You pick US Letter, normal margins, and page numbers. A README of about 600 words runs to about two pages, and the status line under the buttons shows the count. You press Download PDF, save the file, and send it. The whole job takes under a minute.
Paper sizes and margins
Use US Letter for the United States and Canada. Use A4 almost everywhere else. If you are not sure, ask the person who will print it.
| Option | Value | Good for |
|---|---|---|
| US Letter | 8.5 x 11 in | United States, Canada |
| A4 | 210 x 297 mm (8.27 x 11.69 in) | Europe, UK, Australia, and most other countries |
| Narrow margins | 0.5 in | Long tables and code, fewer pages |
| Normal margins | 0.75 in | Most documents |
| Wide margins | 1 in | Letters, essays, and anything you will bind or mark up |
| Text size 10, 11, 12 pt | Small, medium, large | Dense notes, normal reading, easy reading |
Why use this converter?
- Private. Conversion happens on your device. Your text is not uploaded.
- No watermark and no daily limit. Make as many PDFs as you like.
- Live preview. You see the page as you write, and the page count updates.
- Safe output. The converter removes scripts and unsafe HTML from your text before it shows the preview.
- Works on a phone. The editor and the preview stack, and the buttons are large.
Tips for a better PDF
- Add the language after the three backticks, for example
jsorpython, so the code gets colors. - Keep table cells short. Wide tables look best with narrow margins.
- Use headings in order. Level 1 for the title, level 2 for sections.
- Page numbers print in Chrome and Edge. Other browsers may skip them. If yours does, add the numbers in a PDF viewer.
- If you see a date or web address in the page margins, turn off "Headers and footers" in the print dialog.
- Images need a web address that allows hotlinking, or a
data:link. Local file paths do not load in a browser. Images you link load from their own server. - Your lines run together? That is normal Markdown. End a line with two spaces, or leave a blank line, to start a new line.
- Headings stay with the text after them, and short code blocks and table rows do not split across pages. Very long code blocks may split.
- Wide table or diagram? Choose Landscape in the Orientation menu.
- Need help? Write to us on the contact page.