Markdown is source; PDF is the handout
Markdown is designed for git and editors: # headings, - lists, code, and optional tables. Browsers and chat apps preview it; printers do not. Markdown to PDF on ToolPin renders that source into a paginated PDF so you can email or print it. The file is uploaded to a temporary server, converted, and deleted after download. The tool is free and does not require signup.
This is not the same as Markdown to HTML in the text tools. That utility stays in the browser and returns HTML you can paste into a page. This tool returns a PDF and therefore needs a print pipeline on the server.
Which Markdown flavour to expect
Write portable Markdown: ATX headings (#, ##), emphasis, links, images by URL or that the engine can fetch, fenced code blocks with a language hint, and GitHub-style tables if you need grids. Footnotes, definition lists, and raw HTML may be ignored or sanitized. YAML front matter (title, author between --- lines) is often stripped rather than used as a cover page — put the title in an H1 if it must appear.
Keep one H1. Use H2/H3 for sections. Deep heading stacks look cramped on paper. Horizontal rules become thin lines; do not use them as a design system.
Code blocks are the usual print problem. Long lines wrap or clip. Keep examples narrow, or accept wrap. Line numbers are not added unless your source already contains them.
Images, links, and size
Relative image paths like ./diagram.png will not resolve on a server that only received the .md file. Use absolute https URLs for images, or embed is not available here the way a local pandoc run with a working directory is. If diagrams matter, export them as PDF pages separately and merge with the browser-local Merge PDF tool after you have this PDF.
Links in the PDF are often clickable if the renderer keeps them. Printouts obviously are not — write important URLs in full if the paper copy is the deliverable.
A Markdown file itself is tiny; the PDF grows with images and fonts. That is normal.
Privacy and what not to upload
The .md is sent to the server. Do not paste secrets, API keys, or unpublished security write-ups into a file you upload. For private notes, run pandoc locally. ToolPin deletes the job after download, but you still transmitted the text.
After you download
Skim every page. Markdown tables wider than the page will break; split columns or convert that section to a list. If you need tighter control (custom CSS, A4 margins, syntax highlighting themes), a local toolchain is the right next step. ToolPin is the quick path: free, no account, good enough for READMEs, class notes, and internal specs.
Related: RTF to PDF and DOCX to PDF if the source is not Markdown; HTML to Text if you are going the other way from markup.