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

Similar Messages

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?

Save to Web Color Shift with sRGB Working Space

I'm having a problem a lot of other people have, which is the color shift when saving to web or viewing my work in a web browser.
The solutions I've found in the past have been to simply make sure my working color space in Photoshop is sRGB and that my files are being built with that profile as well. I'm under the impression that sRGB is essentially the same color space as is used in a web browser, and therefore my work should look identical in both Photoshop and a web browser.
So why am I still getting a color shift? Everything in a browser appears darker and with more contrast, as though the colors have been pumped up a bit.
My monitor color has been calibrated with a Spyder 3 Pro and I'm using the profile it created for me as my OS X color profile. Thinking the shift may be related to my monitor profile, I tried switching to other profiles, but I still get a color shift in every single one.
Any ideas? Thanks!

sRGB based on capabilities and trends of development (circa late 1990s) for commodities CRT computers displays. sRGB per se has nothing to do with web browsers. The reason it has become associated with the web is the assumption that most web users are looking at content using a commodities CRT monitor using Microsoft Windows.
It should be obvious that the use of a standard of some kind for display is better than none if there is to be any trend towards predictability of image display. Today, in commodities computing, that standard is sRGB: neutral color where R=B=G, and a gray ramp and primaries typical of the electron gun and phosphors used in CRT displays perfected for use in color television. It just so happens that this coding is rather will suited to get good value out of a minimum numbers of bits for color representation (e.g, 8 bits per channel 24 bit color)
Web browsers in and of themselves don't have a color space. A few, such as Mac Safari, use the ICC color management capabilities of the system, and these display compensated color just like Photoshop does: if the image is tagged with an ICC profile, compensation will be applied in the browser window. But for the vast majority of computers and users, browser color is monitor color, and it's easier and most reliable for designers to just assume sRGB because it's the space that's the best approximation of the internet at large.
You work usually will not look identical in Photoshop and a web browser (assuming that the browser does not or cannot do color management) because Photoshop is always soft proofing the working space onto the display. It is this quality that leads you to see parity between photoshop and the web browser when you choose you monitor profile as the working space: the soft proof produces no compensation.
But while this fixes up your local experience it is -not- the solution because this projects your monitor characteristics into the image when you share it. For example, if your monitor has a lumpy non-linear tonal response and you correct image shadows or saturation for a certain look the image data will code your monitor response as well as your intentions for the image appearance. Others will see the combination of your correction for your monitor response mapped over their monitor response, in fact they will see an inversion of your monitor's response coded in the image, and to whatever extent your monitor deviates from the norm is the extent which at the very least others displays of the images you correct will deviate from your intentioned look.
The answer to your problem--and this may surprise you--is to tolerate and appreciate the difference in display between photoshop's rendition of color and your browsers. Photoshop is showing your image more truly--within certain significant local limits--in terms of your working space than your web browser. By choosing an appropriate working space, and for the web it should be sRGB, and by profiling your monitor as you have, you are ensuring your images are normalized to current standards for web presentation. Others may still see crap, but it's most likely their problem and if they don't want to do anything about it that's their problem, not yours.
There are a wide variety of reasons why a properly calibrated monitor will not match a working space which the soft proof cannot overcome. A monitor gamut larger than sRGB is not one of them. Photoshop will properly display sRGB data if the display profile properly characterizes the larger gamut display. This leads to questions about the effects of monitor quality on workflow. Maybe the most important of these is "How do I know my Spyder has properly calibrated my display!!!" But this is a topic for a whole 'nother thread.
Where I run into trouble is when trying to make visual color comparisons during web design between my photoshop website mockup and a published site. I get confused and try to make color picker style matches by eye rather than by the numbers because I forget my web browser is not color managed. Sometimes I forget how all the parts play together and get confused and disoriented, then I make compounding mistakes. Then I start blaming my tools. Pity me.

