PDF to Word Conversion Quality: 24-File Test (2026)

·

Reproducible first-party product test

We submitted 24 controlled English PDFs to the live converter and inspected every returned DOCX. The service produced 22 downloadable outputs and 2 cases did not reach a downloadable result. This page publishes the method, per-file data, and source/output evidence.

Test run: August 13, 2026 | Data generated: August 13, 2026 | Last reviewed: August 17, 2026

Key results

In this run, 22 of 24 jobs reached the ready state and 22 outputs passed the DOCX package check. Across scored outputs, mean normalized character recall was 99.9% and mean token recall was 99.6%.

22/24Jobs that produced a downloadable DOCX
22/22Returned files that passed the DOCX package check
99.9%Mean normalized character recall across scored outputs
99.6%Mean normalized token recall across scored outputs
54.3%Mean word error rate; lower is better
3.19 sMedian observed time to the ready state

Editorial repair assessments: 0 ready without edits, 2 minor repair, 20 major repair, 2 failed.

A successful job is not the same as a faithful document. The service status only reports whether a downloadable file was produced. Text scores, document structure, and editorial repair assessments answer different quality questions and are reported separately below.

Why PDF-to-Word results vary

A PDF commonly records where text, pictures, and vector graphics appear on a page without storing all of the relationships that make an editable document, such as paragraphs, tables, and columns. A converter must infer those relationships. Microsoft describes the same structural problem in its official guide, Opening PDFs in Word (source reviewed 2026-08-13).

This is why the test separates text retention from editable structure. A table can retain every visible word while still becoming plain paragraphs, and an image caption can survive even when the image itself is missing.

How we ran the 24-file test

The corpus contained 22 digital files, 2 scanned files. All were processed through one recorded live run; results were analyzed offline from the saved run log and returned files.

  1. We created a controlled corpus of 24 synthetic English PDFs with stable case IDs, source hashes, and matching ground-truth text files.
  2. Each file was submitted individually to the live PDF to Word converter. Job states, public errors, output hashes, and observed times were recorded.
  3. Every returned DOCX was checked as an OOXML package. The analyzer counted paragraphs, tables, cells, media, drawing objects, section properties, page-break signals, external relationships, and macro indicators.
  4. Extracted text was compared with the ground truth using the published normalization rules. Word page rendering was unavailable, so returned DOCX files were assessed from extracted text and measured OOXML structure rather than from Word screenshots.

The complete procedure, normalization profile, run metadata, and analyzer definitions are included in the downloadable methodology.

What each metric means

Ready
The live job reached the service state ready. It does not mean the output needed no edits.
Character recall
The share of normalized, non-space ground-truth characters found in the extracted DOCX text. It does not test reading order or layout.
Token recall
The share of normalized ground-truth tokens found in the output. It is based on token overlap and does not reward correct order.
Word error rate
An order-sensitive token edit distance divided by the number of ground-truth tokens. Lower is better; values can exceed 100%.
Word structure
Counts of actual OOXML elements such as tables, media, drawings, and page-break signals. These counts do not prove visual fidelity.
Editorial repair assessment
A structure-based label: ready without edits, minor repair, major repair, or failed. It is based on extracted text and measured OOXML structure, not a rendered Word page. The per-file note explains the decision.

Results by test category

Category averages are shown with their sample sizes. Digital-text files and image-only files remain separate so that one source type cannot hide the behavior of another.

Aggregate results by manifest category
CategoryFilesReadyValid DOCXCharacter recallToken recallWERWith tablesWith mediaMedian ready time
Columns222100.0%100.0%86.2%0021.58 s
Forms222100.0%100.0%35.0%002.99 s
Headers Footers111100.0%100.0%127.0%0022.25 s
Headings111100.0%100.0%26.5%002.65 s
Images111100.0%100.0%70.0%002.35 s
Links222100.0%100.0%61.0%0026.18 s
Lists111100.0%100.0%31.7%002.19 s
Mixed Layout111100.0%100.0%25.0%004.20 s
Multipage111100.0%100.0%188.9%002.49 s
Ocr200———00—
Page Geometry222100.0%100.0%30.5%0023.07 s
Plain Text111100.0%100.0%25.6%004.00 s
Punctuation111100.0%100.0%20.4%0033.27 s
References111100.0%100.0%31.6%0040.69 s
Tables22298.7%95.3%42.4%002.28 s
Technical Text111100.0%100.0%46.4%002.47 s
Typography222100.0%100.0%45.5%0012.76 s

