Copy link to clipboard
Copied
If your file contains items that are not supported in your required format (e.g. layers or 16 bits/channel) then the file format is moved to the Save a Copy menu. This was driven by changes in the Mac Operating System, although the changes are applied to both Mac and Windows versions to keep the two aligned.
What's new in Photoshop
Dave
Hi All,
We appreciate your feedback on the recent “Save a Copy” change. To address your concerns, we have created two new options in Photoshop 22.4.2 that will enable both revert to the legacy “Save As” workflow and/or omit the addended “copy” when saving as a copy. These options can be found in the File Saving Options section under Preferences > File Handling.
To quickly summarize, you will now have the option to revert to the legacy “Save As” workflow (from before recent changes) on both macOS
...Hi all
You may already know that flatted file formats have been relocated from the "Save as" menu option to the "Save as Copy" option in Photoshop. To learn more about this workflow update, please refer to the following quick tip: https://community.adobe.com/t5/photoshop-ecosystem-discussions/learn-how-to-save-all-file-formats-from-photoshop-s-save-as-dialog-quick-tip/td-p/12933468?cgen=ZFN4FD71&mv=other
Or see this video tutorial link
Hope it helps,
Mohit
Copy link to clipboard
Copied
What the hell they did, who asked about this changes?
Copy link to clipboard
Copied
It's definitely NOT the same save as. Removing "copy" every time is tedious -.-
Copy link to clipboard
Copied
Yes, I am really frustrated with this change too. An awful decision.
There is no Adobe Uservoice - I'm going to bring this up elsewhere.
Copy link to clipboard
Copied
If your file contains items that are not supported in your required format (e.g. layers or 16 bits/channel) then the file format is moved to the Save a Copy menu. This was actually driven by changes in the Mac Operating System, although the changes are applied to both Mac and Windows versions to keep them in step but it also prevents users from inadvertently losing layers etc which was a well hidden issue after saving as PDF.
Dave
https://helpx.adobe.com/photoshop/using/whats-new.html
Dave
Copy link to clipboard
Copied
Not if you include layers and Photoshop compatibility in the PDF.
Such a big change for something that worked fine for years.
Copy link to clipboard
Copied
Again, it was Apple. It worked fine for years, then Apple broke it. This is the only possible workaround given that Apple won't change their policies.
Actually, this reverts to how Photoshop originally worked - only then you didn't even have Save A Copy. If you, for instance, wanted to save a layered file as jpeg, you simply couldn't, there was no way - for the simple reason it's not allowed in the jpeg specification. You had to get rid of all the offending properties before you could save.
The ability to directly save a jpeg-copy-on-the-fly was introduced sometime around CS4.
I have to admit that I secretly applaud this change. This way, it's right up front: this is what the jpeg specification supports, and this is what it doesn't support. If you go ahead, you will lose your layers, you will lose 16 bit depth, this is a point of no return.
The double Save prompt, first the jpeg, then the layered original, was a lot harder to explain than this.
Copy link to clipboard
Copied
I don't understand how Apple broke it?
Anyway - it is the way it is.
I wish there was a simpler option - just an Export option and pick your file format.
Copy link to clipboard
Copied
I don't understand how Apple broke it?
By @Eugene Tyson
There's been about a million threads here on the Photoshop forum, and on the feedback forum, since Catalina was released. It's probably been the top complaint from the Mac users. It was never a problem on Windows.
Copy link to clipboard
Copied
Thanks - I guess I should visit these more often.
Copy link to clipboard
Copied
Have to say in the last 25 years - never been an issue at all. Actually never heard of anyone having an issue with this.
It's very strange. But Apple broke it - suppose it's up to Adobe to fix it.
Copy link to clipboard
Copied
That is the point. The fact that it overcame the PDF issue was a bonus, remember that issue could uncheck layers and affected your next save as a PSD or TIFF. There have been many threads on these forums from those who lost work due to that issue. The driver of this change though was the OS changes made by Apple. Some might argue that only the MAC version could have been changed but that would have left the MAC and Windows versions acting very differently which impacts those who use both, or write actions for both.
Dave
Copy link to clipboard
Copied
I understand this - but surely it should be optional.
If someone wants the Save to act as an option to choose different formats.
This actually affected our team greatly last week, as the files created are performance reviewed. Where running actions is part of the common workflow - saved the file as a .pdf but it was .psd format, and wouldn't open in Acrobat - but opened up fine in Photoshop as .psd when the extension was amended. As files aren't checked until the following day - the team ended up with a negative review for those files.
It was a completely unexpected change to the software UI - and in my eyes, it's unforgivable.
It really should be optional.
As of now, we have had to roll back to a previous version of Photoshop.
Crazy.
Copy link to clipboard
Copied
@Eugene Tyson wrote:As of now, we have had to roll back to a previous version of Photoshop.
Keep in mind that Adobe may not change this in future versions.
~ Jane
Copy link to clipboard
Copied
Instead of rolling back to a previous version Adobe should make it something that can be set up in preferences. We (users) should have the choice.
Copy link to clipboard
Copied
Adobe had no choice but to change in order to address the long reported issue since the Catalina operating system. Apple did not change so Adobe, who had to work within the operating system, had to change. It could be argued that only the MAC version should change, but for a long time now both versions have worked the same way. If they diverged, both workflows and things like actions would need to diverge which is not deemed acceptable.
Dave
Copy link to clipboard
Copied
I still think that Adobe got this wrong. There is a better way to offer saving different file formats.
Could it be possible thave basic other file formats
File>Export
PDF
JPG
PNG
Other...
That would be far more UI-friendly.
Copy link to clipboard
Copied
It may have overcame the PDF issue but it broke many Actions that use Save As that is a problem. Now the Actions will have to Flatten because there is no Save a Copy in the other versions of Photoshop they use. So they have to edit their Action insert a Flatten before the save as so save as will work, then after the save as back up in history. Even if they only use 22.4 they still have to edit their actions remove the save as and add a Save A Copy. Why did Adobe Rename Save As to Save a Copy and the add a Save As the can do some of the things Save a Copy can do. The New Save As is not requited to save the user work. Save a Copy does that. Its a new issue out of Adobe doors.
Copy link to clipboard
Copied
JJ it is a pain to have to rewrite actions but as discussed in many threads now this was driven by an operating system change. It fixes an issue on Macs introduced by that OS change. Adobe could not do nothing. The only debate is should Adobe have changed the Windows version to match the changes enforced on Macs. They did, which has annoyed some users. If they had not then the Mac and Windows versions would work differently in fundamental steps of saving which would annoy other users.
Dave
Copy link to clipboard
Copied
So Adobe dose not know what OS Photo is running on the be able to program Photoshop to function correctly. This is more like Customer abuse than a fix breakage is not a fix, I love Photoshop however, Adobe "BS" still stinks and impacts all users.
Copy link to clipboard
Copied
You still seem to see this strictly from a Windows point of view, JJ. No, there never was any problem in Windows, and things could have continued as they were.
But Photoshop has always worked identically on both platforms. That has always been an axiom. It was probably not even on the table to leave PS Windows as it was.
Apple broke this, and we all have to live with it. The operating system sets the rules, and there is nothing the application can do that the OS doesn't allow.
Personally I welcome the change. This way it's all up front. When you're saving out a copy, which is what you did all along, it should be perfectly clear that it's a copy. And now it is.
Copy link to clipboard
Copied
Actions do need to be changed but if you look at the actual Action steps, it all uses "Save As" whether its a save, save as, or save a copy. I didn't know this before.
Copy link to clipboard
Copied
Jump to older version!
Copy link to clipboard
Copied
This is probably a fantastic example of Hanlon's Razor.
Copy link to clipboard
Copied
Hanlon's Razor ? - 'Never attribute to malice that which you can explain by stupidity'
Perhaps you can explain which part of changing Photoshop so that it will work after APIs have been withdrawn by Apple is stupid?
Or do you mean aligning the two platform versions, which if diverged causes issues for those who work on, or develop plug ins and actions for, both?
These changes are neither malicious or stupid. Adobe could not win on this one no matter what they did.
Dave
Copy link to clipboard
Copied
I meant from Apple point of view to change their OS so everyone else had to jump through hoops for them, again.