If a form says "JPG only" and your file ends in .jpeg, you may wonder whether you need to convert it. You almost never do: JPG and JPEG are the same format, byte for byte. The difference is only the spelling of the file name, and it dates back to the 1990s. Here is where the two names came from, what the rarer .jfif and .jpe endings are, and what to do when a portal still says no.
Are JPG and JPEG the same thing?
Yes. JPEG is the name of the image compression standard, created by the Joint Photographic Experts Group and published in 1992. .jpg and .jpeg are two file extensions for files made with it. The data inside is identical, the official media type for both is image/jpeg, and every viewer opens both.
You cannot tell the two apart by quality, size or colour. A photo saved as photo.jpeg and renamed photo.jpg is the same file — the same bytes, the same pixels, the same KB. Converting a .jpeg "to JPG" in an editor only changes the name, unless the editor re-saves the image, in which case it also adds a small amount of fresh compression.
Why are there two spellings?
Because of MS-DOS. Early Windows and DOS file names allowed only eight characters, a dot and a three-letter extension, so .jpeg had to be shortened to .jpg. Mac and Unix systems had no such limit and used .jpeg. When Windows dropped the limit, both spellings were already everywhere.
Cameras and phones mostly settled on .jpg (often in capitals, .JPG), web software uses either, and the official IANA registration for the image/jpeg media type lists both jpg and jpeg as extensions. Neither spelling is more correct; .jpg is simply more common.
What are .jfif and .jpe files?
They are JPEGs too. JFIF — the JPEG File Interchange Format — is the standard wrapper most JPEG files use, so a .jfif file is an ordinary JPEG with an unusual extension. .jpe is another old short form. Both open as normal photos once renamed to .jpg.
You usually meet .jfif by accident: on some Windows PCs, images saved from a browser come out as .jfif because of a file-association setting, even though the website served a normal JPEG. The picture looks fine, but a portal that only allows ".jpg" or ".jpeg" in the file name refuses it. Renaming fixes it, or use JFIF to JPG if you would rather not touch file extensions.
| Extension | What it really is | Rename to .jpg? |
|---|---|---|
| .jpeg / .JPEG | JPEG | Safe |
| .JPG (capitals) | JPEG | Safe — some portals are case-sensitive |
| .jfif / .jpe / .jif | JPEG (JFIF wrapper or old short form) | Safe |
| .png | PNG — a different format | No — convert with Image to JPG |
| .webp | WebP — a different format | No — convert |
| .heic / .heif | HEIC (iPhone) — a different format | No — convert with HEIC to JPG |
Why does a portal reject my .jpeg or .jfif file?
Usually because the upload form checks the file name, not the image. Many government and exam portals have a fixed list of allowed endings — sometimes only ".jpg", sometimes not even ".JPG" in capitals. A perfectly valid JPEG named .jpeg or .jfif fails that text check.
Stricter portals also read the first bytes of the file. Every JPEG starts with the same signature (the hex bytes FF D8 FF); a PNG starts with a different one. If you renamed a PNG to .jpg, the name check passes but the signature check fails, often with an unhelpful "invalid file" message. Rarer causes include CMYK JPEGs straight from some office scanners, which certain validators and browsers handle badly, and files that are simply over the KB limit. The photo checker reads the real format from the bytes, so you can see which problem you have.
Renaming vs re-encoding: which do you need?
Rename when the file is already a JPEG and only the ending is wrong — .jpeg, .JPG, .jfif. It is instant and loses nothing. Re-encode, meaning convert, when the file is really PNG, WebP or HEIC, or when you also need to change its pixels or KB anyway.
- Windows: in File Explorer turn on View → Show → File name extensions, then rename and confirm the warning.
- Mac: select the file, press Return, edit the ending, and choose "Use .jpg".
- Phone: many file managers hide or lock the extension. It is easier to run the file through a converter that saves a .jpg — JPEG to JPG or JPG to JPEG if a form insists on the long spelling.
Converting re-saves the image, which is lossy, but at a high quality setting the change is invisible. If the form also has a size limit, do it in one step: the exam resizers and compress to custom size always output a genuine .jpg.
Frequently asked questions
- Is JPG better quality than JPEG?
- No. They are the same format; only the extension differs. Quality depends on the compression setting used when the photo was saved, not on whether the name ends in .jpg or .jpeg.
- Can I just rename .jpeg to .jpg?
- Yes. The bytes do not change, so nothing is lost and the file stays a valid JPEG. The same is true for .jfif and .jpe.
- Why do my downloaded images save as .jfif?
- On some Windows PCs a system setting maps the image/jpeg type to the .jfif extension, so browsers name saved JPEGs that way. The image is a normal JPEG; rename it to .jpg or change the default.
- Does converting JPEG to JPG reduce quality?
- A pure rename does not. A converter that re-saves the image adds a tiny amount of compression, invisible at high quality. Avoid converting the same file over and over.