CMYK vs RGB: Colour Spaces, Gamut Limitations, and File Setup for Print and Screen

The single most expensive misunderstanding in graphic design is the difference between the RGB and CMYK colour models. Settle the RGB-versus-CMYK workflow question before you place a single pixel. RGB is additive: your monitor, phone, and projector emit red, green, and blue light, and the combination of those three primaries creates the hues you see. CMYK is subtractive. Ink on paper absorbs light, and the cyan, magenta, yellow, and black dots that make up a printed page reflect only the wavelengths that survive the ink layer. These are not two versions of the same thing. They are two different physics. An RGB tone that glows on a backlit screen is often outside the CMYK gamut entirely. No combination of the four printing inks can reproduce it. The consequence is not a slightly worse print. It is a desaturated, muddy approximation of what you designed, and nothing on your monitor warns you it is coming. The only tool that shows you the disaster before you commit to press is a soft-proof: a proof that simulates the final output on screen using an ICC profile and a D50 viewing condition. If you do not soft-proof, you are flying blind. The ink will tell you what you should have known.

Every screen that has ever shown you a design uses the additive colour model. The pixels emit light. In the dark, a black screen is really an off pixel. In RGB, mixing red and green produces yellow, red and blue produces magenta, and all three at full intensity produce white. The gamut, or the volume of tones a device can reproduce, is defined by the primaries it uses. The sRGB colour space, the default for the web, Windows, and most consumer displays, covers roughly 830,000 cubic units in the CIELAB colour volume. Adobe RGB, built for photography and high-end proofing, expands that to about 1,200,000 units. Display P3, the colour space of modern Apple devices, sits between them. None of these volumes matter to a press. A sheet-fed offset press running to the ISO 12647 standard and characterised by the Fogra 39 or Fogra 51 data sets has a CMYK gamut that is dramatically smaller than even sRGB in the bright cyans, saturated greens, and vivid oranges. The electric blue that looks perfect in Figma or Photoshop is simply not reachable with cyan, magenta, yellow, and black inks. When you convert that colour to CMYK, the conversion engine must map the out-of-gamut value to the nearest in-gamut equivalent, a process called gamut clipping. The result is a tone in the same hue family but far less saturated, and you will not see the loss until you soft-proof under ISO 3664 lighting with the correct ICC profile loaded.

How the Failure Plays Out

The failure mode is not subtle. A designer works in RGB, exports a PDF, and sends it to a printer who converts to CMYK at the RIP stage with no instruction and no soft-proof. The blue that was #0033CC becomes a flat, purple-tinged navy. The bright green logo turns olive. The client, who saw the RGB version on a laptop, is angry. The designer cannot explain why, because they never looked at the file through a proper proofing simulation. The fix is to understand that CMYK is not a filter you apply at the end. It is the medium of the print. You must design in it, or at least proof in it. If you are designing for a product that will live on both a screen and paper, you design two files. Or you design in CMYK and accept that the screen version will be less saturated. There is no way to have the full RGB gamut on paper. Anyone who tells you otherwise is selling you a press that does not exist.

The question of when to design in CMYK has one correct answer for print-first work: before you start, not at the moment of export. If the final destination is a commercial press, set up the document in Adobe InDesign or Affinity Publisher with a CMYK document profile from the first page. Choose a named output intent, not a generic 'CMYK' preset. In Europe, that means Fogra 39 for coated stock and Fogra 51 for the newer, more neutral paper standards. In North America, it is GRACoL2006_Coated1v2 for sheetfed and SWOP for web. These are characterisation data published by Fogra and the IDEAlliance. They define a specific press condition, not an abstract colour space. When you convert an RGB image to CMYK in Adobe Photoshop, the conversion uses the working CMYK space in your Colour Settings. The default for North America is U.S. Web Coated (SWOP) v2, which is a reasonable approximation but not identical to the GRACoL profile your sheetfed printer will actually run. If you send a PDF built to one output intent to a press running another, the printer's preflight will flag a mismatch. Many small printers do not check, and the result is another set of shifted tones.

