Turning a PDF into a Notion- or wiki-ready Markdown document

Moving a PDF's content into Notion, Obsidian, a GitHub wiki, or any other Markdown-based tool usually means either retyping the whole thing or pasting it in as one shapeless block of text with every heading, list, and table flattened into plain paragraphs.

How structure gets inferred from a PDF

A PDF doesn't actually store "this is a heading" or "this is a bulleted list" as a labeled concept the way a Word document or Markdown file does — it just has text positioned and sized on a page. PDF to Markdown works backward from that: text noticeably larger than the surrounding body text becomes a heading, lines starting with a bullet character or a number become a list, and text arranged in aligned columns becomes a Markdown table.

What carries over well, and what doesn't

• Clickable links in the original PDF are preserved as Markdown links, not just plain text.
• Cleanly formatted, single-column documents — reports, articles, simple guides — convert well with little cleanup needed.
• Dense multi-column layouts or unusual formatting are harder to infer correctly and may need manual touch-up afterward.
• A scanned PDF with no selectable text layer has nothing to extract — run OCR PDF first.

When you just want the raw text instead

If you don't need structure at all — just the words, to paste somewhere or search through — PDF to Text skips the heading/table inference entirely and exports a plain, line-broken text file instead.