Is save for web just for posting or for sending, too?

I need to send files with layers, so I won't use Save for web or I'll lose them, I was thinking of a general save as. I heard that save for web translates your file into the web language, now these files will be worked again, and, eventually, posted, but not by myself right now. I am just sending them.
Is save for web recommended all the time you send files to an email, or just for posting?
Sorry I have to go right now but I will be happy to read you tomorrow.

I don't think Jeffrey quite caught this:
margieannejulie wrote:
…now these files will be worked again, and, eventually, posted, but not by myself right now. I am just sending them…
If the images are going to be edited ("worked on"), you should NOT be dealing with JPEGs at all. TIFFs or PSDs will do just fine.
Use a JPEG when the file is in its final destination stage, when no further editing or manipulation is required.
margieannejulie wrote:
…I heard that save for web translates your file into the web language…
That's inaccurate, to put it politely. All Save for Web does is, if you tell it to, remove the embedded color profile, strip all metadata and generate the lightest (weight or size-on-disk wise) possible file. It absolutely does not "translate" anything into anything else, and certainly not "web language" which does not exist in regard to displaying images.
Wo Tai Lao Le
我太老了

Similar Messages

Why is Save to Web greatly increasing my image size?

Hi! I am starting with a 6 inch by 6 inch 600 pixel TIFF image. When I use Save to Web to create a JPEG, it decreases pixels to 72 which is what I want--but the image size of the new file shows as like 20 inches by 20 inches. I know that the original is untouched. Should I be ignoring the image size here? Here is my concern. I want the viewer to see the complete image. Is Save to Web truly jumping up the image size here? If I email myself the image---I do see the whole picture. I am concerned that the new file says 20 inches by 20 inches. Will a recipient be receiving a 20 inch by 20 inch file that might not be viewable on their screen. Hope this makes sense--confusing to me! I have read a few websites that say when using Save to Web just focus on the pixels--not on the image size. Why is image size showing as much bigger than original? Thanks!!!

SaveForWeb is just removing the resolution value (600), and the image loads at the default (72).
Web browsers don't care about resolution, just the number of pixels - which remains the same.

CS3 Save for Web bugs - No answer from Adobe in all forum posts

I just upgraded to Illustrator 13.0.02 and the problem is the same: Slice names and output settings are not remembered/saved like all previous AI versions.
I don't understand why this post was closed: CS3 Save for Web Problems
http://www.adobeforums.com/webx?128@@.3bc41aeb.
and this one: "Save for Web" names of frames vanish
http://www.adobeforums.com/webx/.3bc4cd31/2
It is the same as: AI CS3 - Save for Web & Devises image name problem
http://www.adobeforums.com/webx?128@@.3c057eab
Concerning slice name: It looks like they now have to be saved via drop down menus in order for Illustrator to remember the slice names for export again: "Object - Slice - Slice Options, and then in Save for Web, set the Output Settings for Saving Files"
In my opinion this is incredibly poor UI design. In prior versions of Illustrator, I would save the names in the Save for Web dialog box by simply double clicking the slice frame, and it would remember the names of my slices for export again.
Clicking through drop down menus just to name a slice is inefficient compared to just double clicking a slice frame to name the slice.

This is a bit of an old thread, but I too have recently discovered this problem in working with AI CS3.
I contacted Adobe support with the question. I asked them why it was not possible to select and optimize individual slices in the Save for Web and Devices dialog in CS3, and then maintain those settings after saving the slices or clicking "Done"... even though that very feature was available and working in CS2.
Adobe's answer was, quite simply, that they have ceased any development on CS3, including bug fixes, and that anyone who wants the problem fixes would have to buy CS4 in order to "fix" the problem.
In short, they are quite aware of the problem, but would rather have us pay for a new product in order to have it fixed, than to pay a programmer to spend a few hours or a few days in tracking down the problem and getting it sorted out. This is their short-term solution to a long-term problem.
There is a workaround to the slice naming, as you have found - name the slices from the Object - Slice - Slice Options menu. It's a royal PITA, I know, but it does maintain the slice name settings.
However, there is no real workaround to save the optimization and output settings (such as color tables and JPEG/GIF/PNG settings) for each slice. It's a completely broken feature, or in Adobe's own words, "a problem". A big fat bug. Let us not mince words here - it is technical and corporate incompetency. Technical incompetency can be excused - publishing a new build will fix the problem. But corporate incompetency, which tells the programmers that they don't need to fix the problem for "marketing" reasons, is totally inexcusable.
It doesn't cost Adobe anything to just shelve a problem... at least, not now. But I refuse to buy Illustrator CS4 as a result, because I don't want to give in to their ineptitude and lack of attention to the customer in this case. Which costs them more now, to pay the programmer to fix the error and then publish a new build on their web server... or to tell the customer that the problem won't be fixed and to buy the newest version? You do the math. Read 'em and weep.
Makes you want to migrate to Fireworks for web comp design, doesn't it. At least Illustrator has an excuse - it's an all-purpose vector graphics application, not specifically a web comp design app. If this were Fireworks, on the other hand, I think that there would be oodles of furious programmers screaming colorful obscenities at Adobe's front door.
I really like Illustrator for what it does, but I'm not using CS3 for any more web comps after this.
Jeff Chapman