Choosing Your Rendering Intent

The structural decision is your rendering intent. Adobe Photoshop and InDesign give you four choices, but for almost all real work, you choose between two. The perceptual rendering intent is for photographic images. It compresses the entire colour gamut proportionally, so that out-of-gamut and in-gamut tones all shift together, preserving the visual relationships and the overall appearance of a photograph. If you have a landscape with a vivid blue sky and saturated green grass, a perceptual conversion keeps the sky blue and the grass green, even though neither will be as intense as the original RGB file. The relative colorimetric rendering intent maps the white point of the source to the white point of the destination and then clips only the out-of-gamut tones to the nearest reproducible hue. In-gamut tones remain exactly the same. This is the correct choice for vector graphics, logos, and spot colour elements. It preserves the exact hue of a Pantone colour that falls inside the CMYK gamut. Choose the wrong intent, and a photographic image looks flat and washed out. Or a vector logo shifts to a tone that violates the brand. There is no universal best. There is only the correct intent for the image type in front of you.

Before you convert anything, decide which RGB colour space to edit in. This is where the sRGB-versus-Adobe RGB choice does real damage. sRGB IEC61966-2.1 is the default colour space of the web, of Canva, of Figma, and of most consumer monitors. It is also the correct target for any image that will be displayed on a screen without colour management. The vast majority of unmanaged web browsers and mobile apps assume sRGB and will render any other profile as if it were sRGB, producing oversaturated or undersaturated tones. Adobe RGB (1998) has a wider gamut, particularly in the green and cyan range. It is the right choice for photographers who shoot raw and will output to a high-end CMYK press or a wide-gamut monitor. But if you design a document in Adobe RGB and forget to convert the images to sRGB when you export for the web, they will look desaturated and grey on most devices. The same file, opened in Photoshop with a properly configured Colour Settings dialogue, will look identical to the original, because the profile is embedded. The problem is not the colour space. It is the failure to convert at the point of output.

The Print Decision

For print, the decision is different. An Adobe RGB image contains more colour information than an sRGB image, but that information is not automatically retained when you convert to CMYK. The conversion engine maps the source gamut to the destination gamut. If the destination is Fogra 39, the extra green and cyan range of Adobe RGB is mostly out of gamut and will be clipped regardless of which source you started with. The practical result: starting with a wider RGB space does not give you a wider printed gamut. It just gives you more data to throw away. What it does buy you is headroom. If you shoot a raw file and need to make aggressive tonal adjustments, an Adobe RGB or ProPhoto RGB working space prevents banding and posterisation in the highlights and shadows. The intermediate values are numerically finer. You then convert to CMYK at the end, using the perceptual intent for photos, and the image quality survives the round-trip. For a flat-colour logo or a vector illustration, there is no benefit to a wide gamut. Designing in Adobe RGB in InDesign while your images are sRGB will cause a mismatch when you export. Pick one RGB space for all your screen work. Make it sRGB unless you have a specific reason to use another.

You cannot soft-proof without an ICC profile. You cannot soft-proof correctly without the right one. An ICC profile is a device characterisation file, a standardised description of how a specific device reproduces colour, published under the ICC.1:2001-04 standard or the newer ICC.1:2010 (Profile version 4.3.0.0) specification. For print, the profile you need is the one that matches your printer's press condition. In Europe, the standard for coated stock is Fogra 39, also called ISO Coated v2. It is the default output intent in InDesign and Photoshop for the European print market. For uncoated stock, use Fogra 29. In North America, the sheetfed standard is GRACoL2006_Coated1v2, and the web press standard is SWOP2006_Coated3v2. Japan uses JapanColor2011Coated. These profiles are not interchangeable. Using the wrong one produces a simulation that lies. If you proof a file destined for a GRACoL press using a Fogra 39 profile, the simulation may show tones that the press cannot actually hold. The printed result will be darker and more magenta than the proof promised.

