You can capture the results of a preflight inspection in various types of reports. You can capture the results in a text file, an XML file, or a single PDF file. A PDF report can include just an overview or detailed information presented in different ways.

A PDF report includes information about the document and problem objects in layers, which you turn on or off in the Layers navigation pane.

Create a report of preflight results

Report types

PDF Report Creates a summary of problems accompanied by details that are shown using transparent masks, comments, or layers for each problem object.

Overview Condenses the preflight results into a short document that includes applied fixups, a results summary, and document information.

Details Reports additional information about each problem object—for example, where the object is located on the page. Problems Highlighted By Transparent Masks places a colored mask, similar to a Photoshop mask, over areas to make the problem areas stand out. You can change the mask color using Preflight preferences. Problems Highlighted By Comments inserts preflight results as comments. Problems Highlighted By Layers shows the file separated into layers of mismatches or found objects according to the criteria used in the profile itself. Another layer called Other Objects includes objects that have nothing to do with the profile used.

XML Report Produces a structured report for workflow systems that can interpret and process the preflight results. For details, contact your print service provider.

Text Report Produces a report in plain text format, with each line indented according to the hierarchy in the Preflight Results dialog box. You can open the report in a text editor.

Hide or show layers in a PDF report

About inventory reports

An inventory report shows resources used in a PDF, including color spaces, images, patterns, shadings, metadata, and fonts and glyphs in each font family. Related information is grouped together and arranged on a PDF page so that you can scan and locate items. You can run an inventory report before or after you run a preflight inspection. Unlike a preflight results report, which provides only the information requested by checks in the selected profile, an inventory report does not filter the PDF content. Together, a preflight inspection report and an inventory report can help you identify and fix problems.

The information in an inventory report can be useful when you perform tasks such as these:

• Exploring files that seem unusual, such as those created by an unknown application, or files with slow screen redraw or copy-and-paste actions that don’t work.

• Examining processing issues, such as failure to print correctly, or problems encountered during color conversion, imposition, placement on an InDesign page, and so on.

• Identifying aspects of a PDF that are not ideal, such as the inadvertent embedding of a font because of an unnoticed space character on a master page, or cropped images with extraneous image data, or objects that are not of the expected type (such as type or vector objects converted to images or merged with an image).

• Providing additional information about an object besides its presence. For example, by locating a spot color in the inventory report, you can determine whether it is used by itself or in combination with other colorants, such as in a duotone image. Or you can determine which glyphs in a font are embedded, what they look like, and which character they are supposed to represent. This information can help you resolve a missing-glyph error.

• Exploring XMP metadata embedded with the file, such as its author, resolution, color space, copyright, and keywords applied to it. This information is stored in a standardized way using the Extensible Metadata Platform (XMP) standard.

Create an inventory of PDF content