Activation of "Convert to sRGB" in "Save for Web"

Hello,
I am using a script scaling and exporting my image via "Save for Web and Devices". When I open the menu there's a checkbox called "Convert to sRGB" - I want to activate that checkbox via Script, as then I get the wanted colour results. I already had a look at the guide PDFs, but I didn't found that option, not as part of the export options array, nor generally elsewhere in the PS scripting guide.
So here's my question: how can I activate that checkbox with script?
Thank you
Thomas

I believe the 'ColorSpaceType' of the Export options is what you need.
EDIT: Sorry, I may have misspoken, I was under the impression that was part of the Export Options, but it does not seem to be.

Similar Messages

  • Turn off convert to sRGB in save for web CS4

    Hello,
    In CS3 I had the option of turning this off. In CS4 It's turned on and grayed out so I can't turn it off. See attached picture. Any suggestions are greatly appreciated.
    Thank you. -chris

    I do not know what caused this for you but it is still an option in CS 4 perhaps your setting folder corrupt.
    So it is time to trash your preferences.

  • CS4 Save For Web GIF settings confusion

    Hi,
    I am working on a new website and have run into a problem I just can't seem to solve: my navigation links are made using a GIF and for some reason the background color of the GIF is not matching the background color of the page.
    The test page is here:
    http://www.johnblaustein.com/webtest2/
    Note that nothing in the page is working yet.  If you look closely, you will see that the navigation image is a slightly different color than the background.  Very slight, but different.  (Once I solve this color issue, I will make each link into a separate button with slices.)
    In PS, I have created a file as follows:  new file (72dpi), fill background with the same color I use on the webpage: c4c0b4.  Create new layer and add the type.  The new file is in Adobe RGB, but I convert to sRGB before saving for web (although I don't think that matters).  When I Save For Web, I started with the default GIF settings, but when I got the color mismatch, I tried any number of other settings.  I read a post here that suggested turning off the background layer of the image before Save For Web, but that resulted in the text looking bad.  I've tried different color settings (32, 128), matte settings and other settings with no luck.  Convert to sRBG is always checked.
    I like solving these things on my own, but I struck out on this one.  I am here in the hopes that one of you gurus can tell me what I am doing wrong.
    Thanks very much.
    John

    SUCCESS!
    Curt.... you were correct.  I needed to create the new file in sRGB, not create the file in Adobe 1998 and then convert.
    Here is another test, showing that the text box has completely disappeared:
    http://www.johnblaustein.com/webtest2/nav-srgb-test
    The text box is exactly the same size as in the original page I posted.
    What I did is this:
    Create new file to specified dimensions.  In the New File dialog, for Background Contents, I selected my webpage color, c4c0b4.  I clicked the Advanced arrow and selected sRGB as the color profile.  I added white text, then flattened the image.  In the Save For Web dialog, I clicked the Preset dropdown and selected GIF 128 Dithered and did not change any of those preset settings.  I inserted the new image into a copy of the webpage and you can see that there is absolutely no indication of where the image ends and the page background starts.
    I may not need 128 colors, so I'll play with that, but at least I know where the problem is.
    So... thank you Curt!
    What would we do without these forums?
    John
    By the way... I see your message was cut off in the forum, but the full message came to my email: "I am over my head on this subject. The only thing I noticed is that you are adding the color in AdobeRGB and then converting to sRGB. Will this give a slightly different color than using sRGB for the New Image from the start?"

  • CS6 "Save for Web" "Convert to sRGB" Issues

    Hello,
    I'm aiming to take RAW photo files, edit them in a wide color space, and when posting them to the web, save them as sRGB.
    My workspace is as follows:
    I open RAW files in Photoshop via ACR as 16-bit ProPhoto smart objects.
    When I finish editing them, I use "Save for Web" with the "Convert to sRGB" and "Embed Color Profile" boxes checked.
    Photoshop and Bridge tell me the profile in photos saved as such is sRGB as expected. When I upload to a site like flickr, however, the metadata says the photo is still in ProPhoto. See an example here: http://www.flickr.com/photos/nrbelex/7950202448/meta/in/photostream
    If I use "Convert to Profile" and change it to sRGB, then upload to flickr, the metadata says the photo is in sRGB, as it should be.
    What am I missing here?
    Thanks!

    Without using Flickr, I'm not seeing any problem with any of the color-managed software I have here.
    The ProPhoto test file I prepared, when Save For Web is used, is saved with sRGB numbers and (since I checked the box) has the sRGB IEC61966-2.1 profile embedded in it.
    Photoshop re-opens the file and correctly judges that it has the sRGB IEC61966-2.1 profile.
    A search through the binary data from the file Saved For Web using a text editor turns up a number of references to sRGB IEC61966-2.1, but none to ProPhoto RGB.
    Your first image above, however, has BOTH references to sRGB IEC61966-2.1 and ProPhoto RGB, the latter appearing in a string of text data that looks like:
    <rdf:Description
    rdf:about=""
    xmlns:xmp="http://ns.adobe.com/xap/1.0/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:aux="http://ns.adobe.com/exif/1.0/aux/"
    xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/"
    xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/"
    xmlns:stEvt="http://ns.adobe.com/xap/1.0/sType/ResourceEvent#"
    xmlns:stRef="http://ns.adobe.com/xap/1.0/sType/ResourceRef#"
    xmp:Rating="3"
    xmp:ModifyDate="2012-09-07T12:40:05-05:00"
    xmp:CreateDate="2012-09-06T19:18:56"
    xmp:MetadataDate="2012-09-07T12:40:05-05:00"
    xmp:CreatorTool="Adobe Photoshop CS6 Windows"
    dc:format="image/jpeg"
    aux:SerialNumber="022031001932"
    aux:LensInfo="70/1 200/1 0/0 0/0"
    aux:Lens="EF70-200mm f/2.8L USM"
    aux:LensID="165"
    aux:LensSerialNumber="0000000000"
    aux:ImageNumber="0"
    aux:ApproximateFocusDistance="4294967295/1"
    aux:FlashCompensation="0/1"
    aux:Firmware="1.1.3"
    photoshop:DateCreated="2012-09-06T19:18:56.056"
    photoshop:ColorMode="3"
    photoshop:ICCProfile="ProPhoto RGB"
    xmpMM:DocumentID="xmp.did:0F84D078F91311E19565E271D59D6831"
    xmpMM:OriginalDocumentID="98EDC08C95F6E809F2FB9CADB1F3442D"
    xmpMM:InstanceID="xmp.iid:0F84D077F91311E19565E271D59D6831">
    -Noel

  • Preview options in the "save for web" dialog

    According to the reference, the previews in the "save for web" dialog are there only for showing how the image can be seen on various platforms with different gamma values.
    But, if we open a non-sRGB image (ProPhoto for example) by the "save for web" option, the preview options (other than the "use document profile) in the "save for web" dialog assign sRGB color space to the image even when the "convert to sRGB" option is unchecked ... this causes unrealistic, dull previews for the image.
    What is the reason behind that PS assigns sRGB to the image previews if we uncheck "convert to sRGB" option?

    Basically, how animation works with GIF and Save for Web in PSE is that each layer in your document is a frame of animation. So you see one layer, then the next, and so on. You should not see the contents of the last frame/layer when looking at the current/next frame of the animation.
    Could you post a screen shot of your layers panel and give us a link to the GIF that is coming out of Save for Web?

  • Color management in Save for Web not working

    The Save for Web dialog box in the CS6 Beta is ignoring color profiles, so color is not managed. This has not been a problem in previous versions.

    The saved output is just fine. I was referring to the images in the Save for Web dialogue
    I just checked my settings. CS6 apparently changed my Preview setting from "Use Document Profile" to "Monitor Color." It also changed my Metadata setting. It should not do that!
    Restoring the correct Preview setting solved the color management problem, but ONLY for the Preview image. The Original image is still not color managed.
    I'm on a wide-gamut monitor, so sRGB images come out looking garish if there's no color profile embedded or it's ignored. That's what's happening here with the Original image in Save for Web. I imported an sRGB image with profile embedded, and it looks just fine in Photoshop while editing. Then I went to Save for Web, with the settings Embed Color Profile, Convert to sRGB, and Preview: Use Document Profile. The JPEG preview too looks just fine with these settings, but the Original looks garish, showing a lack of color management. The color in the two views is showing as completely different, though they both represent the same image with the same color profile embedded.
    Going back to CS5, the same image is properly color managed in both Original and Preview. Both images show identical color, as they should.

  • Color difference between PNG and JPG in Save For Web

    I am working on a website and I while building images for the site I am using a mix of png and jpg images. When I "Save for Web" the same source image creates two different color images when I save them as either png or jpg. How do I make sure the images are saving with identical colors in both png and jpg. Thanks

    >My working space is Adobe RGB but I'm not opening the sRGB PNG into Adobe RGB. I am choosing "Leave as is (don't color manage)" this should preserve the PNG's RGB numbers.
    are you certain it is not being converted when you open it?
    The numbers you quoted are the numbers I get if I open an untagged sRGB image into Adobe RGB (assuming Adobe RGB), and then convert to sRGB.
    If I open my sRGB images, either PNG or JPEG, into sRGB, they always match. I've been working on a web site for the past 3 weeks, doing this regularly.
    If you are working in Adobe RGB with sRGB images that are not tagged, you add a level of complexity that requires you make the right decision at every step. You need to open them without conversion, then assign sRGB, to keep working.
    Or just open the images in Firefox 2, which cannot color manage, and see if the sRGB jpeg and the sRGB PNG match. This is the acid test.

  • A different take on the "Save For Web" color shift issue...

    Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
    But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
    Nothing new here.
    Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
    Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
    Anyone know of such a beast?   I would gladly pay for a plug-in that really works and fixes the problem.
    And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
    Anyone got a decent solution for this?

    Sorry, I think I'm being unclear.  This has nothing to do with individual monitor profiles.  In Proof Setup, "Monitor RGB" amounts to turning off ALL color management, and simply letting the monitor do what it will.  It is what the vast majority of web browsers do (even if the operating system provides color management, the browsers don't take advantage of it), so that is what you need to consider for images that will be viewed on a web browser.  If you convert your image to sRGB,  select Monitor RGB in Proof Set up, and turn on Proof Colors, you will see the image as it would appear on a web browser (after you save it as a jpg or use "Save For Web/Devices" to save it as a jpg).   Since almost everyone is running different uncalibrated monitors, there will be lots of variation in how it will look to them, so precise control of the color is unimportant.
    That said, I would expect the color on a calibrated monitor (such as the one I use when editing) to be reasonably close to the colors I am seeing while editing in PS.  To the extent a monitor deviates from "calibrated", those colors will vary, but a good monitor should show good colors.   Unfortunately, this is NOT the case, as my previous post shows.  The colors produced by the steps above are oversaturated and significantly shifted in hue.  There is, to my mind, anyway, no reason for this.  Adobe clearly knows what the mapping is between the colors as it displays them in PS and the un-controlled "Monitor RGB" -- that is, it is the color map they are using during normal editing display.  If they were to reverse-apply that map prior to saving it as a jpg, then the image would appear on a browser on that same (presumably calibrated) monitor very similar to what you set up when editing.  Anyone else viewing the image on a web browser with a calibrated monitor would also see good colors.  To the extent other viewers' monitors are out of calibration, their colors will suck, but there's nothing you can do about that.
    I guess in some sense I AM "asking for a Color-Mamangement-solution for a "non-Color-Management-situation", but specifically I'm asking for PS Color Management to do the best it can for non-Color-Managed situations that we all face every day.
    Does that make more sense?

  • Looking for a better solution to the "Save for web" color shift issue

    Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
    But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
    Nothing new here.
    Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
    Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
    Anyone know of such a beast?   I would gladly pay for a plug-in that really works and fixes the problem.
    And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
    Anyone got a decent solution for this?

    Chris
    I spent all day Googling and doing side by side comparisons of my old and new systems.
    My display is a Dell U2410. It has several presets, including sRGB and Adobe RGB. I've been using sRGB.
    On my OLD system, (Win XP, PsCS2, DwCS4) there seems to be no distinction between color managed and non color managed apps, even on this wide gamut display. I could capture (digital camera) in Adobe RGB, open and edit in PsCS2, save as .psd, convert to CMYK for print, or convert to sRGB for SFW. All images looked identical and they printed and displayed perfectly. I thought this was normal, and seemed logical. This also seems to be the source of my incorrect assumptions. I was trying to get my new machine to behave like my old one.
    So I get this new machine (Windows 7, PsCS5, DwCS5) and now (still in sRGB display mode) all color managed apps appear de-saturated. Non color managed apps are OK. If I switch the display to Adobe RGB, color managed apps are OK, but non color managed apps are way too saturated. From my investigation, I believe this is normal behavior on a wide gamut display. I've tried changing the Control Panel > Display > Screen Resolution > Advanced settings > Color Management options, but to no avail. Either I'm missing something, or Windows 7 is doing color management differently.
    It seems my only option now is to use Adobe RGB display setting for Ps, etc. and switch to sRGB for Dw and non color managed apps. Or, have 2 separate files for print and web. I've Googled 'til my eyes are numb and still not sure I'm getting this. Any enlightenment would be greatly appreciated.
    Finally, I don't see an edit function here, so I can't remove my previous incorrect reply. Moderator, please feel free to do so.
    Thanks

  • Save for Web... and grayscale images

    I noticed a strange behavior when I use "Save for Web and Devices" on scanned BW negatives...
    I import the negatives via the scanner's twain driver in Photoshop as 16bit grayscale images. My grayscale working space is normally set to the default DotGain 20% profile. When I want to show these images on the web, I use "Save for Web and Devices..." and I have selected the convert to sRGB option. For some reason, the "embed color profile" option is disabled (grayed out) when the document is in grayscale mode.
    When I view the the exported image (in a color managed application or browser) it looks too dark and shadow detail is lost. Examining the file info shows that the JPG file is in RGB color space and has the sRGB profile assigned.
    When I convert the image to RGB mode before I do save for web... the exported image will look exactly like it looked in Photoshop. Also, the mode change doesn't cause a change in appearance. Also, after changing to RGB, the "embed color profile" option in save for web... becomes enabled.
    I experimented with other working color spaces and noticed that an image exported from a grayscale image in "GrayGamma 2.2" working color space will display almost like an image that was exported from a grayscale image converted to RGB.
    I would like to understand this behavior and whether it is correct. My assumption would be that a conversion to sRGB during the export should yield the same result like a manual conversion of the image in photoshop but for some reason the results are quite different.
    How can I export my grayscale images to sRGB JPG without having to convert to RGB manually while preserving the tonality from the original image?
    I have attached an image which I hope might illustrate the effect I'm describing. The crop on left hand side looks as expected and is the result of exporting from an image that was converted from grayscale to RGB mode (sRGB working space) before using save for web...
    The image in the middle is the result from converting to GrayGamma 2.2 color space but leaving the image in grayscale mode before saving for web and devices. It is almost identical to the crop on the left. The crop on the right hand side is the result of using save for web and devices from the original image in grayscale mode with the default DotGain 20% profile.
    Thanks
    /lars

    These are my settings. Are they the same in your SFW dialog?

  • Save for web color shift - only on images smaller than 150x150px

    I'm getting a color shift only on small images (150x150px or smaller) when I save for web in Photoshop CC and CS6. That's very weird as it doesn't happen to images larger than 150x150px! That issue happens with images with different measurements as well (e.g. rectangle), the small looks dull and the larger display the right color.
    My Color Settings are set to "Monitor Color". Under save for web I have the following options not ticked: Embed Color Profile and Convert to sRGB. (viget.com/inspire/the-mysterious-save-for-web-color-shift)
    I'm running the OS X 10.8.4 on a macbook pro, I tested that on both, Safari 6.0.5 and FF.
    The squares in the screenshot were saved exatly the same way. The largerer displays the right color #FFCB32, but the smaller displays the color wrong.
    I appreciate your help.
    Cheers
    P

    JPG & PNG = Color Profile "Don't Color Manage this document". Save under save for web I have the following options not ticked: Embed Color Profile and Convert to sRGB. (viget.com/inspire/the-mysterious-save-for-web-color-shift)
    Resizing in photoshop (Image Size), but the color shifts even with cropped image after save for web.

  • Save For Web vs. Resizing vs. File Size vs. PNG

    In playing around with some settings while saving a .png file, I noticed some weird results. For this example, the original image is 300 x 300, but I want the final size to be 200 x 200. I get different results depending on the order I perform the following operations (I never thought the order mattered until now).
    1. start with 300 x 300 image, choose save for web, select png-24, with transparency, white matte, convert to sRGB, change image size to 200 x 200, then save - the file size is 37kb
    2. start with 300 x 300 image, use Photoshop's "image size" to change to 200 x 200, then save for web, etc - the file size is 111kb
    So depending on which step I resize the image, the file size is significantly different - if I resize BEFORE using save for web, the file size is much larger. This is just weird to me, but I always resize AFTER choosing save for web, so that's why I've never caught this until now. In case you ask, while using Photoshop's "image size", all three options are checked at the bottom of that window, so nothing is getting re-sampled or anything like that.
    The only thing I can think of is each of those methods treat pixel data differently when reducing the dimensions. When I overlay both exported .png files on top of each other, I see no difference in pixel quality and/or color shift - so why the big difference in file size? Unsurprisingly, if I just save the file straight to .png, the sharpness is much better, and the file size is 46kb. I did notice when saving for web, the colors become a little more saturated.
    Are all these results typical? I've never really paid much attention to the results when exporting .png's. I always thought the results were lossless (in general).

    Too many variables
    What? There are 2 variables here (variables = scenarios = steps). Only two different operations.
    1. resize the image, THEN use "save for web" = 91kb
    2."save for web", THEN change image size = 157kb
    Hopefully my logic translates here:
    All other settings are the same. I even made sure the .psd was sRGB this time. The specific question was "why does the different workflow order produce such a big difference in file size"?
    In creating a new test file (http://www.shan-dysigns.com/userForums/photoshop/savePNG.zip), I did notice an interesting thing: (I'm including my files in case you want to follow along or test for yourself)
    If I merge all layers BEFORE performing the steps above, the file sizes were relatively closer to one another - 168kb and 157kb (respectively from the 1, 2 list above)
    One thing to note is all the .psd layers are either shapes or text - this whole scenario may be totally different if each layer had rasterized content (actually, it does, by about -20kb).
    The file size in step 1 above didn't jump until it had to consider rastered text/shapes into the calculation. So all this tells me the difference in file size has to do with how each process handles vector data. Maybe when you allow PS to resize the image first, the overall file size is smaller because the vector data gets recalculated???
    I don't know how to properly interpret all these differences, but I do know there is something about PS's operation of resizing the canvas with vector data versus resizing the canvas with rasterized data - this has to be where the difference in file size lies.
    Maybe I've just wasted a bunch of time on the obvious, but I think I learned something here. Now my head hurts and my eyes have popped out of my head.
    So, Chris, I guess there ARE more variables in this situation. My curse is being nosey and wanting to know more technically about PS than most casual designers probably would care about.

  • Colour issue with 'Save for Web' - Photoshop Elements 6 (Mac)

    Cross posted here, but no answer so far. Sorry for cross posting. For me, this is urgent, but I know it's not for anyone else, so apologies for putting 'urgent'.
    http://www.mac-forums.com/forums/images-graphic-design-digital-photography/150670-colour-i ssue-save-web-photoshop-elements-6-a.html#post840419
    This is a similar issue to this:
    Save for web color issue
    Except the user who posted the above was using photoshop cs3, and I'm using Adobe Photoshop Elements 6.
    When I work on a photo, I get it just right, then go to Save for Web, and the original it previews is loads lighter than the orginal I was working on in the first place. See 'Picture 1' attachment.
    I have changed the colour settings on the Save for Web options - I've chosen each one in turn, and none fix the problem.
    There seems to be no similar option in PSE6 to this that fixed it in CS3:
    IN the save for web box there is a small round button with an arrow in it (near the Done button).
    In the list when this button is pressed deselect Convert to sRGB
    I used to use PSE2 on a PC, and never had this problem. I didn't need to mess about with colour profiles or anything similar on the PC. The original was the original, not a washed out version of the original. Why spend ages getting the file just right, only for Save for Web to screw it up?
    Any advice to fix this would be much appreciated.
    Thanks

    Thanks very much for your reply.
    I've uploaded the images here:
    http://jimpix.co.uk/images/Picture 1.jpg
    http://jimpix.co.uk/images/Picture 2.png
    I deleted the prefs. file you suggested, and then opened PSE6.
    I then tried the profile setting you suggested - but it's not an option:
    http://jimpix.co.uk/images/Picture 3.png
    I tried 'remove profile' just in case that worked, but the same effect happens on Save for Web.
    Not sure what to try next!
    Thanks

  • CS3: Having problems creating an Action to "Save for Web"

    Hello All,
      I'm trying to create an Action to convert my psd. files to JPEG's suitable for the web.  I'm using a Mac Pro running CS3.  My workspace is Adobe RGB (1998), all files begin as Canon CR2 RAW, are edited at 16 bits, and then saved as psd.  I created an Action the following way from an open psd. image in Photoshop:
    1) Windows>Actions
    2) Create New Action
    3) Re-named "Save For Web" then clicked Record
    4) Image>Duplicate>OK
    5) Edit>Convert to Profile
    6) Changed Destination Space to sRGB IEC61966-2.1>OK
    7) File>Save As
    8) Format> No JPEG option ??????????  What?
      Everything seemed fine until I reached the Format stage.  I had many choices, but JPEG was not one of them.  Can someone please tell me what I'm doing wrong?  Thank you!
    Mike

    Ramón G Castañeda wrote:
    MJCarnegie wrote:
    It never occured to me that I should convert back to 8-bit before saving, and truthfully I had no idea how to do that anyhow.  I know, what a Newbie, huh?
    Go to the Image menu in Photoshop:
    Image > Mode > 8 bits.   Pretty straight forward and fast.
    MJCarnegie wrote:
      …strange, in Matt's article…
    I'll pass on that.  Generally speaking, I'm not a fan of the Scott Kelby crowd, so I don't follow them regularly.
      Thanks again Ramon, I can't believe I've overlooked the Image>Mode>8 bit path for this long. 
    Cheers,
    Mike

  • Photoshop CS3 color management "Save for Web" problem

    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

    >> First of all... I'm using an Adobe RGB image master... I open it and get the Profile Mismatch Screen... I choose Use Enbedded profile... all looks well. Next I go to Proof Setup > Monitor RGB... again all looks well, no change that I can tell.
    This has further confused the issue on several points, not the least of which version PS you are doing this with?
    >> AdobeRGB> Convert to Profile > Working Space sRGB-2.1... all still looks well... but now, when I go to Proof Setup > Monitor RGB... I see the insane oversaturated look that is driving me nuts.
    That is your strongest clue...it sounds like you have a bad system or bad monitor profile. To rule out the monitor profile: Set sRGB as your monitor profile in System Prefs> Displays> Color.
    >> Adobe RGB image master... I open it and get the Profile Mismatch Screen... I choose Use Enbedded profile... all looks well. Next I go to Proof Setup > Monitor RGB... again all looks well
    That doesn't make sense, stripping an embedded AdobeRGB profile should desaturate the color in Softproof MonitorRGB, especially the reds -- you have something wacky going on there.
    At this point I think you need to review the links and get a grip about how color management and profiles work...
    BTW, forget about setting ColorSync in PS COlor Settings, use Adobe ACE.
    MO,
    I think SFW is fixed under CS3 :) By default it Converts to sRGB and strips the profile.

Maybe you are looking for