Convert PDF to Numbers on iPhone (2026 native workflow)

The PDF is already on your iPhone. It arrived as a Mail attachment, an AirDrop from someone’s Mac, or a download in Safari, and it has a table in it you want in Apple Numbers — the invoice line items, the bank transactions, the price list. Not in Excel, not in a web tool that emails you a link, in Numbers: the spreadsheet that is already on your phone, syncs through iCloud to your Mac and iPad, and opens the instant you tap it. The catch is the same one every spreadsheet has — Numbers has no “import PDF” button. On the iPhone it is even starker than on a Mac: there is no Preview, no Text to Columns, no desktop app to lean on for the in-between step.

The usual workarounds are all bad on a phone. Copy-pasting from a PDF in Files dumps the whole table into one mangled cell. Emailing the file to a desktop converter defeats the point of doing this on the device the file already lives on, and ships your financial data to a stranger’s server. Retyping a statement on a phone keyboard is a special kind of misery. What you want is a path that stays on the iPhone, 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 iPhone — the PDF read on-device, never uploaded — with clean columns that carry straight into Numbers.

Why Numbers, and why the iPhone makes sense for this

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

And the iPhone is a genuinely good place to do this, not a compromise, for three concrete reasons:

• The document is read on the iPhone. The PDF itself never leaves the phone — only the text recognized on-device is sent to ignitai’s private pipeline. For a bank statement or a pay stub, that matters directly: the file is never uploaded. On iOS 26, Apple’s newest document recognition reads tables natively for sharper extraction.
• The share sheet is the entire workflow. The PDF is already in Mail, Files, or Safari. You tap Share, send it to the converter, and you are one step from a Numbers file — no detour through a desktop, no cable, no “email it to myself.”
• It is the device you actually have. The statement lands on your phone the moment the bank sends it. Doing the conversion there means the moment you have the PDF is the moment you can have the spreadsheet, in line at the coffee shop, not when you are next at your desk.

But Numbers was never built to ingest PDFs. Its import path accepts CSV and Excel — 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.” A PDF has no concept of a cell — the text you see in a tidy grid is, underneath, 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 iPhone the constraint is tighter, so the in-between step has to do more of the work.

Method 1: ignitai on iPhone (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 iPhone flow:

1. Send the PDF to ignitai. From Mail, Files, or Safari, tap Share and pick ignitai. Or open ignitai first and import from the Files browser. Several PDFs at once are fine — a batch of receipts imports in one motion.

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

   “Extract the transaction table: date, description, amount. One row per transaction. Skip the summary block at the top.”

   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 — which is exactly where drawing boxes on a phone would be painful.

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 iPad too — you can start it on the phone and finish it on the desktop.

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, on a phone, which is the worst place for fiddly cleanup. Consistent bare values 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 (it usually lands there automatically).
3. Open Numbers, tap the … button → 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 bank-statement-to-CSV flow on iPhone if your endpoint is a budgeting app rather than a Numbers sheet.

A worked example: an invoice to Numbers, on the phone

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

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. Tap Convert. A few 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 on iPhone — swap the prompt for the transaction columns and the output is a Numbers ledger instead of an invoice sheet. Because the sheet lives in iCloud, the spend total you build on the phone is on your Mac the next time you open it.

Which PDFs convert cleanly, and which need a prompt

Knowing what kind of PDF 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 on a phone.
• 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 with the iPhone camera, a statement that came 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 born-digital PDF, which is the entire reason a snapped receipt converts on the iPhone as easily as a downloaded invoice. If you mostly work with paper, the scan-receipts-to-spreadsheet flow on iPhone is built around exactly this case.

The practical rule: one table you want all of, one short line; several tables 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 iPhone

The phone is not limited to one file at a time. Select several PDFs in the Files browser, send them to ignitai, apply one prompt, and every document flows into the same workbook — one row per record, with document-level fields like the vendor or date repeated on each row so every line stays attributable. A month of receipts 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 printed on the PDF — the invoice total, the statement ending balance, the row count — 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 even on a phone. This is the whole 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 iPhone 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 entire 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. The longer explanation of how the on-device reading works is in the AI PDF-to-CSV walkthrough.

Bottom line

Numbers cannot open a PDF, but your iPhone can turn one into a Numbers file without the data ever leaving the phone. Share the PDF to ignitai, describe the table you want in a sentence, convert to Excel, and open the result in Numbers — the PDF is read on-device on every supported iOS version, one formatting pass sets the currency and date columns, and one Save writes a real .numbers file. The sheet syncs to your Mac and iPad through iCloud, and the printed total ties out to a SUM in under a minute. For the same job on a bigger screen, see convert PDF to Numbers on iPad or on Mac.

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

FAQ

Can I convert a PDF to a Numbers spreadsheet on my iPhone?

Yes — share the PDF into ignitai, describe the table in one sentence, convert to Excel (XLSX), and open the result in Numbers. Each field lands in its own column, and one Save in Numbers writes a real .numbers file.

Will the file sync to Numbers on my Mac and iPad?

Yes — save it to iCloud Drive and it behaves like any Numbers document: open on the iPhone now, and the same sheet is on the Mac and iPad seconds later.

Is the PDF uploaded during the conversion?

No — the PDF is read on-device on every supported iOS version and never uploaded. Only the text recognized on the phone goes to ignitai’s private hosted pipeline to build the spreadsheet.