Photoshop: Saving copy not saving over jpg file

  • 78
  • Problem
  • Updated 10 hours ago
  • (Edited)
working on Catalina OS. saving file extension works now but does not save over jpg when saving it creates a copy which is annoying and time consuming to fix
Photo of Steven Paslawsky

Steven Paslawsky

  • 4 Posts
  • 0 Reply Likes

Posted 9 months ago

  • 78
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 2969 Posts
  • 1270 Reply Likes
Not sure I understand this. The problem was that Photoshop would not update the file extension if you save a file in another format, so for example you have a tiff file now and you choose save as jpeg. That will obviously always save a copy.
Photo of Jen

Jen

  • 1 Post
  • 9 Reply Likes
It's not overwriting an existing jpeg when saving with the same file name, it's adding 'copy' to the end of the file name and saving a second jpeg file. It will however, when saving for a third time automatically choose the 'copy' version to overwrite, but brings up a new pop-up box after the normal 'do you want to replace...' warning, which seems to double check that you want to replace it (adding even more time spent saving).
Photo of Steven Paslawsky

Steven Paslawsky

  • 4 Posts
  • 0 Reply Likes
This is my issue thanks Jen
Photo of Leslie Stacks

Leslie Stacks

  • 7 Posts
  • 5 Reply Likes
I had this same issue -- could not overwrite an existing jpeg when saving with the same file name.  I contacted Adobe and got these instructions, which worked for me:  

1) Close all Adobe related processes in activity monitor (Creative cloud, Core sync, CC library, services for adobe desktop app, adobe desktop service, Adobe IPC broker, AAM updater)

2) Navigate to following locations and assign the current user full permissions to adobe folders. To navigate click go from menu bar at then click goto.. type /Library/application support/   and click go.

3) To assign the permission right click on adobe folder and click Get info.. A property window will open. Then click on lock symbol to enable editing. Then click + sign to add your username. Then change read only to read and write. Then click gear symbol at the bottom and click apply to enclosed items and click ok.





Photo of David Gill

David Gill

  • 6 Posts
  • 3 Reply Likes
Thanks for sharing Leslie, unfortunately, this is not working for me. Does it work for other people?
Photo of Jason Hughes

Jason Hughes

  • 5 Posts
  • 8 Reply Likes
I attempted this fix as well, and it did not work for me either.
Photo of Leslie Stacks

Leslie Stacks

  • 7 Posts
  • 5 Reply Likes
Sad to say, after working correctly for about 1 day, this fix no longer works for me, either.
Photo of Jonny

Jonny

  • 12 Posts
  • 6 Reply Likes
i have this issue and not an admin on my work computer, is this getting fixed? it's so frustrating when you are updating images that are linked to a premier pro file for example.
Photo of Hila Schurr

Hila Schurr

  • 7 Posts
  • 2 Reply Likes
same issue, here!!
Photo of Laura Ross

Laura Ross

  • 7 Posts
  • 11 Reply Likes
Same issue here--I have to edit files in Photoshop while working in Lightroom and by golly, it always saves as a copy even though it indicates it is overwriting the original jpg, so I have to manually go back, find the original file, drop it into the trash, take off copy from the new jpg, go back to Lightroom and flip around a few times before it accepts the new jpg. VERY time-consuming. I have to take reflections off glasses and I dread it each time. 

It only started doing this to me with 21.0.2 in Catalina. It seems like every time they fix something they break something else.
Photo of Matt Rock

Matt Rock

  • 11 Posts
  • 5 Reply Likes
Same issue here. Very frustrating.
Photo of Jacinthe Brault

Jacinthe Brault

  • 2 Posts
  • 1 Reply Like
