Common for cameras, monitors and many photo-lab files
Print preparation guide
Choose RGB or CMYK Without Guessing the Print Workflow
Understand document profiles, output profiles, gamut, soft proofing and when a printer expects RGB, CMYK or a supplied PDF color condition.
Quick answer
RGB and CMYK are color models, not automatic quality levels. A tagged file tells color-managed software what its numbers mean. Some photo labs request sRGB and perform their own conversion; some commercial workflows request a specific CMYK profile or PDF OutputIntent. Follow the provider, not a generic 'convert everything' rule.
source profile → color conversion → output profileOutput condition depends on press, ink and paper
Defines how numeric values map to appearance
Decision table
Color decisions that are often confused
| Action | What it does | When it is useful | Risk when guessed |
|---|---|---|---|
| Assign profile | Changes interpretation of existing numbers | Correcting missing or wrong tagging | Large unintended appearance shift |
| Convert profile | Changes numbers to preserve appearance | Preparing for a known destination | Clipping or unnecessary conversion |
| Soft proof | Simulates an output condition on screen | Reviewing gamut and paper effect | False confidence on an uncalibrated display |
| Embed profile | Carries color meaning with the file | Color-managed handoff | Untagged values interpreted inconsistently |
| PDF OutputIntent | Declares the intended output condition | Standards-based print PDF | Wrong condition for the actual press |
Color numbers need a profile to describe appearance
The same RGB triplet can appear different in two RGB spaces, and the same CMYK values can print differently on coated and uncoated stocks. An ICC profile describes the color space or output condition so managed software can translate values consistently.
An untagged file carries numbers without a reliable color-space definition. Guessing a profile can change its appearance; preserve the profile attached by a known source or establish the correct one before editing.
RGB is not automatically wrong for print
Cameras and scanners usually begin with RGB data, and RGB spaces can retain colors outside a particular press CMYK gamut while the image is edited. Many photographic services explicitly request an sRGB JPEG because their production system performs the final conversion.
Sending RGB to a workflow that requires a supplied CMYK condition can still be wrong. The provider's specification decides the handoff model and profile, not the fact that the job will eventually place ink or toner on a surface.
CMYK is a family of output conditions
CMYK does not name one universal color space. Ink set, paper, press behavior and regional standard affect the printable gamut and total ink behavior. A generic conversion to an arbitrary CMYK profile can make a file less suitable for the actual device.
When the provider supplies a profile or PDF preset, use that destination and its documented rendering settings. Preserve an editable master before converting because repeated conversions can discard color relationships that the smaller destination cannot represent.
Assigning and converting are different operations
Assigning a profile tells software how to interpret the existing numbers and can visibly change the document. Converting calculates new numbers intended to preserve appearance in a destination space within its gamut.
Do not assign a destination CMYK profile to RGB numbers or use Assign Profile as a shortcut for conversion. If a file arrives untagged, identify its origin and make a controlled decision rather than cycling through profiles until one looks pleasing.
Soft proof the known output condition
Soft proofing uses an output profile to simulate how the destination may reproduce color. It can reveal out-of-gamut saturated colors, changes in shadow separation and the influence of paper white.
The preview is still limited by monitor calibration, ambient light and the accuracy of the output profile. For brand, skin-tone or art-reproduction work, a physical contract or production proof remains more informative than a browser preview alone.
Prevent double color management at output
When an application performs the conversion for a desktop printer, the printer driver should not perform another conflicting conversion. Alternatively, a managed printer workflow may expect the application to preserve the source and let the device handle color.
Document the chosen handler, profile, rendering intent and proof. Reopen exported PDFs in an output-preview tool when appropriate and confirm that the embedded profiles or OutputIntent match the provider's requested workflow.
Practical workflow
Use this order before you export.
- Read the provider's required model, profile and file type for the exact product.
- Keep an embedded source profile and an editable master.
- Soft proof and convert once to the supplied destination only when requested.
- Inspect the exported file and use a physical proof for color-critical work.
Sources and method
Check the requirement behind the number.
These guides explain repeatable calculations and planning ranges. The print provider's written specification remains the final production requirement.
Put the guide into practice
Open the full preflight checklist →Preserve an embedded source profile and convert only to the color condition requested for the real output device.
Use the linked calculator with your own dimensions, then verify the result against the provider's production requirement.