JPEG to JPG
Rename JPEG files to JPG with zero quality loss, right in your browser. Free and private; satisfies uploaders that insist on .jpg.
About this tool
JPEG and JPG are the exact same format; .jpg exists only because 1990s Windows limited extensions to three letters. Unfortunately, some strict upload systems whitelist one spelling and reject the other. This tool hands your file back with the .jpg extension, byte-for-byte identical.
No re-encoding happens, so it is instant and completely lossless, and it runs entirely in your browser.
Common uses
- Satisfy upload forms that reject .jpeg but accept .jpg
- Normalize file extensions across a batch of photos
- Fix files exported by Mac software with the four-letter extension
Automate via API
The same conversion is available as a REST endpoint for scripts, pipelines, and backends. POST the file, get the converted file back:
curl -X POST https://formatably.com/api/v1/tools/jpeg-to-jpg \ -H "X-Api-Key: YOUR_API_KEY" \ --data-binary @photo.jpeg \ -o photo.jpg
Direct requests accept up to 4 MB; the large-file flow handles up to 100 MB. Both are covered in the API documentation · Get an API key
JPEG notes
JPEG and JPG are the same format; the three-letter version exists because ancient Windows systems only allowed three-character extensions. Some strict upload forms nevertheless insist on one spelling.
- .jpeg and .jpg files are byte-identical; only the file extension differs.
JPG notes
JPG (JPEG) is the universal photo format: every camera, phone, website, printer, and government upload form accepts it. It compresses photos well but does not support transparency, and each re-save loses a little quality.
- JPG has no transparency; transparent areas are filled with white during conversion.
- JPG is lossy: converting into it trades a small amount of quality for compatibility and size.
Frequently asked questions
Is there any difference between JPEG and JPG?
No difference at all in the file content. JPG is just the three-character spelling of JPEG, a relic of MS-DOS and early Windows filename rules.
Does the conversion change my photo at all?
No. The image data passes through byte-for-byte; only the filename extension changes. There is no re-encoding, no quality loss, and no change to metadata.
Are my files uploaded to a server?
No. The conversion runs entirely in your browser using WebAssembly and the canvas API; your files never leave your device. There are no ads and no trackers on tool pages. You can verify this yourself: open your browser's developer tools, watch the Network tab while converting, and you will see no upload requests. It even works offline once the page has loaded.
Is there a file size limit?
In the browser there is no hard limit; you are bounded only by your device's memory, and files of a few hundred megabytes are usually fine. The REST API accepts files up to 4 MB in a direct request, or up to 100 MB using the large-file upload flow described in the API docs.
Related tools
Convert PNG to JPG in your browser. Free, private, no upload. Shrinks big PNGs into email-friendly, uploadable JPGs.
Convert JFIF files to JPG instantly in your browser, zero quality loss. Free and private; fixes web-saved images Windows names .jfif.
Convert iPhone HEIC photos to JPG in your browser. Free, private, no upload: files never leave your device. Batch convert supported.
Convert WebP images to JPG instantly in your browser. Free, private, no upload. Fixes images saved from the web that won't open.