Same issue here also :(
Photo of makcw

makcw

  • 5 Posts
  • 0 Reply Likes
Same issue. This issue appeared after software updated to release 21.0.2. Very Frustrating.
Photo of Victoria Peñuelas

Victoria Peñuelas

  • 2 Posts
  • 0 Reply Likes
Ey
Photo of Angeliki Jackson

Angeliki Jackson

  • 1 Post
  • 1 Reply Like
Yes. Please, someone, figure out a fix. This is so annoying and super time-consuming!
Photo of Joe

Joe

  • 1 Post
  • 0 Reply Likes
Same damn issue. 01.20.20
Photo of Mitchell Kemp

Mitchell Kemp

  • 1 Post
  • 0 Reply Likes
Same issue! Has this been fixed?
Photo of Lisa Wandrei

Lisa Wandrei

  • 6 Posts
  • 3 Reply Likes
me two. very annoying. ugh!
Photo of Hila Schurr

Hila Schurr

  • 7 Posts
  • 2 Reply Likes
I think I just stumbled upon a workaround fix!! If you use the "Save For Web" feature it seems to actually overwrite the file rather than saving it as a copy.  Let me know if this works for you!!
File > Export > Save for Web

Photo of Mike Vago

Mike Vago

  • 1 Post
  • 0 Reply Likes
Just checking to see if anyone's got a better workaround. I only just switched to 2020. In fact, I held on to CS5 as long as possible, because I actually owned CS5 and didn't have the money-grubbing scumbags at Adobe reaching into moy pocket every month. But Catalina doesn't support CS5, so I had to grudgingly upgrade, and so far 2020 is *maddening*.

Every single time I have to overwrite a file (which I do a few dozens times a day), I deliberately tell Photoshop to overwrite, it tells me it's overwriting, but instead it creates a second file with "copy" in the name. So I have to manually delete the original and then rename the new file. A few dozen times a day. And I'm paying them every month for the rest of my life for the privilege! I'm about ready to find Adobe's headquarters and burn it to the ground.
(Edited)
Photo of Hila Schurr

Hila Schurr

  • 7 Posts
  • 2 Reply Likes
@mikevago read the comment right above yours - it has a workaround!
(Edited)
Photo of JEFF LAMBERT

JEFF LAMBERT

  • 45 Posts
  • 24 Reply Likes
@hilaschurr a good workaround if you need web file format, but not useful for Tiff, which we rely on for InDesign imports.
Photo of Hila Schurr

Hila Schurr

  • 7 Posts
  • 2 Reply Likes
good point!
Photo of Steve Guthrie

Steve Guthrie

  • 1 Post
  • 0 Reply Likes
Good work around if you are working with in that same folder, but when jumping from project to project you have to dig back into the exact directory you want the file saved to each time, rather than it going to the directory in which the original file was created. There's gotta be a fix for this :) Your tip will help workaround it for now. Thanks Hila.
Photo of Scott K. Fineshriber

Scott K. Fineshriber

  • 1 Post
  • 2 Reply Likes
I'm with you all. Not overwriting the existing file when I tell it to, then saving another file with "copy" appended is ridiculous. I was already annoyed by how cumbersome it was to save a file without "copy" being appended, but at least it would show in the Save As dialog box before actually saving. Now it doesn't even show you, it just does it. Adobe needs to stop catering to first-time users with these types of "fool-proofing" features and take better care of long-time, professional users. We're not idiots. And they're wasting our valuable time.
Photo of C Tschumy

C Tschumy

  • 2 Posts
  • 0 Reply Likes
it will save over .psd files. Can't save over tif files... I dont know how long this will work but i thought that i would share my findings. 
Photo of C Tschumy

C Tschumy

  • 2 Posts
  • 0 Reply Likes
it will save over .psd files. Can't save over tif files... I dont know how long this will work but i thought that i would share my findings. 
Photo of McKay Andeson

McKay Andeson

  • 2 Posts
  • 1 Reply Like
YES!!! Please fix this ASAP! This means that if I want to make an update then I have to save, navigate to the appropriate folder, double check that I am deleting the right one, then delete, then rename the other one. And I have to do this EVERY TIME I need to resave my JPEG. It is ridiculous. 
Photo of Judith ten Velden

Judith ten Velden

  • 1 Post
  • 1 Reply Like
I hate it when computers want to "help" protect me from "human errors". It's the Microsoft paperclip and autocorrect allover. Might work for some people, but we should be able to turn it of, in a natural workflow.
Photo of Gordon Moir

Gordon Moir

  • 1 Post
  • 0 Reply Likes
If this is done by Adobe on purpose, then they need to give themselves an uppercut. It's causing all sorts of problems in my workplace by NOT overwriting the existing jpeg, even though the pop-up window says "xx.jpg" already exists. Do you want to replace it? I click "replace" but it doesn't replace it. Instead, adding another jpeg in the same location with "copy" added, leaving the original jpeg untouched. This affects InDesign docs where the jpeg is linked, as they are still linking to the old jpeg, not the updated, renamed "copy" version. This has resulted in incorrect artwork being dispatched. Please admit you messed up and fix it fast.
Photo of Michelle F.

Michelle F.

  • 1 Post
  • 0 Reply Likes
Having the same problem as Steven. I created a layered photoshop image and save it as .psd. Once finished I flattened the image and did a "SAVE AS" and chose JPEG. The file extension never changed to .jpg. It kept the .psd extension an over wrote my layered file. Which now can not be recognized by photoshop when I try to reopen it. have to start from scratch. 
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 2849 Posts
  • 1219 Reply Likes
Please read what Steven wrote. This is not the same problem. What you describe is the problem I mentioned above, where the file type is not updated. That problem should be fixed in the Photoshop 20.0.7 update that came out last week.
Photo of Steve Mabin

Steve Mabin

  • 3 Posts
  • 9 Reply Likes
I too have the exact same problem. I had an online chat with an adobe helper but he didn't seem to have any idea how to fix it. I'm not even sure he fully grasped what the problem was. I am going to get back to them tomorrow afternoon.
Photo of Steven Paslawsky

Steven Paslawsky

  • 4 Posts
  • 0 Reply Likes
exactly how my conversation went with adobe. The girl claimed that it has always been this way....
Photo of Hila Schurr

Hila Schurr

  • 7 Posts
  • 2 Reply Likes
Adobe online tech support is literally the worst.  don't waste your time.  It's a third-party outside the US.  very entry-level support.  
Photo of Lisa Wandrei

Lisa Wandrei

  • 6 Posts
  • 3 Reply Likes
It has not always been this way. It makes adjusting elements for indesign a nightmare.
Photo of Nadine Cormier

Nadine Cormier

  • 1 Post
  • 3 Reply Likes
Been having the same problem lately (NO it wasn't always like this!!) and it drives me insane!! 
Photo of McKay Andeson

McKay Andeson

  • 2 Posts
  • 0 Reply Likes
Definitely hasn't always been like this.
Photo of Elizabeth Scott

Elizabeth Scott

  • 5 Posts
  • 18 Reply Likes
I am having the same issue! I am working in Photoshop and wish to save my work as a .jpg -- no problem there. However, when I make changes (to the original layered .psd file) and try to save again as a .jpg --- it adds "copy" to the file name instead of overwriting the existing image. 

I'm "Save as > .jpg" - and then choosing the existing image location. I do get a prompt - "do you wish to overwrite" to which I say "Yes" ---- but still, "copy" is added to the file name and a new file is created, keeping the old file in tact. Annoying that I have to manually update the name, trash the old image, etc!
Photo of Jason Hughes

Jason Hughes

  • 5 Posts
  • 8 Reply Likes
Same problem here! And it just started doing this recently and is a massive time-leech deleting all these original (now unedited/un-updated) files and renaming the new file without "copy" in it. 
(Edited)
Photo of Dave Zambrano

Dave Zambrano

  • 2 Posts
  • 9 Reply Likes
Same problem here guys!  Photoshop will not overwrite a JPG, it adds "copy" to the filename which is so bad for my workflow.

I called photoshop support and they said it was a known bug, and would be fixed in the next update.  

I hope that's true....

Photo of Nichole Warman

Nichole Warman

  • 2 Posts
  • 0 Reply Likes
HAHAHAHAHAHA nope, sure wasn't. Running 21.2.0 and it's STILL wrong.
Photo of Sean Driver

Sean Driver

  • 1 Post
  • 0 Reply Likes
true and I just can't get used to it.
Photo of Steve Mabin

Steve Mabin

  • 3 Posts
  • 9 Reply Likes
Are we going to be compensated by Adobe for these major and time consuming faults in their program?
Photo of David Gill

David Gill

  • 6 Posts
  • 3 Reply Likes
Same here. Adobe please fix.
Photo of Mahee Velivela

Mahee Velivela

  • 3 Posts
  • 2 Reply Likes
Updated to version 21.0 but the jpg overwrite issue still remains. Waiting for a fix.
Photo of Alison Vella

Alison Vella

  • 15 Posts
  • 11 Reply Likes
Same here - Do you want to replace existing jpg? Pressing yes does not replace, but creates a copy.
This affects my work a lot.  If I overlook this, the wrong image is appearing on all the tablets of my salesreps.  Their software is looking for image A001.jpg not A001copy.jpg 
Photo of Alison Vella

Alison Vella

  • 15 Posts
  • 11 Reply Likes
This reply was created from a merged topic originally titled xyz.jpg already exists, do you want to replace it?.

Trying to save over an existing jpg image.  
xyz.jpg already exists, do you want to replace it?
Usually I simply say "replace" and it overrides the previous jpg.  Now it is letting me believe that all is good, HOWEVER it is creating a new file called xyzcopy.jpg

Photo of Nathan Bower

Nathan Bower

  • 1 Post
  • 2 Reply Likes
Same problem as everyone else and it's really messing up my organization as I like to save any edits over an existing file with the same name. Now I have to look for copy along with the original file name. What is going on? I finally decided to look this up because I knew this wasn't right.
Photo of Peter Heine Bech

Peter Heine Bech

  • 3 Posts
  • 7 Reply Likes
This reply was created from a merged topic originally titled Photoshop 2020 creates a copy instead of owerwrite jpg files..

When I save out a jpg file on top of an existing jpg to overwrite, Photoshop makes a new file with a " copy" in the end of the filename instead of owerwrite the original. Its extremely frustrating and it it is a huge part of the Photoshop to Indesign daily workflow for most graphics artists.

Photshop even gives me the popup saying that the file already exists and asks me if I want to replace it. I click "Replace" or "Overwrite" or whatever it is in english, and it creates a copy instead. And my linked jpg file in my Indesign layout of course isn't updated automatically and I have to find the file, delete the original and the rename the new copy so it has the same name as the original. This is a pretty huge game breaker in my daily workflow.
Photo of Melissa Linares

Melissa Linares

  • 21 Posts
  • 3 Reply Likes
Same problem. I want to Save As and replace a file, but it does not overwrite or replace, Photoshop adds "copy" to the end of the file name instead. Then I have to delete the old file and rename the new file by removing "copy" in the file name. It is happening with the TIFFs and JPEGs that I'm saving.
(Edited)
Photo of Leslie Stacks

Leslie Stacks

  • 7 Posts
  • 5 Reply Likes
In case you haven't seen my previous post about the solution:  I had this same issue -- could not overwrite an existing jpeg when saving with the same file name.  I contacted Adobe and got these instructions, which worked for me:  

1) Close all Adobe related processes in activity monitor (Creative cloud, Core sync, CC library, services for adobe desktop app, adobe desktop service, Adobe IPC broker, AAM updater)

2) Navigate to following locations and assign the current user full permissions to adobe folders. To navigate click go from menu bar at then click goto.. type /Library/application support/   and click go.

