Why this tool is different
Here is the thing nobody tells you: .jpeg and .jpg are the same format. The three-letter extension is a leftover from MS-DOS. So when a form demands a .jpg and you have a .jpeg, no conversion is needed — only a rename. Most online converters decode and re-encode anyway, quietly costing you quality for nothing. We verify the file really is a JPEG and give you back the identical bytes.
How it works
- 1
Add your .jpeg files.
- 2
We check the JPEG signature in the actual bytes.
- 3
The same bytes are handed back with a .jpg extension — nothing is re-encoded.
- 4
Download individually or as a ZIP.
What to watch out for
Genuinely lossless
The output is byte-for-byte identical to the input. Quality, dimensions, metadata and colour profile are untouched, because nothing is decoded in the first place.
If the file is not really a JPEG
Some files are named .jpeg but contain PNG or WebP data. We detect that from the magic bytes and tell you, rather than producing a file that fails on upload for a different reason.
You could do this yourself
Renaming the file in your file manager achieves the same thing. This tool is for when you have fifty of them, or when the extension is hidden and you cannot get at it.
Frequently asked questions
Is there any difference between JPG and JPEG?
No. They are the same format. Early Windows only allowed three-letter extensions, so .jpeg became .jpg, and both stuck.
Does this lose any quality?
None at all. The file is not decoded or re-encoded — the identical bytes come back with a different extension.
Why does the upload form reject .jpeg then?
Because it is checking the extension text rather than the file contents. It is a limitation of the form, not of your image.
Are my files uploaded to a server?
No. The conversion runs in JavaScript and WebAssembly inside your own browser. Open your devtools, switch to the Network tab and run a conversion — there is no upload request to see. Closing the tab clears the working session.