Numbers File Won't Open in Excel: How to Convert

A colleague on a Mac sends you budget-q4.numbers. You double-click it, Excel pauses, then says the file format or file extension is not valid — or it offers to recover the file and hands back an empty grid. Nothing you click inside Excel will fix it. The file is not damaged and it is not a corrupted workbook; Excel simply has no reader for Apple’s spreadsheet format.

The good news is that conversion is routine. The bad news is that the route you choose decides whether formulas, multiple tables, and accented characters survive — so pick deliberately instead of grabbing the first online converter you find.

Why Excel cannot open a .numbers file

A .numbers document is a zip package, not a flat file. Inside it you will find Index.zip (or an Index/ folder) holding .iwa files, plus preview.jpg, Metadata/, and a few property lists. Since Numbers 3.0 in 2013, those .iwa files — iWork Archive — are a protobuf-based store that Apple has never documented.

An .xlsx is a different animal: an OOXML package with xl/workbook.xml, xl/worksheets/sheet1.xml, and a shared string table. Excel identifies files by extension and by content sniffing, and a .numbers package fails both tests. That is why you get the “file format or file extension is not valid” message rather than a repair dialog — there is nothing to repair, because Excel never got far enough to read a cell.

The second mismatch is structural. A Numbers document is a free-form canvas that can hold five independent tables at arbitrary positions on one sheet; an Excel workbook is a grid of worksheets. Any conversion has to invent a mapping, and each converter invents a different one.

Fix 1 — Export from Numbers on a Mac

This is the only route that preserves formulas and cell formatting reliably, because Apple wrote both ends of it. Open the document in Numbers, then choose File → Export To → Excel…. In the dialog keep All Sheets selected, open Advanced Options, and turn on the one-worksheet-per-table setting if your document stacks several tables on a single sheet — the label moves between Numbers versions, but the option is there. You get a real .xlsx that opens in Excel without complaint. If the file sits on your Windows machine, this route needs a Mac for two minutes, which is usually cheaper than the workarounds below.

Fix 2 — Convert through Numbers for iCloud

No Mac in the building? Numbers runs in a browser at icloud.com/numbers. Sign in with the Apple ID that owns the file, or upload the .numbers file, then open it.

Once it renders, use wrench icon → Download a Copy → Excel. iCloud converts server-side and gives you an .xlsx. Two caveats: very large documents, or ones using features the web app does not implement, may open read-only, and a free iCloud account has a storage cap a graphics-heavy workbook can hit.

Fix 3 — Ask the sender for .xlsx, not .csv

If the person who made the file is still reachable, one message saves an hour: ask them to run File → Export To → Excel and send that. Sending a CSV instead feels easier for them and is almost always worse for you.

A CSV export from Numbers covers one table per file. A document with a summary table, a detail table, and a chart on one sheet means three exports and a manual reassembly in Excel. Formulas, number formats, merged headers, and column widths are gone by definition, and non-Latin text may arrive mangled — see CSV opens with garbled characters in Excel for the import step.

Fix 4 — Open it without a Mac at all

Two options when nothing above is available.

LibreOffice Calc has an iWork import filter and often opens a .numbers file directly, recent IWA-based ones included. Expect a partial import: tables usually come through, charts frequently do not, and Numbers-only functions arrive as errors or plain values. Good enough to read the figures; not good enough to send back to a client.

Look inside the package. Copy the file, rename the copy’s extension from .numbers to .zip, and open it. You cannot extract cell data this way, but preview.jpg is a rendered image of the document — enough to answer “what was in this file”, and faster than any conversion for a twenty-row table you can retype.

One warning that costs people their data: never rename .numbers to .xlsx. Excel will decide the file is corrupt, run recovery, produce an empty workbook, and if you save, you have replaced a working file with a blank one. Work on copies only.

What does not survive the conversion

Even the clean Numbers export is lossy in predictable ways:

• Several tables on one sheet arrive as stacked ranges separated by blank rows, not separate sheets.
• Interactive controls — checkboxes, star ratings, sliders, pop-up menus — flatten to static values.
• Numbers’ category summaries do not become Excel pivot tables; you get rows and rebuild the pivot.
• Conditional highlighting usually becomes plain cell fill, so it no longer updates.
• Charts may arrive as editable charts or as pictures; comments and text overflowing a merged cell are the first things dropped.

If a formula references a Numbers-only function, the cell converts to #NAME?. Search for that after import rather than trusting a visual scan.

When it is worth rebuilding instead

A one-table sheet with thirty rows is faster to rebuild from the preview image than to debug through a partial import, and the result is cleaner. A workbook with cross-sheet formulas, named ranges, or a few hundred rows is worth the export route even if it means waiting for a Mac.

If the .numbers file will not open in Numbers either — the app crashes, or says the document cannot be opened — the package is truncated, and no converter will help. That is a repair problem, not a format problem. Our file repair service takes these on per file and will say up front if the structure is too far gone.

FAQ

Can I just change the extension to .xlsx? No. The bytes inside never change, so Excel sees an OOXML extension wrapped around a protobuf package. It reports corruption, and saving the “recovered” result overwrites your only copy with an empty workbook.

Does Microsoft 365 include a Numbers importer? No version does — not Microsoft 365, not Office 2021, not Excel for Mac. Apple has not licensed the format and .iwa is undocumented, so conversion happens on the Apple side or through a third-party filter.

Will my formulas still work after export? Formulas that exist in both apps — SUM, SUMIFS, VLOOKUP, INDEX/MATCH, IF chains — normally convert intact. Numbers-only functions, and anything referencing an interactive control, will not. Check for #NAME? and #REF! right after opening.