3) To assign the permission right click on adobe folder and click Get info.. A property window will open. Then click on lock symbol to enable editing. Then click + sign to add your username. Then change read only to read and write. Then click gear symbol at the bottom and click apply to enclosed items and click ok.
Photo of Leslie Stacks

Leslie Stacks

  • 7 Posts
  • 5 Reply Likes
Sadly -- after working for 1 day, this "fix" no longer solves the problem.
Photo of money_launderer

money_launderer

  • 3 Posts
  • 1 Reply Like
Oh hell no... Adobe needs to deploy a patch, not a convoluted workaround.
Photo of Teresa Weier

Teresa Weier

  • 7 Posts
  • 1 Reply Like
Thank You, Leslie!  Now it works as it always had.
Photo of Jacinthe Brault

Jacinthe Brault

  • 2 Posts
  • 1 Reply Like
This solution does not work for me.
Photo of Ninjapuss

Ninjapuss

  • 5 Posts
  • 0 Reply Likes
Thanks Leslie! Worked for me too. Hopefully it stays fixed. 
Photo of Ninjapuss

Ninjapuss

  • 5 Posts
  • 0 Reply Likes
Scratch that. Still broken and more annoying than ever.
Photo of Cezz

Cezz

  • 4 Posts
  • 0 Reply Likes
