OmniDocConvert PDF to Markdown on Mac Step by Step
Convert a PDF to Markdown on your Mac by exporting it to Word in the OmniDoc desktop client, then cleaning up headings, tables and lists for a .md file.
If you work on a Mac and need to move a PDF into Markdown, you have probably hit the same wall: PDFs store text as positioned characters, not as headings, lists and tables. Copying and pasting into a plain text file loses the structure, and the result is hard to read and harder to reuse in a README, a static site or a notes app. This guide is for Mac users who want a clean .md file and are willing to do a short cleanup pass.
The method below uses the OmniDoc desktop client for macOS to prepare the content. You export the PDF to Word first, because Word files keep headings, lists and tables as real structure that you can check and fix. Then you move that structure into Markdown syntax and save the file.
You will get a repeatable workflow: check the PDF, run OCR if needed, export to Word, clean up, convert, and verify. You will also see what to look for if you are comparing free options.
How do I convert a PDF to Markdown on a Mac? The short answer
Export the PDF to Word in the OmniDoc desktop client, fix the structure in the Word file, then write that content out as a UTF-8 .md file and check it in a Markdown preview.
| Your situation | What to do | Why |
|---|---|---|
| The PDF has selectable text | Export it straight to Word in the desktop client | Headings, lists and tables are easier to keep when the text is already live |
| The PDF is a scan | Run OCR in the PDF editor, then export to Word | Scanned pages are images, so there is no text to export until OCR adds it |
| The PDF is long, with many tables | Export, then check each table before converting | Tables are a common place where structure is lost |
| The PDF has equations or code | Export, then rebuild them by hand in Markdown | Complex formatting rarely maps cleanly, so review those parts closely |
| You only need the text | Export to Word, copy the clean text, and add Markdown headings | Less cleanup is needed when you skip the layout details |
Before you start
Check these items before you open the file. They save you from redoing work later.
- Mac version and client. Download the OmniDoc desktop client for macOS from download.omnidoc.top and install it the way you install any other Mac app. Working in the desktop client keeps your PDF on your machine while you prepare it.
- Whether the PDF is digital or scanned. Open the PDF and try to select a line of text. If the cursor selects words, the text is live. If nothing is selected, the page is probably an image, and you need OCR before export.
- Where the Markdown will go. A README, a documentation site, and a notes app each use Markdown a little differently. Knowing the target tells you whether you need plain headings and lists or more advanced syntax like tables and code blocks.
- Whether images need to stay. Markdown does not embed images the way Word does. If the PDF has figures you want to keep, plan a folder for the image files and a relative link path before you start.
- Encoding of the final file. Save the .md file as UTF-8. Mismatched encodings are a common cause of broken accented letters, curly quotes and symbols after conversion.
Converting a PDF to Markdown on your Mac, step by step
- Open the PDF in the desktop client. Launch OmniDoc on your Mac and open the file you want to convert. Keep the original PDF untouched so you can compare against it later.
- Check whether the text is selectable. Select a line or two of body text. If you can select it, you can skip OCR. If you cannot, go to the next step first.
- Run OCR on scanned pages. Use the OCR option in the PDF editor to add a text layer to the scanned pages. This step makes the text available for export, but you should still read the output carefully for misread characters.
- Export the PDF to Word. Use the export function in the PDF editor and choose Word as the format. Word keeps paragraphs, heading levels, lists and tables as separate elements, which is what you need for a clean Markdown result.
- Clean up the Word file. Open the .docx and review the headings, bulleted and numbered lists, and tables. Remove repeated headers and footers, page numbers, and stray line breaks that came from the PDF page layout. Apply Word heading styles where the structure is clear.
- Convert the content to Markdown. Write the cleaned text into a plain text file and add Markdown syntax:
#for headings,-for bullets,1.for numbered lists, and pipe tables for simple grids. You can do this by hand for a short document, or use a general-purpose document converter that outputs Markdown for longer ones. Check the output against the Word file section by section. - Save and verify the .md file. Save the file with a
.mdextension and UTF-8 encoding. Open it in a Markdown preview, then run through the checks in the next section.
Check the result
Once you have the .md file, work through this table. It covers the problems that show up most often after a PDF-to-Word-to-Markdown conversion.
| Check | How to see it | If it's wrong |
|---|---|---|
| Heading levels | Preview the file and look at the outline | Reassign #, ## and ### to match the Word heading styles |
| Lists | Confirm each item starts on its own line | Add a blank line before the list and make sure every item starts with - or 1. |
| Tables | Check the column count and row alignment in the preview | Rebuild the table by hand, or simplify it if it has merged cells |
| Special characters | Look for odd symbols, curly quotes or garbled accents | Re-save as UTF-8 and correct characters against the original PDF |
| Equations and code | Compare against the PDF page by page | Rewrite equations as plain text, or put code in fenced code blocks |
| Images | Check for missing picture references | Save images as separate files and link them with relative paths |
| Reading order | Read the preview from top to bottom | Move paragraphs back into order, especially in multi-column pages |
Machine-generated text and OCR can both introduce mistakes, so compare every important sentence, number and citation with the original PDF before you publish the file.
Choosing a free PDF to Markdown option on a Mac
Many people searching for a free option want to know what to look for, not a single answer. When you compare free tools, check these points in the tool's own documentation or by testing it with a sample page:
- File size and page limits. A free tier may restrict how large or how long a file can be.
- Watermarks or branding in the output. Confirm that the exported file is clean.
- Where your file goes. If the tool uploads your PDF to a server, check its privacy terms before you upload a confidential document.
- Whether structure survives. Test a page with a heading, a list and a table. If those break, the tool will cost you more time than it saves.
A workflow that exports to Word first gives you a checkpoint you can inspect, whichever tool you use for the final Markdown step.
❓ FAQ
1. Is there a free way to convert PDF to Markdown on a Mac?
Free options exist, but they vary in file limits, watermarks, privacy and how well tables survive. Test any free tool on a page that has a heading, a list and a table before you rely on it for a full document.
2. Why does my Markdown look different after converting?
PDFs describe how text looks on a page, not what it means, so headings and lists have to be inferred. Word export gives you a better starting point, but you still need to check heading levels and list formatting.
3. Can I keep the images from my PDF in the Markdown file?
Yes, but Markdown only links to images rather than embedding them from Word. Save each figure as its own file, put the files in a folder next to the .md file, and link to them with relative paths, for example images/figure1.png.
4. Why are my tables broken after conversion?
Tables with merged cells, multi-line cells or no clear grid are hard to represent in Markdown. Simplify the table or rebuild it by hand, and check the column count in every row.
📝 Summary
Converting a PDF to Markdown on a Mac works well when you prepare the content first. Export to Word in the OmniDoc macOS desktop client, clean up the structure, and then write the .md file in UTF-8. Check headings, lists, tables and special characters in a preview before you publish.