The Two-Step Soft-Proofing Process

Soft-proofing is a two-step process. First, assign the profile to the document, either by embedding it or by converting the file to the destination colour space. Second, turn on the soft-proof view in your design application. This simulates the print by transforming the document colours through the destination profile and displaying them on your monitor. The viewing condition matters as much as the profile. ISO 3664 specifies a D50 light source at 500 lux for print evaluation. A D50 viewing booth is the only environment in which the proof is valid. If you soft-proof at your desk under a warm LED bulb, the tones will look different from the same file viewed under the D50 booth at the printer. The difference is not small. A 10-15% shift in perceived brightness and a magenta cast are common when the viewing conditions are wrong. When you set up the soft-proof in Photoshop, choose the 'Simulate Paper Color' option to see the effect of the paper white. Choose 'Simulate Black Ink' to see the darkest shadow the press can hold. If the file contains total ink coverage above the press limit, the soft-proof will show plugging in the shadows. You must reduce the ink density before you export. The limit for coated stock is around 300%, and for uncoated it drops to 260%, as specified in the ISO 12647 standard.

The rendering intent you choose at the moment of RGB-to-CMYK conversion is a structural decision, not a technical detail. The perceptual rendering intent exists to preserve the visual impression of a photographic image. When an image contains tones outside the destination gamut, perceptual mapping compresses the entire tonal range. It shifts in-gamut tones as well as out-of-gamut ones, so that the relationship between colours remains visually plausible. A sunset photograph with a deep orange sun and subtle pink clouds will convert with the orange and pink both slightly muted. But the sky will still look like a sky, and the sun will not suddenly turn brown. The relative colorimetric intent takes a different approach. It maps the source white point to the destination white point, which means that paper white becomes the brightest value. Then it clips only the tones that fall outside the destination gamut. In-gamut tones are reproduced exactly. The only tones that change are the ones that cannot be printed. This is the correct intent for vector graphics, solid areas of colour, and logos. A brand blue that is exactly within the CMYK gamut must stay exactly that blue. It must not shift because the rest of the image needed to be compressed.

The Correct Workflow

The mistake most designers make is using the same intent for everything. If you convert a photographic image with relative colorimetric, the out-of-gamut tones clip abruptly. The result is a flat, banded area where the image had smooth gradients. If you convert a vector logo with perceptual, the entire palette shifts. A logo that was a precise Pantone 300C becomes a different blue because the conversion compressed it down. Convert images and vector elements separately. Or rely on the output intent in the PDF/X file to handle the conversion at the RIP. The safest route: assign the destination CMYK profile to the document, set the rendering intent per object in InDesign, and let the PDF/X-4 export embed the ICC profile and the output intent. The Ghent Workgroup, the organisation that publishes the PDF/X-4 compliance guidelines, recommends this workflow. It preserves live transparency and embedded profiles, giving the RIP the maximum information to work with. A PDF/X-4 file that declares Fogra 39 as its output intent and embeds the ICC profile is far more reliable than a PDF that converts everything to CMYK at the application level and strips the profiles.

When you export a PDF for a commercial printer, the export format that solves the most problems is PDF/X-4, defined by the ISO 15930-7 standard. PDF/X-4 is the first version in the PDF/X family to support live transparency. A drop shadow or a soft edge that you apply in InDesign or Illustrator is preserved as a vector object rather than flattened into a raster image. It also supports the embedding of ICC profiles, so the PDF can carry both the source RGB data and the destination CMYK output intent. It allows a mixture of colour spaces in the same file. The Ghent Workgroup, an international body of print production experts, publishes a set of conformance rules that go beyond the ISO standard. Their PDF/X-4 specification is the one that print buyers and prepress departments use to validate files. A file that passes the Ghent Workgroup PDF/X-4 checks is more likely to print correctly on the first run, with no unexpected colour shifts and no missing fonts.

Why the Preset Is Not Enough

