Fixed: Photoshop 2020 File name bug when saving a replacement of an existing file

Forum|Forum|6 years ago
October 25, 2019
24 replies
19442 views

Hej! The old photoshop behaviour used to be that when you save to overwrite an existing file it asks you to confirm that you want to replace it, you say yes, and the old file gets overwritten. In the latest version if you click "replace" it still does not replace the file, but adds "copy of" text at the end after the fact without any way to not do that. Please give us an option to have the old behaviour, or change it back to how it used to be by default.

This topic has been closed for replies.

Show previous replies

C

Clacey81

Participant

I contacted Adobe as well and they told me that I just need to wait for the next Photoshop update which should eliminate this issue. Until then, we just have to deal with it I guess. There was no timeframe as to when it will be fixed.

sevdestruct

Participating Frequently

Cannot deselect save as copy on jpgs, pngs—any output—even if electing to overwrite existing file (to be clear this is when the systems asks to overwrite the existing file and you select YES. It does not. Not at all. Not like it used to) creates a new file as copy regardless. In other words this is forcing Save as Copy. It cannot be deselected. This is a bug. Please fix. This has been causing extra work per file when saving output over previously Save As output (something we have all done for decades without issue until now).

OS: macOS Catalina

D Fosse

Community Expert

Right. Rewind time for me. I tried it (on Windows 10) - and you're all correct. A layered PSD does in fact overwrite a derivative jpeg, without making a copy of it with a different name, when you save out a second time.

It just leaves the layered original open on screen, and of course you need to decide what to do with that separately.

So the described behavior does qualify as a bug, in the sense that it's not "normal". I stand corrected there.

The reason some of us are so insistent, is that there's a bigger picture here. The "save as copy" behavior would in fact be equally justifiable, and if it was up to me I'd probably make that the default.

We see people here all the time who don't understand the severe limitations in the jpeg format, and why that makes jpeg a very special case in almost all scenarios. That's not a reflection on anyone present here - it's just a fact. Lots of people don't understand why a layered file can't simply be saved as a jpeg. A jpeg is by nature a copy. It's born as a copy and exists solely for the function of being a copy.

So trying to explain why jpeg always needs special treatment and lots of special considerations, has become a matter of routine for all of us regulars. In any case, using Export or Save For Web should avoid the whole problem.