Convert PDF to Numbers on iPad (2026 native workflow)

You have a PDF with a table in it — an invoice, a price list, a bank statement, a roster — and you want it in Apple Numbers on your iPad. Not in Excel, not in some web tool that emails you a download link, but in Numbers: the spreadsheet that is already on your iPad, syncs through iCloud to your Mac and iPhone, and opens the moment you tap it. The trouble is that Numbers has no “import PDF” button. You can open a PDF in Files, you can mark it up, you can share it — but you cannot turn its table into editable Numbers rows without a step in between.

The usual workarounds are all bad. Copy-pasting from a PDF in Files dumps the table into one mangled column. Emailing the PDF to a desktop converter defeats the point of working on the iPad at all, and sends your financial data to a stranger’s server. Retyping is retyping. What you want is a path that stays on the iPad, never uploads the file, and ends with the table in Numbers with proper columns — a real .numbers file after one Save.

This guide is that path: convert PDF to Numbers on iPad — the PDF read on-device, never uploaded — with clean columns that carry straight into Numbers.

Why Numbers, and why this is harder than it should be

Numbers is the right spreadsheet for a lot of iPad work. It is free, it is Apple-native, its tables look good without fiddling, and it round-trips through iCloud so the sheet you build on the iPad is on your Mac before you have closed the lid. For anyone living inside the Apple ecosystem, a sheet that ends up saved in Numbers beats one left stranded as a stray .xlsx.

But Numbers was never built to ingest PDFs. Its import path accepts CSV, TSV, and Excel files — not PDF. So the real task is not “open the PDF in Numbers”; it is “turn the PDF’s table into structured data Numbers will accept, without losing the column boundaries along the way.” A PDF has no concept of a cell. The text you see in a tidy grid is, underneath, just a stream of characters with x/y coordinates, and the moment you copy it, the grid is gone. That is why every copy-paste attempt collapses into a single column.

The Mac has the same limitation, which is why the PDF-to-Numbers workflow on Mac exists. On the iPad the constraint is tighter — there is no Preview, no Text to Columns, no desktop spreadsheet to lean on — so the in-between step has to do more of the work.

Why the iPad is a genuinely good place to do this

It is easy to assume the iPad is the compromise device and the “real” work happens on a Mac. For PDF-to-Numbers, that is not true, for three concrete reasons:

• The document is read on the iPad. The PDF itself never leaves the tablet — only the text recognized on-device is sent to ignitai’s private pipeline. For a bank statement or a pay stub, that matters: the file is never uploaded. On iPadOS 26, Apple’s newest document recognition reads tables natively for sharper extraction.
• The share sheet is the whole workflow. A PDF arrives as an email attachment, an AirDrop, or a download in Safari. On the iPad you tap Share, send it to ignitai, and you are one step from a Numbers file — no file-management detour through a desktop.
• Apple Pencil and split view make the spot-check fast. Put the source PDF on one half of the screen and the new Numbers sheet on the other, and verifying that the totals match is a glance, not a context-switch.

Method 1: ignitai on iPad (the no-upload way)

ignitai reads the rendered page the way a person does — it sees the table as a table — and writes the result to a clean Excel file that Numbers opens directly. The full iPad flow:

1. Send the PDF to ignitai. From Files, Mail, or Safari, tap Share and pick ignitai. Or open ignitai first and import from the Files browser. Multiple PDFs at once are fine — a month of invoices imports in one multi-select.

2. Describe what you want, in plain English. You do not draw selection boxes. You type a sentence:

   “Extract the line-item table: description, quantity, unit_price, and line_total, one row per item. Skip the header and footer blocks.”

   If the PDF is a simple single-table document, a one-line prompt — or a tap on the Tables starter template — is all it takes; a prompt is always part of the flow. The detailed sentence is there for when the page has more than one table and you want a specific one.

3. Choose Excel (XLSX) as the output format. ignitai produces an .xlsx with every field in its own column and clean, consistent values — ISO dates, bare amounts — and Numbers opens XLSX natively.

4. Tap Convert. ignitai reads each page on-device and builds the table. A single multi-page PDF finishes in a few seconds; a batch shows live progress as pages are read and parts upload.

5. Open in Numbers, format, and tap Save. Tap the result and it opens in Numbers directly, columns intact. Give the amount column a currency format and the date column a date format — one selection each — and one Save writes a native .numbers document; keep it in iCloud Drive and it is on your Mac and iPhone too.

The reason clean extraction matters: the usual web-converter output fuses symbols into the text — $45.20 as a string, three date styles in one column — and the untangling is yours, cell by cell. Consistent bare values from a prompt-driven extraction keep the Numbers formatting pass to one selection per column.

Method 2: the CSV-then-import fallback

If you’d rather extract to CSV first — a handy interchange format when the sheet is headed somewhere beyond Numbers — the path is one step longer:

