JPEG to JPG Without a Converter — Same Format, Just Rename (and Spot the .jpeg That's Really WebP)
An upload form says 'JPG only' and your photo ends in .jpeg. Before handing it to a converter site, know that there is nothing to convert: JPEG and JPG are two spellings of one format, and on Windows the change is a rename. I checked it on a Windows 11 PC — the file bytes, the registry, the old 8.3 short name that explains the three-letter spelling — and tested the cases where a rename is not enough: a .jpeg that holds WebP or PNG, and a folder where renaming runs into a name that already exists.

If the first bytes say WebP or PNG, drop the file in and save it as JPG. It decodes the file by its contents, so a WebP named .jpeg still converts. It runs in your browser; nothing is uploaded.
- ✓ Free
- ✓ No install, no sign-up
- ✓ Runs in your browser
- ✓ Files are never uploaded
- ✓ Open source
🔒 Your file is never sent to a server or anywhere else — it is processed only in your own browser.
JPEG and JPG are one format with two spellings
I copied a photo saved as photo.jpeg, renamed the copy to photo.jpg and compared them. Both were 36,816 bytes with the same SHA-256 hash (179cffca942d27d8…), and both start with FF D8 FF E0 00 10 4A 46 49 46 — the JPEG start-of-image marker followed by JFIF. A rename changes the name in the folder, not a single byte of the picture.
| Extension | Registry type on this PC | Perceived type |
|---|---|---|
| .jpg | jpegfile | image |
| .jpeg | jpegfile | image |
| .jpe | jpegfile | image |
| .jfif | pjpegfile | image |
Outside Windows it's the same story. The Library of Congress format description for JFIF lists jpg, jpeg, jpe, jfif and others as extensions of one format with the MIME type image/jpeg, and Microsoft's list of common file name extensions describes jpg and jpeg with the same words: 'Joint Photographic Experts Group photo file'.
Microsoft's documentation on file names explains the three letters: the MS-DOS FAT file system allowed 8 characters for the name and 3 for the extension. Today's file systems keep long names but can still create an 8.3 alias. On this PC's drive C:, dir /x showed photo.jpeg as PHOTO~1.JPE and holiday photo.jpeg as HOLIDA~1.JPE; drive D: showed no short names at all — Microsoft notes the alias can be turned off per volume.
That short name still matters in one odd place. On drive C:, dir *.jpe in Command Prompt and Get-ChildItem -Filter *.jpe in PowerShell both listed the two .jpeg files, because the pattern matched their short names. Keep that in mind before deleting or moving files by a *.jpe pattern.
Rename one file in File Explorer
- 1Make the extension visible: in File Explorer, select View > Show > File name extensions (Microsoft's own wording).
- 2Select the file and press F2 (or right-click → Rename).
- 3Change only
.jpegto.jpgand press Enter. - 4Windows warns that changing the extension might make the file unusable. For a real JPEG it doesn't — click Yes.
Don't skip step 1. With extensions hidden, the rename box shows only photo, and typing photo.jpg keeps the hidden .jpeg on the end — you get photo.jpg.jpeg. This PC already shows extensions and I left that setting alone, so I didn't reproduce it here; but a file I created named photo.jpg.jpeg was listed as a JPEG (not JPG) file, because only the part after the last dot counts.
If a form rejects the renamed file, the extension wasn't the problem — the next section shows how to check what's inside.
When a rename isn't enough: a .jpeg that's really WebP or PNG
The extension is only a label. A file can end in .jpeg and hold WebP or PNG data — for example when someone renamed it by hand, or a tool kept the old name. To test this, I saved the same picture as WebP and as PNG, named both .jpeg, then renamed those to .jpg too. Explorer's Type column labeled every one of them a JPEG/JPG file by extension alone (here 'ALSee JPEG File', since ALSee is this PC's default viewer). The first bytes told the truth.
Open PowerShell in the folder (in Windows 11, right-click an empty area of the folder → Open in Terminal) and look at the first line of Format-Hex:
Format-Hex .\photo.jpeg | Select-Object -First 1
# 00000000 FF D8 FF E0 00 10 4A 46 49 46 00 01 01 00 00 01 .Ø.à..JFIF......| Test file | First bytes | Inside | Rename to .jpg enough? |
|---|---|---|---|
| photo.jpeg | FF D8 FF E0 … 4A 46 49 46 (JFIF) | JPEG | Yes |
| fake_webp.jpeg | 52 49 46 46 … 57 45 42 50 (RIFF…WEBP) | WebP | No — still WebP after renaming |
| fake_png.jpeg | 89 50 4E 47 0D 0A 1A 0A | PNG | No — still PNG after renaming |
To check a whole folder, this reads only the first 4 bytes of each .jpg and .jpeg file and prints a True/False column:
Get-ChildItem -Filter *.jp*g | ForEach-Object {
$fs = [IO.File]::OpenRead($_.FullName); $b = New-Object byte[] 4
[void]$fs.Read($b, 0, 4); $fs.Close()
$h = ($b | ForEach-Object { $_.ToString('X2') }) -join ' '
[pscustomobject]@{ Name = $_.Name; First = $h; JPEG = $h.StartsWith('FF D8 FF') }
}Name First JPEG
---- ----- ----
fake_png.jpeg 89 50 4E 47 False
fake_png_renamed.jpg 89 50 4E 47 False
fake_webp.jpeg 52 49 46 46 False
fake_webp_renamed.jpg 52 49 46 46 False
photo.jpeg FF D8 FF E0 True
photo.jpg.jpeg FF D8 FF E0 True
photo_renamed.jpg FF D8 FF E0 TrueFor the False ones, convert instead of renaming. In Chromium 152 I gave a WebP and a PNG the type image/jpeg and the name disguised.jpeg; createImageBitmap — the call the Image Converter uses to read your file — decoded both by their contents. So the converter opens them despite the wrong name and saves a real JPG. For WebP files in general, see the WebP to JPG guide.
Rename a whole folder — and the file that gets skipped
In PowerShell, from inside the folder:
Get-ChildItem -Filter *.jpeg | Rename-Item -NewName { $_.BaseName + '.jpg' }Or in Command Prompt: ren *.jpeg *.jpg. I ran both on copies of the same test folder: 20 files img01.jpeg–img20.jpeg, 3 in capitals CAM1.JPEG–CAM3.JPEG, and dup.jpeg sitting next to an existing dup.jpg. Each command renamed 23 of the 24 .jpeg files (PowerShell took 0.37 s), the capitals included — they became CAM1.jpg — because Windows matches names without regard to case.
dup.jpeg stayed behind. PowerShell printed Rename-Item : Cannot create a file when that file already exists. and Command Prompt A duplicate file name exists, or the file cannot be found. Neither overwrote dup.jpg, which is good — but in a big folder that one red line is easy to miss. This version picks the next free name instead:
Get-ChildItem -Filter *.jpeg | ForEach-Object {
$new = $_.BaseName + '.jpg'; $i = 2
while (Test-Path -LiteralPath (Join-Path $_.DirectoryName $new)) {
$new = "$($_.BaseName) ($i).jpg"; $i++
}
Rename-Item -LiteralPath $_.FullName -NewName $new
}In a folder with a.jpeg, b.jpeg, x.JPEG and dup.jpeg — where dup.jpg and dup (2).jpg already existed — it produced a.jpg, b.jpg, x.jpg and dup (3).jpg, and left both existing files untouched.
The same one-liner works for .jfif files: change *.jpeg to *.jfif. Those are JPEG inside too — the JFIF to JPG guide covers why Chrome saves them that way.
FAQ
Q. Is JPG better quality than JPEG?
No. They are the same format, and renaming doesn't re-encode anything — the renamed file in this test had the same bytes and hash. Running it through a converter is what would re-compress it.
Q. Will renaming .jpeg to .jpg break the file?
Not if it's a real JPEG, i.e. its first bytes are FF D8 FF. Windows' warning about changing extensions is generic; in the registry both names point to the same jpegfile type.
Q. I renamed it and the site still rejects it.
Check the first bytes with Format-Hex. If they start with 52 49 46 46 (WebP) or 89 50 4E 47 (PNG), the file was never JPEG inside — convert it to JPG instead of renaming.
Q. Does upper-case .JPG or .JPEG matter?
Not to Windows: the bulk rename matched CAM1.JPEG with *.jpeg and Microsoft's naming rules say not to assume case sensitivity. The rename also turned the extension lower-case (CAM1.jpg).
Q. What about .jpe and .jfif?
On this PC .jpe maps to the same jpegfile type as .jpg and .jpeg. .jfif maps to pjpegfile but is still JPEG inside — rename it the same way.
If the first bytes say WebP or PNG, drop the file in and save it as JPG. It decodes the file by its contents, so a WebP named .jpeg still converts. It runs in your browser; nothing is uploaded.
- ✓ Free
- ✓ No install, no sign-up
- ✓ Runs in your browser
- ✓ Files are never uploaded
- ✓ Open source
🔒 Your file is never sent to a server or anywhere else — it is processed only in your own browser.
Comments 0
No comments yet. Be the first.
Only members can comment.
Comments with ads, abuse, personal information or illegal content are hidden or removed. Members who post ads, spam, or hateful content are removed from the site, and everything they wrote is deleted. Comments are shown with your nickname. Privacy Policy