All 24 file results

The table reports every case, including failures and analysis errors. A dash means that the metric could not be calculated; it does not mean zero.

Per-file conversion, text, structure, and editorial repair-assessment results
CaseTestCategorySourceJob statusCharacter recallToken recallWERDetected Word structureRepair assessmentReview note
en-01-plain-textPlain English paragraphsPlain TextDigitalReady100.0%100.0%25.6%Tables 0; media 0; page signals 0Minor repairText retention was high, but the returned document used one nonempty paragraph and needs paragraph and style review.
en-02-mixed-fontsMixed font families and stylesTypographyDigitalReady100.0%100.0%60.0%Tables 0; media 0; page signals 0Major repairThe returned package was valid, but the main document stored the extracted content in a single nonempty paragraph.
en-03-punctuationPunctuation and symbolsPunctuationDigitalReady100.0%100.0%20.4%Tables 0; media 0; page signals 0Minor repairText retention was high, but the returned document used one nonempty paragraph and needs paragraph and style review.
en-04-urls-emailURLs and email addressesLinksDigitalReady100.0%100.0%40.7%Tables 0; media 0; page signals 0Major repairThe text was returned, but OOXML inspection found no external relationships, so link behavior requires manual rebuilding and verification.
en-05-listsOrdered and unordered listsListsDigitalReady100.0%100.0%31.7%Tables 0; media 0; page signals 0Major repairThe returned package was valid, but the main document stored the extracted content in a single nonempty paragraph.
en-06-headingsDocument heading hierarchyHeadingsDigitalReady100.0%100.0%26.5%Tables 0; media 0; page signals 0Major repairThe returned package was valid, but the main document stored the extracted content in a single nonempty paragraph.
en-07-two-columnsTwo-column reading orderColumnsDigitalReady100.0%100.0%76.3%Tables 0; media 0; page signals 0Major repairThe source used multiple layout regions, but the returned DOCX stored the content in one nonempty paragraph with no editable column structure.
en-08-three-columnsThree-column project briefColumnsDigitalReady100.0%100.0%96.2%Tables 0; media 0; page signals 0Major repairThe source used multiple layout regions, but the returned DOCX stored the content in one nonempty paragraph with no editable column structure.
en-09-simple-tableSimple inventory tableTablesDigitalReady100.0%100.0%36.0%Tables 0; media 0; page signals 0Major repairThe visible source structure was not returned as an editable Word table; OOXML inspection found zero table objects.
en-10-complex-tableComplex service tableTablesDigitalReady97.3%90.7%48.8%Tables 0; media 0; page signals 0Major repairThe visible source structure was not returned as an editable Word table; OOXML inspection found zero table objects.
en-11-headers-footersHeaders and footers across pagesHeaders FootersDigitalReady100.0%100.0%127.0%Tables 0; media 0; page signals 1Major repairThe returned package was valid and exposed 1 page-break signals, but editable structure still needs reconstruction.
en-12-typographyTypography and emphasisTypographyDigitalReady100.0%100.0%31.0%Tables 0; media 0; page signals 0Major repairThe returned package was valid, but the main document stored the extracted content in a single nonempty paragraph.
en-13-multipageThree-page operations reportMultipageDigitalReady100.0%100.0%188.9%Tables 0; media 0; page signals 2Major repairThe returned package was valid and exposed 2 page-break signals, but editable structure still needs reconstruction.
en-14-landscapeLandscape capacity schedulePage GeometryDigitalReady100.0%100.0%23.1%Tables 0; media 0; page signals 0Major repairThe returned package was valid, but the main document stored the extracted content in a single nonempty paragraph.
en-15-rotated-90Rotated page testPage GeometryDigitalReady100.0%100.0%37.9%Tables 0; media 0; page signals 0Major repairThe returned package was valid, but the main document stored the extracted content in a single nonempty paragraph.
en-16-technical-identifiersTechnical identifiersTechnical TextDigitalReady100.0%100.0%46.4%Tables 0; media 0; page signals 0Major repairThe returned package was valid, but the main document stored the extracted content in a single nonempty paragraph.
en-17-image-captionEmbedded process diagramImagesDigitalReady100.0%100.0%70.0%Tables 0; media 0; page signals 0Major repairThe source included visual content, but OOXML inspection found zero embedded media files in the returned DOCX.
en-18-interactive-formInteractive review formFormsDigitalReady100.0%100.0%45.0%Tables 0; media 0; page signals 0Major repairThe visible source structure was not returned as an editable Word table; OOXML inspection found zero table objects.
en-19-invoiceSynthetic service invoiceFormsDigitalReady100.0%100.0%25.0%Tables 0; media 0; page signals 0Major repairThe visible source structure was not returned as an editable Word table; OOXML inspection found zero table objects.
en-20-footnotesFootnotes and referencesReferencesDigitalReady100.0%100.0%31.6%Tables 0; media 0; page signals 0Major repairThe returned package was valid, but the main document stored the extracted content in a single nonempty paragraph.
en-21-hyperlinksInternal and external hyperlinksLinksDigitalReady100.0%100.0%81.2%Tables 0; media 0; page signals 1Major repairThe text was returned, but OOXML inspection found no external relationships, so link behavior requires manual rebuilding and verification.
en-22-mixed-layoutMixed layout reportMixed LayoutDigitalReady100.0%100.0%25.0%Tables 0; media 0; page signals 0Major repairThe source used multiple layout regions, but the returned DOCX stored the content in one nonempty paragraph with no editable column structure.
en-23-scan-paragraphEnglish image-only scanOcrScannedFailed———Tables 0; media 0; page signals 0FailedThe live job failed and no DOCX was returned; the source was an image-only scan that requires OCR.
en-24-scan-tableEnglish image-only table scanOcrScannedFailed———Tables 0; media 0; page signals 0FailedThe live job failed and no DOCX was returned; the source was an image-only scan that requires OCR.

