Skip to main content
Participating Frequently
October 31, 2007
Question

Photoshop CS3 color management "Save for Web" problem

  • October 31, 2007
  • 680 replies
  • 62136 views
This problem is getting the best of me.......

After spending 3 full days researching this problem, I am no closer to finding an answer than when I started. I still cannot produce a usable image through the "Save for Web" feature of Photoshop CS3. I have read web page after web page of "Tips, Tricks and Recommendations" from dozens of experts, some from this forum, and still I have no solution... I am exhausted and frustrated to say the least. Here's the simple facts that I know at this point.

I have a web design project that was started in PS CS1. All artwork was created in photoshop and exported to JPG format by using "Save for Web". Every image displays correctly in these browsers (Safari, Camino, FireFox and even Internet Explorer on a PC).

I have recently upgraded to PS CS3 and now cannot get any newly JPG'd image to display correctly. My original settings in CS1 were of no concern to me at the time, because it always just worked, and so I do not know what they were. I have opened a few of my previous images in CS3 and found that sRGB-2.1 displays them more or less accurately. I am using sRGB 2.1 working space. Upon openning these previous image files, I get the "Missing Profile" message and of course I select "Leave as is. Do Not color manage". CS3 assumes sRGB-2.1 working space, opens the file, and all is well.

The problem is when I go to "Save for Web", the saturation goes up, and the colors change. The opposite of what most people are reporting. Here's another important point... new artwork created in CS3 does exactly the same thing, so it's not because of the older CS1 files.

I have tried every combination of "uncompensated color", "Convert to sRGB", "ICC Profile", etc. while saving. I have Converted to sRGB before saving, and my monitor is calibrated correctly.
I have tried setting the "Save for Web" page on 2-up and the "original" on the left is already color shifted before I even hit the "Save" button. Of course, the "Optimized" image on the right looks perfect because I am cheating by selecting the "Use Document Color Profile" item. Why do they even have this feature if doesn't work, or misleads you?

Does anyone have any ideas what could be happening here? Why is this all so screwed up?
CS1 worked fine out of the box.

Final note: I do have an image file I could send along that demonstrates how it is possible to display an image exactly the same in all 4 of the browsers I mentioned with no color differences. It is untagged RGB and somehow it just works.

I am very frustrated with all of this and any suggestions will be appreciated

Thanks,
Pete
    This topic has been closed for replies.

    680 replies

    Participating Frequently
    November 7, 2007
    >I like to refer to people who hand me untagged files as morons who deserve to be beaten with a baseball bat.

    Then lobby Adobe to F-ing listen to me and change the retarded way we manage color.
    Participating Frequently
    November 7, 2007
    OK... I guess that's the best way then... profiles, death and taxes... I like that.
    Ramón G Castañeda
    Inspiring
    November 7, 2007
    I agree with Mike: keep the embedded profile.

    I like to refer to people who hand me untagged files as morons who deserve to be beaten with a baseball bat.
    Ramón G Castañeda
    Inspiring
    November 7, 2007
    >since most viewers are on PC's

    with uncalibrated monitors.

    No matter what you choose, Windows Color, sRGB, Monitor RGB, you still have no idea what your image will look like to any individual viewer.

    Only viewers using Safari and an accurately profiled monitor will see exactly what you see if you embed the profile in your web images, which, incidentally adds only about 4 KB to the size of your file. Otherwise, don't sweat it.
    Participating Frequently
    November 7, 2007
    At this time - my opinion is to convert to sRGB because it's a linear color space. Monitors are not such animal and considering that a majority of web images are used for multi-purpose, the file will represent what you intended to hopefully more people then less. People should stop discarding profiles in RGB images PERIOD. aka this mess of a thread.

    Look at the image in sRGB "tagged image". Set your working space to sRGB for untagged images. Convert in SFW to sRGB - regardless of what the image's color space is. Embed the profile. Stop paying taxes.
    Participating Frequently
    November 7, 2007
    So, since most viewers are on PC's... we should select Windows Color?
    Ramón G Castañeda
    Inspiring
    November 7, 2007
    >What is the significance of 'Proof Colors' being on or off?

    When it's on, you get a much better idea of what your image will look like in the end on the intended device, which in the case of web images boils down mostly to the viewer's monitor.
    Ramón G Castañeda
    Inspiring
    November 7, 2007
    FWIW, my position is that Proof should be set to whatever your final output device is. For web I would use Monitor RGB (for the gazillion uncalibrated, non-color-managed users that make up 95% or so of web viewers) or sRGB if I'm going to embed the sRGB profile in the file.
    Participating Frequently
    November 7, 2007
    Peter (or anyone else) - Are you then suggesting that Proof Setup be set to sRGB or???

    What is the significance of 'Proof Colors' being on or off?

    Thanks!
    Participating Frequently
    November 7, 2007
    Raven,

    Don't convert to Monitor RGB. Convert to sRGB. You will only end up confusing things more if you use Monitor RGB as an actual working space. I only talked about using it for troubleshooting. You have to understand WHY to use in order to actually do it and not pay for it later.