.jpg and .jpeg file extension inconsistency
Using the Bridge 2020 Export panel to export images as JPEG files produces files with .jpeg extension whereas using the Photoshop Image Processor produces files with .jpg extensions. This is inconsistent behaviour. Could we have the choice of which extesion we would like please?

-
Kukurykus commented
-
Michael Kormos commented
Our online photo management system reads JPEG files and corrupts them for some reason. Their tech support advised us to upload JPG instead of JPEG. For some reason Adobe Bridge developers have yet to give us an answer why they force all exports with JPEG extension. Please fix this. Our photo studio is jumping through hoops because of this.
-
Giulio commented
completely agree also for the possibility to choose, maybe directly in "export" and also in the raw camera processor, or in preferences
-
Paul commented
This is real problem. Not even Mac publishers want this.
-
Valdur Rosenvald commented
Looking forward to the fix!!!!!!!!!!
-
Keith Brown commented
I cannot use bridge if the file extension is different to that used by lightroom on export. I need to end up with one single set of exported files regardless of the software used to create them. Bridge has now become a singular problem in my workflow.
-
Stephen Marsh commented
Photoshop throws a warning that the the .JPEG extension is non-standard (for Photoshop).
More here:
https://community.adobe.com/t5/photoshop-ecosystem-discussions/jpg-jpeg/m-p/12760785
-
Birnou commented
both extension nomination must be accessible and include in all export
-
Alex Alden commented
It's indefensible not offering the choice and in addition it's an inconsistent, lazy implementation not to take this into consideration considering that both are widely used and that adobe has always defaulted to .jpg in the past.
People have systems and processes and these details do matter. Batch rename makes it worse, as it creates a duplicate if file allready exists which makes more and more mess.Slow. Hand. Clap. for Adobe.
This needs fixing. -
Alex Alden commented
batch rename doesn't work I guess as I need it to overwrite for my workflow.
this is an impressive oversight from adobe. Export is entirely useless to me because of this.
To fix it's just one character.
-
Daan commented
Its not a solution, but a workaround;
After the files have been saved as a jpeg
create a Batch rename with NEW EXTENSION as NEW FILE NAME.
And DONT forget to only selected jpegs....;-) -
Paul commented
Is this being addressed? Or is Adobe trying to change the extension to jpeg to purposely conflict with other software? Not being facetious, actually wondering because this is often a marketing strategy.
-
Wes Duenkel commented
Every other Adobe application saves files as "jpg"
Why on earth would Bridge start exporting as "jpeg"
It makes NO sense, and especially if you want an exported file to overwrite a file made in another application, such as Photoshop.
Baffling.
-
RF commented
I agree, also for the ".tiff" and ".tif" and where is the option for LZW? ZIP only?
-
Andreas Fenrich commented
I also have problems with the file extension "jpeg" because my CMS requires the extension "jpg". It would be great if this could be adapted.