Just downloaded CS6 and got Save For Web error

I just downloaded Photoshop CS6 and I made a GIF and saved it then realized it was to big so I saved it again with the Colors as 128 instead of 256 and got a "Could not complete this operation. An unknown error has occured." now I can't Save For Web at all. I deleted the save for web preferences and I'm still getting the same error. I'm using Windows 7 Starter btw

It should work just fine. Perhaps load the 64 bit version?
Also, there are problems with gif and save for web so read this http://feedback.photoshop.com/photoshop_family/topics/cs6_gif_save_for_web_error

How to "Save for web" just the layer effect but not the content area?

I fill the area with white, then add outter glow to the layer. Now I want to "Save for web" the outter glow effect but not the white area. I want the white area to be transparent. If I delete the white area, the layer effect goes away, if I merge the layer with another to flatten (think then I can delete the white middle while keeping the layer effect stay), the layer effect look totally different after flatten.

Set the fill to 0% in the layers panel (not the opacity). Then save for web as a PNG24, with transparency checked.

Save For Web Just Stopped Working

PSE3 on Mac
This'll teach me to stop for lunch !
I was quite happily using the feature this morning,but after lunch
it too had decided to take a break. I reset preferences and repaired permissions but it still refuses to cooperate. The error message I get
is ' could not complete the operation the file was not found ' which is
very strange as I'd already saved about 20 images for web from the same
folder this morning.
Any suggestions ?

Spooky !!
Save For Web has decided to return from lunch with no further
intervention on my part - I had carried on working on files throughout
the time this feature wasn't working
Now,although I don't want a cure,I'd be interested in any explanations
as to why my normally very stable PSE3 has decided to play up.

Can i batch process/save for web various images to the same exact KB size? not just the quality perc

Hello,
I have a batch of 500 jpg images all in different sizes 732 KB, 634 KB, 664 KB etc... I need to compress / save for web down to 130 KB the entire batch.
I've managed to create an action which compresses them lower than 130 KB at different sizes depending on how light or dark the images are, but still not to an exact number. Is there a way to create such an action or script?
I'm working off of Photoshop CS5, iMac 10.5.8
thank you for time,

Thank you for your response eartho, I have a client which needs them at that size for their site.
I figure i'll compress them as close as possible to 130 KB, but when I automate the batch resize certain images don't fall under 130 KB which is forcing me to go through the entire batch and look for those, and thus compress them individually.

Possible bug in Save for Web -- Color Changes!

Hi,
I'm new to CS3 and also new on the Mac (and also to thiis forum). So I might be overlooking something but I am an experienced user user of Photoshop 7 on a pc. Never had a problem like this.
When I try to save an image with the color #c51076 as a gif using the Save for Web function I get a totally different color. Much lighter!!! I don't get it. I can't get the color I want.
I jjustt found out that iit also messes up webcolors: it swaps one webolorr for another.
Does anyone know a solution?
Thanks!

Thanks for sharing. First let me say I think it's really great that you have shared all the documentation about these color issues. I read your page before posting here, and I tried each of the suggested solutions, and wasn't able to fix it. Maybe it is a problem with the Mac OS and the way it displays images non-color managed images. But it's not like all the images I view on Firefox are dull-just the ones I've edited, because they appeared different in CS3.
As I mentioned above, I am not the only one who is having this problem, despite trying all of the fixes suggested (see the link to forum thread posted above). I think my next step is to schlep my MacBook over to the Mac store and see if they can verify my monitor profile. But if anyone else has any suggestions, please let me know!
Emily

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 for Web isn't using the correct size of artboard