But selecting 'PDF/X-4' in the export dialogue is not the same as producing a compliant file. The export preset in InDesign or Affinity Publisher is a starting point, not a guarantee. The preset sets the output intent, the profile, and the transparency flattening options. It does not check your content. If your images are in RGB and you chose 'No colour conversion' in the preset, the PDF will contain RGB images and the output intent will be ignored at the RIP. The print will not match the soft-proof. If you have spot colours that are not defined as Pantone and are instead process builds, the PDF will contain four-colour simulations that look different from the intended spot colour. The only way to know whether the file is actually compliant is to run a preflight check, either in the application or in a dedicated preflight tool like Enfocus PitStop or Adobe Acrobat Pro. The preflight checks for the presence of the output intent, the correct profile for the images, the total ink coverage per pixel, and the font embedding permissions. A font embedded with 'Print and Preview' permission is allowed in a print-only PDF. A font with 'Installable' permission is not always safe. A font that is not embedded at all will cause the RIP to substitute a fallback that changes your layout.

Gamut clipping is the moment when the conversion engine decides that a colour cannot be reproduced and substitutes the nearest available alternative. It is not a gradual loss of saturation. It is a hard cut-off. A gradient that goes from a saturated cyan to a slightly less saturated cyan in RGB may hit the clipping point partway through, producing a visible band where the gradient suddenly stops changing and becomes flat. The same thing happens with a photographic sky that contains a range of light blues. The light blues are within the CMYK gamut, but the deeper blues are not. The conversion will either clip them to a darker navy or compress the whole range, depending on the rendering intent. You cannot see the clipping in the RGB image. The screen can display the full range. You can only see it in a soft-proof, and only if the soft-proof is set to show the gamut warning, which highlights out-of-gamut areas in a bright overlay. Learn to use the gamut warning tool in Photoshop and InDesign. It is the only way to know which tones will survive the trip to ink.

Total Ink Coverage Limits

Total ink coverage is a separate limit that has nothing to do with colour and everything to do with physics. When you print a colour that uses 100% cyan, 100% magenta, 100% yellow, and 100% black, the total ink coverage is 400%. The ink layer is so thick that it will not dry, will smear, and can crack when the paper is folded. The practical maximum for coated stock in offset printing is around 300% total ink coverage. For uncoated stock it drops to 260%. The default warning threshold in Adobe Photoshop and InDesign is 300%. The application will flag any combination of CMYK values that exceeds that limit. The warning is a safety net, but it is not a design tool. A rich black, used for a large background area, should be built with a maximum of 300% total ink. For example, 60C 40M 40Y 100K avoids the mottling that appears when the ink never dries. Newsprint, which is more absorbent, has a limit of 240-260%. These are not arbitrary numbers. They are derived from the ISO 12647 process control standard and from each paper mill's characterisation data, and they vary by substrate. The only way to know the exact limit for your job is to ask the printer, or to check the 'total ink coverage' value in the preflight report. Ignoring the limit produces a printed piece that is wet, smeared, and unprofessional. It is a failure that a soft-proof cannot catch.

No discussion of RGB and CMYK is complete without a warning about the most common source of print failure in the design world today: Canva. Canva is a template-based design platform that operates entirely in the sRGB colour space. It has no CMYK working space, no soft-proofing, and no way to view a file that simulates the printed result. When you export a design from Canva as a PDF, the platform converts the sRGB colours to CMYK using a fixed conversion, targeting the SWOP Coated profile in North America. The conversion is automatic. It uses a single default rendering intent and gives you no control over gamut clipping or ink coverage. A saturated design that looks perfect on your monitor will print as a desaturated version of itself. There is nothing you can do about it inside the platform. The failure is not a bug. It is a consequence of the business model, which serves users who want speed and simplicity and are not trained in colour management. For a one-off flyer or a social media graphic that is not brand-critical, this is acceptable. For a business card, a brochure, or any piece that represents a company's identity, it is a liability.

How to Work Around the Limitation

