PDF Vector in Converting a complex PDF into clean Markdown with a hosted API
Scenario-level performance from current published Results.
7 of 12 scenarios published
Where PDF Vector failed
7 of 7 graded scenarios. Open a Result to see the conversation and the evidence.
A document containing a code block
PDF Vector returned the code without code fences or indentation in Markdown. The listing ran directly into the following prose.
View Result →A document containing mathematical equations
PDF Vector did not keep the equations of a three-page technical note as math. At each of the six equations only its number remained, the bodies reappeared at the end of each page as broken fragments, and the returned Markdown holds no math markup. Sentences that used the symbols lost them too.
View Result →A document with a data chart
PDF Vector failed to preserve the chart as an image in the graded run. The default output returned Markdown only and left the chart, its title, and its axis label out of the page-3 slot; separate pro and max runs brought back the chart text, and max added HTML figure markup, but neither returned an image.
View Result →A document with figures and captions
PDF Vector failed to keep the figure with its caption in place. The caption stayed in the right spot, but the figure itself was missing from the Markdown and the response, and the run card saved no asset files.
View Result →Footnotes at the bottom of the page
PDF Vector kept all 13 footnotes but did not keep them out of the body or link them to their references. In the returned Markdown, each page's notes come before that page's text in one undivided block, and the reference marks are plain digits attached to the preceding word. Choosing higher model tiers by hand moved the notes to the end of each page, but the marks stayed unlinked.
View Result →A simple, clearly formatted table
PDF Vector’s default conversion lost the structure of a simple table. All 32 values and four header labels stayed in source order, but the output did not retain cells or columns.
View Result →An ordinary digital text document
PDF Vector returned every body word of a seven-page briefing note in order and invented nothing, but it put the running header and the 'Page N of 7' line inline at every page boundary. At four of the six boundaries they land inside a sentence broken across the page, so the returned text has sentences the source does not.
View Result →How PDF Vector performed
Open a capability to explore its scenarios. Each row reports the test set in its published Result.
Code Extraction1 fail
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 happenedPDF Vector returned the code without code fences or indentation in Markdown. The listing ran directly into the following prose. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Equations & Mathematical Notation1 fail
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A document containing mathematical equations | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedPDF Vector did not keep the equations of a three-page technical note as math. At each of the six equations only its number remained, the bodies reappeared at the end of each page as broken fragments, and the returned Markdown holds no math markup. Sentences that used the symbols lost them too. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Figures & Charts2 fail
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A document with a data chart | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedPDF Vector failed to preserve the chart as an image in the graded run. The default output returned Markdown only and left the chart, its title, and its axis label out of the page-3 slot; separate pro and max runs brought back the chart text, and max added HTML figure markup, but neither returned an image. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| A document with figures and captions | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedPDF Vector failed to keep the figure with its caption in place. The caption stayed in the right spot, but the figure itself was missing from the Markdown and the response, and the run card saved no asset files. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Heading & Section Structure1 fail1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Footnotes at the bottom of the page | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedPDF Vector kept all 13 footnotes but did not keep them out of the body or link them to their references. In the returned Markdown, each page's notes come before that page's text in one undivided block, and the reference marks are plain digits attached to the preceding word. Choosing higher model tiers by hand moved the notes to the end of each page, but the marks stayed unlinked. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| A document with styled headings and subheadings | No published result | ||
Table Extraction1 fail1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A simple, clearly formatted table | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedPDF Vector’s default conversion lost the structure of a simple table. All 32 values and four header labels stayed in source order, but the output did not retain cells or columns. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| A table that continues across a page break | No published result | ||
Text Fidelity1 fail
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| An ordinary digital text document | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedPDF Vector returned every body word of a seven-page briefing note in order and invented nothing, but it put the running header and the 'Page N of 7' line inline at every page boundary. At four of the six boundaries they land inside a sentence broken across the page, so the returned text has sentences the source does not. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Reading Order & Layout1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A page laid out in multiple columns | No published result | ||
Scanned Document OCR2 no Result yet
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 | ||
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.
Out of 12 scenarios
The summary counts each of the 12 scenarios once. A scenario fails when any of its published test cases failed. “No published Result yet” means nothing is public for that scenario; it does not say whether PDF Vector was tested on it.