P: Saving copy not saving over jpg file

Report · Oct 23, 2019

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

Report · Oct 27, 2020

This is wild. A core function of the program is saving the file. Outrageous that this problem persists through multiple version updates. This with the move - unmove bug and constant freezing makes the app nearly unusable. I'm feeling marginalized and I'm a loyal, hardcore user.

Report · Oct 27, 2020

@Oliver Woodcock My best... er... guess... is that Adobe has decided that the "Export As..." feature is what everyone is "supposed" to use now. (I've given up an remapped cmd+shift+S to Export As...) Because that functions properly.

Of course, this is only helpful for people saving things as .jpg, .png, .gif, and .svg. It doesn't help anyone working with .tiff, .pdf, or even .psd.

I very much have the sense that Adobe is making decisions about how it thinks things should work, and then afterwards discovering that their userbase uses Photoshop in different ways than they expected.

If only they had a way to poll their audience, or ask users about usecases as they developed new features... oh well. Maybe someday we'll have the technology to do that.

Report · Oct 27, 2020

Then why does it give me the option to "save over" it in the first place? Shocks me that this is okay with Adobe QC professionals! Really a shame to say I'm losing faith, because I've been a brand advocate for DECADES. I'm sure I'm not alone here.

Report · Oct 27, 2020

Yep, me too. Been using since the very beginnings of Adobe. (Way before there was "autosave.") I always found the "Export as" function to be cumbersome and more geared towards web designers. I work primarily in print. Another work around I use is "copy all layers" then paste into a new file and save that. Seems so stupid. Like, a person should be able to SAVE A FILE HOWEVER THEY WANT AND WITH WHATEVER NAME THEY WANT, right? Don't make me come over there Adobe...

Report · Oct 27, 2020

Not only is this frustrating, some time in the past year, maybe since the last major version update, I have had a saving error issue in just clicking command + s or save from the file menu. Which is unrelated to this "save as" glitch, but it is a saving problem nonetheless.

I have seen other forum discussions on it, and I gave up and live with it. If I do a few changes or turn off and on a layer a few times, sometimes maybe just zoom in or out of the image, then click save, I'm able to get the save error to go away. This happens with mostly every file not like one or two files. The software has become so unstable and unreliable in the past few years.

Report · Oct 28, 2020

Let me just add how ticked off I am about being forced to use the alternate Quick Export to be able to save and replace. I just discovered that Quick Export changes whatever your file's resolution is to 72 dpi. Pixel depth does not change, meaning a 2000 x 2000 pixel image stays 2000 x 2000, but instead of being 300 dpi it's only 72 dpi. This affects how huge it is when Acrobat places images in a PDF for client approval. And if you're working on a team, and their files are 300 dpi at the same pixel depth, theirs will appear tiny.

Again, thanks, Adobe, for your complete lack of effort to fix this issue.

Report · Oct 28, 2020

@chazcron You are correct, the export feature is not a solution for many of us. I also tried with Export As, but the feature removes all the paths. My client needs the paths. They also want Tiff files so export is not a workaround for me.

Report · Oct 31, 2020

When I do a save as and chose to replace an existing file, It saves the new file as a copy, instead of replacing the old file, like I asked. Now, I have to go in and manually delete the old file and rename the new one. Could you please fix this.

Report · Oct 31, 2020

When I do a save as and chose to replace the old file, it saves thee new file as a copy and keeps the old file. The I have to delete the old file and rename the new one. Could you please fix this?

Wess

Report · Nov 01, 2020

Terrible this copy/save issue hasn't been resolved in over a year. Updates to Photoshop over this time have removed some basic editing and saving tools with no acknowledgement from Adobe about the removal, or any intention to fix what was not broken despite numerous threads here and other related PS forums. One example: now highlighting the entire file name with extension in the save panel instead of just the file name (older behavior). These seemingly mindless or careless changes ruin work flow. Why can't/won't Adobe fix these things? 😡

Report · Nov 04, 2020

STILL NOT FIXED!!

Please stop adding crap that I don't want!!!!

I just want Photoshop to work properly!! PLEASE!!!!!

Report · Nov 07, 2020

I can't believe that this problem hasn't been fixed for a year long... It's not a minor problem, overwriting an existing file is an everyday task in photoshop! We don't deserve to be using tricks or other software to be able to.. save a file!

Report · Nov 07, 2020

Another point to make. Adobe’s wonderful auto recovery feature. So you crashed. Great. Not unexpected. We are talking about Adobe. Regular crashing is still a thing. Relaunch Photoshop, Yay!! Your file is only missing five minutes of progress. Still stinks to be you if you’ve spent the last 5 minutes painstakingly using the pen tool for masking. Now what do you do? It’s a layered Photoshop file. You absolutely cannot save over your original. This bug has made sure of that. Thanks Adobe. Guess you’re gonna have to save as, go to the desktop, select the original, copy the full name, then, put an extra character in your original, Select the recovered file, paste in the other file’s name. Hope there isn’t some extra space in there somewhere, and move the obsolete original to the trash. But don’t empty the trash, just in case. Open the new file. Did it open? Yes. Good! Now you can close the “recovered” file, which will ask if you want to save changes. You nervously click no.

Boy, don’t you feel great now.

After a while, (we have had a year, after all) I discovered a better workaround. Open the original in Photoshop, drag the history of the recovered file into the original file. Of course, Adobe didn’t make it that easy. You can’t drag history from one file to another in tabs the way you can a layer. You have to be able to see both windows fully to be able to drag history from one file to another. Now you can save your original, because it has all the history of your recovered file. This way, there’s no space–copy suffix bug tomfoolery.

Report · Nov 13, 2020

Well, folks,

I installed Big Sur today strictly to see if our issue was resolved.

And lo-and-behold... IT's FIXED!!!!!

No more copies! Woohoo!!

Report · Nov 13, 2020

Going to be a while before I’m interested in trusting Big Sur especially being a Wacom user.

Report · Nov 13, 2020

My Intuos Pro is working fine so far 🙂

One unrelated issue I have found is VPN not working (Global Protect) on my work computer. I am sure I will discover more glitches as I open more apps 🙂

Report · Nov 13, 2020

@Angel_Jackson I installed Big Sur last night, and (unfortunately) the issue persists. Perhaps you tested using a flattened file?

(Also, my VPN works, as well as my Wacom Intuos Pro M tablet)

Report · Nov 13, 2020

@mattrock1 OMG! You are so right! I wanted it to be fixed so bad that I forgot it happens when you overwrite the jpg from a PSD🤦🏻‍:female_sign:

This makes me so sad and mad ... again!!!

I also fond out that my company has to provide us with a new version of the VPN. We have an archaic one that is not supported.

Report · Nov 13, 2020

Dammit. Was about to update to Big Sur but will now hold off. Thanks for the updates. Let’s hope that Adobe takes this one seriously, since logical and efficient file saving is such a core feature for even the most casual user.

Report · Nov 14, 2020

@Angel_Jackson yea a bit too early to celebrate. My favorite part is say you go to save "test.jpg" of the existing file. And you get the prompt:

“test.jpg” already exists. Do you want to replace it?" you hit replace it creates "test copy.jpg" Now back in your file, make change and say save as again to create "test.jpg" tell it to write over again but instead of making "test copy 2.jpg" which would almost make some kind of backward since it ACTUALLY copies over the file "test copy.jpg" so it CAN write over a file just not the right one. Sighhhh

Report · Nov 17, 2020

Ok, is this a bug or a feature, I can't figure it out...
Furthermore...

Why has this not been fixed yet?
I lost a layered file today because of this BS.
With all the great new features in 2021, this in itself makes me want to

go back to CS5 on my Mac mini, because I'm infuriated...
October of 2019... and all you are offering is A WORKAROUND???

Did we not just have MONTHS off to figure something like this out???
%#%$ @^ #*(@^ ?!?!?
INFURIATING!!!!

I should not have to rename a jpg every damn time I make a revision proof.
FIX THIS!!!!

FIX THIS OR REFUND ME!!!!

Report · Nov 17, 2020

Not Acceptable... FIX IT!!!

Report · Nov 17, 2020

I lost hours of work because of this today!!!!

Report · Nov 17, 2020

Still not fixed either...

Report · Nov 17, 2020

Still not Fixed... gRRRRR