The failure mode is specific and repeated. A small business owner uses a Canva template to design a logo and prints it on a mug. The logo contains a bright orange that is outside the CMYK gamut. The print comes back a muddy brown. The owner blames the printer, reorders, and the same thing happens. The printer cannot help. The file was assembled in RGB and converted at export with no soft-proof. The design looks fine on screen, but the print is wrong. No one is at fault, and yet the customer is disappointed. The solution is not to tell people to stop using Canva. It is to understand the platform's limitations and work within them. If you must design in Canva, design with the final print in mind from the start. Choose colours that are naturally within the CMYK gamut. Identify them by using a colour picker that shows the CMYK equivalent. Avoid the bright sRGB-only tones that are common in web design. Export to PDF, and then, if you can, open the PDF in a professional tool and run a soft-proof against the printer's ICC profile. If the printer accepts the file, ask them to send a hard proof. A hard proof, which is a physical print made on the actual press or a calibrated inkjet, is the only way to see the final result before the full run. It is the last line of defence against a Canva RGB-only export that fails on press.

Adobe InDesign is the professional standard for multi-page print documents. Its colour management system is the difference between a predictable press run and a costly reprint. The first thing you do when you create a document for print is set the colour settings in the Edit > Colour Settings dialogue. The working space for CMYK should match the output intent of the print service. If you are in Europe and the printer runs ISO Coated v2, select 'Coated FOGRA39 (ISO 12647-2:2004)'. The working space for RGB should be sRGB IEC61966-2.1 unless you have a specific reason to choose Adobe RGB. The colour management policies should be set to 'Preserve Embedded Profiles' for both RGB and CMYK. A file that enters your document with a profile is not accidentally converted. The conversion options should default to Adobe (ACE) as the engine, with the relative colorimetric intent selected as the default. Enable the 'Use black point compensation' checkbox. It ensures that the deepest black in the source is mapped to the deepest black in the destination, rather than remaining a dark grey.

The Transparency Blend Space

InDesign's transparency blend space is a subtle but critical setting. When you apply a drop shadow or a blend mode to an object, InDesign must decide whether to blend the colours in RGB or in CMYK. If the document's output intent is CMYK, the blend space should be set to CMYK. Find it in the Document Setup or by selecting the page and opening the 'Transparency Blend Space' submenu in the fly-out menu of the 'Effects' panel. If the blend space is RGB and you have a CMYK output, the blend will be computed in RGB and then converted, producing a colour shift in the shadow. The same principle applies to Affinity Publisher. It defaults to the sRGB IEC61966-2.1 profile for RGB and the U.S. Web Coated (SWOP) v2 for CMYK. These are sensible defaults, but they are not the same as the printer's characterisation data. Open the file in the application and check the working space before you start placing images. Colour management is not a one-click solution. It is a discipline that requires checking the source profiles, the output intent, and the soft-proof at every stage of the workflow.

CMYK is a process colour system. Every hue is built from a dot screen of the four inks, and the eye blends the tiny dots into a solid colour. But for a brand colour, a spot colour is often the right answer. The Pantone Matching System is a proprietary, physical reference standard where a colour is specified by a swatch number, not by a CMYK or RGB value. When you specify a logo in Pantone 300C, the printer mixes a single ink to that exact formula. The printed result will be identical across every press run, every substrate, and every print shop that has the Pantone ink book. A process build of the same colour, using 100% cyan and 30% magenta, can vary from press to press. The ink density, the paper, and the press conditions all affect the final colour. The Pantone system removes that variability by specifying the ink as a physical formula. The trade-off is cost. A spot colour adds a fifth printing unit to the press, which costs more than the four-colour process. For a one-off flyer, a process build is the only sensible choice. For a corporate identity that will appear on a hundred thousand business cards, a spot colour is the only way to guarantee brand consistency.

Working with Spot Colours

