Does LlamaParse preserve styled heading hierarchy in Markdown?
LlamaParse turned every heading into a Markdown heading but kept only two of the source's three heading levels. On page 1, the subsections Chain of custody and Condition on arrival came out at the same level as their parent, Reception, and the third-tier headings shared a level with the second. A separate run with a custom prompt asking for three heading levels did not preserve the hierarchy either.
1 of 1 test case failed
Every test case in this scenario has a result.
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.
Styled headings — hierarchy preservedFailEvidence
We uploaded the complete three-page laboratory procedure to LlamaParse's conversion API in one request.
Markdown output: headings in two levels; Chain of custody and Condition on arrival share Reception's level
Copied from Output file (Markdown), lines 9–17
## Reception Samples are received at reception between 08:00 and 17:30 on weekdays and between 09:00 and 12:00 on Saturdays. Outside those hours clients who hold a key may use the refrigerated drop box at the rear entrance. ## Chain of custody Every delivery arrives with a completed submission form. Reception staff check that the form is signed, that the number of containers matches the number listed on it, and that each container carries a legible client reference. The form is signed and timed on receipt and the top copy is returned to the person making the delivery. ## Condition on arrival
API response: the completed job at the default tier, with all three pages processed
Copied from Captured file (JSON), job › status
COMPLETED
| ✗ | Expected: Headings become Markdown headings with the source's heading hierarchy kept, not turned into plain or bold text.Found: All headings became Markdown headings, but three source levels became two: Chain of custody and Condition on arrival sit at Reception's level; both third-tier headings share the second tier's level. |
- job › tier
- agentic
- job › name
- procedure_KAL-SP-06_sample_reception.pdf
Every heading became a Markdown heading, but three source levels came back as two: two subsections sit at their parent's level, while the same construction under Storage nests correctly. A custom-prompt run asking for three levels still did not keep them and promoted the title block to a heading.
Title lines left as text. The three page-1 title lines, including Sample Reception and Handling, are set in body type in the source and come out as plain text, not as headings.
Body text complete. Every one of the source's 1,255 body words comes back in order; the only additions are two page-break rules.
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.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
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.
- 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.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Converting a complex PDF into clean Markdown with a hosted API → | 12 scenarios · 13 tools |
| Capability | Heading & Section Structure → | |
| Scenario | A document with styled headings and subheadings → | |
| Tool | LlamaParse → |
Global scenario definition → · Global capability definition → · LlamaParse product page →
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.
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.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →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.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.