Getting a PDF into Obsidian as Markdown

Dropping a PDF into your vault gives you an attachment. Converting it gives you a note.

Why the attachment is not enough

Obsidian will happily store a PDF in your vault and preview it. What it will not do is treat the contents as part of your notes. A PDF attachment:

• does not appear in search results for text inside it,
• cannot be linked to at a specific heading with [[note#section]],
• produces no backlinks and no graph connections,
• cannot be edited, quoted or transcluded into another note.

Converting it to Markdown turns the document into a first-class note that does all four.

The process

1. Convert the PDF to Markdown. Keep the headings — they become your [[note#heading]] link targets.
2. Save the .md into your vault folder. Obsidian picks it up immediately; no import step.
3. Add frontmatter for whatever your vault uses — source, tags, a date. iLoveMD writes a source line automatically so you can always trace a note back to its original file.

Keep the original

Conversion is lossy by design: page layout, images and exact pagination do not survive. For a contract or an invoice, keep the PDF in an attachments folder and link to it from the note. The Markdown is what you search and quote; the PDF remains the record.

Where extraction struggles

Worth knowing before you convert a hundred files:

• Scans have no text to extract. They need OCR first — otherwise you get an empty note.
• Multi-column academic papers can interleave columns; check the first page before trusting the rest.
• Complex tables may flatten into lines. If a document is mostly tables, convert it locally with a library that reconstructs grids.

This is the reason iLoveMD opens the result in an editor rather than downloading it straight away — you get to see what came out before it lands in your vault.

Questions people ask