When you use a spot colour in a design, you cannot soft-proof it in the same way as a process colour. A Pantone colour is outside the RGB gamut. No screen can display it accurately. The soft-proof will show you a simulation, but the simulation is only as good as the ICC profile for the Pantone library. Adobe's licensing of the Pantone colour books changed in 2022, removing the preloaded books from Creative Cloud. You now have to buy a Pantone plug-in to get the full library. Many designers do not bother. They specify a Pantone colour by name and rely on the printer to match it. The correct workflow: define the spot colour in InDesign as a new swatch of type 'Spot Colour', set the ink to the Pantone formula, and then use that swatch for any element that must match exactly. In the PDF/X-4 export, the spot colour is preserved as a separation. The printer can use the embedded name to find the correct ink. If you convert the spot colour to process, you lose the ability to match it. The printed colour will drift with the press run. A hard proof is the only way to see the actual spot colour, because the screen simulation is a guess. If the brand colour is non-negotiable, request a drawdown or a colour chip from the printer before you commit to the full run.

The conversion from RGB to CMYK is where the most damage is done. It is also where the most control is possible. The first rule: never convert the same image twice. Each conversion is a lossy operation. A file that is converted from RGB to CMYK and then back to RGB will lose colour information irreversibly. The second rule: perform the conversion on a copy of the image, never on the original. You need the full RGB data to go back to. The third rule: use the correct source profile. If your image came from a camera, it may be in Adobe RGB or ProPhoto RGB. Converting from sRGB to CMYK will produce a different result than converting from Adobe RGB because the source gamuts are different. The safest route is to embed the profile in the image file, so that Photoshop or InDesign can read it. When you are ready to convert, choose Image > Mode > CMYK. The conversion will use the working CMYK space and the default rendering intent. But do not use the default. Choose the intent per image. For a photographic image, the perceptual intent will preserve the look of the photo. For a flat-colour graphic, the relative colorimetric intent will keep the tones exact. Photoshop allows you to choose the intent in the conversion dialogue. Use the 'Preview' checkbox to flip between the RGB and CMYK versions and see the difference.

After the Conversion

After the conversion, check the total ink coverage in the darkest shadow areas. The black point of the image, which in RGB is pure black (0,0,0), converts to a rich black in CMYK. A typical build is 40% cyan, 40% magenta, 40% yellow, and 100% black. This total is within the 300% limit. But if the image has deep shadows that are clipped in the original, the conversion can push the total above the limit. The 'Gamut Warning' in Photoshop will show you the areas that are out of gamut before you convert. Use a Hue/Saturation adjustment layer to reduce the saturation of those specific tones until the warning disappears. This is called gamut mapping. It is the difference between a print that looks like the screen and a print that looks like a faded poster. The alternative is to accept the clipping and let the conversion engine choose the nearest available colour. The printed image will then have flat, featureless shadows. The best workflow: address the out-of-gamut tones before the conversion, using the soft-proof and the gamut warning as your guide. Then perform the conversion as the final step before export. This gives you the most control and the least loss of saturation.

Colour is not a property of the object. It is a property of the light that hits the object and the eye that receives the reflected light. This is why the ISO 3664 standard exists. Published by the International Organization for Standardization, ISO 3664 specifies the viewing conditions for graphic technology: a D50 light source, which is a daylight simulator with a colour temperature of 5000 Kelvin, at a luminance of 500 lux, against a neutral grey background with a Munsell N8 reflectance. When you look at a printed piece under a warm incandescent bulb, the tones appear warmer, more yellow. Under a cool fluorescent light, they appear bluer. The D50 standard is designed to simulate the average lighting in a print studio. It is the only way to compare a proof to the press sheet reliably. If you soft-proof a file on your monitor under your desk lighting, the monitor is calibrated to D50, but the room is lit by a daylight LED. The two do not match, and the proof is misleading. The professional way to view a proof is in a viewing booth that meets ISO 3664, with the room lights dimmed and the booth lights the only source. The printer has such a booth. If you are serious about matching colour, ask them to produce a hard proof and view it in a booth of your own.