Hi, I found a fix. If you set your export, command +k > export to jpeg from png. Set the quality to 100. And then when you go to quick export, it overwrites the file. It took me a while to stop hitting the shortcut for save as, but that appears to be working for me.
Photo of Peter Heine Bech

Peter Heine Bech

  • 3 Posts
  • 7 Reply Likes
Has there been any word about this bug from Adobe? As I see it, it is one of the most serious issues for everyone working in the industry.  
Photo of Patrick Mauldin

Patrick Mauldin

  • 15 Posts
  • 20 Reply Likes
This reply was created from a merged topic originally titled Bug: Saving as a 'Copy' instead of Replacing file.

Since I upgraded Photoshop, it has been giving me this very annoying bug:

- I'll be working in my PSD file
- Then save as a jpg
- Go back to my PSD and make changes
- Save as jpg again with same name
- Says file must be saved as a copy (can't uncheck)
- In dialog box, I select Replace file
- Still saves with "copy" at the end of the file

Why can I not replace the original jpg with my new changes? Why do I have to save as a copy? Doesn't make any sense. Did not use to be this way.

Screenshots of process:




Photo of Dave Zambrano

Dave Zambrano

  • 2 Posts
  • 9 Reply Likes
Yup, multiple app updates and Mac OS Catalina updates and still no fix.  If anyone finds a solution besides waiting for adobe, please post it here.
Photo of Andrew Croft

Andrew Croft

  • 3 Posts
  • 10 Reply Likes
Possible solution is for all of us to switch to Affinity Photo. Clearly Adobe doesn't care enough about its subscription base to want to do anything anytime soon.
Photo of Kaleb Lopez

Kaleb Lopez

  • 5 Posts
  • 0 Reply Likes
The only way I was able to work around this problem is to first save your layered file, then flatten image, then save as and save the file with the same file name of the file that you are trying to replace. Annoying I know, but it works.
(Edited)
Photo of Philip Wels

Philip Wels

  • 12 Posts
  • 10 Reply Likes
I don't know enough about Photoshop actions, but would it be possible to make an action which would flatten the file, save it, and then unflatten it automatically?
Photo of Sophia Caldwell

Sophia Caldwell

  • 9 Posts
  • 3 Reply Likes
Yes, I did create an action for this. I'm happy to share, but I'm not sure if I can attach a file to this thread? Here are the steps to create the action:

1. Begin recording action.
2. Select all (Command + A)
3. Copy merged (Command + Shift + C)
4. Create a new document (Command + N) and 'Create'
5. Paste into the new document (Command + V)
6. Merge visible (Command + Shift + E)
7. Click the hamburger button (top right on your Actions Panel) and choose 'Insert Menu Item'. Ignore 'Insert Menu Item' popup and go onto step 7.
8. File > Save.
9. Select 'OK' in the 'Insert Menu Item' popup.
10. File > Close > Don't Save
11. Stop recording action.

This action takes the layers and copies them into another document, saves the file and then closes it. That way, there's no danger of you merging your original document by mistake.

Hope this helps!
Photo of Sophia Caldwell

Sophia Caldwell

  • 9 Posts
  • 3 Reply Likes
I am also having this issue. It is super annoying because I have to go through and rename all my resaved files after each resave!
Photo of Mark Larson

Mark Larson

  • 2 Posts
  • 6 Reply Likes
You guys are being too kind.  This is the most annoying Photoshop bug I've seen since Photoshop 3.0.  I know several Adobe developers and they are all very bright and capable guys.  They could have fixed this bug in minutes. This is Adobe management not caring about the end user.  They could have fixed and tested this bug in 1/100 time it takes to add a useless new "feature".
Photo of Patrick Mauldin

Patrick Mauldin

  • 15 Posts
  • 19 Reply Likes
Adobe has shown time and again they do not care enough about their users to do the necessary amount of QA before launching updates. They would rather just send it out and then work on it later.

I miss the days when companies had to actually ship a complete product and ensure as many bugs as possible were fixed before putting it on the market.
Photo of Andrew Croft

Andrew Croft

  • 3 Posts
  • 10 Reply Likes
I have stopped asking Adobe for any support of any kind because it is non-existent. There is just a room full of monkeys answering the chat/phone who simply look at a cheat sheet for the app and tell you what they read, not what they know. I too remember Adobe Illustrator 88 and getting phone support where the person clearly knew the app inside and out and was a professional. They use monkeys for this now.
Photo of James Gray

James Gray

  • 63 Posts
  • 31 Reply Likes
I am sorry that your experience is so bad.  My experience with Adobe support is much better.  If I were one of the Adobe support technicians, I am not sure I would be going out of my way to help a customer who thought I was a monkey.  I do think they have a problem triaging the support requests, many of which are likely resolved by consulting a cheat sheet.  Some of the request are over the head of the front line consultants.  It sounds like you have another issue than this annoying business with saving not resulting in writing over the original file when you tell Photoshop to replace.  I worked for 35 years as a software engineer and discovered that users cannot tell the difference between a 5 minute fix and 5 man-year enhancement.  Part of their problem is the upgrade by Apple to Catalina.  I am sure that Apple provided Adobe with a pre-release of Catalina.  I am equally sure that the version Apple released was not the same as the pre-release that they provided to Adobe.  I am scheduled today for a call from Adobe Tech support for an issue with Bridge.  Good luck to you.
Photo of Stokestack

Stokestack

  • 16 Posts
  • 1 Reply Like
This reply was created from a merged topic originally titled Photoshop saves as a copy when told not to.

Sometimes yes, I want to overwrite a file. Photoshop will confirm that I want to overwrite the file with the same name, and then... write it with a different name without my permission.

So there are two defects here: Ignoring my directive to save with the same name, and then prompting to overwrite but not doing so.

Photo of JWL

JWL

  • 3 Posts
  • 3 Reply Likes
Exact same issue as everyone. Waiting for a solution to this.
Photo of Llewellyn Martin

Llewellyn Martin

  • 3 Posts
  • 3 Reply Likes
Same issue here as well. Very frustrating and time consuming. 
Photo of money_launderer

money_launderer

  • 3 Posts
  • 1 Reply Like
I thought I was going nuts - looking for my file and Bridge was displaying all these damn copies... I'm like wtf Adobe thanks for tossing yet another wrench in there. And I thought missing file extensions was annoying, hah.
Photo of Stephane Lamontagne

Stephane Lamontagne

  • 2 Posts
  • 4 Reply Likes
Same issue here too. I was sure something was wrong. My files organisation had always worked well until that catalina update, with those copy I can't overwrite. They definitely should give us  a discount for paying such an undertested software that we pay overpriced. A solution Adobe? Now!
Photo of Lynn Lim

Lynn Lim

  • 1 Post
  • 1 Reply Like
Exactly. same issue on the save as jpg with copy instead of replacing. Other than that after update to Catalina PS 2020, my jpg, psd, tiff files are unreasonably HUGE. Cant solved the problem and uninstall PS2020 and use back 2019 (files size becomes normal). Anyone has the same problem here? Been using mac for the past 20 yrs and its getting worse after each update.  sigh.....