Saving as Copy instead of Overwriting: PS 2020 with macOS Catalina [locked]

[courtneys95419822]

Having an issue with the new update. Finally, I am seeing my extension name update when a new one is selected in the save as dialog box... however I am still having an issue with saving over original files. If I make changes to a file then try to save over the .png file it keeps saving as filename-copy.png. I am not able to unselect the "Save as a copy" box. Anyone else?

[subject edited for clarity]

[Osiyo1]

Because Adobe doesn't care about you or its software - it cares about making money - Photoshop is aold technology!

[chanaart]

We are all volunteers trying to help! try to be a bit nicer online. Adobe cares about the software and the customers.

[joshuas65444475]

nobodies mad at the volunteers, we're pissed at the engineers who increasingly break useful functionality for no apparnet reason.

[Osiyo1]

like taking your to get the oil changed and you drive out with no brake

[mrbobdobolina]

This has been fixed (at least for my use case) in 22.4.0. The "new" Save a Copy command replaces the file the way I expect.

[lizuare]

Updating now my fingers are crossed once again 🙂

[joshuas65444475]

I updated after seeing this and it's fixed for me too. Only took a year and a half.

PS, you beat me to that username!

[Erik5FA2]

Except they didnt' REALLY fix the problem. They just moved it to a different part of the work flow. 

Now, if you are starting with a freshPSD, and want to save as a .jpg for the first time you are FORCED to select "Save a Copy" and it adds the "copy" indicator to the file name. You still have to remove it before saving. 

The overwrite feature was fixed, but this is still a cluster [removed]

[D Fosse]

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. Apple did not want to change this, and there was no way for Adobe to work around it. The Save As jpeg function was terminally broken and finished, 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, but with Catalina it was no longer possible to hide.

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.

[wellingsome]

Just updated to v22.4 today. Now we have 'save a copy' and it adds 'copy' in the filename if you switch to another file format. So now I still have to go back and manually delete 'copy' in the filename if just saving a jpg on my desktop from a PSD. This is bull! Why the hell am I dropping almost $60 a month on this crap?

[D Fosse]

If you read the post directly above yours, you'll find the explanation for why this had to happen.

[Treehouse5C82]

Yes I read the post.
And I'm not happy about this either.
Affinity is looking better and better all the time Adobe.

[jane-e]

I'm locking this thread from October 24, 2019. The issue is about the bug Apple introduced with Catalina that Adobe fixed with PS 22.4 and it is now getting posts from those who do not like the fix, which is a different issue. 

If you don't like the fix, please add to one of the many posts on the same topic or start a new thread.

~ Jane