Skip to main content
Inspiring
October 23, 2019

P: Saving copy not saving over jpg file

  • October 23, 2019
  • 834 replies
  • 29425 views

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

834 replies

Inspiring
November 17, 2020

This is a f****** joke. Adobe, act on this case. This has been a huge problem for so many of us, for over a year by now.

Participating Frequently
November 17, 2020

This is not fixed. This is a work around. When will we get an actual fix???
It has been over a year now!!!

Participating Frequently
November 17, 2020

So does no one at Adobe read these?

Participating Frequently
November 17, 2020

And Still not fixed!!!

Participating Frequently
November 17, 2020

Still not Fixed... gRRRRR

Participating Frequently
November 17, 2020

Still not fixed either...

Participating Frequently
November 17, 2020

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

Participating Frequently
November 17, 2020

Not Acceptable... FIX IT!!!

Participating Frequently
November 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!!!!

Inspiring
November 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