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

Does Nutrient.io keep a data chart when it converts a document to Markdown?

Nutrient.io's default Markdown conversion dropped the page-3 bar chart entirely: no image, no title and no marker where it stood. The paragraph before the chart runs straight into the one after it, and the response carried the Markdown alone, with no image asset.

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.

Data chart — preserved with titleFailEvidence
What we sent

The complete four-page PDF was sent to Nutrient.io's conversion API in one request.

InputDocument (PDF)
Input PDF: the four-page survey report with an image-only bar chart on page 3
Open the PDF ↗
What the tool returned

Returned Markdown: the page-3 text with no image or chart title

Copied from Output file (Markdown), lines 103–111

Markdown
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.


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.
Open the Markdown file ↗

HTTP exchange record: the conversion request and a Markdown-only response

Copied from Output file (JSON), response

JSON
{
  "status_code": 200,
  "headers": {
    "date": "Wed, 09 Sep 2026 08:52:33 GMT",
    "content-type": "text/markdown",
    "content-length": "5757",
    "content-disposition": "attachment; filename=\"result.md\"",
    "server": "Cowboy",
    "x-pspdfkit-remaining-credits": "42",
    "x-pspdfkit-request-cost": "1",
    "x-request-id": "GNObCwNz-SKmdXEAAPfh"
  },
  "content_type": "text/markdown",
  "body_bytes": 5757,
  "delivery": "raw markdown body (content-type text/markdown)",
  "markdown_chars": 5755,
  "zip_members": null,
  "asset_names": null
}
Open the whole JSON file ↗
Expected vs. Found
✗Expected: The page-3 chart appears as an image at its position with its title; added chart data is optional.Found: No image, caption, title or placeholder where the chart stood; the paragraph before it runs into the one after, and no image syntax or chart title appears anywhere.
Supporting proof
Proof 1Screenshot
Run card: the request and its result
Open original ↗
Why this result

The chart had to come back as an image at its place, with its title. The returned Markdown has no image, title or placeholder there and no image anywhere, so both required elements are missing.

Also observed in this test case

Text-layer captions kept. The page-2 survey plan's caption, which sits in the text layer, is kept as plain text; the chart's title is inside the image and is lost with it.

No chart values invented. No axis label, tick value or legend entry from the chart was invented 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
Nutrient.io
Build or version
Not exposed by the hosted product
Plan or tier
free tier
Surface
API
Set up before the run
A PDF with a data chart and title had to be converted to Markdown in one default-pipeline pass on the complete file.
Pipeline
Markdown output · no extra processing steps · Build API default pipeline, single pass
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
21 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/nutrient-io/a-document-with-a-data-chart · 0 pass · 1 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 · 301 KB
Output file (Markdown) ↗text/markdown · 6 KB
Output file (JSON) ↗application/json · 1 KB
Proof 1 · Screenshot ↗image/png · 90 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)75b2bcc613580942d7d3222254c0f0d084525c2c6521f55cffa629c49f64c608
Output file (Markdown)f4798cb6749fb2adfa19f7f11dc8559353ef188dab3409cf4bfa00c5b2a9f800
Output file (JSON)38dd9beeb5533c3032fbaa448d687de07a69695c6fcb617f28dd62d13b639404
Proof 1 · Screenshot4df923b352f1db222bc899c8d42d750878fd626c71f3892880ab88ddddef7c12