Make Save for Web overwrite original file

Hi,
Has anyone come across a way to make the "Save For Web" function overwrite the existing file rather than export a new one.
There are a few workarounds I've found but all involve manually finding the original file and saving over it – which is cumbersome in the system I'm using.
Thanks in advance for any help on this.

I made an action to save large batches to a designated "pics" folder. Then when I'm done with a big batch, I just move them to the original folder and let the OS overwrite them. May seem like a lot of work, but I can do a batch of 500 gallery thumbnails in about four minutes and it takes about 30 seconds to move them and replace the originals.

Similar Messages

"Save for web" overwrite (rather than a save-as) within an action?

Hello.
I have created an action with the last step being a 'save for web' save.
The action works well with regards to saving the processed image(s) to the folder specified in the save for web dialog when recording the action.
I however now need to use the save for web command and have it overwrite the open image in place (then close it).
I can't see how to do this, is it possible?
Thanks,
Richard.

in your actions palette you have the ability to tag the action to stop during playback and give you the opportunity to change the export variables. Check the box to the left of the export command in your actions setup. That with pause the action during it's run and allow you to make the changes on the fly.
There are also some interesting naming conventions allowed in Bridge that may work well in conjunction with the ability to run Photoshop action commands from Bridge.
If this doesn't do what you want take a screen grab and post it to the list so I can see what your working with.
Brett

Curious: How does "Save for Web" reduce the file size?

I do know HOW TO USE "Save for web" -- no questions there. I'm wanting to understand better what's going on under the hood.
When I start with say, an 8x10 JPG at 300 dpi, I understand completely how bringing that down to 72 dpi yields a much smaller file. Simple math.
What I don't understand is how the "Save for Web" function can reduce that smaller file size so drastically at the same dimensions, still 72dpi, with negligible image loss (at least at the 80% quality). Maybe it's just my amateur eyes, but for everyday casual web pages, I can discern no significant difference between the two 72dpi images. (At lower quality settings, I do see differences.)
Can anyone explain a bit more of HOW Photoshop does this? Is it simply compression? For example, is it -roughly- analogous to converting an AIF sound file as an MP3?
Thanks,
cb

Thanks, that worked. I figure there was a setting in there somewhere and was even in the right tab, but didnt think to click on that.

Quicktime 10 "Save For Web", spaces in file names?

Maybe I'm overlooking something here, but:
When using Quicktime 10's "Save for Web" function, it exports movie source files that all have spaces in the filenames (i.e. "Movie - iPhone.m4v" etc)
Now correct me if I'm wrong, but most web servers DO NOT like having spaces in the filenames, and every time I try to upload them to one of our web servers, I'm getting an error message that says it doesn't like the file.
Simply removing the spaces from the filenames causes the Quicktime reference movie to stop working, as you might expect.
Am I missing something here? How would someone possibly get this to work?

Thanks for the reply - actually it was helpful, and was the final nail in the coffin for Yahoo Webhosting for us. We've been using it for years, and even though it ***** terribly (and I mean TERRIBLY, horribly, painfully), we've stuck with it just because it's been easier to use it than to not switch. But you're exactly right... I tried uploading files to Cachefly with spaces in the name, and bingo, works perfectly.
Thanks.

Save for Web with Optimize File Size for Batch Process

I have a client who needs to be able to run a batch process on jpg images ranging in size from 600KB to 2.5MB optimizing their file size as close to 200KB as possible. The feature is included in Photoshop's save for web optimize dialog but it doesn't work for batch processes. If you record an action with the optimize to file size option set it processes all the images in the batch based on the quality settings required to resize the image you used during recording, meaning if the image you recorded was 1.5MB the quality setting might be 70 percent to hit the 200KB mark but that wouldn't be the correct quality setting for a 600KB file nor a 2.5MB file those would either be too small or too large.
I've done quite a bit of searching both online and in the photoshop scripting forums but I haven't been able to find anything that would point me in the right direction.
My client's paying for this work so if there's someone who knows how to script this who'd rather be paid than just do some pointing we can arrange for that quite easily.
Thanks in advance for your assistance and suggestions.
In case it's of importance we're using Photoshop CS4.

If you don't mind spending a few bucks on a shareware prog, Jpegsizer has the option to save to a filesize.
You can find it here.
http://www.tangotools.com/jpegsizer/register.htm
There is a free trial version, but you can't save files.

Another save for web devices error - File already exists?

I've been using the same Photoshop CS4 on Windows 7 for about a year now, and only now this problem occurs to me.
Whenever I try to preview gifs in any browser (tried a few), I get the error message "Could not complete this operation. A file by this name already exists."
Tried renaming the files, replacing them, creating new ones, tried to enter preview on old files that previously worked, but always get the same error message.
I did some research and tried deleting both the main Save for Web and Devices pref file, and the other so called "hidden one" in the plugins folder. I've tried reinstalling photoshop from scratch. Nothing works.
Please help me. I'm near desperate :/

