Convert Apple Numbers to Excel (Mac & iCloud)

Need to convert Apple Numbers to Excel? It’s one of the most common cross-platform headaches in the Apple world. You built a beautiful budget tracker, invoice, or project plan in Numbers on your Mac — then your accountant, client, or colleague on Windows asks for it “in Excel,” and your .numbers file is gibberish to their computer. The fix is built right into Numbers and takes about twenty seconds, but there are details worth knowing: which export options to pick, what happens on iCloud.com when you don’t have a Mac handy, and which Numbers features don’t survive the trip to Excel format. The “apple numbers to excel” export is built into Numbers — File › Export To › Excel — and this guide covers Mac, iCloud, and iOS.

This guide covers every way to turn a Numbers spreadsheet into a genuine .xlsx file: the File › Export To › Excel flow on Mac, the iCloud.com method that works from any browser (including Windows PCs and Chromebooks), exporting from the Numbers app on iPhone and iPad, and what to check before you send the file so your formatting, formulas, and charts arrive intact. Whether you’re a freelancer in Austin sending invoices, a student in Toronto sharing group-project data, or a shop owner in Birmingham emailing stock sheets to a supplier, you’ll have a clean Excel file in minutes.

Apple Numbers to Excel: What Actually Happens in Conversion

Apple Numbers and Microsoft Excel are both spreadsheets, but they think about documents differently. Numbers treats a spreadsheet as a freeform canvas: you can place multiple tables, charts, text boxes, and images anywhere on a sheet, resize them freely, and arrange them like a design document. Excel is grid-first: everything lives in the rigid row-and-column structure of worksheets. When you export Numbers to Excel, Apple’s exporter translates the canvas model into the grid model — tables become worksheet ranges, charts become Excel chart objects, and free-floating elements get anchored to nearby cells.

For straightforward data — tables of values, basic formulas, standard formatting — the translation is essentially perfect. Your SUM and VLOOKUP formulas keep working (Numbers converts them to Excel’s equivalents), number formats carry over, and conditional highlighting survives. Where things get approximate: Numbers’ interactive charts become static images or simplified charts, some custom shapes and text effects flatten, and Numbers-only functions get converted to their closest Excel match (or to static values if no match exists). None of this affects typical business spreadsheets — invoices, budgets, lists, reports — which convert cleanly.

One more thing to understand: exporting doesn’t change your original. The .numbers file stays exactly as it was; Numbers creates a new .xlsx file alongside it. So you can export, check the result in Excel (or Google Sheets, which opens xlsx files fine), and re-export after tweaks without ever risking your master copy. With that mental model in place, let’s do the export.

Method 1: Export on Mac — File › Export To › Excel

The primary route, and the one Apple intends you to use:

1. Open your spreadsheet in Numbers on Mac.
2. Go to File › Export To › Excel…
3. In the export dialog, you’ll see options: choose whether to include a summary worksheet (usually leave this off unless you want an extra sheet describing the document) and set a password if the Excel file needs protection.
4. Click Next…, choose where to save, name the file, and click Export.
5. You’ll get a .xlsx file ready to email, upload, or open in Excel.

Method 2: The iCloud.com method (no Mac needed)

No Mac handy? Maybe you’re on a Windows PC at work, a Chromebook, or a friend’s computer. As long as your Numbers document is in iCloud Drive, you can convert it from any browser:

1. Go to icloud.com and sign in with your Apple ID.
2. Open the Numbers web app.
3. Find your spreadsheet and double-click to open it.
4. Click the wrench/toolbox icon (or the … menu, depending on the current iCloud design) and choose Download a Copy.
5. Select Excel as the format. The .xlsx file downloads to the computer you’re on.

Two caveats: the iCloud web version of Numbers is slightly less capable than the Mac app, so extremely complex documents convert a touch more conservatively — and you need the document synced to iCloud Drive first (on your Mac/iPhone: save to iCloud Drive, or drag the .numbers file into iCloud Drive in Finder/Files and wait for sync). For typical spreadsheets, the result is indistinguishable from a Mac export.

Method 3: Export from Numbers on iPhone and iPad

