JFIF to JPG converter
Save JFIF images with a JPG extension while preserving their original bytes by default, locally in your browser without uploading.
1 KB = 1000 bytes. JPG and WebP use automatic quality and may shrink further to meet the target. PNG ignores this setting. A target is not guaranteed.
Resize settings
Keep small images sharp: Contain adds margins without enlarging pixels; Cover and Stretch may return smaller dimensions. SVG scales freely, with a maximum side of 4096 px.
Presets use Exact size and Cover. Disable “Do not enlarge” if a small image must fill the preset. The passport preset is 413 × 531 px, approximately 35 × 45 mm at 300 DPI. Set 300 DPI when printing; this preset does not write DPI metadata or check official photo requirements.
Enter whole pixel dimensions from 1 to 20000. Rendering is limited to 64 million pixels per image; available device memory may impose a lower limit.
For JPEG input with Keep size and no target: save the original bytes as .jpg. Quality and background settings do not affect these files. Original metadata, including EXIF and GPS, stays in the file.
| File | Before | After | Download |
|---|
Everything runs in your browser. Re-encoding removes EXIF metadata, including GPS, and applies the image orientation.
Rename-only output is the exception: it preserves the original file and all its metadata.
PNG preserves the decoded pixels but cannot recover detail already lost in the source. Animated images become a still image of the first frame. Very large batches depend on device memory.
Change a JFIF file into a JPG copy
- For JFIF to JPG, select the JFIF image whose extension is causing trouble in an upload form or application.
- Keep the default “Keep original quality (rename only)” option enabled to avoid another encoding pass.
- Leave the dimensions unchanged and the target size empty so rename-only processing remains available.
- Look for “Unchanged” in the results: it indicates that the output keeps the original file bytes.
- Download the .jpg copy, or disable rename only first if you specifically want to re-encode with a quality setting.
Situations where renaming is enough
- Resolve a filename extension restriction on a form that expects .jpg.
- Give a downloaded JPEG image the extension requested by a colleague.
- Avoid adding compression artefacts to an already compressed photograph.
- Standardise image filenames while keeping embedded camera information intact.
- Choose deliberate re-encoding when a smaller JPEG matters more than identical bytes.
Understanding JFIF and JPEG
Is JFIF a different image codec?
A JFIF file is already a JPEG image with a different extension. In many workflows, saving the same data with a .jpg name is all that is required.
Does rename only change the quality or size?
It changes neither the encoded image nor its byte count. For example, a 240000-byte JFIF remains 240000 bytes in the downloaded JPG copy.
Why does the quality slider have no effect?
The original data bypasses re-encoding while rename only is active. Disable that option to make the quality setting affect a newly encoded JPEG.
Are GPS coordinates removed when I rename?
No. Original metadata, including EXIF and any stored GPS coordinates, remains in the file. Re-encoding removes that metadata and applies image orientation instead.
When is rename only unavailable?
It requires recognised JPEG input, JPG output, unchanged dimensions and an empty target-size field. Requesting resizing or a target means the pixels must be encoded again.
Can changing the extension repair a broken image?
Renaming does not repair damaged JPEG data or bypass an application's other restrictions. The source must still decode successfully, and very large images depend on available device memory.