TS4435 Apple's temporary fix to drag each picture in iPhoto is not really a solution for a big pic file. Better to use the save all feature and save to a temporary place before importing it to iPhoto.

Apple's temporary fix to drag each picture in iPhoto is not really a solution for a big pic file. Better to use the save all feature and save to a temporary place before importing it to iPhoto.

Can you explain why the image size matters when dragging and dropping into iPhoto?

Im completely new to Mac. Im swapping my windows laptop for macbook pro and looking for network storage solution which the Time Capsule seems to do. Is it possible to use this as NAS for my desktop Windows PC - windows 7

Im completely new to Mac. Im swapping my windows laptop for macbook pro and looking for network storage solution which the Time Capsule seems to do. Is it possible to use this as NAS for my desktop Windows PC - windows 7

Broadly speaking I want some sort of network storage( wireless or through my existing wifi router) that I can access files for both my windows PC and Macbook and also to access files to my iPad/ iPhone. Some sort of backup and sychronisation so that I can access certain files remotely.
Buy a real NAS.. synology or QNAP are the standard... although companies like Netgear and Western Digital and Seagate make them as well.
There is no problem sharing between Mac and PC now.. you do not even need a NAS to do that.. you simply share the hard disk directly. Mac talk SMB.. everything talks SMB nowadays.. so it is easy.
ipad and iphone are not designed to use NAS.. they are designed to backup only to the cloud or itunes.. but you can load an app like file browser if you want.
http://www.stratospherix.com/products/filebrowser/
Remote access to the Apple TC is somewhere between difficult, to impossible from a PC.. Apple use BTMM and iCloud but the service is not offered to PC.
A real NAS will offer HTTPS or SFTP or several other methods.. that both Mac and PC can use.
You simply plug it into the current wireless router.. it is a network device and assessable over the network. It is not necessary to buy another router.. in fact that is a waste.

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?

The save for the web function has stopped working in my copy of photoshop elements 12. I get this message, " The operation could not be completed. The system cannot find the path specified" Resetting preferences did not fix.

The save for the web function has stopped working in my copy of photoshop elements 12. I get this message, “ The operation could not be completed. The system cannot find the path specified” Resetting preferences did not fix.

my os is windows 7. elements 12 worked fine for many months then save for the web stopped working

Is the PNG generated by the "Save As" option the same as the png-24 from the "Save for Web" option?

It would speed up my workflow if I could go through the save for web option rather than the save as. Are these files the same?

No, SaveAs includes more metadata, while SaveForWeb makes the metadata optional.

When I upload my images to the web they are not as vibrant. I am using the Save for the Web feature.

When I upload my images to the wed they are not as vibrant. I am using the Save for the web feature and my sRGB is checked. I dont know what else to do. HELP!

We really need to see what you're seeing.
Can you post links to before and after?

Labview 7.1 crashes windows XP when using VI's saved with the 'Save for Previous Version' option available in Labview 8

I am trying to work with a series of vi's developed in Labview 8 in Labview 7.1. The code was saved with the 'Save for Previous Version' option available in Labview 8. When trying to use the code in LV7.1 my entire Windows XP system locks up (cursor freezes). Are there any ideas what's going on and how to fix this?
Thanks for your help!
Mike

I have seen some problems with the save for previous option in the past. Instead of saving the entire hierarchy, try seperating the code into several different pieces and saving each piece individually. Then, see if you can open the different pieces in 7.1.
If that doesn't help, you should post some more details, like when exactly does it lock up, does it have things like DLL calls, and maybe attach the code.
Try to take over the world!

The Wifi storage options are interesting but it seems they only allow to read files from the device on the iPad but not transfer files to the storage device via WiFi. I'm looking for a possibility to use the iPad for photography while traveling, without

