How to open a .pages file on Windows

A .pages file in a Windows inbox looks like a dead end. Word refuses it, Google Drive will not preview it, and double-clicking produces a dialog asking which program you would like to use. It is not a dead end. In most cases the document is already sitting inside the file and comes out in about ten seconds.

What you are actually holding

A .pages file is a zip. Inside it, the document body is stored as IWA, Apple's own dialect of protocol buffers, with a schema that is undocumented and shifts between releases. Nothing outside Apple's software reads it dependably, and anything that claims to is reverse engineering a moving target.

Sitting alongside that body, in most files, is something far more useful. When a document is saved with previews enabled, which is the default, Pages writes a complete PDF render of the finished document into the package so that Finder, Quick Look, Mail and iOS can display it without launching the app.

That PDF is the whole document, drawn by Pages, on the author's machine, with the author's fonts. It is both the fastest way out and the most accurate one.

Route one: the PDF that is already in there

Taking the preview out is an extraction rather than a conversion, and that distinction is the whole point. There is no layout to recalculate, no font to substitute and no table to rebuild. What you end up with is what Pages produced.

The limits are worth stating plainly. The result is read-only, and it shows the document as it stood the last time somebody saved it on a Mac. If you need to change a figure or fix a name, this route gets you a picture of the problem rather than the problem.

Route two: Pages in a browser, free

Apple runs Pages as a web application and it costs nothing. Create an Apple Account if you do not have one, sign in at iCloud, open Pages, and drag the file into the window. It opens the real document rather than the preview, because iCloud is Apple's software reading Apple's format. Apple's Pages for iCloud guide covers the editing side once it is open.

From there the tools menu offers Download a Copy, with PDF and Word among the choices. Editing works, comments work, and the layout holds because the thing rendering the page is Pages.

This is also the route that rescues the files route one cannot touch. Extraction depends on a PDF being present in the package. iCloud does not, because it reads the document itself, so a file saved without previews still opens.

Doing the extraction by hand

The unzip is simple enough to do yourself, and worth knowing because it tells you in one step whether the preview is in there at all.

Start by making file extensions visible. Windows hides them by default, so a file showing as Report is really Report.pages and renaming it appears to do nothing. Microsoft's guide to file name extensions has the toggle: it sits under View, then Show, in File Explorer.

When neither route is open

Two situations leave you asking the sender, and both have a short answer.

The first is a file with no preview that is too sensitive to upload. Apple's export instructions take about ten seconds at their end: File, then Export To, then PDF. On an iPhone or iPad it is the three dots, then Export, then PDF.

The second is a file that is not a zip at all. On a Mac, .pages can be a package, which is a folder the system draws as a single file. Copied across to Windows by certain routes, it arrives as an ordinary folder full of parts. Nothing is damaged. Open it and look for the QuickLook folder, exactly as above.

Keynote and Numbers files

Same package, same preview, same two routes. A .key file carries a PDF of the slides at one per page, which is usually what you wanted anyway.

A .numbers file is the one to be careful with. Its preview is the printed layout of the sheets, which is a picture of the numbers rather than the numbers. If you need to work with the data, iCloud and an export to Excel is the honest route, and extraction will only frustrate you.