Convert PDF to Numbers on Mac (2026 native workflow)

You opened the PDF in Preview, selected the table, copy-pasted into Numbers, and got one column of mashed text where the rows should have been. You tried File → Open from Numbers and got a polite refusal — Numbers opens .numbers, .xlsx, .csv, and .tsv, not .pdf. You searched “convert PDF to Numbers” and got a list of web tools that want you to upload your file, then deliver an .xlsx full of stringified columns you re-type by hand.

The gap is real. Numbers is the spreadsheet for a Mac-primary user — handoff to Pages, native iCloud sync to iPad and iPhone, sane chart defaults, the Smart Categories pivot view that Excel still can’t quite match. But the file format is a closed bundle, the import paths are narrow, and the world ships PDFs not XLSX.

This guide covers the workflow that actually works in 2026: convert PDFs to Apple Numbers spreadsheets on Mac — files read on-device, never uploaded — with clean columns, formulas re-applicable, and the round trip to iPhone and iPad working over iCloud.

Why Numbers (and how the XLSX hop actually works)

There is no converter — ignitai included — that writes a .numbers file directly, because Apple’s format is a closed bundle with no public writer. The honest fastest path is a two-step: extract the PDF to a clean XLSX or CSV, open it in Numbers (which imports both natively), and do one File → Save — from that moment the document is a native .numbers file. What decides whether this works well is not the Save; it’s whether the columns arrive clean:

Clean values make the formatting pass trivial. The extraction writes consistent values — ISO dates, bare numbers with nothing glued on — so giving each column its format in Numbers is one selection per column (Format → Data Format), and from the first =SUM() after that the sheet behaves natively. The usual web-converter output — $45.20 fused into a text string, three date styles in one column — is what turns the cleanup into an afternoon.
Numbers-specific features are added after the Save, and they stick. Conditional formatting, slider controls, checkboxes, and Smart Categories don’t exist in XLSX — you add them in Numbers once the document is .numbers, and they persist through every iCloud round-trip. Just don’t export back to XLSX afterward, or they’re lost.
iCloud sync is reliable for .numbers, less so for XLSX left un-saved in the Numbers app. A .numbers file edited on Mac, opened on iPad, edited again on iPhone, and reopened on Mac just works. The one-time Save is what buys you that.
Numbers handles freeform layouts that Excel doesn’t. Multiple tables on the same sheet, floating images and shapes between tables, tables that aren’t anchored to A1 — all first-class in Numbers once the document is native, and worth arranging after the Save.

For a quarterly report that lives in Numbers across three Apple devices, the goal is a native .numbers document with honest cell formats — the clean-XLSX hop plus one Save is the shortest route there.

What “PDF to Numbers” actually means

There are three kinds of PDF a Mac user typically wants in Numbers, and they need different treatment:

A PDF with a table that’s literally a table. Bank statements, sales reports, supplier price lists. Drawn grid lines, rows are rows, columns are columns. The job is to extract the table and land it in a Numbers sheet with the columns intact and the values consistent enough that one formatting pass makes them numbers, dates, and currency.
A PDF with implicit tabular data. Receipts, invoices, contracts with embedded line items, lab reports. The data is structurally a table — line items, totals, key/value metadata — but visually it’s a designed page with boxes, headers, and prose around it.
A scanned PDF. A paper document photographed or scanned. The “PDF” is really an image wrapped in a PDF container; the OS doesn’t see selectable text. OCR is a prerequisite before any extraction.

The first case has a few decent free paths. The second and third are where the workflow matters.

Method 1: ignitai → Numbers (the no-upload way)

ignitai treats extraction as a language task: take the PDF (text or scan), describe what you want, get back a structured spreadsheet. On Mac, the path into Numbers is the clean XLSX plus one Save.

Open ignitai. Drag the PDF in. A single PDF or a whole selection of them. Each file is read on-device — the PDFs are never uploaded — and only the recognized text is sent to ignitai’s private hosted pipeline to build the spreadsheet.
Describe what to extract, in plain English. For a typical sales report:

“Return one row per line item with date (ISO 8601), product_sku, product_name, quantity, unit_price, line_total, customer_name, and region.”

Save the prompt as a preset for next quarter. (Want the report-level metadata — total revenue, report period — as its own table? Run a second pass with a summary prompt; each run produces one table.)
Pick Excel (XLSX) as the output format. ignitai writes an .xlsx with one sheet — one row per line item, values as clean, consistent text ready for a one-pass format in Numbers.
Hit Convert. A single PDF usually converts in under a minute; a large batch takes a few minutes.
Open the XLSX in Numbers, format, and hit File → Save. Numbers opens the workbook directly with every field in its own column. Give the amount columns a number or currency format and the date column a date format — one selection each — and the Save writes a native .numbers document.

