JFIF to JPG

Convert JFIF to JPG in your browser. Nothing is uploaded.

Free, no limit Nothing uploaded No watermark Works on mobile

Drop your JFIF files here

Drop as many JFIF files as you like. Nothing is uploaded.

Choose files

A JFIF is already a JPEG with a confusing name

JFIF stands for JPEG File Interchange Format, and it is the standard container that virtually every JPEG on Earth already uses. A file named .jfif and a file named .jpg usually contain the same thing, byte for byte.

The problem is purely the extension. Windows sometimes saves images from a browser with a .jfif extension because of a registry association, and then Windows itself refuses to open them, along with most upload forms, which check the extension rather than the contents.

This tool decodes the image and writes a clean, correctly named JPG. That guarantees the file is valid rather than merely renamed, which matters if the source was actually a PNG or WebP that got the wrong extension somewhere along the way.

A JFIF file being renamed and re-encoded as a standard JPG
How it works

Three steps, no upload

Your browser does the decoding and the encoding. There is no queue and no waiting.

1

Add your files

Drop in as many JFIF files as you like, or pick them from your device.

2

Check the settings

There is nothing to set. The output is JPG, which is what this page is for.

3

Download

Each file is ready straight away, with its old and new size shown. Take them one by one or as a zip.

JFIF and JPG, side by side

JFIF, what you have

Not a separate format at all. JFIF is the standard container that nearly every JPEG already uses, so a .jfif file and a .jpg file usually hold identical data.

Where it works: Anything that reads JPG, provided the software looks at the contents rather than the extension. Windows and most upload forms look at the extension.

JPG, what you get

The oldest and most widely supported image format there is. It throws away detail your eye is unlikely to notice, which is why photographs end up several times smaller than they would otherwise be.

Where it works: Everything. Every browser, every operating system, every printer, every upload form and every television made in the last thirty years.

Both formats are lossy, so this is a second compression pass over an image that has already been compressed once. At a high quality setting that is not visible, but it is a reason to convert from your best original rather than from a copy of a copy.

How these formats compare

The four things that decide which format you should be using, for every format involved on this page.

FormatCompressionTransparencyAnimationIntroduced
JFIFLossyNoNo1992
JPGLossyNoNo1992
PNGLosslessYesNo1996
WebPLossyYesYes2010

Age matters more than it looks. A format introduced in the 1990s is read by everything ever made, and one introduced in the last ten years is read by browsers and very little else. That single fact explains most of the reasons people convert images at all.

What happens to the file size

Expect a moderate change either way. Both formats compress lossily, so the result depends on which encoder handles your particular image better and on how much detail your particular image holds.

Two things drive the number more than the format does. The first is the content: a photograph of a landscape holds far more unique detail than a screenshot of a spreadsheet, and detail is what costs bytes. The second is the pixel dimensions, which no format conversion changes. A twelve megapixel photograph is twelve megapixels whatever container it sits in.

If you need to hit a specific size rather than simply make the file smaller, converting is the wrong tool. Our image compressor takes a target in kilobytes and finds the highest quality that fits under it, which is what upload forms with a stated limit actually require.

Why Windows keeps producing these

The cause is a registry entry that some browsers and Windows updates change.

  • Saving images in Chrome or Edge on Windows, which picks the extension from a system MIME association that can be set to .jfif.
  • Copying an image out of an email client, which does the same thing.
  • Certain scanner and camera utilities that write .jfif deliberately.

You can fix the cause in the Windows registry by changing the extension associated with the image/jpeg content type, though that is an awkward thing to recommend to anyone who did not go looking for it. Converting the file is quicker.

Everything runs on your device

There is no upload. Your browser decodes the file, draws it onto a canvas in memory and encodes it again in the format you asked for. The picture never travels anywhere, no server sees it, and nothing is stored or logged.

That matters most for the images people actually convert: identity documents, medical scans, private photographs, unreleased design work. On a conventional converter every one of those is copied to a machine you do not control, kept for some period you are not told about, and processed by software you cannot inspect.

It is also simply faster. There is no queue, no upload wait and no download wait, so a large batch finishes in the time it takes to read this paragraph. The only real limit is your device's memory, and a modern phone handles dozens of full resolution photographs without difficulty.

Your filename is kept

The converted file keeps the name you gave it, with only the extension changed. Nothing is appended, no brand is inserted and no counter is added. These files get uploaded straight into forms that sometimes check the name, and an unexpected one is one more thing that can be rejected for no good reason.

There is no watermark either, at any size, on any number of files. A watermark on a free converter exists to sell you the paid version, and we would rather not have that conversation with you at all.

Converting several files at once

Drop as many files as you like. Each one is converted separately and appears in the list with its original size, its new size and the difference between them, so nothing about what happened is hidden from you.

Download them one at a time, or use Download all to take the whole set as a single zip. The archive is built in your browser too, from the files already sitting in memory, so it costs one click and no waiting. Images are already compressed, so the zip stores them rather than compressing them again, which would only make the file larger.

If a file cannot be read, that row says so and the rest carry on. One awkward file in a folder of fifty does not stop the other forty nine.

What happens to the metadata

The conversion decodes the picture and encodes it again, so the embedded metadata does not travel with it. That includes EXIF data: the camera model, the exposure settings, the date, and on a phone photograph the GPS coordinates of wherever it was taken.

For most people that is a benefit rather than a loss. A photograph taken at home and uploaded to a public listing carries the location of your home inside it unless something strips it, and very few sites do. Converting the file removes it as a side effect.

If you actually want the metadata kept, for a photography portfolio or a copyright claim, this is the wrong tool and you should keep the original alongside the converted copy. Colour profiles are handled the same way: the image is converted into the standard sRGB space that browsers and the web use, which is right for anything published online and wrong for a print workflow that depends on a wider profile.

FAQ

JFIF to JPG

The questions people ask most about this conversion.

Almost always, yes. JFIF is the standard container format for JPEG data, and nearly every .jpg file is technically a JFIF file. Only the extension differs.

Usually, yes. Changing the extension to .jpg works most of the time. Converting is safer, because it verifies the file really is a JPEG and produces a clean one either way.

There is one re-encoding pass, so a very small amount at a high quality setting. It is not visible in normal viewing.

A registry association for the image/jpeg content type is set to .jfif on some installations. Browsers follow it when saving, and then other Windows software refuses the result.

Completely, with no limit on how many files you convert or how large they are. There is no account, no paid tier and no watermark, because the conversion runs on your device and costs us nothing to provide.

No. Your browser decodes and re-encodes the image in memory on your own machine. Nothing is transmitted, nothing is stored and nothing is logged. You can disconnect from the internet after the page loads and it will still work.

No. There is no watermark, no logo and no added border, whatever the file size and however many you convert.

Yes. Only the extension changes, so a file called scan-final.jfif becomes scan-final.jpg. Nothing is added to the name.

Yes. Drop a whole folder in and each file is converted separately, then download them individually or take the entire set as one zip built in your browser.

Yes, on both iPhone and Android. The layout adapts to a narrow screen and the conversion uses the same browser image pipeline your phone already relies on.

Need a different conversion?

Over a hundred free tools, all running in your browser. Nothing is uploaded and nothing is capped.