Markdown을 PDF로

Click Upload and pick a .md, .markdown, or .txt file, or paste the text into the left pane, and the rendered preview appears on the right. Click Export PDF or press Ctrl+S (Cmd+S on a Mac), then choose Save as PDF as the destination in the print dialog that opens.

Set those in the print dialog: choose Letter, A4, or another paper size, adjust the margins, and lower the scale if a wide table gets cut off. Turn off Headers and footers there too if you don't want the date and URL printed on each page.

Fenced code blocks get syntax highlighting for JavaScript, TypeScript, Python, Go, Rust, Java, C#, C++, SQL, Bash, YAML, JSON, HTML, and CSS, and standard pipe tables render as tables. Mermaid code blocks are drawn as flowcharts, sequence diagrams, and other chart types in both the preview and the PDF.

Task lists, footnotes, definition lists, abbreviations, subscript and superscript, ==highlight== and ++insert++ marks, emoji shortcodes like :smile:, and automatic linking of bare URLs. The settings dialog has switches for raw HTML, line breaks, autolinking, and typographic quotes.

No. The theme toggle only changes the editor colors on screen; the print stylesheet forces a white background and dark text, so the PDF looks the same either way.

Put ${toc} on its own line where you want it and a table of contents is generated from your headings when the document renders. Headings also get anchor IDs, so in-document links to a heading work in the preview.

Use standard Markdown image syntax with a full image URL or a data URI and the image renders in the preview and prints into the PDF. Relative paths to files on your disk won't load, because the editor has no access to your local folders.

No. The Markdown is rendered to HTML by markdown-it in your browser and the PDF is created by the browser's print function, so neither the text nor the finished PDF touches a server. Notes, drafts, and internal docs stay on your machine.