Drop a PDF and get its text back as clean Markdown — headings, paragraphs and reading order intact, converted in your browser.
Converted in your browser — the file is never uploaded. 20MB limit.
A PDF is a description of where ink goes on a page, not a document with structure, which is why copying out of one gives you text with the line breaks in the wrong places and no headings at all. This converter reads the text runs pdf.js extracts, measures the font sizes across the whole document, and uses the outliers to work out which lines were headings — so a report comes back as # and ## rather than a wall of paragraphs. Everything happens inside your browser tab: the file is never uploaded, which matters when the PDF is a contract, a medical letter, or an unreleased spec. The most common reason people want pdf to markdown now is feeding a document to an AI model or a docs repo, and both want structure, not a screenshot of a page.
A support lead is moving a vendor’s 24-page integration guide into their team’s internal docs, which are Markdown files in a Git repo. Selecting the text in a PDF reader and pasting it gives them one continuous block: every line wrapped where the page column ended, the section titles indistinguishable from body text, and the numbered steps run together. Rebuilding the outline by hand for 24 pages is the kind of job that gets postponed forever. They drop the PDF here instead. The heading levels come back because the guide’s section titles are set several points larger than its body copy, so the converter can tell them apart. The file chip reports 24 pages with a text layer, so they know nothing was quietly skipped. They download document.md, paste it into integration-guide.md, spend ten minutes fixing the two tables that did not survive, and open the pull request the same afternoon.
Free links last 7 days with a free account. On a paid plan every page you create stays online permanently.
See pricing