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

Does LlamaParse keep figures and captions in place?

LlamaParse replaced the figure with prose rather than preserving it in the default Markdown output. Its caption remained in place, but the image was neither embedded nor linked.

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 uploaded the complete 4-page survey PDF to LlamaParse's document-to-Markdown API in one request.

InputDocument (PDF)
Input PDF: a survey with a captioned map on page 2
Open the PDF ↗
What the tool returned

Returned Markdown: the graded output replaces the map with prose and keeps its caption

Copied from Output file (Markdown), lines 34–40

Markdown

The plan below shows the four lines as they were surveyed in January, together with the saltmarsh edge as it stood at the 1998 survey. The 1998 edge is drawn because it is the last edge surveyed on the ground rather than taken from photography, and because it is the line against which the advisers have asked that marsh extent be reported.

map: survey transects at Kellow Sands and Thrimby Point showing T1, T2, T3, and T4 lines with sampling stations

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 ↗
Key momentslines 34–40

API response: the graded output contains no image assets

Copied from Output file (JSON), images_content_metadata

JSON
{
  "total_count": 0,
  "images": []
}
Open the whole JSON file ↗
Expected vs. Found
✗Expected: Preserve the image, embedded or referenced at its original position, with its caption.Found: The survey map's position and exact caption were retained. The image became a prose description, with no embedded image, image reference or returned image assets.
Supporting proof
Proof 1Screenshot
Side-by-side comparison: the source map and the graded output's description in its place
Open original ↗
Proof 2Captured file (Markdown)
Returned Markdown: the separate image-enabled conversion places the map reference before its caption
Markdown69 lines
## **Intertidal survey of Kellow Sands and Thrimby Point**

Report BEP/SR/2026/11 · Survey of 19 to 23 January 2026 · Issued February 2026

### **Summary**

The four fixed transects at Kellow Sands and Thrimby Point were resurveyed in January, in the third winter since sediment recharge began. This report sets out the method, the profiles measured, and the change on each transect since the surveys began.

Levels were taken at five-metre intervals along each transect with a total station from the survey marks on the training wall and at the lifeboat house. Sediment samples were taken at the mid-shore station on each transect for particle size, and are reported by the laboratory separately.

Conditions during the survey were settled, with no swell and a spring range near the mean. Nothing about the week's weather is likely to have affected the levels measured.

### **Background**

The Partnership has surveyed the intertidal at Kellow Sands since 2019, when the four transects were established to provide a baseline for the sediment recharge then being planned. The first two winters were surveyed before any material was placed. Placement began in the winter of 2023/24 and has been carried out in each winter since, most recently between November 2025 and January 2026.

The purpose of the survey is a narrow one. It is meant to answer whether the intertidal profile at Kellow Sands is gaining or losing sediment, and at what rate, on lines whose position is fixed. It is not a study of where the placed material goes, which would need tracer work the Partnership has not commissioned, and it cannot by itself attribute a change to the recharge rather than to the weather.

### **Method**

Levels were taken with a total station from the two survey marks used since 2019, at five-metre intervals along each transect and at every break of slope between them. Each line was run twice, out and back, and the two sets agreed everywhere within the tolerance the method allows. Where they did not, which happened once on transect three, the point was re-observed.

The horizontal position of each line is fixed by a mark set in concrete at the landward end and by a pin in the training wall or the marsh edge at the seaward end. All eight marks were found and checked against the 2019 coordinates before work began. The pin at the seaward end of transect two has moved and was re-established from the landward mark; the correction is recorded in the level book and is smaller than the interval between observations.

Sediment samples were taken at the mid-shore station on each line, in the order in which the lines were surveyed, and delivered to the laboratory the same afternoon. Particle size is reported separately and is not discussed here.

---

## **The transects**

Transect one runs from the seawall opposite the boatyard to the low water mark, crossing the widest part of the sand. It is the longest of the four lines and the only one on which the whole intertidal profile can be surveyed within a single tide.