I've been using CS5 for about 5 days now and have just run into this problem.
My artboard is 800x600 px. I have 6 layers of an animation I need to export as pngs so I can manipulate them in Imageready (yes, I still use it.)
I Save for Web, export as CSS layers, original size is 800x600 px, new size is 800x600 px (I don't touch those settings), art optimized and clip to artboard is checked.
But when I Save and check my files, not only are they 550x90 (the size of the art on the artboard) but they're cut off on the right side. It's like Illustrator is saving them as actual size, registared to 0,0 (top right corner) of my artboard.
I need to save my layers using save for web so I can drag them into other animated files in Imageready. I need them at 800x600 px because that's the size of my final art and it's easy to center a lot of layers if they're all the same size.
I can post image files if my question doesn't make sense.

UPDATE:
I've been experimenting. My artboard is 800x600 px. I have 2 layers. My artwork is 900x700 on both layers.
I Save For Web with Clip to Artboard checked.
I save a jpeg and my file is 800x600.
I save a png and my file is 800x600.
I save as png and check Export As CSS Layers and my 2 layers are 900x700. This ONLY seems to happen with the Export as CSS Layers checked.
Also, I use File->Export->PNG and check Use Artboards and my file is 800x600.
I use File->Export->JPEG and check Use Artboards and my file is 800x600.
I use File->Export->BMP but I can't check Use Artboards, it's greyed out and uncheckable. Huh? I need to export my image as a BMP at 800x600.
I don't understand what I'm missing here.

Save for web 72ppi

running CS5 on a 64bit win 7 PC....
When I use the 'save for web' option and enable the 'include all the metadata info'
the saved image (jpeg) is not at 72ppi, which is clearly best for the web as that is apparently the idea resolution for our screens.
instead it saves it at 300ppi
(please no debate on 72ppi v's XXX ppi , there are enough posts on that as it is).
but if you disable the 'include metadata option' then the image saves as a 72ppi jpg as i require.
Does anyone have an answer to this.
there is no reason why an image cannot be saved at 72ppi and have metadata.
one assumes that the whole 'save for web' feature is about optimizing the image for that very reason.
this sounds like a bug to me ?

Sorry to disagree with some of the above...
there clearly are some useful facts listed.
but you have to ask with ref to the above, why did adobe bother with the 'save to web' option
if most of you seem to imply it really doesn't make any difference on your uploads.
well it does, i have a few photosharing websites
and some display the images very well others do not, they can look quite blurred.
i've been putting this down to resolution. (i've tried using the photo sites options of not adjusting file size
as clearly im aware their own scaling systems could alter the photo's appearance.
so what have i found.
well reducing the image to 72ppi and say 1000 pixels wide looks good online
as apposed to uploading the original which not only is a larger files size it also has different parameters.
you need a different approach to sharpening for online images than for print images.
hence back to the original, adobe implented this feature for a reason, we can all goto edit, image size in PS,easy
but adobe added this feature where you can choose 'bi-cubic sharpening etc etc.....
and this is why i want my metadata kept in place and 72ppi or 96 as stated above. which is why i still believe it to be a bug.
also this also acts as image license protector as i doubt 72ppi (1000 pixels wide) images would be much use in print for picture thiefs.
(72ppi is just a starting base point as i understand this goes back to CRT monitors, other displays can go higher though i doubt 300ppi)

Save for Web keyboard key stroke not worky

I'd swear I've asked or seen this discussed in these forums...but I can find no thread, even when I search for my own screen name. At any rate, I think it also happened to me back in version 6. I'm now in version 8 on a Mac.
The symptoms are the same as the last time this happened. The "shortcut" key strokes (on the Mac) are command + shift + option + S (probably use 'alt' instead of 'option and "control' instead of 'command' on Windows?). This will usually show a brief darkening of the File menu, but nothing else happens. Until...the same keys are pressed again! Of course, mousing to the menu item works fine, but I have managed to avoid carpal tunnel syndrome and still press all four keys with one hand! Sometimes I get my cat to help...
Since Adobe is gracious enough to provide about three dozen various pref files, it should be a breeze to start archiving them and deleting the originals. NOT! However, in my searching for the likely pref file, I have discovered that the "Adobe Save For Web 8.0 Prefs" file seems to be AWOL on my System! I have over a dozen backups of that file in Time Machine, despite the fact that they all show exactly the same Modified date, which would normally be the only reason TM would save another copy of the file. This may also indicate why the settings for the Save For Web dialog never remember the last used settings; the file thinks it is getting written to but never changes its Modified date even thought that 'state' is obviously recognized by the OS. But that's all beside the point and I digress...
SO...does anyone remember the 'trick' for getting PSE 6/8 to remember the Save For Web keystrokes the first time they are used, instead of waiting for 'verification?'
Thanks!

Barbara B. wrote:
Uh oh. You should have had an uninstaller in the PSE 8 folder in applications. I'm afraid you may have set yourself up for bigger problems by doing it this way. You may well find that you will eventually need to download and run the CS4 cleanscript to get straightened back out again.
You may be correct, but I've had no other problems after all the different un-install methods. The only pieces that are hard to find are those that Adobe chooses to hide deep in System areas. I suppose since they were one of the first Mac developers, they think they have special capabilities to put stuff any and every where they want. As well as special dispensation to do things anti-Mac ways. I can't claim to be a power-user, but I have never, ever felt the need to purchase/use any special "uninstaller" app. And I can't think of another app I've ever owned that even needed an "uninstaller" for it. That includes Canvas, php, Apache setups, etc. Frankly, and this is simply my opinion and obviously of little importance to absolutely no one else, the way Adobe does things seems to be extremely un-organized, not-well-thought-out and downright non-Mac. The only thing even marginally close to their confusing instal/uninstall process is Stanford's Folding@home set up. It sometimes requires a few Terminal commands...
I will perform a search for that CS4 "clearscript" thing, however. Thanks!
Even the response I got from my Support post assured me that...
reset/restore the Preferences, click Yes or OK . Now try to use the "Save for Web" keyboard command by pressing "Alt+Shift+Crtl+S". I am positive that after following the above steps your issue will be resolved .
OK, I get the rest/restore step. but what does the "alt+shift+Crtl+S" have to do with anything? It certainly is not the keyboard short cut for the Mac version of Elements. Perhaps the chap didn't notice the details in my message or the hardware/software information that came with my request for help. I find it strange that somehow the language differences cause the tech's positive belief that his steps would fix the issue that he also presents:
If the issue is still not resolved then please send us the below mentioned information so that we can provide you with the best possible resolution:-
1. Have you recently made any changes to your computer?
2. Are you logged in as administrator ?
3. Does the issue persist on another system or another user account ?
4. Do you get any error message while pressing the combination of "Alt+Shift+Crtl+S" keys on the keyboard? if yes then send us the screen shot of the error message that you are getting
5. Please provide the exact system Configuration with details along with the Versions.
Every single one of those questions was included with the initial message I sent.
I suspect that the problem is, indeed, in my System, somewhere. I installed Elements on my wife's MBP and it operated normally, even the command+option(alt)+shift+S command. So, when I get some time this week, I'll start up in Safe mode and see if that helps. If not, I'll start removing third-party Pref Panels and apps, a few at a time. If none of that helps, I may try retrieving files from Time Machine. As a last effort, I can always do an Archive and (re)Install of Snow Leopard. I'm just not sure it's worth all the effort to get one measly short cut... The only thing I know for sure is that I will not be seeking any more help from Adobe's "tech support." Why bother, they don't/can't even read the messages their own system sends!

Save for web 72ppi (part 2)

Hi all, the old post was http://forums.adobe.com/thread/662903
The Include Metadata option in Save For Web... saves the info found in File > File Info with the image. No resolution data.
This has zero effect on the image. Image resolution only affects printing the image. For viewing on the web, all that matters is height x depth measured in pixels.
Save For Web strips all resolution data from the file. The file simply doesn't have a resolution out of SFW.
The 72 ppi or whatever appears when you reopen into Photoshop, because Photoshop needs some resolution figure and therefore assigns 72 purely as a default value.
I have to save some images for my DPS workflow with 72ppi and the same also 108ppi.
I save the first using Save for Web and i think that is correct.
The problem is the 108ppi output - how is the best workflow to this? Can i use Save for Web? I think no!
I understand that Save for Web do not save 72ppi or any other ppi size...

Think what you are quoting is what I have read also. Not sure why they would specify 72 and 108 ppi. That is just the pixels per inch of the display. Perhaps they want a larger image on the website. This could be acomplished by making the pixel size larger, without resampling. At least that is the way I see it, but could be wrong.
Take an image and open image/image size and play with the ppi with resampling off to check this out.

When batching Save for Web, Illustrator also saves copy of .ai file

This question was asked and abonadoned here, so I'm posting because it's also happening to me.
CS4 & CS5 (I tried both), Mac OS 10.6
1. I select the "Save for Web PNG" action, which is part of the default set, and select "Batch."
2. I choose a source folder and choose a destination folder, and check "Override Action 'Save' Commands."
3. Illustrator then performs the Save for Web action, but puts the .png files in the original destination specified in the action. It also puts copies of the .ai files in the destination folder I created and specified in the Batch dialog box.
I want the .png files in my folder, and I don't want copies of the .ai files.
Pulling my hair out on this one, going to lunch. Thanks in advance for any help

Ah, ok. That worked, for the most part. When I used "Folder" as the destination, my jpegs were saved to that folder, but I also got the .ai copies again. Argh. It was only when I chose "Save and Close" as the destination that I got just the jpegs.
So "Save for Web" is actually a type of export, rather than a save. It's confusing, since the action is called "Save for Web…" Plus, the batch works — in the original way I set it up — with a regular Save command.
btw, the top section only goes gray when "Save & Close" is selcted (see screen shot). Thanks for your help.

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

Is save for web just for posting or for sending, too?

Similar Messages

Maybe you are looking for