Source and DOCX structure evidence

Each composite shows a rendered source PDF page beside extracted DOCX text and measured OOXML structure. These are not before-and-after Word screenshots and do not establish final Word page appearance.

Plain-text extraction

English PDF-to-Word evidence graphic for benchmark case en-01-plain-text
Composite evidence: rendered source PDF at left; extracted DOCX text and OOXML structure at right. This is not a Word screenshot.
The source and structural panel show complete text retrieval, while the DOCX contains one nonempty paragraph rather than the source paragraph structure.

Two-column reading order

English PDF-to-Word evidence graphic for benchmark case en-07-two-columns
Composite evidence: rendered source PDF at left; extracted DOCX text and OOXML structure at right. This is not a Word screenshot.
The source has two columns; the extracted DOCX text is stored in one paragraph and the column streams are flattened.

Simple table structure

English PDF-to-Word evidence graphic for benchmark case en-09-simple-table
Composite evidence: rendered source PDF at left; extracted DOCX text and OOXML structure at right. This is not a Word screenshot.
All table words are present, but OOXML inspection found zero Word table objects, so rows and cells are not editable as a table.

Image and caption

English PDF-to-Word evidence graphic for benchmark case en-17-image-caption
Composite evidence: rendered source PDF at left; extracted DOCX text and OOXML structure at right. This is not a Word screenshot.
The caption and nearby text were extracted, but OOXML inspection found zero embedded media files, so the process diagram is absent.

Image-only scan

English PDF-to-Word evidence graphic for benchmark case en-23-scan-paragraph
Composite evidence: rendered source PDF at left; extracted DOCX text and OOXML structure at right. This is not a Word screenshot.
The image-only source returned a failed job and no DOCX because the current service does not provide OCR.

Limitations and interpretation

  • This is a controlled engineering sample of 24 synthetic files, not an estimate for every English PDF on the web.
  • The findings describe the recorded live run and converter version. They are not a permanent service-level guarantee.
  • Timing includes the observed workflow and may reflect upload, queue, conversion, polling, and download overhead.
  • Text recall does not measure page geometry, typography, reading order, editability, or image quality.
  • OOXML element counts identify document structure but do not prove that it looks correct in every Word version or operating system.
  • The package checks report external relationships and macro indicators. They are not a malware certification.
  • Image-only files test the live service response for files without an embedded text layer. They do not evaluate every scanning condition or image quality level.
  • Editorial repair assessments involve judgment and are based on extracted text and OOXML structure because Word page rendering was unavailable. They do not establish visual fidelity in Word.

Download the files and results

Use the CSV for direct per-file results. The versioned publication bundle contains the complete JSON results and reproducibility files; the checksum ledger identifies the exact packaged files used in this run.

Dataset license: CC BY 4.0 for the synthetic benchmark dataset and documentation. Check the included README before redistributing files.