In Photoshop CS6 actions when we save the image as JPEG through save for web it doesn't work when we run it, instead it runs and saves the image as HTML, i guess some error in it. I tried it again and again but it doesn't remember my save for web settings and saves the images as HTML.

If I rename the HTML extension to JPG then the pictures shows, So I tried again to check what extension its taking and I found the format selected as "Images Only" then also its generating HTML extension for the JPEG images.

It a new bug in CS6 though when you recorded the action you saved jpeg images to you desktop and you only entered file names onto the save for web action steps the action recorder recorded name.html. I replaced you save for web steps on my machine for my desktop and CS6 recorded name.html. I then did the same with CS5 though I only entered names CS5 recorded name.jpg.

If you expand the export steps tou will see the hard coded file names and extention

An action like this will always save the same files it can not be batch because you recorded Path and Names in the save for web steps. The .html files saved on with CS6 are actually jpeg files and if you rename them hrom name.html to name.jpg you can use them,

This is a HUGE inconvenience and surely needs to be addressed sooner than later. I have found that importing actions from older versions will work...the only problem is if the machine name/user name/folder path changes it is worthless.

Luckily I have PS5.5 installed on my other computers and I use that...however, I just got my new MBP with Retina and won't be able to install 5.5, only the CC6 version.

This still isn't fixed? I have an action that I save as the image as x.jpg and then later in the action it uses x.jpg so I have to be able to make the name a generic name. Grrrrr, another reason I am not that happy that I upgraded to cs6!

Adobe does not publish a fix schedule or even commit to fixing problems. I have submitted bug reports to Adobe that Adobe has accepted as bugs introduced in CS4. I submitted bug reports on the problems in CS5 and CS6 on them. The best reply I received from Adobe was three or four years ago and it was perhaps they will be fixed is some future release. You can use a copy of CS5 to record the action and it will work in CS6.

Also all CS6 recorded Save for web steps do not have the problem. It depend on how you record Save for web. Sone recorded steps record .html or .htm instead of .jpg. Others record no file extension. Only the one that have recorded .htm or .html are a problem. The ones that do not record the extensions work and the ones that save the wrong files extension actually save a jpeg file with the wrong extension. Renamming the saved image.html files to image.jpg will fix the files. Often all one need to do is a wildcard rename *.htm to *.jpg.

Usually when you record a save if you do not change the default offered like path and file name the path and file name will not be recorded in the action step like save as where all you change is the file type pull down where you set the type. Like you do when processing a layered psd file and saving files like jpeg, gif and png. If you don't change file type the original file is updated. When these action steps are played the current document path and name will be used unless there is destination folder specified in a dialog like automate batch or script image processor they will override the default path. When path location and file name are not recorded into actions save step the save will be to the current documents location with the current document's file name. Any recorded Path and or File name will override the current document path and name and Batch and scripts can override recorded location and names.

If you add a layer to a jpeg document a save would want to save a psd and with a psd file you usually want to save the psd file as well as other image file formats that is why batch and image processors exist you have much better control over output.

The image processors scripts I have looked will not overlay any existing file it would add an serial suffix to the file name if the output file it wanted to save exists.

I have a solution that works for Windows. I create a .bat file in the same directory as all the html file to rename all the .html files to .png

Here's how to do it, it's really simple.

Create a new text file in any old text editor. Add this one line:

rename *.html *.png

(Change .png to .jpg if you want jpgs)

Save it as something like "renameHTMLtoPNG.bat".

Run your Photoshop batch job to dump all the .html files into the same folder. Make sure this .bat is in the same folder as the .html files, then click on it to run it, and it'll rename everything to the correct extension.

Since the problem is that the wrong file extension is being stored in the action...

Has anyone tried saving an action set as a .atn file, hacking into a saved .atn file and changing the characters .html to .png (or whatever's desired)? Use a null character (00) to blank out the L. Then load the hacked .atn file back into Photoshop.

If you don't know how to do this, post a copy of an action file online and I will be happy to give it a try.

Very easy to do. X created a set of tools scripting tools for Photoshop. In the Xtools package there are many supplied utility scripts. Two of them could be used to do what you want.

The script names are ActionFileToXML and ActionFileFromXML. So if you record an action the has a save for web step that when when you expand the step you set the the save file name is .html not .jpg like this one.

Save the Action Set into an .atn file and run ActionFileToXML the edit the XML file and change the .html" to .jpg save the XML file and run ActionFileFromXML. The delete the action set in the Actions palette and load the updated .atn file. Expand the save for web steps to check that the steps not shows .jpg..

Does anyone else find it odd that we are discussing hacks and workarounds for something that worked flawlessly in a previous version of the software. If they haven't fixed this in a year, I cannot imagine that they are very interested in doing so in the future. How can Adobe not care about such an important basic function of the software.

It not odd to disgust bugs at all and Adobe addressed the bug in CC. However they did not fix CS6 which is typical Adobe behavior. Here is save for web recorded in CC the file extension is once again jpg and not the html that get recorded in CS6.

Strange My CS6 is up to date and when I record a save for web as jpg and change the default fname what gets saved is a jpeg file however what get recorded in the action is FileName.HTML and when the action is plated though a jpeg file is save its name is FileName.html.

Yes if you do not change the default file name offered no file name information is recorded in the action step and CS6 works correctly. The problem in cs6 has always been if you change the default offered .htm gets recorded not .jpg. Its been fixes in cc.

jj, it may have been working for you, but it didn't start working for me until I got an update a couple of days ago. We do a lot of site management where customers send in articles in Word. We Copy the images into photoshop to manipulate as they are usually huge, then we use an action to save them all of at once. We have been doing this for years and it stopped working in CS 6.

A typical web update will have over 100 images, so the difference between doiing them one at a time and simply hitting the action a few times is HUGE!

This process saved us too much time to continue to use 6 without it so I am particularly grateful that they fixed it.

I haven't tried using it while renaming the image as it would simply save all of the images over each other and that would defeat out purpose.

As mentioned previously, In instances where the original files name has been changed at export is when the Custom File Name line will be added e.g., JJMack's screenshots above. I have found to fix the action, i simply open or use a file already open > Double-click the Export step in the action which will run that step and save the file as it's original name. This will strip off the Custom File Name.