Pages to PDF Converter

A .pages document is not simply a PDF with a different extension. It is an Apple iWork document package containing structured document data, assets and, in many compatible files, a preview that macOS can use without fully opening the document. This page uses that preview when it is available. That boundary makes the result predictable: the tool can preserve the stored PDF pages, but it cannot recalculate the editable Pages layout.

How to convert Pages to PDF

1. Choose one .pages file. The current browser workflow accepts a modern Pages package up to 100 MB. The embedded PDF can contain up to 500 pages and use up to 150 MB after extraction.
2. Wait for the package check. The tool opens the ZIP-based package locally and looks for QuickLook/Preview.pdf.
3. Inspect the embedded preview. The left panel displays the PDF stored in the package and reports its page count, size and package details.
4. Choose all pages or a custom range. Keep the full embedded preview or enter page numbers such as 1-3, 5, 8-10.
5. Review the title and filename. The title is written into the new PDF metadata. The filename controls what your browser downloads.
6. Create the output. The selected source PDF pages are copied into a new PDF without browser reflow or page screenshots.
7. Check the final result. Compare the generated preview with the source preview, then review page geometry, file sizes and metadata before downloading.

Changing the page range, title or filename clears the previous result. This prevents an older download from being mistaken for the settings currently shown.

Understand the embedded PDF

The main question is not whether a filename ends in .pages; it is whether the package contains a readable PDF preview. The tool validates both parts. Renaming an unrelated ZIP or PDF file to .pages will not create the expected package structure.

When a preview is present, it represents a fixed view saved with the Pages document. The tool does not interpret paragraphs, fonts, tables, shapes, comments or tracked changes from the editable iWork data. It copies PDF pages from the embedded preview. This approach has several practical consequences:

• page dimensions and orientations come from the embedded PDF;
• text and vector objects already present in that PDF are not rasterized by base97;
• selected pages keep their original visual order and geometry;
• interactive Pages editing features are not recreated;
• unsaved changes that were never included in the package preview cannot appear in the output;
• the embedded preview may differ from a fresh export created by the latest Pages version.

The source panel reports the complete .pages package size and the embedded PDF size separately. A Pages file can be much larger because it may contain original media, thumbnails, indexes and editable document data that are not needed in the PDF output.

Choose all pages or a range

Use All preview pages when the complete document should be shared. This copies every page detected in the embedded PDF.

Use Custom page range when the recipient needs only part of the document. Separate individual pages with commas and use a hyphen for a continuous range. For example:

The range must use page numbers from the embedded PDF, not section numbers displayed in the Pages document. The output sorts selected pages into their original ascending order and removes duplicate selections. It does not reorder pages into an arbitrary custom sequence.

The result report identifies whether all pages or a custom range was used. It also checks the selected page dimensions. A document can contain portrait and landscape pages or multiple custom sizes; those pages remain mixed in the output rather than being forced onto one paper size.

Review the pages and result

Start with the embedded source preview. Confirm that it contains the expected first and last pages, current wording, correct images and complete tables. If the source preview itself is old or incomplete, this tool cannot create a fresher layout from the editable Pages data.

After conversion, compare the result preview with the selected source pages. Check:

• the first and final selected page;
• page order and total page count;
• portrait, landscape and custom page sizes;
• text, images, charts, headers and footers;
• any links or annotations that matter to the recipient;
• the PDF title and downloaded filename.

The output method is deliberately light. pdf-lib copies the selected pages into a new PDF and writes the requested metadata. There is no image rendering step, quality slider or compression setting because the page content is not being recreated. Output size can still differ from the embedded preview because the new PDF package has its own object structure and includes only the selected pages.

When a Pages file is not compatible

The tool stops with a specific message when it cannot produce a trustworthy result.

The file is not a readable modern package. Older Pages formats, damaged downloads or encrypted files may not open as a ZIP-based package. Open the file in a compatible Pages version and save or export it again.

The package has no Quick Look PDF. The file may contain iWork document data without QuickLook/Preview.pdf. The browser cannot reconstruct the document because Pages layout data is proprietary and can depend on Apple fonts and rendering behavior.

The embedded PDF is empty, damaged or password protected. A preview path alone is not enough. The PDF must pass parsing and page-count checks before the Convert button is enabled.

The browser runs out of memory. Large packages and long PDF previews must be held in browser memory while the archive is inspected and selected pages are copied. Close unrelated tabs or use the official Pages export workflow for unusually large documents.

The preview is older than the editable content. Reopen and save the document in Pages, then try the new file. This page cannot detect editable changes that are absent from the stored preview.

Official Pages export and other options

When you have access to the Pages app, Apple's own export command is the authoritative option because Pages can render the current editable document and offer PDF-specific export choices. Apple documents this workflow in Export to Word, PDF, or another file format in Pages on Mac.

Use the official export route when you need a freshly rendered PDF, password settings, accessibility review, comments or other options exposed by Pages. Pages for iCloud is also a practical route when you do not have a Mac but can open the document through an Apple account.

Use this base97 page when the package already contains the desired PDF preview and you want to inspect it, select pages and download the result without installing software. It is especially useful for checking what is recoverable from the file before deciding whether a full Pages export is necessary.

Do not upload a Pages file to a random converter when the document contains confidential material unless you understand that service's processing and retention model. The current base97 workflow reads the package in the browser and does not require a base97 conversion endpoint, but browser extensions, device security and downloaded-file handling remain under the user's control.

Illustrative Pages to PDF examples

Share selected portfolio pages

Assume a 14-page Pages portfolio contains a readable embedded preview, but a client needs only the introduction and three case studies. Enter 1-2, 5-9, create the PDF, and verify that the output contains seven pages in their original order.

Recover a PDF on a non-Mac computer

Assume a Windows user receives a .pages file and cannot install Pages. If the package includes QuickLook/Preview.pdf, the user can inspect and download that preview locally. If no preview exists, the correct next step is Pages for iCloud or asking the sender to export a PDF.

Keep mixed page orientations

Assume a report begins with portrait text pages and ends with a landscape chart. Select all pages. The output keeps both page geometries because the converter does not force them onto A4 or US Letter.

Illustrative examples. Compatibility, page count, metadata and output size depend on the actual Pages package and its embedded PDF.

Common questions