After that one Save you have a Numbers document, not a Numbers-flavored XLSX. Smart Categories work, sliders work, conditional formatting saves correctly, and iCloud round-trips to iPhone and iPad without rewriting cell types.

Method 2: Preview → copy → Numbers (the no-install path)

For one clean text-based PDF with one obvious table:

Open the PDF in Preview.
Hold Option to toggle rectangular selection. Drag a rectangle around the table.
Cmd-C to copy.
Open Numbers, place the cursor in cell A1, Cmd-V to paste.
If the result lands as a single column of concatenated rows, undo, and use Edit → Paste and Match Style instead. If that still mashes, the PDF lacks proper table structure and Method 1 is the right path.
Spot-check three things: the row count matches the source, the right-most column landed as numbers (Numbers has “Number” in the column-type indicator), and the date column landed as dates (not text strings that look like dates).

Works on PDFs with proper text + table structure. Fails on every scanned PDF and on most PDFs from older accounting software that draws tables as positioned text boxes rather than tagged tables.

Method 3: tabula-py + a script (the DIY path)

For a Mac-primary developer with a recurring single-source PDF (one supplier, one statement format, stable layout):

brew install tabula-java
pip install tabula-py pandas

Then a script that opens the PDF and writes a CSV that Numbers opens cleanly:

import tabula
tables = tabula.read_pdf("report.pdf", pages="all", lattice=True)
tables[0].to_csv("report.csv", index=False)

Open report.csv in Numbers; File → Save writes it as a native .numbers document.

This is a perfectly fine path for one stable PDF source. It breaks the moment the source is a scan, the layout changes, or the PDF has multiple tables of different shapes you have to stitch back together. For a single recurring report, the script pays for itself once. For a varied batch, the per-PDF maintenance burden eats the savings.

Method 4: Web converters (and why most Mac users shouldn’t)

Smallpdf, iLovePDF, Adobe’s PDF-to-Excel — all work, all output XLSX, all want you to upload. The reasons not to use them for a real Numbers workflow:

The output is a messy XLSX. Numbers will open it, but the values tend to arrive fused — currency as text with a $ glued on, three date styles in one column — and the untangling is yours. Prompt-driven extraction at least hands you consistent, clean values (ISO dates, bare numbers), so the one formatting pass in Numbers stays one pass.
Privacy surface. A bank statement, a salary file, or a supplier price list is exactly the kind of document you don’t want in a shared upload bucket — even with a documented retention policy, your data left the device.
Free-tier gating. One to three files free, then a monthly subscription. The recurring fee is the same magnitude as a one-time on-device app while keeping your data on the third-party server.
No Apple-aware output. None of them know what Numbers wants — Smart Categories, ISO date parsing, currency-symbol recognition. You get an XLSX, and the polish is yours to redo.

For a tutorial PDF with no real data, fine. For your actual Mac workflow, no.

What “preserved formatting” looks like in practice

A clean PDF-to-Numbers result has four properties the extraction either sets up or doesn’t:

Values that format in one pass. A bare 1234.56 becomes a number cell the moment its column gets a Number format — no stray symbols or footnote markers to strip first. Numbers’ formula bar tells you where you stand: a number cell shows the bare number; a text cell shows literal text.
Currency in the format, not fused into the text. Ask the prompt for bare amounts (one consistent currency, or a separate currency column), then apply Numbers’ Currency format so the $ or € is carried explicitly. An extraction that fuses $45.20 into a text string loses the unit and fights the format.
Dates that behave as dates. Extract ISO 8601 (2026-04-17) and one Date & Time format on the column makes sorting chronologically, grouping by month, and =YEAR()/=MONTH() all work. Three date styles mixed in one column break all three.
One table per pass, assembled in Numbers. Header metadata and line items are two extraction passes — one prompt each — and the two results become two sheets you keep in one Numbers document, so a formula in the metadata sheet can point at a SUM over the line items. Rearranging them onto one Numbers sheet, side by side, is a drag after the Save.

If your converter gets the table out but hands you fused, inconsistent values, you’re inheriting work — every column needs hand-cleaning before its format will take. Method 1’s prompt-driven extraction lets you specify the value shapes up front (ISO dates, bare signed numbers); the other methods leave them to chance.

A worked example: turning a quarterly bank statement into a Numbers ledger

Concretely: you have a 14-page Q1 bank statement PDF and want a Numbers ledger that splits transactions into income, recurring expenses, and one-off purchases for the quarter. The end-to-end flow on Mac:

Drag the statement into ignitai.
Prompt:

“Return one row per transaction with date (ISO 8601), description, amount (positive for credits, negative for debits), running_balance, and category (one of: income, recurring_expense, one_off, transfer). Infer category from description; mark recurring if the description matches another transaction within the same statement period.”
Pick XLSX output.
Open the workbook in Numbers, give amount and running_balance a currency format and date a date format — one pass — and hit File → Save. The transactions now live in a native .numbers document.
Add a Smart Category in Numbers grouped by category. Numbers shows quarterly totals per category natively, with subtotal rows you can collapse.
The same .numbers file syncs to your iPad over iCloud. You can review the summary on the iPad on the train without re-importing.