Ah, sorry, now I see what you're doing.
I haven't had the issue myself, but I can guess that one or more of the temporary files it needs to create in order to show them in your browser must be failing in creation. Check the permissions on the folder identified by your TEMP environment variable - you should have Full Control of your TEMP area..
Specifically, it creates a "Save for Web" subfolder there. You might be able to delete that entirely in order to start afresh.
Just to test, I've opened Photoshop CS4, entered Save for Web & Devices, and pressed the Preview button myself and it worked okay here... Your TEMP area is likely different than mine.
-Noel

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.

Illustrator CS2 "Save for Web" not functioning properly.

Illustrator CS2, OS X 10.4.11.
I am creating graphics for the Web with Illustrator CS2. When I go to Save for Web, the Save for Web window opens properly but the original graphics and type (even though the type is converted to outlines), become pixelated therefore my Web images are pixelated.
Attached is an example of a jpeg saved at maximum 100 quality.
I am not umderstanding why my originals become pixelated when doing Save for Web. It used to work until yesterday.
Does anyone have any suggestions? Can anyone help?
Much appreciated and thanks in advance.

Mom,
I figured there's nothing wrong with my native file as a co-worker did the same and Save for Web worked.So why is it that when I do Save for Web, the native file pixelates when previewing the "original"?
That's what I can't figure out. One minute it worked fine, the next... bang!
That, and gprobst also being save correctly, imply that there is something wrong with your preferences.
No time to wait for the server. Here is an extract of the most important part:
THE CURE:
Up to Illustrator 10, almost all the preference settings were included in the aiprefs file, and almost all issues with corrupted settings could be solved by deleting or moving it; in some rare cases, moving or deleting the folder holding the settings was required.
From Illustrator CS on, the preference settings have been spread over a number of files/subfolders so in many cases deleting the aiprefs file is not enough: the easy solution is to move the whole folder rather than trying to figure out which file(s) may be corrupted; just deleting the folder without moving it first has proved fruitless in some cases.
Therefore, the cure all consists of the following steps:
1. Close Illustrator.
2. Make a Windows search including hidden files and folders and including subfolders for the folder holding the preference files; the name of the folder depends on the Illustrator version, and the position of the folder depends on the OS version. There is one folder for each version and for each user so it is important to find the relevant one.
Up to version 10, the name of the folder is Adobe Illustrator [X],
From version CS on, the name of the folder is Adobe Illustrator [X] Settings.
[X] is the version number; as standalone versions, CS (Creative Suite) is called 11, CS2 is called 12, and CS3 is called 13, but the version numbers with CS are used in the folder name.
3. Either:
a) Create a subfolder and move all the contents into it; or
b) Move the whole folder to the Desktop.
With both you may recover the contents of the folder by moving it back if the issue is not solved and get your preference settings back.
a) requires creation of the subfolder, but it makes recovery easier, especially if you create a shortcut to the preference settings folder, and you can skip the search if/when corruption occurs again.
You may delete the folder/contents subsequently.
4. If you have Windows Vista, restart Windows. If not, continue to 5 without delay.
5. Restart Illustrator, and see whether the issue is solved.

A script for "Save for Web" as .jpg

