P: Saving copy not saving over jpg file

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

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.

@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.

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.

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.

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...

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.

@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.

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.

Fix this!  Just go back to letting save the jpg by overwriting what is there.