The iOS/iPadOS Numbers app exports just as well as the Mac version:

1. Open the spreadsheet in the Numbers app.
2. Tap the … (More) button at the top of the screen.
3. Tap Export, then choose Excel.
4. Choose how to send it: Mail, Messages, WhatsApp, Save to Files, AirDrop — whatever fits.

This is the fastest path when someone asks for the Excel version while you’re away from your desk — the whole thing takes under a minute, and the recipient gets a proper .xlsx attachment, not a screenshot.

Compatibility notes: what transfers and what doesn’t

For typical spreadsheets — tables, numbers, text, basic formulas, standard charts — the Numbers-to-Excel export is essentially perfect. Here’s the honest breakdown for everything else:

Transfers cleanly: cell values and formatting (fonts, colors, borders, number formats), merged cells, multiple sheets/tables, standard formulas (SUM, AVERAGE, IF, VLOOKUP/XLOOKUP equivalents), conditional highlighting, filters, frozen rows/columns, and standard bar/line/pie charts.

Approximate: interactive charts become static (the interactivity is a Numbers-only feature), custom shapes and drawn elements may shift position slightly, and Numbers-specific functions convert to their closest Excel match — always spot-check formula results after export.

Doesn’t transfer: AppleScript/automation attached to the document, Numbers-only templates’ scripting, and some advanced table features like checkbox-driven filtering logic. If your spreadsheet leans heavily on these, consider rebuilding the logic in Excel natively rather than exporting.

The golden rule: always open the exported .xlsx and skim it before sending — especially the first time you export a particular document. Ninety-nine percent of the time it’s flawless; the one percent is always the chart on page three you didn’t check.

Bonus: exporting Numbers to CSV first

Sometimes the recipient doesn’t want Excel at all — they want raw data for a database import, and CSV is the ask. Numbers handles that too: File › Export To › CSV… on Mac (or Export › CSV on iOS). One Numbers-specific behavior to know: Numbers exports each table as its own CSV structure choice — if your sheet has multiple tables, you’ll pick which tables to include. For a single clean data table, it’s one click. And if you later need that CSV back in Excel form, our free CSV to Excel converter closes the loop.

Troubleshooting Numbers-to-Excel conversion

“Export To › Excel” is greyed out. The document may still be downloading from iCloud (wait for sync) or open in another session. Close other instances and retry.

The .xlsx opens but formulas show errors. A Numbers-only function didn’t map to Excel. Note which cells break, and replace those formulas with Excel-native equivalents.

Charts look wrong in Excel. Interactive charts flatten on export — rebuild critical charts in Excel if pixel-perfect presentation matters.

File size ballooned. Embedded images export at full resolution. Compress images in Numbers before exporting (Format › Image › reduce size) if the XLSX needs emailing.

iCloud.com download fails. Check that the document finished syncing (look for the upload indicator in the Files app or Finder), then retry. Very large documents sometimes need the Mac app export instead.

Recipient says “I can’t open it”. Confirm the file actually has the .xlsx extension (not .numbers) — occasionally people attach the original by mistake. Also confirm their Excel isn’t ancient: .xlsx needs Excel 2007 or later.

Hit an edge case — a template that exports strangely, a chart type that vanishes? join the discussion in our community forum and describe the document; the community has seen most Numbers quirks before.

Numbers vs Excel: An Honest Feature Comparison

People usually arrive at Numbers-to-Excel conversion from one of two directions: they love Numbers and must placate Excel users, or they’re stuck with a Numbers file and just need it to work. Either way, understanding the real differences helps you predict what the export will look like.

Where Numbers wins

Numbers is the better design tool: its freeform canvas lets you arrange tables, charts, and text like a layout app, which is why invoices, reports, and dashboards built in Numbers tend to look beautiful with minimal effort. It’s free on every Mac, iPhone, and iPad, syncs effortlessly via iCloud, and its templates are genuinely gorgeous. For personal finance, small-business paperwork, and anything where presentation matters, many Mac users honestly prefer it.

Where Excel wins

Excel is the better data engine: Power Query, pivot tables, 1M+ row capacity, VBA/macros, and an enormous function library make it the professional standard for analysis. It’s also the compatibility standard — when someone says “send me the spreadsheet,” they mean .xlsx. Excel’s collaboration story (co-authoring in Microsoft 365) has caught up to and passed iCloud sharing for business use.

What this means for your exports

The export direction tells you what to watch: Numbers’ strengths (layout, design, interactivity) are exactly what translate approximately, while its plain data tables translate perfectly. So the practical rule: if your Numbers document is mostly tables of data with straightforward formatting, export with total confidence. If it’s a heavily designed, canvas-style document with floating elements and interactive charts, budget ten minutes to tidy the XLSX afterward — or consider whether a PDF might actually serve the recipient better than a spreadsheet that only approximates your design.

Round-Tripping: Sending Excel Files Back to Numbers

Conversion isn’t always one-way. Your colleague edits the XLSX you sent, sends it back, and now you want it in Numbers again. Good news: Numbers opens .xlsx files directly — just double-click (or File › Open) and Numbers imports it, converting Excel-isms to Numbers equivalents as best it can.

The same asymmetry applies in reverse: plain data round-trips beautifully, while Excel-specific features (pivot tables, Power Query connections, VBA macros, complex conditional formatting) get simplified or dropped on import. Each round trip is slightly lossy for exotic features — so for documents that bounce back and forth regularly, agree on one master format with your collaborators. If the team is mixed Mac/Windows, that master is almost always XLSX with both sides tolerating minor imperfections, rather than converting back and forth and compounding the losses.

One practical tip for round-trippers: keep a changelog sheet in shared workbooks — a simple tab noting who changed what and when. When a formula breaks after a round trip, the changelog tells you exactly which version to compare against instead of playing detective across three file copies.

Password-Protecting Your Exported Excel File

Sending financial data, HR records, or client lists? The Numbers export dialog includes password options — use them. When you choose File › Export To › Excel… on Mac, tick Require password to open and set a strong password before exporting. The resulting XLSX is encrypted with standard Office encryption, so it opens in Excel (Windows or Mac) with a password prompt — no Numbers needed on the recipient’s side.

Password hygiene matters more than the checkbox: send the password through a different channel than the file (file by email, password by phone call or messenger), never use the same password across documents, and note that anyone with the password can remove it in Excel and re-save unprotected. For genuinely sensitive data, consider whether Excel is even the right container — sometimes an encrypted disk image or a proper document-management system beats a passworded spreadsheet. But for everyday “keep honest people honest” protection on invoices and internal reports, the export-time password is quick, effective, and built in.

Collaborating with Excel Users Long-Term

If you regularly exchange spreadsheets with Excel people — a bookkeeper, a distributed team, a client — stop thinking in terms of one-off exports and set up a sustainable pattern:

Agree on the master format. If most collaborators are on Excel, consider doing the shared work in Excel format from the start (Numbers opens and edits XLSX files directly). You lose a little Numbers magic, but you eliminate an entire category of conversion surprises. Reserve native Numbers documents for work that’s truly yours alone.

Version discipline. Every export creates a fork. Adopt a naming convention with dates (budget-2026-10-08.xlsx), keep one shared folder as the source of truth (iCloud Drive shared folder, or better, a neutral spot like Google Drive or OneDrive everyone can reach), and never let two people edit different copies simultaneously without a merge plan.

Schedule format check-ins. Every few months, open your exported files in actual Excel (the free Excel for the web works) and confirm nothing has drifted — especially if you’ve started using newer Numbers features. Catching a translation issue in a quarterly review beats discovering it in front of a client. And when the collaboration is truly Excel-centric week after week, the kindest thing might be switching to Excel yourself for that project — tools serve workflows, not the other way around.

A final habit worth building: keep a “sent” log — a simple note of which Excel version you sent to whom and when. When someone replies three months later asking for “the latest,” you’ll know exactly what they already have instead of guessing. Combined with dated filenames and a single shared folder, this tiny bit of bookkeeping eliminates the most common long-term collaboration headache: nobody knowing which file is current. It takes thirty seconds per send and pays for itself the first time it prevents a duplicate-work disaster — cheap insurance for any ongoing collaboration.