Affinity Publisher's preflight check feature can be used to ensure that your document exports or prints as intended. The preflight check can be run on demand—e.g. prior to output—or 'live' on a continual basis.
The Preflight panel.
Preflight checks the contents of your file for errors, ensuring the file is ready for print or export.
Preflight notifications
With preflight enabled, the Preflight panel's icon will change color to indicate whether warnings or errors have been detected in the document:
Grey indicates that preflight is not enabled, i.e. live checks are not being performed.
Green indicates that preflight is active and no errors or warnings have been found.
Red indicates that preflight is active and errors that will interrupt export have been found.
Yellow indicates that preflight is active and issues that will not affect export have been found.
Editing the Preflight profile
The Preflight panel uses a default set of checks, but these can be customized. The Preflight panel's Edit profile function allows you to tailor preflight checking to your needs. You can control the severity level for preflight issues, set values and thresholds that trigger preflight warnings and errors, and control how placed documents work with preflight.
Errors and warnings
The Preflight panel displays a full list of warnings and errors it has found, allowing you to pinpoint and correct certain errors where they appear in your document.
The types of items that are listed are determined by the active preflight profile's settings. Two different icons may be shown to indicate severity:
A yellow icon to the left of an entry is a warning of an issue that will not affect export.
A red icon to the left of an entry indicates an error in the file that will interrupt export.
The full list of preflight warnings and errors is as follows:
Bleed Hazard—appears when an object is positioned outside of the bleed zone. You can adjust the safe zone edge via the panel, which will change what preflight checking will identify as a bleed hazard.
Check copy—appears if a preflight user comment has been attached to an object. Can be used as a reminder to, for example, check final text copy or to check image copyright.
Cross-reference out of date—appears after making certain changes to your document that require a cross-reference's value to be manually updated. Tap Fix to update the cross-reference.
Cross-reference target is missing—appears if the target of a cross-reference has been deleted from the document, e.g. an anchor has been removed.
Cross-reference book target is missing—appears if the target is in a book chapter that is not open for editing, and so nothing more about the target is known.
Cross-reference target is not a list—a cross-reference contains a List Number subfield but its target is not an item in a numbered or bulleted list.
Cross-reference target is not a note—a cross-reference contains a Note Number subfield but its target is not a footnote, sidenote or endnote.
Cross-reference target is not in a book—a cross-reference contains a Chapter Name subfield but its target is not a book chapter.
Cross-reference expansion includes itself—a cross-reference contains a Paragraph Body or Numbered Paragraph subfield whose value includes the cross-reference's text.
Cross-reference target is not in text—a cross-reference contains a text-based subfield, such as Paragraph Body, but its target is not text. For example, the cross-reference is linked to an anchor on a shape or image.
Cross-reference has no string for language—a cross-reference contains an Above/Below subfield but translations have not been set for the text's language. Translations can be set via Edit Strings on the Cross-References panel's Preferences menu.
Cross-reference value is empty—a cross-reference contains a subfield for which its target provides no value, e.g. a Paragraph Body subfield when the cross-reference's target is an empty paragraph. This check is optional and can be disabled by editing the preflight profile, selecting Cross-References, and then unchecking Check for empty values.
Field (field name) not found in source (data source file name)—appears when a row or column in the external data source has either been renamed or deleted.
Hidden Object
Hyperlink to Invalid Anchor (anchor name)—appears where a hyperlink's anchor is missing or has been deleted.
Hyperlink to Invalid Page—appears where a hyperlink's target page is missing or has been deleted.
Linked resource is missing/Linked resource is out of date
Mismatched color space (RGB)
Missing characters (character)—appears when text uses a glyph that is not present in the currently applied font.
Missing Font—appears if the document is opened on a device that does not have the used fonts available.
Non-Proportional Scaling—appears when an object is not proportionally scaled, e.g. when an image has been accidentally squashed.
One or more table of contents entries need updating—appears when the TOC is out of date because referenced text in the document has been added to, modified or deleted. Tap Fix to update the TOC and resolve.
Overflowing path text—appears where there is overset text on a path.
Overflowing text frame—appears where there is overset text within a text frame.
PDF passthrough—a series of different preflight checks for PDF passthrough. These will report as:
Placed PDF has image adjustments applied. The PDF will be rasterized on export.
Placed PDF has effects applied. The PDF will be rasterized on export.
Placed PDF has transparency applied. The PDF will be rasterized on export.
Placed PDF Version (version) is not compatible with the PDF export version. The PDF will be rasterized on export.
Placed PDF has objects of a color not compatible with the PDF export version. The PDF will be rasterized on export.
Placed PDF is missing or broken.
Placed PDF has unsupported page box. The PDF will be rasterized on export.
Placed PDF has objects of a color different to the document colorspace. The PDF will still pass through.
Placed image DPI too low—appears when an image's DPI is too low for the file, with the image's DPI listed in brackets beside the error.
Spelling Mistake
Stroke too narrow (Stroke width)—appears when the stroke width is too narrow.
Text patterns—a series of different preflight checks for text patterns that are commonly found in edited or imported copy which may cause inconsistency. These will report as:
Multiple spaces.
Space after Tab.
Space after break.
Consecutive breaks.
Straight quotes.
Ellipsis with full stops.
Double hyphen for dash.
The document index needs updating
Fill ink density too high (Percentage) / Stroke ink density too high (Percentage) / Text ink density too high (Percentage)—appears when an object uses a color with an ink density over a specified threshold.
Fill uses too rich black (Percentage) / Stroke uses too rich black (Percentage) / Text uses too rich black (Percentage)—appears when an object uses a rich black ink density over a specified threshold.
Fill uses CMY / Stroke uses CMY / Text uses CMY—appears when an object's Cyan. Magenta or Yellow levels do not conform to the document's expectation of only gray and spot colors.
Double-tapping on an issue in the panel will take you to its location in the file. A Fix button beside certain issue types allows you to fix them immediately.
If enabled, preflight will be re-run on print and export. If there are errors (not warnings) in the file, a dialog offers the chance to abort the export and go to the Preflight panel to review the errors.
Preflight user comments
Preflight user comments can be added to objects in your publication using the desktop version of Affinity Publisher, creating a custom check to be made prior to print or export. This has many uses, including the ability to:
Check specific layers are hidden or visible at export.
Check text and picture frames are populated.
Check text frames with placeholder text that may need replacing.
Check images that need copyright checking or creative approval.
Check images using temporary colors.
Check copy.
Ensure copy is approved.
When a user comment is present in a document, it will be listed in the Preflight panel.
To configure preflight settings:
From the Preflight panel, tap on the Profile options menu and select Edit Profile.
The Preflight Profile dialog will appear. From here, you can establish which issues you wish to check for in your file and how extensive you would like your checks to be.
After you have finished editing your profile, close the dialog. The Profile setting will now display Custom.
To save a preflight preset:
From the Preflight panel, tap on the Profile options menu and select Create preset.
Type in a name for your preset and tap OK.
To change the bleed hazard safe zone edge:
From the Preflight panel, tap on the Profile options menu and select Edit profile.
The Preflight Profile dialog will appear. From here, select the Bleed Hazard tab.
Select one of the Safe Zone Edge options.
To enable preflight to check for issues:
From the Preflight panel, select one of the Check options:
Export will check the file for issues just prior to export.
Live will actively check the file for issues as you update it.
To disable error checking:
From the Preflight panel, go to the Check options and select Never.
To check for issues immediately:
From the Preflight panel, select Check Now.
To view an object marked with an issue in the file:
Double-tap on the issue in the Preflight panel.
To automatically fix an issue in the file:
Where applicable, tap the Fix button in the Preflight panel.
Grey indicates that preflight is not enabled, i.e. live checks are not being performed.
Green indicates that preflight is active and no errors or warnings have been found.
Red indicates that preflight is active and errors that will interrupt export have been found.
Yellow indicates that preflight is active and issues that will not affect export have been found.
Edit profile function allows you to tailor preflight checking to your needs. You can control the severity level for preflight issues, set values and thresholds that trigger preflight warnings and errors, and control how placed documents work with preflight.
A yellow icon to the left of an entry is a warning of an issue that will not affect export.
A red icon to the left of an entry indicates an error in the file that will interrupt export.