D50 Versus D65

The D50 standard is not the same as the D65 standard used in some display calibration. D65 is a cooler white. Many monitors are calibrated to D65 as their native colour temperature. When you soft-proof, the ICC profile contains a white point. The colour management engine converts the white point of the monitor to the white point of the paper. If the paper is a bright white, the proof will show a brighter white than the press sheet. This is why the 'Simulate Paper Colour' option is so important. It tells the soft-proof to use the paper white as the white point, which can make the image look darker and more yellow than the screen version. This is a shock the first time you see it. It is the reason so many designers think their print is too dark. The print is not too dark. The screen was too bright. The only way to know what you are getting is to soft-proof under the correct D50 conditions, with the paper white simulated. Then compare the soft-proof to a hard proof under a D50 booth. If they match, your workflow is sound. If they do not, the ICC profile you are using is wrong, or the monitor is not calibrated.

The final step before you send a file to the printer is the export. The format that is closest to a guarantee of success is PDF/X-4. Select File > Export, choose the PDF/X-4 preset, and then make a series of choices that determine whether the file is compliant. The output intent must be set to the printer's ICC profile. In Europe, that means Fogra 39 or Fogra 51. The colour conversion must be set to 'Convert to Destination'. All RGB and Lab colours in the document are converted to the CMYK space of the output intent. The PDF contains only CMYK data. The 'Preserve CMYK values for tagged sources' option should be unticked. Otherwise, any CMYK image that was already converted will not be remapped. The PDF/X-4 standard allows both CMYK and RGB with embedded profiles. But for the highest level of predictability, you want a single output intent and a fully converted file. The Ghent Workgroup's specification adds a further requirement: the PDF must be validated against the 'Ghent PDF Workgroup Output Suite' to ensure that it meets the print buyer's requirements. This is a separate step from the export. It requires a preflight tool that can check the file for compliance with the print standard.

Preflight Is the Last Line of Defence

Preflight is not a luxury. Adobe Acrobat Pro has a preflight function that can check a PDF for the presence of the output intent, the correct fonts, the resolution of the images, and the total ink coverage. Run the preflight, see the list of errors, and fix them before you send the file. A common error is a font that is not embedded. Or an image that is below the 300 ppi threshold for continuous-tone images. A logotype that is a raster image at 72 ppi will look fine on screen and terrible in print, with visible pixel edges. A vector logo, saved as an SVG or EPS, will print at any size without pixelation. This is why the rule is that a logo must exist in a vector format for production. A .jpeg of a logo is a source file failure, not a design asset. The preflight will also catch overprint issues. A white text set to overprint vanishes on press. A black text set to knockout leaves a white halo. These are the details that separate a professional print file from an amateur one. They are invisible on a screen. Only a preflight check and a hard proof will reveal them. When you have run the preflight and the report is clean, send the PDF to the printer. Ask for a hard proof. The hard proof is the final verification. If it matches your soft-proof, you have done everything you can.

The most persistent misconception in the design world is that a printed piece will look exactly like the screen version, and that any difference is the printer's fault. The reality: the screen and the print are physically different media. The difference is predictable. A printed piece is 10-15% darker than the screen version. It is often shifted toward magenta, because the paper absorbs light and the ink subtracts from the reflected light. The only way to compensate is to build the file with the print in mind. Do not correct it after you see the proof. If you design a logo in a dark blue and the print comes back darker, you can lighten the ink values in the file and re-print. But if you wait until after the press run, you are paying for a reprint. The cost of the paper and ink is wasted. Another common misconception is that DPI and PPI are the same thing. DPI, or dots per inch, refers to the resolution of the printed output. PPI, or pixels per inch, refers to the resolution of the digital image. A file that is 300 PPI is sufficient for a continuous-tone print at actual size. But if you enlarge it to 200%, the effective PPI drops to 150, and the print will look soft. The resolution is not a property of the file. It is a property of the output size.

