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

Can Nutrient.io turn a clean scan into accurate text?

Nutrient.io did not recover the text from a clean scan using its default conversion. Although the API returned a successful response, the Markdown contained only two newline characters.

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.

Clean scan — text recoveredFailEvidence
What we sent
InputDocument (PDF)
Input PDF: a one-page scanned laboratory letter
Open the PDF ↗
What the tool returned
JSON
{
  "status_code": 200,
  "headers": {
    "date": "Wed, 09 Sep 2026 08:53:00 GMT",
    "content-type": "text/markdown",
    "content-length": "2",
    "content-disposition": "attachment; filename=\"result.md\"",
    "server": "Cowboy",
    "x-pspdfkit-remaining-credits": "41",
    "x-pspdfkit-request-cost": "1",
    "x-request-id": "GNObDI0-05KFXc0AAPiB"
  },
  "content_type": "text/markdown",
  "body_bytes": 2,
  "delivery": "raw markdown body (content-type text/markdown)",
  "markdown_chars": 2,
  "zip_members": null,
  "asset_names": null
}

API exchange: the default conversion request and response

Copied from Output file (JSON), response

Open the whole JSON file ↗
Output file (Markdown)
Returned Markdown: two newline characters
Open the Markdown file ↗
Expected vs. Found
✗Expected: Recover the visible text accurately.Found: The API returned a successful response, but the Markdown contained only two newline characters and none of the page's words.
Supporting proof
Proof 1Screenshot
Source and output: the scanned page beside the blank Markdown
Open original ↗
Proof 2Screenshot
Run card: conversion conditions, timing and response metrics
Open original ↗
Why this result

The default conversion returned no text from a legible scan, so it failed the text-recovery requirement. Nutrient offers OCR as a separate action; that alternative was run separately and does not replace the default-conversion result.

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 short, clearly scanned image-only PDF containing ordinary text was required. The complete PDF was to be converted to Markdown in one pass using the default pipeline, without per-tool flag tuning.
Pipeline
Markdown output · no actions set (the product's defaults) · one output part; 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
11 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-cleanly-scanned-document · 0 pass · 1 fail · coverage 1/1 · graded 2026-10-13

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 · 747 KB
Output file (JSON) ↗application/json · 1 KB
Output file (Markdown) ↗text/markdown · 0 KB
Proof 1 · Screenshot ↗image/png · 1.1 MB
Proof 2 · Screenshot ↗image/png · 91 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)a459554d58b9480b19bb3a63598c500b961c3ad377492d18ff227bb439e1f68c
Output file (JSON)316ce87b50e970aad71ef8fd3de2c5228f99afeec6cf76aa85e68c25e4c0ab84
Output file (Markdown)75a11da44c802486bc6f65640aa48a730f0f684c5c07a42ba3cd1735eb3fb070
Proof 1 · Screenshot8383e5645b050c9c761bc3d489604723fd0cf5c532a1a2e6728ca271829e3f63
Proof 2 · Screenshot3cbecc43d65c37bd254adec85dd15a3b28f5680c9cc431ed67e9b8c491bd98c8