Check PDF embedded color profile

That distinction is useful before commercial printing because an RGB declaration may signal that conversion is still required, while a named CMYK output profile can document the intended press condition. The check is deterministic, runs without uploading a PDF to another service, and explains which metadata clue produced the classification.

What the checker establishes

A PDF can look correct on a monitor while still carrying color information that is unsuitable or ambiguous for a print workflow. This checker focuses on one narrow, auditable question: does the supplied metadata block explicitly identify a CMYK profile, identify an RGB profile, or contain no recognized profile declaration? It searches canonical color-space terms, common ICC profile families, and Photoshop color-mode values that appear in XMP and related metadata. The result includes the classification, a Boolean indicating whether a profile was found, and concise evidence describing the matched declaration. A complete metadata block with no relevant declaration returns none; that is a valid result, not an error. By contrast, text that is not a complete XMP, RDF, or serialized PDF dictionary is rejected because silently treating missing metadata as an unprofiled document would hide an extraction failure. The tool analyzes metadata only. It does not render pages, inspect every image object, open an OutputIntent stream, or prove that all page elements use the declared space.

How to prepare and interpret metadata

Supply the complete metadata block extracted from the PDF, including its XMP or RDF wrapper, or provide a complete PDF dictionary enclosed by double angle brackets. Preserve profile names and color-space fields exactly; they carry the evidence used for classification. A CMYK result can come from declarations such as DeviceCMYK, a CMYK color-model value, Photoshop color mode 4, or a recognizable press-profile family such as FOGRA, SWOP, GRACoL, or an ISO Coated profile. An RGB result can come from DeviceRGB, CalRGB, sRGB, Adobe RGB, Display P3, ProPhoto RGB, ECI RGB, an RGB model value, or Photoshop color mode 3. If both families are explicitly present, the checker rejects the input as conflicting rather than choosing whichever match happens to appear first. Interpret none literally: no supported embedded profile declaration was found in the supplied block. It does not mean that the PDF contains no color, nor does it guarantee device-independent output. It means the available metadata does not declare a profile the checker can classify.

Using the result in a print-readiness review

Treat this result as an early checkpoint, not as a complete preflight certificate. For offset or digital print production, a declared CMYK profile is often a useful sign because it records a press-oriented color condition, but the correct profile still depends on the printer, paper, ink limits, and regional standard. An RGB result is not automatically defective: modern PDF workflows may preserve RGB content and convert it through a controlled output intent at the raster image processor. It does, however, tell the production team to confirm where and how conversion will occur. A none result deserves a documented decision. The file may rely on device color, a separate job ticket, or output intent data that was not included in the extracted metadata. Combine this check with page-size, bleed, font embedding, image resolution, transparency, overprint, spot-color, and OutputIntent inspection. In automated intake, store the classification and evidence beside the job, route RGB or unprofiled files for review, and reserve hard rejection for rules agreed with the print provider. Via the API, each metadata check costs $0.002.