1. Extract to CSV in ignitai using the same plain-English prompt.
2. Save the CSV to Files (or it lands there automatically).
3. Open Numbers, tap the … menu → Open, and pick the CSV. Numbers imports it as a new spreadsheet.
4. Set the currency and date column formats once. Done.

This is the path Numbers’ own import accepts, and it is reliable — the one-pass formatting is the same either way. The same CSV extraction underpins the AI PDF-to-CSV workflow if you want the longer explanation of how the on-device reading works.

Worked example: an invoice to Numbers

Say a supplier emailed you a PDF invoice and you want the line items in Numbers to roll into a running spend sheet:

1. In Mail, tap the PDF, Share, pick ignitai.
2. Prompt: “Line items only — description, quantity, unit_price, line_total. One row per item.”
3. Output format: Excel.
4. Convert. Seconds later you tap the file and it opens in Numbers. Give line_total a currency format, tap Save, and it’s a .numbers document in iCloud.
5. In Numbers, drop a SUM under the line_total column and confirm it matches the invoice total printed on the PDF. If it ties, the extraction is clean.

The same flow handles a bank statement to a spreadsheet on iPad — swap the prompt for the transaction columns and the output is a Numbers ledger instead of an invoice sheet.

Which PDFs convert cleanly, and which need a prompt

Not every PDF is the same shape, and knowing which kind you are holding tells you how much of a prompt to write:

• A single-table PDF — a one-page price list, a simple invoice, a class roster — converts with a one-line prompt or a tap on the Tables starter template. ignitai finds the table, infers the columns, and hands you a sheet Numbers opens. This is the bulk of everyday documents and the fastest path.
• A multi-table PDF — a bank or brokerage statement, a report with a summary block plus a detail table — is where the plain-English prompt earns its keep. You name the table you want (“the transaction detail, not the summary”) and the rest is ignored. Without that sentence you would get every table stacked together.
• A scanned PDF or a photo of a document — a receipt you snapped, a statement your bank mailed on paper — has no text layer at all, so copy-paste and Numbers’ own CSV import have nothing to read. ignitai reads the rendered image the same way it reads a native PDF, which is the entire reason a scanned receipt converts on the iPad as easily as a downloaded invoice. If you mostly work with paper, the scan-receipts-to-spreadsheet flow on iPad is built around exactly this case.

The practical rule: if the PDF has one table and you want all of it, one short line. If it has several and you want one, spend the extra sentence. Either way the sheet ends up in Numbers, and either way the PDF is read on-device.

Batches on the iPad

The iPad is not limited to one file at a time. Multi-select the PDFs in the Files browser, send the lot to ignitai, apply one prompt, and every document flows into the same workbook — one row per line item, with the invoice number and vendor repeated on each row so every line traces back to its document. A month of invoices becomes a single spend sheet without you opening any of them individually. If a file trips the batch (a password-protected PDF, a corrupt download), unlock or fix it and run the batch again.

The one check that catches every error

Whatever the document, do the same verification: find the total that is printed on the PDF — the invoice total, the statement ending balance, the count of rows — and reproduce it in Numbers with a SUM or a COUNTA. If the spreadsheet total matches the printed one, the table came across correctly. If it does not, sort the column and look for the row that is off; it is almost always a single merged cell or a footnote that crept into the data, and it takes under a minute to find. This is the entire advantage of having the data in Numbers instead of a PDF: the math is checkable.

A note on privacy

A PDF you convert on the iPad with ignitai is read on the device. For a price list that does not matter. For a bank statement, a pay stub, or anything carrying an account number, it is the whole point — the file is never uploaded, never sits on a converter’s server, never appears in an email you have to remember to delete. Only the text recognized on-device goes to ignitai’s private pipeline to build the spreadsheet.

Bottom line

Numbers cannot open a PDF, but your iPad can turn one into a Numbers file without ever leaving the tablet. Share the PDF to ignitai, describe the table you want in a sentence, convert to Excel, and open the result in Numbers — one formatting pass on the currency and date columns, and one Save writes a real .numbers file. The PDF is read on-device and never uploaded, the finished spreadsheet syncs to your Mac through iCloud, and the printed total ties out to a SUM in under a minute. For the desktop version of the same job, see convert PDF to Numbers on Mac.

Get ignitai on the App Store and convert your first PDF to Numbers on iPad today.

FAQ

Can Numbers open a PDF on iPad?

No — Numbers has no PDF import on any platform. ignitai closes the gap: share the PDF in, describe the table you want, convert to Excel (XLSX), and open the result in Numbers — one Save and it’s a native .numbers document.

Do dates and currency columns come in already typed?

The extraction writes clean, consistent values — ISO dates, bare amounts with no symbols glued on — so the formatting pass in Numbers is one selection per column. After that, a =SUM() under the amount column ties against the printed total immediately.

Does the PDF stay on the iPad?

Yes — it’s read on-device on every supported iPadOS version and never uploaded. Only the recognized text goes to ignitai’s private hosted pipeline to build the spreadsheet, which opens in Numbers and syncs to your other devices through iCloud like any Numbers document.