The original visual source. It remains the authority for what appears on each page.
Level 1 · Overview
How PDFMD converts a PDF into structured Markdown
PDFMD reconstructs the logical document—text, paragraphs, lists, notes, tables, page relationships, and meaningful visual evidence—without trying to reproduce the page design.
The deployed converter performs this route with deterministic orchestration and OCR. It does not call an LLM.
The problem
A PDF describes pages, not necessarily a document
A PDF reliably records marks and positions. It may not state that two lines are one paragraph, a number is a page label, or a note belongs to a marker in the body. Recognition infers those relationships and records the source evidence for each decision.
The records
PDF, PDFMD, and Markdown
PDFMD
A document record written in extended Markdown. It stores meaning, page provenance, uncertainty, and asset references.
Markdown
A disposable reading view generated from PDFMD. Changing view settings does not change the canonical record.
Recognition bundle
Detailed observations used for diagnosis and evaluation. The current browser download contains PDFMD, human Markdown, and referenced assets; development runs may retain a separate bundle.
Responsibility
Script, model, and human roles
Documentation map
Continue by subject
Historical recognition gate
Why English text conservation is blocked, what the evidence shows, and what must happen next.
Conversion
Input checks, native and scanned routes, evidence, semantic decisions, PDFMD, and output.
Recognition methods
Paragraphs, lists, type, notes, tables, page furniture, and graphics.
Review and decisions
Supported assertions, unresolved alternatives, bounded model requests, and human corrections.
PDFMD and rendering
The canonical format and the generation of different Markdown views.
Operations
Live conversion, background analysis, retention, and deployment boundaries.
Development and evaluation
Human-built references, two freezes, correction cycles, and independent evaluation.