Skip to main content
courtneys95419822
Participant
October 24, 2019
Answered

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

  • October 24, 2019
  • 82 replies
  • 68029 views

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]

 

This topic has been closed for replies.
Correct answer jane-e

Contacted Adobe support — said that it's a known issue and pointed me here:
Photoshop: Saving copy not saving over jpg file

Maybe it's more useful to write there?


This bug introduced by Apple with macOS Catalina has been resolved with 22.4.

~Jane

82 replies

Participant
June 24, 2020

Same issue here.

Love it when I google an issue and find a thread with a bunch of other people having that problem, but there is no solution! Thanks Adobe!!!!!!!!!!!!!!!!!!!!!
I chatted with an Adobe specialist and was told "it is designed this way"

Whyyyyy Adobe, WHYYYYYYY

Participating Frequently
June 26, 2020

Not only the same problem but the same problem since LAST YEAR. And it's like you're speaking another language when you talk to them. Even showing SCREEN SHOTS apparently doesn't help. WHY.

Participating Frequently
June 22, 2020

Same happening with me, its been happening for months now.  

TwoSteppers
Known Participant
June 21, 2020

Just adding my voice to the limitless crowd, pleading for a fix or at least a response saying no fix will be available so that we can move on to permanent workarounds. The Illustrator group did address the same problem and that program is now overwriting files when I use Save As -- as I intend, as it indicates it will, and as it by all rights should.

Participant
June 17, 2020

Been following this thread for MONTHS. Every macOS update and Photoshop update brings hope, and disappointment. How loud do we need to shout?

Known Participant
June 16, 2020

I can't believe this--Adobe just released a bunch of updates including for Photoshop and the problem has not been solved!!! This is insane. It's one of the most basic functions of working in Photoshop that just about every user, professional and amateur, relies on and has so for decades. All Adobe's efforts need to be directed at fixing this very serious bug.

travis_gray
Participant
June 16, 2020

MacOS Catalina 10.15.5
Photoshop 21.2.0

 

This has been happening in the last few releases of Photoshop on Mac OS Catalina. AND IS STILL IN THE LATEST 21.2.0 RELEASE.

All the Photoshop professionals who work on Mac and keep their computers up-to-date that I've talked to, are having this exact same issue and are also super frustrated. It forces uneccessary productivity and workflow problems on everyone.

 

Why would I want to uknowingly save a copy when I have explicitly pressed the button to "REPLACE" the file?

PLEASE FIX THIS ADOBE.

 

 



 

Participant
June 4, 2020

I'm having the same issue, Adobe please fix!

Participant
June 15, 2020

Is this ever going to get fixed?  I'm having the same issue on my iMac. It won't overwrite jpegs or png's.  Seems like a ridiculous issue to even bring up. All we are asking for is to be able to overwrite earlier versions of our files instead of it making a copy.

Participant
June 4, 2020

Also having the same issue, I even went back to the previous version of Photoshop. Still happens in MacOS Catalina 10.15.3 in Photoshop 2019 - Very frustrating - However using the renamer tool in finder saves time... (select files > right-click > rename files). 

chrisj29001917
Participant
May 26, 2020

.

WesternWitch
Participant
May 21, 2020

I also have this problem. It drives me insane. I'm a storyboard artist and the whole point of my job is to finish boards fast and efficently. The extra added time of replacing boards hurts my work preformance. Someone needs to address and fix this issue.