You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Multi-column tables collapse into unreadable single-column blobs during PDF conversion #173
When a PDF page contains a multi-column layout (e.g. a table with grouped bullet lists per cell), anydoc's Markdown table reconstruction collapses the columns into a garbled single blob, losing row/column structure and legibility.
The source page contains an "Annex III use cases" table with ~9 category rows (Non-banned biometrics, Critical infrastructure, Education, Employment, Public/private services, Law enforcement, Migration, Administration of justice), each listing several bullet points.
anydoc's output merges all of this into a handful of malformed Markdown table rows with empty leading cells, run-together bullet text with no line breaks, and stray glyph artifacts (e.g. |||flfi fi||fififififififififi|) in several rows across the document, not just this table.
Expected behavior
Either:
Reconstruct the table with correct row/column boundaries, or
Fall back to emitting the cell content as reading-order text/lists (as a plain pdftotext-style extraction does successfully on the same PDF) rather than producing a broken table that's less readable than plain text.
Environment
@firecrawl/anydoc version: 0.2.4
Invocation: CLI, no --ocr flag (native PDF text extraction path — same result with --ocr hosted)
It would be really nice to get this fixed. It's blocking a data extraction project I'm working on, which relies on AnyDoc for converting to Markdown before hitting an LLM. By getting a better parsing of nested tables or multi-column tables the data extraction will be more accurate for a wider array of layouts.
Same for me, if a cell has text in every new line (within the same cell), PDF parser parses the position of the cell accuratley, but it makes the text one string, loosing the structure. It must not make it one string, it must preserve the line breaks within the cell
Activity
diego-coba commentedon Sep 24, 2026
It would be really nice to get this fixed. It's blocking a data extraction project I'm working on, which relies on AnyDoc for converting to Markdown before hitting an LLM. By getting a better parsing of nested tables or multi-column tables the data extraction will be more accurate for a wider array of layouts.
MarcoMeyerDev commentedon Sep 29, 2026
Same for me, if a cell has text in every new line (within the same cell), PDF parser parses the position of the cell accuratley, but it makes the text one string, loosing the structure. It must not make it one string, it must preserve the line breaks within the cell