The whole ledger lives natively in Numbers. No web-converter detour, no losing the Smart Category on the next round-trip, no hand-cleaning a mangled date column.

For the broader bank-statement workflow with CSV output, the Mac CSV bank-statement guide covers the QuickBooks / Xero import path. For the iPad-side review, the iPad bank-statement guide is the partner.

Round-tripping Numbers → iPhone and iPad

The Numbers file format syncs over iCloud Drive without any export/import friction. For a Mac-extracted Numbers file:

Save the document into iCloud Drive (any folder).
On iPhone or iPad, open Numbers; the file appears in the Recent list.
Edit on either device; the change syncs back to the Mac within seconds.

That’s the whole appeal of staying Numbers-native. The same .numbers file is the Mac desk view, the iPad couch view, and the iPhone on-the-go view, with no format conversion in the loop. Posts that target the mobile-side workflows — the iPhone receipt scanner guide and the iPad receipt review guide — converge on the same pattern: capture or extract on the right device, sync the Numbers file across all of them.

When Numbers is the wrong target

Honest cases where Numbers isn’t the right output:

Your accountant uses Excel. If the file is going to leave your Mac and land on a Windows desktop, save the final as XLSX (File → Export To → Excel). Use Numbers as the working format, XLSX as the handoff.
You need pivot tables Excel-style. Numbers’ Smart Categories cover most of what pivot tables do, but if you have an accountant building cross-tab pivots with calculated fields, Excel’s pivots are still ahead. Stay in XLSX.
You’re feeding data into a script or a database. Numbers .numbers files are bundles, not flat. Output CSV (or have ignitai write CSV directly) and skip Numbers as an intermediate.
Your data has many sheets that need to behave as a workbook. Numbers handles multi-sheet documents fine, but Excel’s cross-sheet INDIRECT references and named-range scoping are more deterministic. Heavy multi-sheet workbooks belong in Excel.

For Mac-primary single-document personal and small-business work, Numbers is the right native target. For team handoffs to Windows users, fall back to XLSX.

The two reconciliation checks per import

After importing into Numbers, two quick checks separate “I have a file” from “I have a working sheet”:

Column-type spot-check. Click each column header. The column-type indicator should match the data: Number for amounts, Date and Time for dates, Currency for monetary columns. Any column inferred as Text where it should be Number means a formula bar will treat it as a string and your SUM will return zero. Fix in Format → Data Format.
Row-count sanity. The bottom of the table should show a row count that matches what the PDF actually had. PDFs with multi-line cells (a description that wraps onto a second visual line) sometimes import as two rows; the inverse — two source rows merging into one — is rarer but worth catching. Compare against the PDF page count or the visible row count in the source.

Skip these two and the formula error surfaces an hour into the analysis, when you’ve already built three charts on top of stringified numbers.

Bottom line

For a Mac-primary user who wants a Numbers-native sheet from a PDF: install ignitai, drag the PDF in, write the prompt once, convert to XLSX, open the result in Numbers, set the column formats once, and hit File → Save — the document is native .numbers from then on. For a single clean text PDF with no real data, Preview → copy → Numbers paste works in a pinch. For a recurring single-source PDF a developer can script, tabula-py plus a CSV save is fine. For everything else — scans, mixed templates, multiple tables, anything you’d rather not upload — the on-device path is the shortest distance from PDF on disk to a Numbers document that round-trips cleanly across your Apple devices.

The CSV-output equivalent for accounting handoffs is in the Mac CSV with AI guide; the Mac batch pattern across mixed document types is in the Mac batch guide; the Excel-on-Mac path for invoice workflows is in the Mac invoice guide. The app is the same; only the output format changes.

Get ignitai on the App Store — free download, $19.99/mo unlocks unlimited extractions after the 3-day trial.

FAQ

Can Numbers on Mac open a PDF?

No — Numbers has no PDF import. The working path is ignitai: drop the PDF in, describe the table you want in plain English, extract to Excel (XLSX), and open the result in Numbers — one File → Save writes a native .numbers file.

Does the conversion keep number and date formatting?

The extraction writes clean, consistent values — ISO dates, bare numbers with no symbols glued on — so the formatting pass in Numbers is one selection per column (Format → Data Format), and File → Save keeps those formats in the native .numbers document from then on.

Is the PDF uploaded anywhere in the process?

No — the PDF is read on the Mac (macOS 14.4 or later) and never uploaded. Only the recognized text is sent to ignitai’s private hosted pipeline to build the spreadsheet you open in Numbers.