Dosie Foxie

Logo print quality: why the colour changed when it went to print

The logo on your screen is RGB light. The logo on paper is ink absorbing light. They are different physical processes, and some colours simply do not survive the translation. Knowing which ones saves a reprint.

A printer converts your file to CMYK: cyan, magenta, yellow and black ink. Bright greens, oranges and violets often fall outside what those four inks can mix. The conversion brings them into gamut, and the brand colour moves.

This is normal. The failure is not the shift; it is not knowing it happened until the boxes arrive. A production file makes the shift visible and gives the printer a reference to match.

Which colours move

Colour familyWhat happens in CMYK
Bright greenOften dulls and shifts yellow; neon greens are out of gamut
Orange and warm redUsually holds reasonably well, but can lose punch
Violet and deep blueCan shift toward purple or black; rich blacks need care
Metallic and fluorescentCannot be mixed from CMYK; need a spot ink
PastelsUsually fine, but small ink changes are visible on large areas

ΔE is the number used to describe colour difference. Roughly, under 2 is hard to see, 2–3 is noticeable to a trained eye, and above 3 is visible to most people. It is a guide, not a guarantee.

Black is not one colour

A logo that uses black for text and a large background is making two different demands. Small text wants 100% K only, so it stays sharp and does not pick up a colour cast. A large solid area may want a rich black (some cyan and magenta added) so it does not look washed out. One 'black' swatch cannot do both well.

What to send a printer

  1. A CMYK PDF with the conversion already made, so the printer is not guessing.
  2. The original sRGB value written down, so the brand has a reference both ways.
  3. A spot-colour note where a colour cannot be matched in CMYK, with the understanding that it may cost an extra ink.
  4. A one-colour version for the jobs where colour matching is not worth the money.
  5. A small physical proof, if the run is large. Screens lie; paper does not.

Worked example: the green that went dull

The brief

A garden centre has a bright leaf-green mark. It prints 2,000 leaflets and the green comes back olive.

The sRGB green is outside the CMYK gamut. The printer converted it, correctly, to the nearest ink mix. The file had no CMYK reference, so there was nothing to compare it to and no decision to make before the run.

The fix is either to accept a slightly deeper green and record it as the print version of the brand, or to specify a spot green for the jobs where the exact colour matters. Both are legitimate; choosing one deliberately is the production step.

What our pack ships

The pack ships clean geometry and a vector PDF, with the sRGB hex values recorded in spec.json. It does not ship a CMYK master, a spot reference or a ΔE report; your printer converts and measures the shift. That is deliberate: a CMYK build is a property of the press, the ink and the stock, not of the logo file. What the pack fixes is the part before that conversion — no embedded raster, no live text, no traced edges.

Questions

Why does my logo look duller in print?

Because CMYK ink cannot reproduce every colour a screen can emit. Bright greens, oranges and violets are the usual casualties. Recording the CMYK values your printer returns makes the shift predictable; a generic CMYK build from a different press does not.

Should I use Pantone colours?

If exact colour matters and the budget allows an extra ink, a spot colour is the reliable way. For most small-business print, a well-managed CMYK build plus a one-colour version is enough.

What is ΔE?

A number for how different two colours look. Lower is closer. It is useful for comparing the screen colour, the CMYK conversion and the printed result, but it is not a guarantee that two materials will match.

If the file is the problem, the pack is the fix.

The Production Pack is $149, one time: true vector masters, six lockups, a print PDF and EPS, one ink per file and unlimited parametric edits.

See the production pack Audit my current file

Free tools: vector check · 12-file audit · 16px legibility · CMYK shift · stitch estimate

For agents

The same pack is available to a machine: a structured brief, a JSON manifest, x402 in USDC on Base, and an MCP tool contract.

Agent access · OpenAPI · llms.txt · MCP

Agent API: the contract, the free endpoints and the paid x402 checkout are live. USDC on Base, no account, no API key.

Related guides