Convert a PDF Table to an Excel Spreadsheet

Last updated: 2026-09-16

Just the table, not the whole document

Search this and look at what actually ranks: the first result is a Reddit thread in r/ExcelTips called "Convert PDF table into an excel document?", and further down sits a question on Microsoft's own support site titled "Export PDF table into Excel". People are asking each other, in public, in 2025. That is usually a sign that the tools answering the query are answering a slightly different question.

The difference is the word table. Almost nobody wants their forty-page annual report turned into a spreadsheet. They want the fee schedule on page 4, the bank statement rows, the tender's bill of quantities, the lab results — one grid, inside a document that is mostly prose. Pouring the entire PDF into one sheet is technically a conversion, and leaves you exactly where you started.

So the workbook is organised the way the source is: one sheet per page of the PDF, named P1, P2, P3 and so on. Finding your table means opening the sheet whose number matches the page it was printed on. It sits there as a live block of cells — select the range, copy, paste into whatever model you already keep. The rest of the page comes with it, in reading order: the heading above the table, the unit note beneath it, the footnote that says which year the figures are. That context is what makes the numbers mean anything, and a table-only extractor throws it away.

One cell per cell: what "correct" looks like

There are two ways a PDF table lands wrongly in a spreadsheet, and they are worth naming because they are what you should check for in any result, ours included. The first is collapse: a whole row arrives crammed into one cell, so you spend the afternoon in Text-to-Columns. The second is shatter: the row is split, but at the wrong places — a wrapped description becomes two rows, a blank cell shifts everything after it one column left, and the sheet looks plausible while being wrong in a way no total will reveal.

Correct means something narrower than "it looks like the PDF". It means the grid in the document and the grid in the sheet are the same grid:

• Rows and columns as the source drew them — an empty cell stays an empty cell in its own column rather than closing up the row behind it.
• Merged cells stay merged. A header spanning three columns is written as one merged cell over three columns — not repeated three times, and not dumped into the leftmost one. Row-spanning labels down the side of a table work the same way.
• Column widths and row heights come from the source's own measured geometry, so the sheet opens at roughly the proportions the page had instead of every column at Excel's default width.
• Cell borders are carried, so a ruled form still reads as a ruled form.

And then it is checked rather than assumed. After the workbook is written it is validated, re-opened and read back cell by cell, and what came out is compared with what was extracted from the PDF — merges and borders included. That comparison runs on every conversion and is recorded alongside the job. It is no promise that nothing can ever be misread; it is the difference between a converter that hands you a file and one that has looked at the file first.

Three ways a PDF table ends up in a spreadsheet

The first two rows describe categories of tool, not any named product — we have run no competitor benchmark and will not publish numbers we did not measure.

An invoice code that starts with 0 still starts with 0

This is the failure that ruins a spreadsheet silently, and it is worth understanding once. A tax code, a bank account, an ID number, a part number: printed on the page as 012001900211, and arriving in Excel as 12001900211 — the leading zero gone, the identifier no longer matching anything you will try to match it against.

The cause is almost always the same, and it is not the reading — it is the writing. Something downstream looks at a string of digits, decides it looks like a number, and helpfully makes it one. So on this pipeline the type of a cell is decided when the PDF is read, from the glyphs actually printed on the page, and the component that writes the workbook is never allowed to infer it:

• A leading zero makes the cell text, always. No amount of "but it parses" overrides it.
• Very long digit strings stay text too — an 18-digit national ID or a 19-digit card number. Excel stores every number as a double-precision float and quietly loses the tail past about fifteen significant digits, so writing those as numbers would corrupt them inside Excel, where no read-back could catch it.
• A figure that really is a figure is written as a number, with the source's own presentation — a decimal part, thousands grouping, a currency or percentage format — so it sorts and sums without a cleanup pass first.

That is the whole of the "numbers still numbers" claim, and also its limit: what the page printed is what the cell holds.

Tables that are pictures (scanned PDFs)

Half the tables people need are not text at all. A scanned invoice, a photographed price list, a fax of a delivery note — there is no text layer to extract, only pixels, and a converter reading the text layer finds nothing to read.

