A client calls, upset: "I sent a file with a beautiful shadow under the logo, and the proof shows nothing." We check the file - the shadow is there, it looks perfect in Photoshop, a layer in Multiply mode, 60% opacity. We open the PDF in Acrobat - no shadow. Or it is there, but in a completely different shade. This is one of those situations that takes longer to explain than it does to actually fix the file, because the problem is not in what the designer did, but in how PDF handles transparency in general.
What transparency in PDF is and why it causes problems at all
Transparency in PDF is any element that is not 100% opaque - a shadow, a glow, a layer with reduced opacity, a blend mode other than Normal, an object with a mask. For a long time, the PDF format did not natively support transparency at all. The transparency model specification only appeared in PDF 1.4 (Acrobat 5, year 2001), and since then printing RIPs - software controlling imagesetters and presses - have had to learn to interpret it.
The problem is that some older or simpler RIP engines do not understand transparency as such - they can only handle flat, opaque CMYK objects. That is why, during export or file processing, a process called transparency flattening occurs. The software takes all the transparent layers, calculates the final effect, and converts it into ordinary, flat shapes filled with the appropriate color. Sounds harmless. In practice, this is where most things go wrong.
How exactly the effect disappears
Flattening divides the graphic into areas depending on what overlaps with what. Where nothing intersects, a regular vector or image remains. Where layers blend together, the software generates a new, flattened object - often as a rasterized fragment, regardless of whether the rest of the file is vector-based.
And here is the first trap: the quality of this flattening depends on the flattener settings, specifically on the "Raster/Vector Balance" parameter and the raster resolution for blending areas. If these settings are low, or if the file reaches the RIP with old default values, a shadow in Multiply mode can be rasterized at a resolution much lower than the standard 300 dpi we use when preparing raster graphics for print. The result: a subtle shadow turns into a lumpy blob, or, with very low settings, the software simply omits it as visually irrelevant noise.
The second trap concerns the blend modes themselves. Photoshop and Illustrator calculate modes such as Multiply, Overlay, Screen, or Darken in the color space you are working in - often RGB or in a "document blending" mode, which does not always correspond one-to-one with what you will see after conversion to CMYK and flattening. A shadow color that looks deep gray on screen can come out noticeably warmer or cooler after recalculation in a different color engine, sometimes with a visible cast from one of the CMYK channels.
The simplest way to check whether your file will survive flattening: in Acrobat Pro, use the Print Production > Flattener Preview tool. It shows exactly which areas will be rasterized before the file goes to print - not after the fact, once you already have the finished proof in hand.
Why blend modes specifically are the most unreliable
A blend mode tells the software how the color of a pixel on one layer should behave relative to the color of the pixel underneath - whether to multiply it, lighten it, subtract it, compare it. This is math operating on channel values. The problem is that this math is defined differently across different color models and differently across different applications.
Illustrator and InDesign support blend modes according to the PDF transparency model specification, which is reasonably predictable. Photoshop can be more temperamental, especially when Lab mode, knockout layers, isolated layers, or groups with reduced opacity at both the group level and the level of individual layers inside come into play. Stacking several of these mechanisms at once is exactly the scenario where one person sees the effect in Photoshop, another sees something different in Acrobat, and a third - the printing press - gets version number three, because the RIP interprets it yet differently again.
A separate issue concerns the Hard Mix or Difference modes, which can generate colors outside the typical CMYK range. After conversion and flattening, these values are clipped to the nearest possible color in the target color space, which sometimes produces a completely different shade than the one visible on screen in RGB mode.
Raster effects over vectors cause the most damage: If you place a shadow or glow in a blend mode directly over a large vector shape or over text, flattening may rasterize the entire area, not just the effect itself. A large, sharp heading suddenly loses edge sharpness, because the whole fragment of the page has been converted into a bitmap at insufficient resolution.
A concrete scenario: a catalog cover with a shadow and a glow
Let us take a real-life example. A catalog cover design - a product photo on a white background, a soft shadow underneath in Multiply mode at 40% opacity, and above the company name a subtle gold glow in Screen mode. The file looks great in Photoshop, the designer exports a PDF, and sends it to print.
Here is what happens along the way: the shadow in Multiply mode overlaps both the product photo (a raster image, already in CMYK) and the white margin of the page (a vector object, flat color). The flattener splits this area into two parts - where the shadow overlaps the photo, it simply recalculates pixel values, since both elements are already raster. But where the shadow overlaps the white vector margin, it has to create a brand-new raster object on the fly. If the resolution of this newly created raster is set low (which happens with default export profiles tuned for speed, not quality), the edge of the shadow on the margin comes out jagged, while the same edge on the photo stays smooth. The result: a visible seam exactly where the shadow transitions from the photo to the background.
The glow in Screen mode has a different problem - in CMYK, Screen mode behaves differently than in RGB, because in CMYK "lighter" means less ink, and the screen algorithm was originally designed with light in mind (RGB), not ink (CMYK). After conversion, a gold glow that subtly highlighted a letter on screen can come out barely noticeable in print, or the opposite - too contrasty.
The most common mistakes we see in files from clients
By far the most common mistake is sending a PDF file without first checking the flattening preview - exactly what we described above. The designer trusts what they see in their own software and assumes the print shop will see the same thing. Meanwhile, every conversion stage - from RGB to CMYK, from layers to a flat PDF, from vector partially into raster - is another opportunity for something to turn out differently than it did on screen.
The second mistake is leaving transparent effects in RGB mode and relying on automatic conversion during export. The software will indeed recalculate the colors, but not always in a way that captures your intent - especially with blend modes that are heavily dependent on the color model.
The third, less obvious mistake: too many nested levels of groups with different opacities and modes at the same time. The more complex the layer structure, the harder it is to predict the flattening result, because the flattener has to resolve the order and interaction of all these settings at once. A simpler file is a more predictable file.
The fourth mistake, which does not concern transparency itself but likes to pair up with it: raster image resolution below standard. If the photo underneath a multiply effect is 150 dpi instead of the proper 300 dpi at 1:1 scale, then after flattening you will still get a soft, blurred edge - regardless of how well the blend mode itself was handled.
How to prepare a file so the effect actually makes it to print
Rule number one: work directly in CMYK if you know the project is headed for offset printing. Do not design in RGB "because it looks nicer," counting on the conversion at the end to sort everything out. Blend modes calculated directly in the target color space give a result closer to what you will see on the proof.
Rule number two: before the final export, check the flattening preview. In Illustrator and Acrobat Pro you will find the Flattener Preview option - it shows, in color, which areas will be rasterized and which will remain vector. If you see that a large, important fragment of the project (for example, the entire cover) turns into one giant raster, that is a signal to simplify the layer structure or raise the flattener quality settings.
Rule number three: wherever possible, flatten transparency manually and deliberately, instead of leaving it to the automatic process during export. In Illustrator you can select objects and use Object > Flatten Transparency with the quality setting at maximum and a high resolution for raster areas. This lets you see the final effect before the file even reaches the print shop, and you can correct anything that looks different than you intended.
Rule number four: export to PDF/X-1a or a well-prepared composite PDF. The PDF/X-1a standard requires that all colors already be in CMYK (or spot colors) and that transparency be flattened beforehand according to defined parameters - which eliminates exactly the kind of uncertainty we have been discussing throughout this article.
- Project with transparent effects prepared directly in CMYK, not in RGB
- Flattener Preview checked before final export
- Photos under blend effects at 300 dpi resolution at 1:1 scale
- Limited number of nested groups with different modes and opacities at once
- File exported as PDF/X-1a or a correctly prepared composite PDF
- Visual comparison of the effect in the design application and in Acrobat before sending
Looking for a printer? We handle artwork file requirements end to end — from file checks to safe delivery.