no saving big picture (over 8000px) as jpeg possible.

Forum|Forum|4 years ago
May 21, 2021
3 replies
877 views

After this update to 22.4.1, no big picture can save as jpeg.

Only tiff, psb, psd and jpeg2000.

The picture has 14000px with, i need this as jpg, but i can´t save it.

This topic has been closed for replies.

Correct answer D Fosse

"Save As" now lists only the formats that support all the current properties of the file. All other formats, with limited support, are now moved to "Save A Copy".

This was changed because the Save As jpeg function had already been broken for over a year on the Mac side, since Catalina. Saving over a jpeg resulted in a separate file with "-copy" appended. The programming function to strip "-copy" from the filename had been removed by Apple, and there was no way for Adobe to work around it. The Save As jpeg function was rendered useless by this and had to be totally rewritten.

To be clear, saving a layered/16 bit file as jpeg saved out a copy the whole time. That is important to understand! The jpeg format does not allow 16 bit or layers. That fact was just hidden by Photoshop, by removing "-copy", but with Catalina it was no longer possible and "-copy" would always appear regardless.

Everybody should keep in mind that the direct save to jpeg, from 16 bit/layered files, was introduced in Photoshop CS5 in 2010. Prior to that, it was not possible at all to save directly to jpeg. First you had to remove every property in the file that wasn't supported in the jpeg specification. Only then could you save it. So this is nothing new - but this time you can use Save A Copy.

Platform parity has always been a sacred principle in Photoshop, so it had to be changed in the Windows version as well, even though it never was a problem on Windows.

JJMack

Community Expert

JJMack

Community Expert

"SaveDesktopJpeg.jsx"

var Name = activeDocument.name;
var jpegfile =  new File('~/Desktop/' + Name);
SaveAsJPEG(jpegfile, 10);
function SaveAsJPEG(saveFile, jpegQuality){
	var doc = activeDocument;
	if (doc.bitsPerChannel != BitsPerChannelType.EIGHT) doc.bitsPerChannel = BitsPerChannelType.EIGHT;
	jpgSaveOptions = new JPEGSaveOptions();
	jpgSaveOptions.embedColorProfile = true;
	jpgSaveOptions.formatOptions = FormatOptions.STANDARDBASELINE;
	jpgSaveOptions.matte = MatteType.NONE;
	jpgSaveOptions.quality = jpegQuality;
	activeDocument.saveAs(File(saveFile+".jpg"), jpgSaveOptions, true,Extension.LOWERCASE);
}

JJMack

D Fosse

Correct answer

Community Expert

"Save As" now lists only the formats that support all the current properties of the file. All other formats, with limited support, are now moved to "Save A Copy".

This was changed because the Save As jpeg function had already been broken for over a year on the Mac side, since Catalina. Saving over a jpeg resulted in a separate file with "-copy" appended. The programming function to strip "-copy" from the filename had been removed by Apple, and there was no way for Adobe to work around it. The Save As jpeg function was rendered useless by this and had to be totally rewritten.

To be clear, saving a layered/16 bit file as jpeg saved out a copy the whole time. That is important to understand! The jpeg format does not allow 16 bit or layers. That fact was just hidden by Photoshop, by removing "-copy", but with Catalina it was no longer possible and "-copy" would always appear regardless.

Everybody should keep in mind that the direct save to jpeg, from 16 bit/layered files, was introduced in Photoshop CS5 in 2010. Prior to that, it was not possible at all to save directly to jpeg. First you had to remove every property in the file that wasn't supported in the jpeg specification. Only then could you save it. So this is nothing new - but this time you can use Save A Copy.

Platform parity has always been a sacred principle in Photoshop, so it had to be changed in the Windows version as well, even though it never was a problem on Windows.

Q

QuadronetAuthor

Participant

Ah ok, i understand. Now i´m happy, best regard´s

D Fosse

Community Expert

Thank you, Quadronet, that's a nice change 🙂 I've posted this a few times and everybody else seems to take it as a red flag to crank up their anger and frustration at Adobe.

And while I can understand that, there really was no other way this time. Apple changed the rules, and Adobe had no choice but to adapt.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded