Patrick Corless added a comment - 19/Jul/10 2:48 PM After quite a bit of debugging it turns out that this is a colour space issue and not an image issue. I was chasing the PNG predictor value as a possible issue but then got side tracked and took a look at the ColourSpace. The image had a seperation colour space and after reviewing the specification and code we where correctly handling things. For screen rendering we shouldn't be trying to resolve the named colour value and instead rely on the alternative and tint transform. Screen rendering is considered an additive colour model where printing can be subtractive assuming your printing api has control over this sort of thing which we don't in Java. By Changing the colour space logic the PDF in question renders correctly. I also have several other examples where the colour is now being calculated rather then being derived by a named and the resulting colour match is greatly improved.