Header and verdict. Each report opens with the product name, the title Preflight report, and the verdict in a coloured block: PASS, PASS WITH WARNINGS, or FAIL. The HTML file's page title starts with the verdict and the file name, so it reads clearly in a browser tab or an email attachment list.
The facts table. File, SHA-256, Size, Pages, PDF version, and, when the file has them, Title, Producer, and Creator, followed by Profile, Checked (the date, time, and time zone), and Engine (the app version). The Producer and Creator lines often tell you which program made the file, which helps when you write to the designer.
Findings. Three counts sit above the table: errors, warnings, and notes. Each row gives the severity, the check (for example image-resolution, font-embedding, color-space, bleed, or spot-colors), the pages, and the finding in plain words, with a detail line where it helps. A clean file reads "Every check passed under this profile."
Pages. One row per page with its MediaBox, TrimBox, BleedBox, Rotate value, and finished trim size, so box problems can be read side by side.
Images, fonts, and colour. The Images table lists each placed image with its page, pixel size, placed size, effective ppi, colour space, bits per component, and soft mask. The Fonts table lists every font with its type, whether it is embedded or subset, and its pages. The Colour table lists each colour space with what it was used for and where, plus every spot colour by name.
Transparency and output intent. Live transparency is listed by page and kind, with the group colour space, and the output intent section shows the declared condition and the number of components in its destination profile.
Two formats, one result. The HTML report is one self-contained file with no scripts and no external requests, so it opens offline in any browser. The PDF report carries the same content, paginated and with embedded fonts, for email and print. Both are named after the customer's file, as name.report.html and name.report.pdf.
Saving them. The first Save reports asks for a folder and remembers it; later saves go straight there, and a second report for the same file is saved alongside as name.report (2).html rather than replacing the first. The status line confirms both file names and the folder.
Matching a file to its report. The SHA-256 in the report identifies the exact file checked. Get-FileHash in Windows PowerShell computes SHA-256 for any copy; when the two values match, ignoring letter case, it is the same file.