Does Firecrawl preserve a simple table when converting a PDF to Markdown?
Firecrawl preserved the structure of the simple table in this test. It returned all four headers and eight rows, with the values under the correct headers.
1 of 1 test case passed
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.
Simple table — structure retainedPassEvidence
| Determination | Method | Turnaround | Charge per sample | | --- | --- | --- | --- | | Total suspended solids | KAL-M04 | 2 days | £18.40 | | Chloride | KAL-M11 | 3 days | £21.75 | | Ammoniacal nitrogen | KAL-M12 | 4 days | £26.50 | | Total oxidised nitrogen | KAL-M13 | 5 days | £29.20 | | Orthophosphate | KAL-M15 | 6 days | £31.60 | | Dissolved organic carbon | KAL-M22 | 7 days | £44.05 | | Metals suite, eleven elements | KAL-M31 | 8 days | £96.80 | | Particle size distribution | KAL-M47 | 10 days | £58.35 |
Markdown output: the returned pipe table
Copied from Output file (Markdown), lines 8–17
Open the Markdown file ↗{ "scrapeId": "01a08b71-8784-72a3-be00-e0ab421e3784", "sourceURL": "schedule_of_analysis_charges_2026.pdf", "url": "https://parse.firecrawl.dev/uploads/schedule_of_analysis_charges_2026.pdf", "statusCode": 200, "numPages": 3, "totalPages": 3, "title": "Schedule of Analysis Charges 2026", "contentType": "application/pdf", "proxyUsed": "basic", "creditsUsed": 3, "concurrencyLimited": false }
API response: converted charges schedule and source metadata
Copied from Output file (JSON), data › metadata
Open the whole JSON file ↗| ✓ | Expected: The table retained as a table, with correct headers, rows, columns and values.Found: Firecrawl returned one table with four headers—determination, method, turnaround and charge per sample—and eight rows. No values were invented, split or dropped. |
The result is a pass because the table retained its headers and all eight rows, with each cell in the correct column.
Letterhead omitted. The page-one letterhead, including the company name, address, telephone number and email address, is absent from the output. The converted document opens at the title.
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 | Table Extraction → | |
| Scenario | A simple, clearly formatted table → | |
| Tool | Firecrawl → |
Global scenario definition → · Global capability definition → · Firecrawl 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.