the Wifi storage options are interesting but it seems they only allow to read files from the device on the iPad but not transfer files to the storage device via WiFi.
I'm looking for a possibility to use the iPad for photography while traveling, without the access to a computer.
Shooting photo's in RAW format crates pretty big files that will fill up the iPad's memory pretty fast if you shoot a lot during a (let's say) month long trip.
my idea was to use load the photo's to the iPad so i could view them and sort out any bad ones. then copy them over to the storage device so i can continue using my CF cards for shooting. I have an image thank for copying the photo's directly to the HDD but it would be so sweet to be able to check them on the iPad before hand.
any suggestions?

Check out pogo plug device, it allows you to upload camera roll via wifi.

How can I change the "Save as Web..." default behaviour?

In CS6 Adobe re-programmed the "Save as Web..." dialog. Upon exporting slices it puts all graphics in a sub-folder called "images" (in the German version "Bilder"). I'm pretty sure, even in the German part of the world no-one would want to have images go in a folder called "Bilder", most use "images" or "img".
But how about not forcing me to put the pictures in a pre-named folder and have me select where I want them to be saved? It's very tedious to have to move graphic files manually upon every change and re-save...
Is there an option to disable the "create folder" option like there used to be until CS5.5?
Any help appreciated!

Well, that's just the option I wished for - but only Adobe know why they decided to remove this menu item in CS 6... Pay your dues and upgrade for a lot of money to the newest version - and be punished for it.
Here's how the menu looks in CS 6:

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.

HT204053 i have an apple id on my ipod & another for my macbook & iphone. how do i change the id for my ipod to match the one for my macbook & iphone?

i have an apple id on my ipod & another for my macbook & iphone. how do i change the id for my ipod to match the one for my macbook & iphone?

To change the ID:
For iMessage, go to Settings>Messages>Send & Receive (Receive At in iOS 5), tap the ID sign out, sign back in using the other ID.
For FaceTime, do the same thing in Settings>Facetime.
For Purchasing, do this in Settings>iTunes & App Stores (Settings>Store in iOS 5).
For iCloud, you'll have to delete the account, create a new account with the other ID, and migrate your data to the new account. Before deleting the account, if you have any photos in photo stream that are not in your camera roll or backed up somewhere else save these to your camera roll or you will lose them. To do this, open the photo stream album in the thumbnail view, tap Edit, tap all the photos you want to save, tap Share, then tap Save to Camera Roll. Once this is done, go to Settings>iCloud, scroll to the bottom and tap Delete Account. When prompted about what to do with the iCloud data, be sure to select Keep On iPod. Next, set up a new iCloud account using a different Apple ID (if you don't have one, tap Get a Free Apple ID at the bottom). Then turn iCloud data syncing for contacts, etc. back to On, and when prompted about merging with iCloud, choose Merge. This will upload the data to the new account.

How to Restrict printing the document using IRM for a Single Document?Allow printing for some documents and restrict the printing for particular documents in same document library?

Can we able to Configure the IRM in Document Level in SharePoint Document libraries?
The document library contains multiple document sets , Can we restrict the printing according to document sets? Allow printing for some documents and restrict the printing for particular documents in same document library
Is this possible?Please suggest.

Yes, that can be done. But note that all administrators will have the same right to print, so you need to make sure the users are not administrators. You can include a macro to disable printing, but if the users disable macro, they can print the documents.
Hence, there is no foolproof way to prevent printing documents. If you still need a foolproof security, PDF format provides password based security (viewing doesn't require a password) that can be implemented to prevent the document from printing,
which doesn't require any special scripts and is tough.
You can have a look at the following links:
http://msdn.microsoft.com/en-us/library/office/ms458245(v=office.14).aspx
http://msgroups.net/microsoft.public.word.docmanagement/prevent-printing-of-docum/91353
http://www.go4sharepoint.com/Forum/prevent-printing-saving-documents-10150.aspx
The following link explains about the security features in PDF. This is for information purpose only and not for promotion of any products:
http://www.pdflib.com/knowledge-base/pdf-security/
Balaji Kundalam

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

Similar Messages

Maybe you are looking for