To find a page associated with an Affinity PDF export failure on Mac, export smaller page ranges with the same settings, then narrow the failing range. Confirm the result by exporting the suspect page alone and the remaining pages without it.

This guide covers a multipage, page-based document in the current Affinity desktop app. The goal is to locate a reproducible failure before changing the document’s content. The range-testing procedure below is a diagnostic method derived from Affinity’s documented export controls; it is not a built-in automatic fault finder.

What can Affinity identify automatically?

Affinity’s Preflight panel can locate issues covered by its active checking profile. On the panel, click Check Now, hover over an entry for details, and double-click the entry to go to its location. Only some issue types provide a Fix button. These are documented ways to reach a reported problem directly. Affinity’s Preflight documentation

Check Preflight before running repeated exports. Its documented checks include missing fonts, missing or outdated linked resources, and a placed PDF that is missing or broken. However, an entry saying that a placed PDF will be rasterized describes an export treatment; it does not, by itself, establish the cause of an export failure. Preflight checks and PDF passthrough messages

The official Export dialog and Preflight documentation does not describe a command that reliably names the failing page for every PDF export error. A clear Preflight result therefore leaves a separate question: which requested output, if any, reproduces the failure? Controlled page-range exports can help answer that question. Export dialog, Preflight

Establish a repeatable export before narrowing the range

Save your document, and keep a separate working copy before making content changes. For the first tests, leave the layout intact. Removing pages would change the document you are trying to diagnose.

Record the PDF preset and any customized settings used in the failed export. Keep those settings, the destination folder, and the document content constant throughout the range tests. Give each attempt a distinct filename, such as test-01-16.pdf, so an older successful file cannot be mistaken for the latest result.

For a page-based document, Affinity documents All Pages as exporting individual pages, including separate left and right pages in a facing-page layout. All Spreads exports each spread as one PDF page. Those outputs have different boundaries, so record which one originally failed. Affinity’s Area export settings

Use this setup for an individual-page investigation:

  1. Choose File > Export > Export.
  2. Select the PDF preset used for the failed attempt and retain your custom settings.
  3. Set Area to All Pages.
  4. Enter the required range in Pages.
  5. Choose Ask for Location, click Export, name the test file, and click Save.

Affinity documents ranges such as 4-17, individual numbers such as 4,5,6, and combinations such as 4-5,19,27,39. The Pages field becomes available with All Pages or All Spreads. Export dialog instructions

First reproduce the failure using the full document with All Pages. If that succeeds but your original All Spreads export fails, continue with the spread-specific branch below. A successful export after changing the output boundary is a useful comparison, but it has not identified a faulty page.

For every successful test, open the resulting PDF and verify that it contains the intended content and page count. This also checks your interpretation of the page-range input. If numbering is ambiguous, compare a recognizable page using Current Page, which Affinity documents as exporting the active page. Current Page export behavior

Narrow the failure by testing both halves

Once the full document fails consistently, divide its page range into two approximately equal parts. Export each part separately. Continue dividing any part that fails until the smallest reproducibly failing range contains one page.

Test both halves. A successful first half does not establish that the second half fails, and one failing half does not establish that the other half is clear. Keeping both results makes the method useful when several pages are involved.

Worked example: a synthetic 32-page document

Suppose a 32-page document containing neutral text and simple geometric graphics fails to export. The following results are illustrative, not observations from an Affinity test.

Round Ranges exported separately Illustrative result Next action
1 1-16 and 17-32 First passes; second fails Divide 17-32
2 17-24 and 25-32 First fails; second passes Divide 17-24
3 17-20 and 21-24 First passes; second fails Divide 21-24
4 21-22 and 23-24 First passes; second fails Test pages 23 and 24 separately
5 23 and 24 Page 23 fails; page 24 passes Confirm page 23 and its complement

In this example, five rounds reduce 32 candidate pages to one. Testing both halves takes ten export attempts before confirmation. This arithmetic assumes one consistent, page-local failure; actual documents may produce results that require more branches or prevent single-page isolation.

Keep a short record of each range, filename, settings, and result. For a successful export, note that you inspected the PDF. For a failure, record what happened: an error message, an application exit, or an attempt that did not complete. If completion is uncertain, record it as inconclusive rather than treating it as a confirmed failure.

Confirm that the suspect page explains the failure

After finding a page that fails alone, repeat that single-page export with the unchanged settings. Then export the rest of the document without that page. In the synthetic example, enter 1-22,24-32 to test everything except page 23; Affinity supports mixed ranges and individual page numbers. Supported Pages input

The strongest practical result is a repeatable three-part pattern: the full document fails, the suspect page fails alone, and the remaining pages export successfully. That supports describing the page as associated with the failure under the recorded settings. It does not identify the particular object, font, placed file, or export operation responsible.

If the remaining pages still fail, continue dividing that range. You may find another failing page, or discover that the original single-page explanation was incomplete. Do not stop at the first suspect unless excluding it resolves the failure in the remaining output.

What if the range tests do not isolate one page?

The method depends on failures remaining reproducible as the requested page set changes. Use the results below to decide whether to keep narrowing.

Observed result What it establishes Next useful test
One half fails and one passes A smaller requested range reproduces the failure Divide the failing half
Both halves fail More than one range reproduces the failure Investigate both branches
Both halves pass but their combined range fails The failure has not been isolated to one page Repeat the combined range with unchanged settings
Every page passes alone, but the full export fails No individually failing page has been demonstrated Find the smallest repeatably failing combination
Identical tests alternate between success and failure Results are not stable enough for reliable narrowing Repeat the baseline and record the variation

These are diagnostic interpretations, not documented Affinity error classifications. For example, two passing halves do not prove that every page is harmless in every combination. They establish only that those two separate export requests completed.

When no page fails independently, retain the smallest combination that reproduces the problem. A precise finding such as “pages 17–24 fail together, while 17–20 and 21–24 export separately” is more useful than naming an unsupported culprit.

If the original failure occurs only with spreads

Preserve All Spreads while reducing the requested range, and inspect successful output to verify which spreads were included. Affinity’s documented contract is that a spread becomes one PDF page; the Pages field remains available in this mode. Spread output settings, Range selection

Once you have a suspect spread, compare it with Current Spread, then test its constituent pages separately using Current Page. If the spread fails while both individual pages succeed, report a spread-associated failure. Those results do not justify declaring either individual page defective.

What to do after locating the page

Return to Preflight at the suspect location. One concrete documented PDF limitation is that dash patterns must contain 12 or fewer entries; Preflight can report a stroke with a more complex pattern. If that specific issue exists, correct it in your working copy and repeat the same export. Do not assume it explains a failure merely because the document contains dashed graphics. Documented Preflight limitations

For further investigation, change one suspected item at a time in the working copy and repeat the single-page test. Keep the original export settings fixed while testing content changes. Otherwise, a successful attempt will leave you unable to tell which change mattered.

If you deliberately compare rasterization settings, keep it as a separate experiment. Affinity documents Everything as rasterizing all design elements, Unsupported properties as rasterizing unsupported elements, and Nothing as omitting unsupported elements rather than rasterizing them. Choosing Nothing can therefore remove content from the output. A completed export with changed settings needs visual inspection and does not establish that the original failure has been repaired. Rasterization export settings

Finish by repeating the complete export with the intended page or spread mode and final settings, then inspect the PDF. Keep the failing-range record until that succeeds. The useful outcome is either a confirmed page to investigate or a precise, reproducible range failure that shows why a single-page diagnosis is not supported.

Sources