Adobe PDF Extract API in Converting a complex PDF into clean Markdown with a hosted API
Scenario-level performance from current published Results.
1 scenario with a published Result · 12 scenarios in the benchmark
How Adobe PDF Extract API performed
Open a capability to explore its scenarios. Each row reports the test set in its published Result; counts are not combined into an overall score.
Code Extraction1 scenario · 1 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A document containing a code block | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedAdobe PDF Extract API did not preserve the code block as a preformatted or fenced block. The nine-line Python block was collapsed into five ordinary paragraphs, the shell block into two lines, and no output line carried leading whitespace. The whitespace-insensitive character content still matched the source, but the block structure was lost. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Equations & Mathematical Notation1 scenario · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A document containing mathematical equations | No published result | ||
Figures & Charts2 scenarios · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A document with a data chart | No published result | ||
| A document with figures and captions | No published result | ||
Heading & Section Structure2 scenarios · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A document with styled headings and subheadings | No published result | ||
| Footnotes at the bottom of the page | No published result | ||
Reading Order & Layout1 scenario · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A page laid out in multiple columns | No published result | ||
Scanned Document OCR2 scenarios · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A cleanly scanned document | No published result | ||
| A document mixing digital and scanned pages | No published result | ||
Table Extraction2 scenarios · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A simple, clearly formatted table | No published result | ||
| A table that continues across a page break | No published result | ||
Text Fidelity1 scenario · 0 with published Results
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| An ordinary digital text document | No published result | ||
Reading these Results
Published evidence and test coverage answer different questions.
Which scenarios have a Result?
A published Result is public evidence for this tool on one scenario. “No published result” does not say whether testing has taken place.
What does each Result cover?
Assessed includes Pass, Fail and Not gradable. Gradable includes Pass and Fail. Both use the pinned test count in that published Result.
Inventory is not testing progress
The 12 scenarios describe this benchmark’s scope. They are not an assumed applicability or test-coverage denominator for Adobe PDF Extract API.