Does Upstage AI preserve code blocks and their indentation when converting a PDF to Markdown?
Upstage AI did not preserve code-block formatting when converting the PDF to Markdown. Its output kept the code's characters and line breaks, but lost indentation and treated the code as ordinary paragraphs.
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.
Code block — fenced, structure intactFailEvidence
We sent the complete three-page operations-note PDF to Upstage Document Parse's conversion API in one synchronous request, without selecting a parsing mode.
Copied from Output file (Markdown), lines 50–61
from tarnbeck.stations import Export, reload_window def reload_after_reset(station, reset_at): export = Export.open(station) window = reload_window(reset_at, margin_minutes=45) for block in export.blocks(window): if block.checksum_ok(): continue export.requeue(block, reason="gauge reset") return export.commit(dry_run=False)
Copied from Output file (JSON), elements 18
{ "id": 17, "page": 2, "category": "paragraph", "content": { "html": "<p id='17' data-category='paragraph' style='font-size:16px'>def reload_after_reset(station, reset_at):<br>export = Export.open(station)<br>window = reload_window(reset_at, margin_minutes=45)</p>", "markdown": "def reload_after_reset(station, reset_at):\nexport = Export.open(station)\nwindow = reload_window(reset_at, margin_minutes=45)", "text": "" }, "coordinates": [ { "x": 0.1263, "y": 0.1428 }, { "x": 0.592, "y": 0.1428 }, { "x": 0.592, "y": 0.1868 }, { "x": 0.1263, "y": 0.1868 } ] }
Copied from Output file (JSON), elements 19
{ "id": 18, "page": 2, "category": "paragraph", "content": { "html": "<p id='18' data-category='paragraph' style='font-size:16px'>for block in export.blocks(window):<br>if block.checksum_ok():<br>continue<br>export.requeue(block, reason="gauge reset")</p>", "markdown": "for block in export.blocks(window):\nif block.checksum_ok():\ncontinue\nexport.requeue(block, reason=\"gauge reset\")", "text": "" }, "coordinates": [ { "x": 0.1605, "y": 0.2026 }, { "x": 0.5587, "y": 0.2026 }, { "x": 0.5587, "y": 0.2624 }, { "x": 0.1605, "y": 0.2624 } ] }
Returned Markdown: code lines without fences or indentation
Open the Markdown file ↗API response: code classified as paragraphs without indentation or fences
Open the whole JSON file ↗| ✗ | Expected: Code must remain a preformatted or fenced block, with its line breaks and indentation intact.Found: Code became paragraphs without fences or preformatted markup. The source's 4-, 8- and 12-space indents disappeared; characters and line breaks survived. |
- usage
- { "pages": 3, "standard": [1, 2, 3] }
- elements 25
- { "id": 24, "page": 2, "category": "paragraph", "content": { "html": "<p id='24' data-category='paragraph' style='font-size:16px'>$ ssh loader-01.tarnbeck.example<br>$ tarnbeck-maint reload-after-reset --station VQ1 \\<br>--reset-at '2026-01-29T09:15' --confirm</p>", "markdown": "$ ssh loader-01.tarnbeck.example\n$ tarnbeck-maint reload-after-reset --station VQ1 \\\n--reset-at '2026-01-29T09:15' --confirm", "text": "" }, "coordinates": [ { "x": 0.1238, "y": 0.5482 }, { "x": 0.5599, "y": 0.5482 }, { "x": 0.5599, "y": 0.5927 }, { "x": 0.1238, "y": 0.5927 } ] }
Preserving the code's text was not enough: its block formatting and indentation also had to survive. Returning it as ordinary paragraphs left both required features absent.
Heading formatting survived. The returned heading "If the count is short" retained Markdown heading syntax, so the loss of code formatting did not affect all Markdown markup.
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 | Code Extraction → | |
| Scenario | A document containing a code block → | |
| Tool | Upstage AI → |
Global scenario definition → · Global capability definition → · Upstage AI 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.