Transects two and three are the pair the recharge was expected to affect. Both cross the placement footprint at its northern end, transect two some sixty metres from the discharge point and transect three about a hundred and forty. Neither has been moved since it was established, and the marks at both ends of both lines were found in good order.

The plan below shows the four lines as they were surveyed in January, together with the saltmarsh edge as it stood at the 1998 survey. The 1998 edge is drawn because it is the last edge surveyed on the ground rather than taken from photography, and because it is the line against which the advisers have asked that marsh extent be reported.

![drawing: A map showing four survey transects (T1, T2, T3, T4) across Kellow Sands and Thrimby Point, with a north arrow and a dashed line indicating the 1998 saltmarsh edge.]

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.

Transect four crosses the toe of the training wall and has always behaved differently from the other three. It is retained because the wall itself is the reason for the difference, and because the Partnership was asked in 2019 to keep a line there.

The stations shown on the plan are those at which sediment samples are taken, and not the points at which levels were observed: the level observations are too close together to plot at this scale. A full set of profiles is bound into the copy of this report held by the secretariat.

---

## **Change since the first survey**

Change is reported as a mean annual rate over each winter, taken across the whole intertidal part of the line. Accretion varied markedly between transects, and the pattern is the same in each of the three winters measured.

#### **Mean sediment accretion by transect, winters 2023/24 to 2025/26**

<table><tr><th>Transect</th><th>2023/24 (Accretion mm/yr)</th><th>2024/25 (Accretion mm/yr)</th><th>2025/26 (Accretion mm/yr)</th></tr>
<tr><th>Transect 1</th><td>0.4</td><td>0.7</td><td>0.6</td></tr>
<tr><th>Transect 2</th><td>2.8</td><td>3.5</td><td>3.9</td></tr>
<tr><th>Transect 3</th><td>1.9</td><td>2.4</td><td>3.0</td></tr>
<tr><th>Transect 4</th><td>-0.6</td><td>-0.7</td><td>-1.0</td></tr></table>

The rates plotted are means over the intertidal part of each line, weighted by the length of profile each observation represents. A mean of that kind conceals a good deal. On transect two most of the gain is in the upper third of the profile, and on transect four the loss is almost all at the toe of the wall; the profiles show this plainly and a mean does not.

The advisers' view, which the secretariat shares, is that three winters is too short a run to separate the effect of placement from the variation the estuary shows anyway. The transects should be resurveyed next January on the same lines and by the same method before anything is concluded from them.

---

## **The next survey**

The profiles themselves, the level books and the mark check sheets are held by the secretariat and are available to Partnership members on request.

