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

Does MinerU keep bottom-of-page footnotes out of the body and linked to their markers?

MinerU kept bottom-of-page footnotes out of the body text and associated with their numbered references. All 13 footnotes remained in order, with their source wording unchanged.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
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.

Footnote — out of body flow, associatedPassEvidence
What we sent
InputDocument (PDF)
Input PDF: a four-page journal offprint with numbered footnotes at the bottom of each page
Open the PDF ↗
What the tool returned

Copied from Output file (Markdown), lines 25–31

Markdown
<small><span class="docvortex-page-footnote" data-block-type="page_footnote" style="color:#6b7280">1 Braithe Estuary Order 1974, art. 6(2). The Order is reproduced in full in the appendix to R. Sandiman, The Braithe Estuary: A Documentary History (Vardenne, 1988), 211-24.</span></small>

<small><span class="docvortex-page-footnote" data-block-type="page_footnote" style="color:#6b7280">2 Minutes of the Harbour Board, 14 May 1973 (Braithe Record Office, BHB/3/17), 4.</span></small>

<small><span class="docvortex-page-footnote" data-block-type="page_footnote" style="color:#6b7280">3 The point was not argued in Tarbert v Braithe Harbour Board [1981] 2 EstLR 88, where both parties proceeded on the assumption that art. 6(2) applied.</span></small>

<small><span class="docvortex-page-footnote" data-block-type="page_footnote" style="color:#6b7280">4 The Board's file on the 2011 consents (Braithe Record Office, BHB/11/4) contains three letters returned undelivered and a note of a telephone call to a solicitor in Winnipeg.</span></small>

Copied from Output file (Markdown), line 75

Markdown
<small><span class="docvortex-page-footnote" data-block-type="page_footnote" style="color:#6b7280">8 Braithe Record Office, BHB/3/14-24. The marked-up print is BHB/3/22. 9 Notably Prosser, 'Consent and its conditions', 7, who calls the deletion 'tidying'. 10 Minutes of the fourth meeting, 9 July 1973 (Braithe Record Office, BHB/3/19), 2-6.</span></small>

Returned Markdown: footnotes separated from body paragraphs and associated with numbered markers

Open the Markdown file ↗
Expected vs. Found
✓Expected: All 13 footnotes must stay outside the body flow, remain intact and retain their numbered associations.Found: The 13 source footnotes all appeared after their pages’ body text, in order and unchanged, with one corresponding numbered marker each in the body.
Supporting proof
Proof 1Screenshot
Terminal screenshot: conversion with the flash tier completing successfully
Open original ↗
Why this result

Keeping the text separate, unchanged and tied to its markers meets the requirement. This result covers the lighter, native-text flash tier; the default tier could not run because its models could not be downloaded in the test environment.

Also observed in this test case

Footnotes share blocks. Footnotes 8–10 share one HTML block, and 11–12 share another. Splitting the output by block would yield 10 items, not 13 footnotes.

HTML inside Markdown. The footnote blocks include HTML and inline styling, so the output is not plain Markdown.

Tested by Vamshidhar Rao Thumula · evidence dated 25 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
MinerU
Build or version
MinerU 4.0.7
Surface
CLI
Set up before the run
A PDF page with body text referencing a footnote at the bottom of the page; convert the complete PDF to Markdown in one pass with the flash tier and no other tuning.
Tier
flash
Pages
all
Tested
25 September 2026 · Vamshidhar Rao Thumula

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 an open-source library 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-open-source/results/mineru/footnotes-at-the-bottom-of-the-page · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-18

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 · 152 KB
Output file (Markdown) ↗text/markdown · 12 KB
Proof 1 · Screenshot ↗image/png · 24 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)fce3c87776b6f1b8f34dcfb0f6a274b5954edcb3d33ff7ee84840dfe2afbc1ad
Output file (Markdown)f5a33a26ab4f3c55f549b8d286bf054e7569c30b42da04041a542e8287132ee4
Proof 1 · Screenshot3f9e082d131600e91d52829a13a03edafd6f6607ffcbf65584d615bea81f66df