PDF ICC / Output Intent Inspector
Upload the PDF to see whether output intents, ICCBased color spaces and common profile metadata strings are detectable in the file structure.
Look for ICCBased and output-intent evidence
The PDF stays in your browser. InkyValley scans readable structure for profile/output-condition signals and clearly labels absence as inconclusive when compressed object streams may hide them.
Color numbers only become meaningful inside an output condition
PDF color-space and output-intent signals help diagnose a job, but browser-side token inspection does not replace a color-managed separation preview or printer-specific preflight.
Color-space, output-intent, spot/separation or overprint tokens that can be read from the file.
Which profile, TAC limit, black build or conversion policy is correct for this output condition.
Use the printer/prepress profile, proofing workflow and professional output preview where the job is color-critical.
What the result is useful for
It can quickly distinguish “no readable output-intent evidence” from a file that exposes profile/output-condition metadata.
How the calculation works
This is structural token inspection of the local PDF bytes.
What this calculator cannot know
Compressed/object-stream structure can hide metadata from a token scan, and presence does not prove that a profile is valid or appropriate. Verify in professional preflight/output preview.