Output Intents Explained

Overview

An output intent is PDF metadata—required by PDF/X—that identifies the characterized printing condition the file is prepared for. Common examples reference industry conditions such as GRACoL, SWOP, FOGRA39, or a custom ICC characterization registered for a plant.

Think of the output intent as a label on a shipping crate: it tells the receiver which press condition the sender targeted. It does not by itself re-separate every image into that condition. Objects may still carry their own color spaces; the intent guides default rendering and proofing assumptions.

Mis-set output intents create false confidence. A brochure tagged for newsprint but built with sheetfed coated separations may look “compliant” while color expectations remain wrong. Always align the intent with the actual job specification.

Step-by-step

1. 1. Read the job’s press condition before export

   Get the named condition from the printer (profile name, ICC file, or PDF/X job options). Do not invent a popular profile because it “sounds right.”

   Confirm substrate family—coated sheetfed, uncoated, web, newsprint—because that choice drives the intent.

2. 2. Export with the matching PDF/X preset

   InDesign, Affinity, and similar apps bundle output intent selection into PDF/X export presets. Prefer the plant’s preset when provided.

   If you must set it manually, choose the ICC/characterization the printer named and keep PDF/X version constraints consistent with their RIP.

3. 3. Verify the intent landed in the PDF

   Use a preflight tool or PDF inspector to confirm an Output Intent dictionary exists and references the expected profile description.

   Dockzio’s pdf-metadata view is useful for quick documentary fields; for full OutputIntent inspection, use a prepress preflight that surfaces ICC identifiers.

4. 4. Check that content color matches the story the intent tells

   If the intent is a CMYK press condition, confirm critical brand colors were converted or managed with that condition in mind—not left as unmanaged RGB.

   Spot colors should remain spots when the job ticket calls for them; converting spots to process silently can shift color even when the intent is correct.

5. 5. Revisit the intent when the press path changes

   Moving a job from sheetfed coated to a digital press or uncoated stock means the old intent may be misleading. Re-export or re-convert with the new condition.

   For early design reviews, a soft-proof setup that simulates the intent’s condition beats eyeballing untagged RGB on a bright monitor.

Common mistakes

• Assuming the output intent converts all colors. The intent declares the target condition. Conversion still depends on how objects were tagged and how the export or RIP applies color management.
• Copying a preset from a previous client job. Yesterday’s FOGRA condition may be wrong for today’s US sheetfed job. Reset intents per ticket.
• Stripping intents with “optimize” tools. Some compression or PDF rewrite utilities drop OutputIntent dictionaries. Re-check after pdf-compress or similar processing when PDF/X matters.