AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 30 October 2026

Does PDF Vector keep a figure with its caption in place?

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.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

The test case

Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.

Figure with caption — preserved in placeFailEvidence
What we sent

We sent the complete four-page survey report PDF to PDF Vector's document parse endpoint in one request; there was no typed prompt.

InputDocument (PDF)
Source PDF page 2 with the transect plan and caption
Open the PDF ↗
What the tool returned

Markdown output with the caption in place and no figure

Copied from Output file (Markdown), lines 49–50

Markdown
Figure 1. Survey transects at Kellow Sands and Thrimby Point. Sampling stations are shown as filled circles and the 1998 saltmarsh
edge as a broken line.
Open the Markdown file ↗

Raw API response with only text output and no image fields

Copied from Output file (JSON) · an excerpt

JSON
{
  "markdown": "Intertidal survey of Kellow Sands and Thrimby Point\nReport BEP/SR/2026/11 · Survey of 19 to 23 January 2026 · Issued February 2026\nSummary\nThe four fixed transects at Kellow Sands and Thrimby Point were resurveyed in January, in the third w … [5,688 characters in the file]",
  "pageCount": 4,
  "model": "nano",
  "credits": 4,
  "requestId": 272368
}

Excerpt ends here. Open the source for the complete output.

Open the whole JSON file ↗
Expected vs. Found
✗Expected: The image is preserved at its position, with its caption.Found: The caption stays in place, but the figure is missing from the Markdown and raw response.
Supporting proof
Proof 1Screenshot
Source-versus-output comparison for page 2
Open original ↗
Proof 2Screenshot
Run card showing success and zero saved assets
Open original ↗
Why this result

The default full-PDF run succeeded, but the figure never appeared while the caption did, so this is a product fail rather than a run problem.

Also observed in this test case

Figure labels not returned either. Under the default pipeline the plan's own labels, such as Kellow Sands, Thrimby Point and the transect names T1 to T4, were not returned as text either, so nothing of the figure survives in the output.

Tested by Chandresh Bisht · evidence dated 9 September 2026

Configuration and setup

How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.

Software that produced the output
PDF Vector
Build or version
PDF Vector /api/document/parse; model nano (auto-selected by the server)
Plan or tier
free tier
Surface
API
Set up before the run
A PDF with a figure and caption had to be converted as the complete file in one default parse pass, with no per-tool tuning.
Pipeline
single pass · default pipeline, no per-tool flag tuning
Input delivery
complete PDF as base64 in the JSON body
Tested
9 September 2026 · Chandresh Bisht

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.

The rules
  • Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
  • Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
  • Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.

Where this sits in the benchmark

This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.

History of this result

What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.

from the publication record
17 November 2026First publishedConverting a complex PDF into clean Markdown with a hosted API v1

Act on this result

Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/pdf-to-markdown-apis/results/pdf-vector/a-document-with-figures-and-captions · 0 pass · 1 fail · coverage 1/1 · graded 2026-10-30

The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.

Verify the proof files

These files support this result. Open a file to inspect the original evidence.

Input · Document (PDF) ↗application/pdf · 301 KB
Proof 1 · Screenshot ↗image/png · 189 KB
Output file (Markdown) ↗text/markdown · 6 KB
Output file (JSON) ↗application/json · 6 KB
Proof 2 · Screenshot ↗image/png · 50 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)75b2bcc613580942d7d3222254c0f0d084525c2c6521f55cffa629c49f64c608
Proof 1 · Screenshotfeebe736fa3fc72a78777f1ad6e0fe292dfa55ee044250c2b0ee814a903e2142
Output file (Markdown)c4dd96f454ba0fa63601b46da05cd040d6b1bb8a6af05bf42fd713ce09be979c
Output file (JSON)a4c7aa665251f4dee2968a7e3fbf2a059824a50648ed04e08c830ce2f1a1a8ee
Proof 2 · Screenshotc3414878c9de88795661ec68f5a03bb50e4cfa58b43a688479e038ba9365da96