Pulls a table's structure out of a PDF into a real, editable XLSX file. Nothing is uploaded.
PDF to Excel
LocalHow a table gets found without being told where it is
A PDF does not store a table as a table — it stores each piece of text at an exact position on the page, with no record of which pieces belong to the same row or column. Finding the grid means reconstructing it from position alone:
| Step | What happens |
|---|---|
| Rows | Text at a similar height on the page is grouped into the same row, allowing a small tolerance for natural baseline variation |
| Columns | The starting position of every piece of text across every row is clustered into a set of column positions |
| Cells | Each piece of text is assigned to whichever detected column its position is closest to |
| Preview | The resulting grid is shown before anything is written, so you can check it before downloading |
This works well when a document was produced with an actual table — a report, an invoice, a price list — where columns line up consistently. It works poorly on a scanned image of a table, or a layout using merged cells and multi-row headers that do not have consistent column positions to detect.
Compared with the alternatives
| Tool | File goes | Accuracy claim |
|---|---|---|
| This page | Nowhere | None — see the preview instead |
| Smallpdf | Their servers | Not specified, OCR-based for scans |
| Several tools checked | Their servers | “99% accuracy” advertised |
| Adobe Acrobat | Depends on plan | Not specified |
What extracts cleanly, and what does not
| Table type | Result | Why |
|---|---|---|
| A simple grid: consistent columns, one line per row | Good | Column positions are consistent, so clustering finds them reliably |
| A table with a multi-line header | Mixed | Header rows may not align to the same column positions as the data below |
| Merged cells | Poor | A merged cell has no single column position to detect — it may land in the wrong column or split oddly |
| A scanned table (image, no text layer) | Not detected | This reads the text layer only; run PDF OCR first if the document is a scan |
Why the preview matters more than a setting
Row and column detection uses a small tolerance for natural variation — text on the same printed line is rarely at the exact same height to the point, and two genuinely separate columns still need to be told apart from one wide column with extra spacing. Rather than expose those tolerances as settings to tune, the preview shows the actual outcome so you can judge it directly:
| What you see in the preview | What it means |
|---|---|
| Rows and columns line up cleanly | The table is a good candidate — download with confidence |
| Two values merged into one cell | Those columns sit close together on the page; the source document's spacing is the limit here, not a setting |
| An extra blank row or column | Usually a stray mark or page number caught by the detector — harmless, easy to delete once in the spreadsheet |
| No table shown at all | The page's text has no consistent grid to detect — check whether it is a scanned page first |
Common mistakes
Frequently asked questions
Can I adjust how strict the row or column detection is?
There is no setting to tune — the preview exists instead, so you can see the actual outcome directly rather than guessing at a tolerance value. If two columns merge because they sit close together on the page, that is a property of the source document's layout, not something a setting here would fix.
Is my file uploaded?
No. It is read and the spreadsheet is written entirely in your browser — the network panel in developer tools shows no request carrying your document. The only network requests are for the two libraries, and they happen once.
Why didn't it detect my table?
Most commonly because the page is a scanned image rather than real text — this reads the text layer only. Run PDF OCR first if that is the case. It can also happen with layouts that do not have consistent column positions, such as heavily merged cells.
Will it work on any PDF table?
It works best on clear, regular tables with consistent columns — reports, invoices, price lists. Complex layouts with merged cells or multi-row headers may come out wrong. The preview shows the actual result before you download, so you can check rather than guess.
Can I choose which pages to convert?
Yes — type a range like 1-5, 8, or leave it as all. Each page with a detected table becomes its own sheet in the workbook.
Why does one column contain text that should be split into two?
Column detection groups nearby starting positions together; two genuinely separate columns that sit very close together on the page can be merged into one. This is visible in the preview before downloading, so you can catch it there.
Does formatting like bold or colour carry over?
No — this extracts the text and its position, not visual styling. The output is plain values in a grid, ready for formulas and sorting.
Is there a page or size limit?
No cap is imposed. Nothing runs on a server, so there is nothing to ration.
Related tools
See the full list of Document Tools, or try:
- PDF OCR — add a text layer to a scanned table first
- PDF to Markdown — text and tables as Markdown instead
- Markdown Table Generator — build a table from scratch
- Compress PDF — shrink the source file first if it is large
- Crop PDF — trim scanner margins before OCR and extraction