Pages are classified one by one here, and a page with no usable text goes to an AI vision model that reads it and rebuilds it as document structure: headings, paragraphs, table rows. The output format is chosen at the end of that one pipeline — the same reading and the same rebuild produce a Word file, a workbook or Markdown, depending only on what you asked for. There is no separate, weaker path for spreadsheets.

Being straight about it: a scanned table is the hardest input on this page. Skew, stamps over the rules, handwriting in the blanks and a photocopier's dropout all make the grid harder to recover than a born-digital one. Check the sheet against the page before you trust a total. In Basic mode scanned pages come back as page images; AI mode reads them into real editable text, which costs real money per page, so it needs sign-in and a payment method — or your own API key.

Multi-page tables, and when we refuse to join them

A table that runs off the bottom of one page and resumes on the next is put back together before the workbook is written. It lands as one range on the sheet for the page it started on, and the header reprinted above the continuation is dropped rather than left in the middle of your data. A table spanning five pages keeps absorbing until it ends.

The test is deliberately hard to pass: two tables fused into one is damage you cannot see in the output and cannot undo. The columns have to agree — same count, same widths to within a fraction — and either the header repeats word for word or the page says continued (or 续表). Same shape but a different header, and it refuses. When it refuses you get the two halves as printed, on their own sheets — a copy and paste you can see rather than a join you cannot.

Chinese and mixed-language tables

CJK tables break tools in a way Latin ones do not, and the arithmetic is the reason. A full-width character occupies about twice the horizontal room of a Latin letter, so a column sized as though 宋体 text were English comes out half as wide as it needs to be and every cell arrives truncated on screen. Column widths here are measured with East-Asian width accounted for, so a Chinese column opens readable.

Full-width punctuation — the 、 enumeration mark, 《》 title brackets, the full-width comma — is carried as the characters it is rather than swapped for ASCII lookalikes, and a table mixing Chinese labels with Latin product codes needs no setting from you. If the document you are converting is mostly prose with tables in it, our Chinese PDF to Word page covers the Word side of the same engine, including what happens to scanned Chinese pages and to font names.

How to convert (3 steps)

1. Upload the PDF that holds the table — born-digital or scanned, up to 2,000 pages.
2. Output format is already set to Excel (.xlsx) — nothing to change unless you want a Word document instead.
3. Download the workbook and open the sheet numbered after the page your table was on.

Nothing to install, no redirect, nothing emailed to you. If you would rather have the document than the data, the same upload converts to Word instead — that is our main PDF to editable Word converter, and a PDF shaped like a slide deck is routed to PowerPoint automatically.

Scanned tables work the same way — see scanned PDF to Word.

Free, and no email required

Text-based PDFs — anything born digital, which is most reports, statements and exports — convert free in Basic mode, with no email address and no watermark. Basic mode is free and needs no account: 10 pages a day and 100 a month, rising to 100 pages a day and 1,000 a month once you sign in. The output format is deliberately not a pricing dimension: asking for a workbook costs exactly what asking for a Word file costs, which for a born-digital PDF is nothing.

Scanned pages are the exception, because each one has to be read by an AI vision model at a real per-page cost. That is AI mode: sign in and add a payment method, or paste your own Anthropic, OpenAI, Gemini or OpenAI-compatible API key. AI mode, which transcribes scanned pages into real editable text, requires a signed-in account with a payment method on file and draws on that same account allowance; beyond it, purchased pages are charged. Converting with your own API key is not metered at all. Without either, Basic mode still finishes the job free: the text pages come back as data and the scanned ones as page images. Page packs are listed on the pricing page and are not switched on yet; Basic mode and your own key are what is live today.

Uploads and finished workbooks are deleted automatically about six hours after conversion — see the privacy page. That matters more for spreadsheets than for most documents: the tables people convert tend to be the pages with the account numbers and the prices on them.

Sources

Background on the routes above, taken from each vendor's own documentation, each page checked 2026-09-16. Each vendor is quoted only about its own software.

• Adobe Help — Export PDFs to other file formats
• Microsoft Support — Import data from external data sources (Power Query)
• Microsoft Support — Format numbers as text
• Google Drive Help — Convert PDF and photo files to text