Skip to content

docs: clarify built-in PDF conversion limitations #2215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JanCong wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify built-in PDF conversion limitations #2215

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,9 @@ MarkItDown currently supports the conversion from:
- EPubs
- ... and more!

> [!NOTE]
> The built-in PDF converter extracts text and attempts to preserve tables when they can be detected. Because PDF files encode visual layout rather than semantic structure, it may not infer headings, lists, or other Markdown structure, and the result may be mostly plain text. For layout-aware extraction, use [Azure Content Understanding](#azure-content-understanding) or [Azure Document Intelligence](#azure-document-intelligence).

## Why Markdown?

Markdown is extremely close to plain text, with minimal markup or formatting, but still
Expand Down