Format comparison

Which file formats convert best to Markdown

Structured formats convert almost perfectly. Scanned images do not. Everything else sits in between, and the gap usually shows up in tables rather than in the prose. Below is what each source format actually gives you, including where it falls down.

Accuracy and table fidelity by source format

Text accuracy is the share of source text that survives conversion with its structure intact. CSV, JSON and XML hit 100% because they are already structured text — there is nothing to interpret. Scanned images sit lowest because OCR is a best guess.

FormatText accuracyTablesTypical timeBest for
CSV.csv100%excellent1 secondDatabase exports
JSON.json100%excellent1 secondAPI documentation
XML.xml100%good1-2 secondsLegacy system data
Excel.xlsx .xls99%excellent2-4 secondsData tables and datasets
Word.docx .doc98%excellent1-2 secondsDraft documents
HTML.html .htm98%excellent1-2 secondsWeb scraping projects
EPUB.epub97%good2-3 secondsE-books and novels
PowerPoint.pptx .ppt96%good2-4 secondsTraining materials
PDF.pdf95%good3-5 secondsScanned documents
ZIP.zip95%variesvaries by contentBatch document processing
Audio.mp3 .wav .m4a .ogg90%n/a10-30 secondsPodcast transcription
Image.jpg .jpeg .png .gif .bmp .tiff .webp85%fair4-8 secondsScanned documents

Measured on our own conversion pipeline across a mixed corpus. Your documents will vary — a clean native PDF beats a photographed one by a wide margin, and both are counted as “PDF” here.

What each format costs you

Every format loses something. Knowing what, before you convert a few hundred files, is usually more useful than the accuracy number.

CSV

100% · low effort

Rows and columns survive intact.

  • No formatting support
  • Encoding issues with special characters

JSON

100% · low effort

Rows and columns survive intact.

  • Deeply nested structures may be complex
  • Large files require memory

XML

100% · medium effort

Usually clean; complex merged headers need a look.

  • Verbose format
  • Schema validation may be complex

Excel

99% · medium effort

Rows and columns survive intact.

  • Formulas converted to values
  • Multiple sheets require individual processing
  • Complex charts simplified to data tables

Word

98% · low effort

Rows and columns survive intact.

  • Older .doc format may have compatibility issues
  • Complex macro-enabled documents need special handling

HTML

98% · low effort

Rows and columns survive intact.

  • JavaScript-rendered content requires pre-processing
  • External CSS may affect formatting

EPUB

97% · low effort

Usually clean; complex merged headers need a look.

  • DRM-protected files cannot be converted
  • Interactive features lost

PowerPoint

96% · medium effort

Usually clean; complex merged headers need a look.

  • Visual layouts simplified to text
  • Animations and transitions lost
  • Speaker notes preserved separately

PDF

95% · medium effort

Usually clean; complex merged headers need a look.

  • OCR accuracy varies with scan quality
  • Complex layouts may require manual review
  • Encrypted PDFs need password

ZIP

95% · medium effort

Depends entirely on the source markup.

  • Password-protected archives need password
  • Very large archives may time out
  • Nested ZIPs require multiple passes

Audio

90% · high effort

No tabular content to preserve.

  • Background noise affects accuracy
  • Multiple speakers require separation
  • Accents and dialects may impact quality
  • Long files take more time

Image

85% · high effort

Simple tables fine, nested layouts drift.

  • Accuracy depends on image quality
  • Handwriting recognition limited
  • Complex layouts may need manual review
  • Low-resolution images yield poor results

Picking a source format

If you control the export, choose CSV, JSON or XML. They are already structured text, so conversion is lossless and instant. This is the single biggest quality decision available to you, and it happens before anything reaches a converter.

Word and EPUB are the best of the “real document” formats. Both carry explicit heading structure, which is what makes the resulting Markdown useful to a language model rather than just readable.

PDF is the one to watch. A native PDF converts well. A scanned or photographed one goes through OCR, and accuracy then depends on the scan rather than on the converter. If your corpus mixes both, expect two very different quality tiers under one file extension.

Spreadsheets need a decision about formulas. Conversion keeps computed values, not the expressions behind them. For an audit trail you want the source file kept alongside the Markdown.

Convert one and see

The numbers above are averages. The only reliable test is your own worst document — a dense table, a scanned page, a deck with speaker notes.

Start building today

Ship Markdown workflows with confidence

Convert documents, sync to your stack, and automate AI/LLM pipelines without managing infrastructure.