I found a script that saves the current selected document in Photoshop as .png to the Desktop, and use it all the time.
function main() {
          // declare local variables
          var doc = app.activeDocument;
          var docName = app.activeDocument.name.slice(0,-4);
    var saveFile = new File("~/Desktop/" + docName + ".png");
    pngSaveOptions = new PNGSaveOptions();
    pngSaveOptions.interlaced = false;
    doc.saveAs(saveFile, pngSaveOptions, true, Extension.LOWERCASE);
main();
Now I'd really like a similar script to do "Save for Web" as .jpg files, without a colour profile, to the Desktop. Preferably a version to save as 100% quality and one to save as 60% quality.
Any help would be greatly appreciated.

Here you are...
function main(){
if(!documents.length) return;
var Name = app.activeDocument.name.replace(/\.[^\.]+$/, '');
var saveFile = File(Folder.desktop + "/" + Name + ".jpg");
if(saveFile.exists){
   if(!confirm("Overwrite existing document?")) return;
    saveFile.remove();
SaveForWeb(saveFile,100); //change to 60 for 60%
main();
function SaveForWeb(saveFile,jpegQuality) {
var sfwOptions = new ExportOptionsSaveForWeb();
   sfwOptions.format = SaveDocumentType.JPEG;
   sfwOptions.includeProfile = false;
   sfwOptions.interlaced = 0;
   sfwOptions.optimized = true;
   sfwOptions.quality = jpegQuality; //0-100
activeDocument.exportDocument(saveFile, ExportType.SAVEFORWEB, sfwOptions);

Problems with "save for web" app low quality messed up images

Please help I have never had a problem with the "save for web" application before (over three years) I am currently running A.I. cs3 on windows vista. in the past whenever I save anything this way the images were always clean. as of yesterday everything I try to save through the save for web app the images are very low quality all the vector has jagged edges, it is very low rez looking and the file sizes are very small, half the size they normaly would be. What did I do to change the settings or better yet how can I get it back to the way it was.

Thank you for your help I moved the folder but it still did not fix this problem. it is also not just the jpg option under the save for web app but all the setting ie. gif, png, ect. ect. Also the the files sizes are much less, example I exported a design as a jpg with the quality setting about 6 the file size was 374kb when I exported the same design through the save for web app the file size was only 45 kb on the quilty setting of 100. further more in the preview screen of "save for web" the original images as well as the optimized both look messed up. The "save for web" app has always worked for me in the past never a problem and I use this app alot so it is very important.

Photoshop wont "Save for Web"

Ever since I installed CC on my vanilla MacMini (Late 2014) running OS X 10.10.1, I haven't been able to use the "Save for Web" feature in Photoshop (2014.2.2 Release, 20141204.r.310 x64) anymore. I keep getting an error message saying "The operation could not be completed. The file or directory could not be found."
Google and the forums have unfortunately only come up with people having similar problems, but not with any solutions. Any help would be greatly appreciated!

I seem to have skipped your earlier response.
I've been on OS X 10.10.2 for a couple of days now. Pretty much since it was released.
Here's the contents of my ~/Library/Preferences/Adobe Photoshop CC 2014 Settings directory:
Seems like the file is missing and PS can't write in there for one reason or another. These are the permission settings on the folder:
Turns out, my initial idea wasn't the worst: I now transferred the entire ~/Library/Preferences/Adobe Photoshop CC 2014 Settings directory from my tmp-admin user to my actual user. Lo and behold – tataaa – sure enough, there was a Save For Web Prefs.psp file in there. And after starting PS, I can now SFW again.
This issue is worked around, but I am still puzzled and a bit annoyed by the fact, that there doesn't seem to be any real explanation, why on earth that problem happened in the first place and what might still be running differently than it should.
For reference …
The contents of the imported settings-directory (permissions: drwxr-xr-x 20 r8r staff) look as follows:
The contents of the original directory (permissions: drwxrwxr-x 17 r8r staff) like this:
Beats me.
Anyways – thanks a lot for the assistance, and if you have any further ideas on how to get to the root of the problem, I'd be happy to hear about it!

Photoshop Elements: Save for Web is Unavailable

When I try to save an image in 'Save for Web' it is gray and unavailable.

Make sure you have the Save For Web Plug-in file
Applications à Adobe Photoshop Elements 10 à Support Files à Plug-Ins à Import Modules

Write Permission Error Save for Web Adobe CC 2014

Upon downloading and installing the recently released CC '14 apps, I've run into a problem with Photoshop CC 2014.
When I click "save for web" in the file menu, it returns an error message of "The operation could not be completed. A write permissions error has occurred."
It seems like a standard permissions error, so I repaired disk permissions, removed plists and prefs from user library, eventually I uninstalled photoshop and reinstalled it, restarted the computer, all with no progress.
I found another forum for CS5.5 that had a similar issue - with it's resolution being a permissions change on the preferences folder itself. For kicks, I tried this - again no progress.
I need to use the save for web feature. It is not usable on my end. Let's figure this out.
System Specs
Late 2013 iMac 27''
3.5GHz Intel Core i7
32GB 1600 MHz DDR3 RAM
NVIDIA GeForce GTX 780M 4096MB
3.11 TB Fusion Drive
Adobe Photoshop CC (2014)
20140508.r.58 x64

I had the same problem. And, I could not migrate settings. I found another thread about the same problem that suggested reset preferences on Photoshop launch, but that didn't work. the post also suggested to reset permissions for the library preference folder. Mine was fine.
But to fix it I had to go to the main library Preferences folder and reset permissions for the Photoshop CC 2014 Paths file and Photoshop CC 2014 Settings folder.
I am disappointed that Adobe shipped an upgrade with such a fundamental flaw. I feel I should say something disparaging and derogatory about Adobe quality control, about how as a loyal customer, using Photoshop since version 2.5 and a CC subscriber I expect better. But, I'll leave those remarks to others.

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
我太老了

Save for web gif loop settings not working

Photoshop CC 2014 Mac Pro 10.8.5
When I change looping settings from "once" to "forever" when saving a gif it only loops once. I tried multiple times. In the end what got it to work was changing looping back and fourth from "once" to "forever" over and over and over until randomly the preview started looping. At that point when I saved it worked correctly.

I’m not really sure; it could be a Mac problem.
This is the Adobe statement on Lion:
Mac OS 10.7 has some exciting new features such as Autosave, Restore, Versioning, Full Screen Mode, and more multi-touch gestures. For Adobe applications to fully support these features, additional product development is required. Adobe is working to address this issue.
There is one other thing you could try. Open a photo in the Editor and then hold down the Cmd+Opt+Shift Keys and press the letter S
It’s also possible to delete the save for web preferences and then re-start the program to re-build them. This involves holding down Cmd+Opt keys and clicking Save for Web under the File menu. However this may not be possible if save for web is grayed out.
Please let us know if you get it fixed.

Make Save for Web overwrite original file

Similar Messages

Maybe you are looking for