Skip to main content
H
Hjorthmedh
Known Participant
October 25, 2019
Question

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

  • October 25, 2019
  • 24 replies
  • 19191 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.

    24 replies

    M
    Marla5mkd
    Participant
    April 29, 2021

    I am also having this issue and it's extremely annoying! Please fix!

      Mentor Neto
      Mentor Neto
      Participant
      April 29, 2021

      I simply can't understand how a simple bug (because it is obviously a bug, since it contradicts even the option selected by the user to replace the existing file) takes so long and so many versions to be fixed.

      I'm not sure here is the correct forum to ask Adobe to fix it. 

       

      But dozens of bug reports also didn't work...

       

      For some users, like myself, this is crucial for the workflow. My temporary solution was a script that I run after saving files. 

       

        JohanElzenga
        Community Expert
        JohanElzengaCommunity Expert
        Community Expert
        April 30, 2021
        @Mentor Neto wrote:

        I simply can't understand how a simple bug (because it is obviously a bug, since it contradicts even the option selected by the user to replace the existing file) takes so long and so many versions to be fixed.

        I'm not sure here is the correct forum to ask Adobe to fix it. 

         

        But dozens of bug reports also didn't work...

         

        For some users, like myself, this is crucial for the workflow. My temporary solution was a script that I run after saving files. 

         

         

        It's not a 'simple' bug at all. It's a complicated problem. It is caused by changes in the MacOS 'Save' dialog box, introduced in MacOS Catalina. If you run the same version of Photoshop on MacOS Mohave then everything works as expected. Yes, it's taking far too long. But for you and me it is impossible to say what would be a reasonable time to fix this and what is no longer reasonable.

         

        -- Johan W. Elzenga
        adamh56650550
        adamh56650550
        Participant
        April 22, 2021

        Hey Adobe, this has been a known issue for close to 2 years. I'm still on Catalina and a lot of people are saying it's happening on Big Sur. Figure it out. Pause on the cloud library. Put the latest 3D/VR/AR feature to one side. Make this a top priority and then you can continue with a new feature no one wants.

          craki29
          craki29
          Participant
          March 30, 2021

          Something that maybe help if you need to replace a PNG file, go to File/Export/Quick Export As PNG and the file is replacement without this upset issue, this work for me

          C
          christinat17657432
          Participant
          March 25, 2021

          Please add my voice to the chorus!

           

          This issue causes big problems in our design and production workflows when editing images linked to QXP or ID files. The jpg arguments are missing the point. This is happening with all file types where "save as... replace" is selected regardless of layers, flattening, whatever. The dialogue says the file will be overwritten but it is not; instead, a second file is created with "copy" appended to the filename. 

           

          A serious issue and a real PIA.

            D
            D_Haley
            Participant
            March 25, 2021

            Exactly!!

              K
              Karrie-
              Participant
              March 17, 2021

              I'm having this issue too. It's causing me a lot of unwanted files and extra steps to overwrite a file. It's unorganized and unefficient. 

                S
                samlansd
                Participant
                March 12, 2021

                I'm still having this problem as well. Been having it for at least a few months now.

                S
                samlansd
                Participant
                March 12, 2021

                (I'm on MacOS Big Sur 11.2.3, but I was having the same problem on my last mac that I switched from about a month ago, which I think was on Catalina)

                mig15
                mig15
                Inspiring
                March 11, 2021

                Adobe says it is fixed in 22.3. I have updated to 22.3 and IT IS NOT FIXED.

                 

                I'm getting so close to being fed up with Adobe software.

                  D
                  D_Haley
                  Participant
                  March 10, 2021

                  I'm having the same issue with Photoshop 2021 using Catalina.

                  JohanElzenga
                  Community Expert
                  JohanElzengaCommunity Expert
                  Community Expert
                  March 10, 2021

                  Update to version 22.3 that was released today.

                   

                  -- Johan W. Elzenga
                  W
                  Waserone
                  Participating Frequently
                  March 11, 2021

                  Updated to version 22.3, still not fixed (with Catalina at least).

                  If you open a .jpeg or .tif and do a "save as" with the same file name without changing anything on the file itself it actually overwrites the file, but if you change anything and hit "save as" it still creates a copy when you click on "Replace" when PS asks if you want to replace the existing file by overwriting it.

                  B
                  BillC
                  Participating Frequently
                  March 1, 2021

                  Just encountered this bug. I've invested in a new machine in order to upgrade to the latest Adobe CC and this has just happened to me. Did a "SaveAs" fileName.jpg from the layered psd and it saved a "copy" rather than replacing the original. Very surprised this hasn't been fixed seeing as this bug was reported over a year ago. 

                   

                  Also, as an aside.... another bug that hasn't been fixed is the flickering cursor. I had thought maybe my old 2009 Mac with only 16 gigs running High Sierra with 2018 CC was part of the problem but no - it's still there on the new 12 core ram-packed monster running all the latest progs. Still have to hide/quit Photoshop just to work in Illustrator or InDesign.

                  K
                  kobib46717490
                  Participant
                  January 20, 2021

                  Another update, same story..

                   

                  Mac OS Big Sur 11.1

                  Photoshop 22.1.1

                   

                  Problem is still there.

                   

                  Just a quick note to anyone who still thinks it's not a bug, and that it 'existed before':

                   

                  When you have a document with layers—let's call it 'bug.psd'—and you want to save a flat jpg of it, you will use the 'Save As' command, and Photshop will save a copy of that document as a jpg named 'bug.jpg', and the document you have open is still 'bug.psd'. Perfectly normal until now.

                   

                  Now, let's say you've made a couple of changes to the open layered document, and you want to re-write that jpg you saved earlier, you will use the 'Save As' command again, and choose that same name 'bug.jpg'. At this point Adobe will alert you that you're overwriting an existing document and ask you whether you are sure you would like to replace 'bug.jpg'. In the past, if you clicked 'Replace' - the file 'bug.jpg' will simply be overwritten with the new 'bug.jpg' - that's how it was in the past, always!

                   

                  Nowadays, when you hit 'Replace', instead of overwriting the existing 'bug.jpg' - Photoshop creates a 'bug copy.jpg'.

                   

                  THIS IS NOT NORMAL. THIS IS A BUG. And this bug exists for a year a half now, update after update after update. I can't figure out Adobe's thinking here.. why is it not getting fixed?

                   

                    W
                    Waserone
                    Participating Frequently
                    January 20, 2021
                    Exactly, thank you for explaining it so well. Can't understand either why
                    this hasn't been fixed yet. Another thing I noticed is that if you use the
                    "Save for Web" command and try to save a jpeg with the same name of an
                    existing one, Photoshop will ask you TWICE if you want to replace the file,
                    the first time with the same box that appears when you use the "Save As"
                    command, and the second one is a specific popup of the "Save for Web"
                    command (darker color in my system), and in the end it actually replaces
                    the file and doesn't create a copy. But still, it's completely redundant.
                    Show more replies
                    Terms & ConditionsAccessibility statement
                    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices