Guide

Why converting a PDF table to CSV is harder than it looks

Updated

The frustrating thing about this problem is that the table is obviously there on the screen. Understanding why the computer cannot see it makes the rest of the subject straightforward.

Talk to a specialist

Question 1

Open the PDF and try to select a line of text. What happens?

This one test separates the three fundamentally different cases, and it takes five seconds. Everything downstream depends on the answer.

There is no table in the file

A PDF describes where characters and lines go on a page. In general it does not record that characters form a cell, cells a row, or rows a table.

So every conversion is inference. The tool looks at positions and at any ruling lines and reconstructs a grid that was never stored. Two files that look identical can have completely different underlying structure, which is why one converts perfectly and the next one does not.

The three cases

A text layer with a table: the characters are present and only the structure has to be inferred. This is the good case.

A scanned image: there are no characters at all, only pixels, and optical character recognition has to invent them before anything else can happen.

A tagged PDF: the file carries semantic structure describing headings, tables and reading order. This is the best case and it is rare outside documents produced to an accessibility standard.

Why accessibility and extraction are the same problem

A screen reader and a converter are both trying to recover meaning from a file that records appearance. What defeats one defeats the other.

So gov.uk's accessibility guidance, though written for another purpose, is a useful diagnostic. A scanned document cannot be searched or read by a screen reader: exactly what makes it unconvertible.

Its note that PDF and PDF/A cannot be made fully accessible to all assistive technology users explains why PDF extraction is unreliable in general, not only sometimes.

The question to ask before converting anything

Does the source data exist in a machine-readable form? A PDF was generated by something, and that something had the data in a database, a spreadsheet or a report.

Asking for a CSV takes one email and succeeds more often than people expect, particularly with a supplier, a bank or a public body. Every hour spent on extraction is an hour spent recovering something that already exists somewhere in a better form.

Have a lot of these, or one that will not behave?

Tell us what the documents are and how many. Data extraction suppliers who handle that kind of file will contact you directly.

Next: where to reach you.

  • Free, no obligation
  • We never ask you to upload a document here
  • No marketing lists, ever

One selection test, and you know the route

What happens when you select the text, what the data looks like, and whether it is personal. Three answers.

Sources

This site's own datasets, every figure quoted from its source and dated:

  • The Converter File Handling carries 14 published figures read from 11 sources' own pages; the 11 published figures given without a breakdown run from 7 to 90 day, read 11 November 2026.
  • The PDF to CSV Converter Index carries 36 published figures read from 30 sources' own pages; the 30 published figures given without a breakdown run from 5 to 1,500 USD (43 sources publish a figure), read 11 November 2026.
  1. gov.uk, publishing accessible documents
  2. UK GDPR Article 28, processor (legislation.gov.uk)
  3. UK GDPR Article 5, principles relating to processing (legislation.gov.uk)
  4. UK GDPR Article 32, security of processing (legislation.gov.uk)
  5. ICO, UK GDPR guidance and resources
  6. gov.uk, accessibility requirements for public sector websites and apps
Talk to a specialist