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, keeps the data on the device, and lands a real .numbers file with proper columns at the end.

This guide is that path: convert PDF to Numbers on iPad, on-device on iPadOS 26+, with column types and formatting 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, exporting to Numbers beats exporting to a .xlsx you then have to manage.

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:

iPadOS 26+ runs the extraction on-device. On an M-series iPad (and recent A-series Pro models) running iPadOS 26 or later, the document never leaves the tablet. For a bank statement or a pay stub, that matters: the account numbers and balances are read locally, not uploaded.
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 on-device way)

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

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 folder of invoices imports in one motion.
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, you can skip the prompt entirely and let ignitai take the whole table. The prompt is there for when the page has more than one table and you want a specific one.
Choose Numbers as the output format. This is the step that makes the difference. Instead of a CSV you would have to import, ignitai produces a native .numbers file with the column types already set — text columns stay text, amounts become currency, dates become dates.
Tap Extract. The on-device model reads each page and builds the table. A single multi-page PDF finishes in a few seconds; a batch streams in with per-file progress.
Open in Numbers. Tap the result and it opens in Numbers directly, formatting intact, ready to sort and sum. Because it is a real Numbers file in iCloud, it is already on your Mac and iPhone too.

The reason the output-format choice matters: if you export CSV and then import it into Numbers, every column comes in as plain text and you re-type formats by hand — currency, dates, the lot. Exporting Numbers directly skips that entirely. The column types are decided during extraction, where the model already knows that “unit_price” is money and “quantity” is a count.

Method 2: the CSV-then-import fallback

If you are on an older iPad that ignitai exports CSV from rather than a native Numbers file, the path is one step longer but still entirely on-device:

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

This is the path Numbers’ own import accepts, and it is reliable — you just do the formatting that the direct-Numbers export would have done for you. 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:

In Mail, tap the PDF, Share, pick ignitai.
Prompt: “Line items only — description, quantity, unit_price, line_total. One row per item.”
Output format: Numbers.
Extract. Three seconds later you tap the file and it opens in Numbers, the line_total column already formatted as currency.
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 no prompt at all. ignitai finds the table, infers the columns, and hands you a Numbers sheet. 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, skip the prompt. If it has several and you want one, spend the one sentence. Either way the output format stays Numbers, and either way it runs on-device on iPadOS 26+.

Batches on the iPad

The iPad is not limited to one file at a time. Select a folder of PDFs in the Files browser, send the lot to ignitai, apply one prompt, and every document flows into the same Numbers sheet — one row per line item, each tagged with its source filename. A month of invoices becomes a single spend sheet without you opening any of them individually. The per-file progress shows which ones are done, and any that fail (a password-protected PDF, a corrupt download) are listed separately so you re-run only those, not the whole batch.

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 on iPadOS 26+ 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 data is never uploaded, never sits on a converter’s server, never appears in an email you have to remember to delete. If your iPad predates on-device support, ignitai falls back to a hosted pipeline with documented zero retention. Either way the file is not training anyone’s model and not lingering anywhere you did not put it.

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, pick Numbers as the output, and tap Extract — on iPadOS 26+ it runs on-device and lands a real .numbers file with currency and date columns already set. The data stays on your iPad, 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.