The Conversion Cannot Be Fixed at the End

The third misconception is that you can fix a conversion problem by changing the colour mode at the end. You cannot. Once an image is in CMYK, the gamut is fixed. Converting it back to RGB will not restore the tones that were lost. The same is true for a PDF that is exported with the wrong output intent. You can change the profile in Acrobat, but the pixel values have already been converted. The colours are wrong. The only fix is to go back to the source file, correct the conversion settings, and re-export. This is why the workflow matters more than the individual actions. A designer who starts in CMYK, soft-proofs with the correct ICC profile, and exports to PDF/X-4 with the right rendering intent will produce a file that prints as intended. A designer who starts in RGB, exports to PDF without soft-proofing, and hopes for the best is gambling with someone else's budget. The difference is not talent. It is process. Learn the process, and the colours will follow.

If you have read this far, you already know the answer. The practical question remains: what do you do on Monday morning when you are the designer, the marketer, or the developer who has to open a file and make it print? The answer is a checklist. First, determine the final output. If it is a screen, the colour space is sRGB. Design in that space. If it is a commercial print, request the printer's ICC profile, or use the standard profile for your region. Set up the document in that space. Second, soft-proof the file against that profile, under D50 lighting, before you export. Third, choose the correct rendering intent for each image type. Fourth, export to PDF/X-4 with the output intent embedded. Preflight the file. Fifth, request a hard proof and compare it to the soft-proof. If it matches, approve the run. If it does not, adjust the file and start again. This is not a creative process. It is a specification process. It is the difference between a designer who is a professional and a designer who is a hobbyist. The industry calls it the Ghent Workgroup standard. It is the standard to which the best print buyers hold their suppliers. It is also the standard that your printer wishes you knew. Every file that follows it saves them time, money, and a phone call.

The questions below are the ones that come up in every training session, every client meeting, and every forum thread. The answers are short because the longer answers are already above. The goal here is a quick reference, not a repeat of the argument.

Why does my print look darker than my screen?

Your screen emits light and the paper reflects it. The printed piece will be 10-15% darker, and it will have a different contrast range. Compensate by using a soft-proof that simulates the paper colour. Ask your printer for a hard proof.

Can I use RGB colours in a print file?

You can. The PDF/X-4 format supports it. But you must embed the RGB profile and set the output intent to the press condition. If you do not, the printer's RIP will use a default conversion that you have not seen and cannot control.

What is the difference between a spot colour and a process colour?

A spot colour is a pre-mixed ink printed as a single solid layer. A process colour is built from a dot screen of the CMYK inks. Spot colours are more accurate for brand colours but more expensive, because they add a fifth printing unit.

How much ink can a press handle?

The maximum total ink coverage for coated stock is about 300%. For uncoated stock it is about 260%. Exceeding the limit causes the ink to dry incorrectly, smear, or crack. The threshold is set in your preflight report.

Does a wider colour space mean a better print?

No. A wider RGB gamut, like Adobe RGB, contains more tones, but the printed CMYK gamut is smaller than sRGB. The extra data is useful for editing, but it does not translate to a wider print gamut. The print gamut is fixed by the ink and paper.

Why does a PDF/X-4 export fail when the colours are still wrong?

The export preset does not enforce colour management. The file can be named PDF/X-4 and still contain RGB images, unflattened transparency, or an incorrect output intent. The only way to know is to run a preflight check.

Is Canva good for print design?

Canva is useful for quick, disposable designs. It is not a print production tool. It has no CMYK working space, no soft-proofing, and no control over the conversion. For anything that must match a brand colour, use a professional tool.

The sentence that cannot be copied is this: “A file that is 300 PPI is sufficient for a continuous-tone print at actual size, but if you enlarge it to 200%, the effective PPI drops to 150, and the print will look soft.” That concrete number, 300 PPI dropping to 150 at 200% enlargement, is the kind of operational detail that a generic page will not have. It is the difference between a designer who guesses and a designer who knows.