Numbers on a Mac cannot open a PDF as a spreadsheet, so a PDF to Numbers move takes one of two routes. You copy the table from Preview and paste it into a sheet, or you convert the PDF to CSV or XLSX and open that file. Either way, check the columns, dates and amounts afterwards.
Can Numbers open a PDF file directly?
Numbers does not open a PDF file as table data. Apple's guide to importing an Excel or text file into Numbers on Mac covers Excel workbooks and delimited or fixed-width text files. A PDF is neither, so dragging one onto the Numbers icon does not produce a table.
The reason is how a PDF is built. A PDF describes a printed page: each word sits at a position, with lines and boxes drawn around it. It has no idea which words form a row or which belong to the Amount column. A spreadsheet needs exactly that structure. Something has to look at the page and decide where each row and column begins, and Numbers does not do that step.
That leaves two practical routes, plus a fallback for difficult files:
- Copy and paste. Select the table in Preview, copy it, and paste it into Numbers. It costs nothing and suits a short table.
- Convert first. Turn the PDF into a CSV or XLSX file with a converter, then open that file in Numbers. It suits long tables and statements with many pages.
- Retype or re-scan. For a scan or a locked file, neither route may work, which the last section covers.
Copying a PDF table from Preview into a Numbers sheet
Copying a PDF table from Preview into a Numbers sheet works when the PDF has real text, and the table is short. Select the rows with the text tool, press Command-C, click a cell in Numbers and paste. You usually get each printed line as a row, but often with all the fields packed into one column.
What lands in the sheet depends on how the PDF stored its text. Three outcomes are common:
- Each field in its own column. The PDF kept tab characters between fields, and Numbers split on them. This is the best case and the least common.
- One line per row, all in one cell. The fields arrived separated by spaces. The sheet has the right number of rows but only one column. Splitting a stuck column in Numbers handles this result.
- Text in the wrong order. Preview read the page in a different order from the one you see, so a column's values come out in a block after the others, or two columns interleave. Copying one column at a time sometimes helps. For long tables, it is quicker to convert instead.
Watch the page breaks as you copy across pages. Page headers, footers and "continued" lines come along with the rows, and a repeated column heading in the middle of a table will turn a column of amounts into text. Delete those lines before you add any formulas.
Opening a converted CSV or XLSX of the PDF in Numbers
Opening a converted file in Numbers is the cleaner route for anything longer than a page. A converter reads the PDF and writes a CSV or XLSX file with each field in its own column. Numbers opens either one: choose File, then Open, or drag the file onto the Numbers icon in the Dock.
The choice between the two file types comes down to what you need to keep:
| Route | What arrives in Numbers | Good for | Watch out for |
|---|---|---|---|
| Copy from Preview | Plain text lines, often in one column | One short table | Merged fields, page headers, reading order |
| Converted CSV | Plain values, one field per column | Long statements, later import into other apps | Dates and amounts reinterpreted on open |
| Converted XLSX | Values plus number and date formats set by the converter | Keeping types and formatting | Formatting Numbers does not support |
A CSV carries only text, so Numbers decides what each value is as it opens the file. An XLSX carries types, so a date written as a date by the converter usually opens as a date. When the converter writes good types, XLSX saves a step. When you plan to feed the data into a budgeting app or another tool later, CSV is the more portable copy to keep. The step-by-step guide to opening a CSV in Numbers covers the Mac, iPhone and iPad.
The upload is where most converters stall if anything goes wrong. A bar that freezes at 99 percent is usually waiting on processing rather than on your connection, and the checks for a PDF upload stuck sending or processing explain how to tell the two apart.
For bank and card statements, FastBankConvert is being built to return the rows as CSV or Excel with the date, description, amount and balance in their own columns. It is not open yet; the homepage shows how a conversion is meant to work.
Numbers import settings that rebuild PDF columns
Numbers import settings let you re-split a CSV that opened with every field in one column. Select the table, open the Format sidebar, choose the Table tab and click Adjust Import Settings. On the Delimited tab you pick the separator, then click Update Table. The table is rebuilt with the new columns.
Apple's import guide lists the options on the Delimited tab:
- Separate Values Using. Tick one or more delimiters, such as comma, semicolon or tab, or type a custom one.
- Text Qualifier. The character that wraps a field, usually a double quote. It keeps a comma inside a quoted description from starting a new column.
- Text Encoding. Change it when accented letters or currency signs come out as odd symbols.
- Treat consecutive delimiters as one. Useful when a file pads fields with several spaces or tabs.
- Transpose rows and columns. Rarely wanted for statement data.
A Fixed Width tab is there too, for text files where each field takes a set number of characters. You drag markers in the column bar to set where each column starts. That suits some older bank exports that line fields up with spaces.
There is one firm limit. Apple's guide says you cannot adjust import settings after you edit the imported table. Open the file, fix the import settings first, and only then start typing, sorting or adding formulas. If you have already edited it, close the file without saving and open the CSV again.
Why do PDF dates and amounts change once they reach Numbers?
PDF dates and amounts change in Numbers because Numbers formats cells automatically. It reads each value as it arrives and guesses its type. Apple's page on formatting dates, currency and more in Numbers on Mac describes this automatic format. The guess follows your Mac's language and region, not the bank's.
That guess goes wrong in predictable ways with statement data:
- Day and month swap. A UK statement prints 04/03 for 4 March. On a Mac set to the United States, Numbers reads it as April 3. Values such as 25/03 cannot be a month-first date, so they stay as text. The column ends up half dates, half text.
- Year assumed. Many statements print only the month and day. Numbers has to supply a year, which may not be the statement's year for a December to January period.
- Amounts kept as text. A value with a trailing minus, such as 38.20-, or with a CR suffix, often stays text because it does not look like a number.
- Parentheses. Accounting reports print negatives as (38.20). Depending on settings, these may stay as text and drop out of totals.
A check list for the finished Numbers table
Run these checks on the table before you trust any total. The example figures below assume a one-month statement.
- Count rows against the PDF. If the statement lists 46 transactions, the table should have 46 data rows.
- Select the date column and look at the Cell tab in the Format sidebar. A mix of Date & Time and Automatic or Text means some dates were not read.
- Sort the date column. Dates from another month at the top or bottom point to a day and month swap.
- Sum the amounts and compare with the totals printed on the statement. A sum that is too small often means some amounts are still text.
- If the statement prints a running balance, check that the opening balance plus the transactions equals the closing balance.
Real dates that only display oddly take a new style from the Data Format menu. Text dates and swapped dates need the steps in fixing the Numbers app date format.
When the table is right and someone else needs it in Excel, exporting a Numbers sheet to Excel explains what carries over to XLSX.
Scanned and protected PDFs that will not reach Numbers cleanly
Scanned and protected PDFs are the files where neither route works without help. A scanned PDF holds a picture of each page, so there is no text to copy. A protected PDF may block copying altogether, or let you copy only scrambled characters. Both need a different first step before Numbers enters the picture.
Here is how to tell which problem you have and what to do:
- Nothing selects in Preview. You can draw a box around the table but no text highlights. The page is an image. It needs character recognition before its text can be copied or converted, and a converter that reads scans can do this.
- Text pastes as gibberish. The PDF uses a font without a proper character map. The letters look right on screen but copy as symbols. Converting from the page image, rather than from the text layer, usually gets around it.
- Copy is greyed out. The file has a permissions setting that stops copying. If it is your own statement, downloading a fresh copy from the bank, or printing it to a new PDF where that is allowed, often gives you a file without the restriction.
- Pages are sideways. Rotate them in Preview and save before you copy, or the text will come out one character per line.
A scan will never be as reliable as the bank's downloaded PDF, because each digit has to be recognised from pixels. If you can log in and download the statement again, do that first. It saves an hour of checking amounts against the page.