Conservative output policy
Detected structures are not silently discarded. Unsupported review data, risky PDF layouts, and unsupported DOCX objects remain visible or stop the result.
Compatibility and coverage evidence
Know what each tool can verify before you rely on it.
Product claims stay tied to tested file structures, real fixtures, explicit warnings, and reproducible output.
ToolDecisionEvidence
Word reviewValidatedNative DOCX fixture
PowerPoint commentsValidatedLegacy + modern schemas
PDF to MarkdownBoundedFive layout categories
DOCX to MarkdownValidatedStructure + image assets
ChatGPT to WordValidatedStructure + style cleanup
Conversion evidence
Open the fixture-backed limits before choosing a Markdown workflow.
PDF coverage
Reading order, page markers, warnings, and scans
See what is validated for text-based PDFs and why some pages need review.
Open PDF evidenceDOCX coverage
Document structure, image bytes, and relative paths
See which Word objects move into the ZIP and which remain coverage warnings.
Open DOCX evidenceWord formatting coverage
AI text structure, cleanup, warnings, and Word output
See what is preserved, removed, reported, and verified in the generated DOCX.
Open ChatGPT to Word evidenceReview export evidence
Check the tested Office review structures before relying on an Excel handoff.
Word coverage
Comments, replies, anchors, and pending text changes
See which Word review signals become workbook rows and which remain explicit warnings.
Open Word evidencePowerPoint coverage
Legacy comments, modern replies, and thread status
See how verified presentation comment schemas become a sortable Excel register.
Open PowerPoint evidenceBrowser-local processing
Files and generated results stay in the browser. Quality events use categories and counts rather than document text, authors, file names, or output content.