PDF → Markdown

PDFs are built to look correct on a page, not to be edited, linked, or searched. Obsidian is the opposite: every note is plain Markdown text that you can link, tag, and query. Getting PDF content into a vault means converting it into Markdown that keeps its structure — headings stay headings, tables stay tables — and then deciding how the resulting notes should be organized. This guide covers the conversion details that matter, a repeatable workflow, and the conventions that make imported material actually usable months later.

What a clean conversion should preserve

A PDF to Obsidian Markdown conversion is only useful if it keeps the structural signals Obsidian relies on. Check these after any conversion:

• Heading hierarchy. A chapter title should become #, a section ##, a subsection ###. Obsidian's outline pane, graph view, and most table-of-contents plugins depend on this. Flattened headings turn a document into an unstyled wall of text.
• Tables as pipe tables. Markdown tables with a header row, not images or tab-separated text, so you can sort, edit, and search them. Complex tables with merged cells need extra handling — that is covered in the guide to converting PDF tables to Markdown.
• Lists. Bullets and numbered lists should remain lists. They are easier to read and easier to reference from your own notes.
• Unwrapped paragraphs. PDFs break lines at page width. The converted Markdown should join those lines back into single paragraphs, otherwise editing and search results become noisy.
• Emphasis and inline code. Bold, italics, and monospace text often survive as Markdown or backticks.

Page numbers, running headers, and footers should be dropped. They repeat on every page and add nothing inside a vault.

A step-by-step PDF to Obsidian Markdown workflow

1. Convert the PDF to Markdown

Use a converter that outputs structured Markdown rather than plain text. The free PDF to Markdown converter produces headings, lists, and tables in one pass, and the step-by-step conversion walkthrough covers the settings to check. If your PDF is a scan — an image with no text layer — run OCR first; the process is described in the guide to converting scanned PDFs to Markdown. Keep the original PDF as well, stored in a sources/ or _attachments/ folder, so a note can always point back to the page it came from.

2. Split the output by chapter

Most PDFs convert into one long file. Before importing, decide where to split. Chapters are the natural unit for books, sections for papers and manuals, and one note per document for short references. Splitting after conversion is much faster than splitting inside Obsidian, because you can use the heading structure as your cut lines.

3. Clean up repeated artifacts

Run a few find-and-replace passes before the notes land in your vault: strip leftover page numbers, remove repeated headers and footers, and fix words broken across lines with hyphens. Also watch for ligature issues where fi or fl appear as odd characters. Keeping a short cleanup checklist saves you from repeating the same edits on every import.

4. Add frontmatter and rename files

Rename each file after its chapter or section title rather than keeping the converter's default name. Then add frontmatter — the next section covers what to include.

Frontmatter worth adding to converted notes

Consistent YAML frontmatter is what makes imported PDFs queryable later through search or Dataview queries. A workable minimum set:

Do not invent values you cannot verify. If the PDF does not state an author or year, leave the field empty instead of guessing — a wrong year will surface in every query you run later, and correcting it across dozens of notes is tedious. Obsidian's Properties panel edits YAML for you, so the format stays valid even if you never touch the raw text.

Folder structure and linking in your vault

Option A: one folder per source, one note per chapter

• Sources/Book Title/
  • Book Title.md — a hub note with frontmatter and links to every chapter
  • 01 Chapter One.md
  • 02 Chapter Two.md

The hub note keeps your graph readable and gives you a single place to track reading status. Chapter notes stay short enough to edit and cite precisely.

Option B: flat notes with tags

If you prefer a flat vault, name notes as Book Title - 01 Chapter One.md and rely on tags plus links for grouping. Search and backlinks do the work that folders would otherwise do. Pick one approach and apply it consistently; mixing both makes navigation unpredictable.

Linking the imported notes

• Link every chapter back to its hub note with a wikilink such as [[Book Title]].
• Add aliases in frontmatter for short forms of chapter titles that you will actually type.
• Use block references for lines you quote often, so your own notes can cite them precisely.
• Turn recurring terms into their own notes and link the first mention in each chapter rather than tagging every occurrence.
• Let backlinks and unlinked mentions surface connections instead of building a folder tree for every theme.

FAQ

Will the PDF's headings become Obsidian headings?

Usually yes, if the converter maps them. PDFs do not store semantic headings — they store styled text, and the converter has to infer which lines are headings from font size and weight. Converters that output Markdown do this; plain text extractors do not. Check the first chapter after conversion. If headings are missing, the PDF likely has an unusual layout or is a scan, and the OCR route will do better.

How do I keep tables as pipe tables?

Confirm the converter outputs GitHub-flavored Markdown tables with a header row. Simple tables convert reliably. Merged cells, multi-row headers, and tables that break across pages are the hard cases and often need a manual pass after conversion.

Should I convert a whole book into a single note?

Usually no. A note containing tens of thousands of words is slow to open and impossible to cite precisely, and you lose the benefit of linking to individual sections. Split by chapter and connect the pieces with a hub note. The exceptions are short papers, single-page references, and documents you plan to summarize and then discard.