The next survey is due in January 2027. The secretariat proposes to keep the January window, and to ask the laboratory for particle size on the same four stations so that the series stays comparable.
Open the Markdown file ↗
Proof 3Screenshot
Comparison sheet: the separate image-enabled conversion's map reference and caption
Open original ↗
Proof 4Captured file (JSON)
Configuration metadata: the separate image-enabled conversion saved four assets
JSON
{
  "status": "success",
  "tool": "llamaparse",
  "configuration": "inline_images",
  "role": "configured",
  "endpoint": "https://api.cloud.llamaindex.ai/api/v2/parse/upload",
  "params_sent": {
    "tier": "agentic",
    "version": "2026-09-29",
    "output_options": {
      "images_to_save": ["embedded", "layout"],
      "markdown": {
        "inline_images": true
      }
    }
  },
  "started_utc": "2026-10-14T11:55:53.566484+00:00",
  "finished_utc": "2026-10-14T11:56:13.489539+00:00",
  "input_file": "intertidal_survey_BEP-SR-2026-11.pdf",
  "input_sha256_actual": "75b2bcc613580942d7d3222254c0f0d084525c2c6521f55cffa629c49f64c608",
  "input_sha256_expected": "75b2bcc613580942d7d3222254c0f0d084525c2c6521f55cffa629c49f64c608",
  "input_pages": 4,
  "test_cases": ["TC33", "TC34"],
  "markdown_origin": "markdown_full",
  "assets_saved": 4,
  "warnings": [],
  "job_id": "pjb-uxtmyxnxz7qkt8ge9lskdzjmoa2j",
  "result_expand": "markdown,markdown_full,items,metadata,images_content_metadata",
  "reported_model": null,
  "grading_status": "Not yet graded",
  "notes": "Whole input submitted. Native Markdown saved without content or image-link changes. Fresh baseline pairs use the same current API/model request; original baseline runs remain untouched."
}
Open the JSON file ↗
Cited values1 value from this file · long text shortened
markdown
{ "pages": [ { "page_number": 1, "markdown": "# Intertidal survey of Kellow Sands and Thrimby Point\n\nReport BEP/SR/2026/11 · Survey of 19 to 23 January 2026 · Issued February 2026\n\n## Summary\n\nThe four fixed transects at Kellow Sands and Thrimby Point were resurveyed in January, in the … [2,733 characters in the file]", "success": true }, { "page_number": 2, "markdown": "## The transects\n\nTransect one runs from the seawall opposite the boatyard to the low water mark, crossing the widest part of the sand. It is the longest of the four lines and the only one on which the whole intertidal profile can be survey … [1,757 characters in the file]", "success": true }, { "page_number": 3, "markdown": "## Change since the first survey\n\nChange is reported as a mean annual rate over each winter, taken across the whole intertidal part of the line. Accretion varied markedly between transects, and the pattern is the same in each of the three w … [1,610 characters in the file]", "success": true }, { "page_number": 4, "markdown": "## The next survey\n\nThe profiles themselves, the level books and the mark check sheets are held by the secretariat and are available to Partnership members on request.\n\nThe next survey is due in January 2027. The secretariat proposes to keep the January window, and to ask the laboratory for particle size on the same four stations so that the series stays comparable.", "success": true } ] }
Why this result

The default conversion completed, but a description is not a preserved image. Correct placement and caption therefore do not satisfy preservation; the separate image-enabled conversion does not replace the default result.

Also observed in this test case

Image options preserved the map. With image saving and inline image references enabled, the separate conversion on 14 October 2026 saved the page 2 survey map and placed its image reference immediately before the exact caption.

Tested by Chandresh Bisht · evidence dated 10 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
LlamaParse
Build or version
Parse API v2, tier agentic, version latest (build not exposed)
Plan or tier
free tier
Surface
API
Set up before the run
The complete survey PDF was converted to Markdown in one pass without customized options. The test focused on page 2's survey map and its caption in normal text.
Conversion pipeline
Default, single pass, no customized options
Tested
10 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
18 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/llamaparse/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.

Proof 1 · Screenshot ↗image/png · 186 KB
Input · Document (PDF) ↗application/pdf · 301 KB
Output file (Markdown) ↗text/markdown; charset=utf-8 · 6 KB
Output file (JSON) ↗application/json · 15 KB
Proof 2 · Captured file (Markdown) ↗text/markdown; charset=utf-8 · 6 KB
Proof 3 · Screenshot ↗image/png · 326 KB
Proof 4 · Captured file (JSON) ↗application/json · 1 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshota03dc40a2eee4f9a387c4d91bc82d9d355f187b94c060001c56ac68752d80620
Input · Document (PDF)75b2bcc613580942d7d3222254c0f0d084525c2c6521f55cffa629c49f64c608
Output file (Markdown)8c0c43233f85d190c803882b044ce7083d791b36f7a0835ea9e0e9853c5c2791
Output file (JSON)062b06e5528d2b62f5952f7729ddd4620e5bb60bf2d07eda1358414fb446ac84
Proof 2 · Captured file (Markdown)1a43e149d676977807bf2faebfdada1fc0ea976e48be588ce577aa9c87715ab2
Proof 3 · Screenshot980086fb2907f6bbd73ad692a3d47ad16b3df2313752b336a0501f9c47746662
Proof 4 · Captured file (JSON)cdd34ef41e6750b2f91c6baa391cd86f069381f7bb2096144b3efaedd256b9e4