JFIF to TIFF, lossless and private. Nothing ever uploads.

Drop JFIF photos below — get a TIFF per file with LZW or Deflate compression and print-ready DPI tags, in batches of up to 20. Converted entirely on your device.

Your file data never leaves the device
LZW / Deflate / PackBits / uncompressed
Batch up to 20 files + ZIP
Multi-page TIFF combine + DPI tags to 600

Privacy you can verify, not just trust

Most online JFIF converters upload your photos to their servers first — and some keep a download link live for hours afterwards. This one can't: your browser decodes JFIF natively and the TIFF encoder runs entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no decoder to download and no file fetched after load for the conversion itself. Don't take our word for it:

New cross-origin requests during use: 0

Press F12 to open developer tools, then the Network tab.
Convert any JFIF above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
Extra credit: disconnect your internet after this page loads — conversion still works.

How to convert JFIF to TIFF without uploading it

Every "free" online JFIF converter you've used uploads your photos to a company server, converts them there, and — in several documented cases — keeps a copy or a live download link for hours. For personal photos and anything you wouldn't post publicly, that's an unnecessary risk. The safer approach is to convert the file where it already is: on your own device.

This tool does exactly that. When you drop a JFIF here, your browser:

Decodes the JFIF natively — a JFIF file is an ordinary JPEG, and every browser includes a JPEG decoder, so there is no decoder file to download and no waiting for a library to load. The JFIF header version (for example JFIF 1.01) is detected and shown on each file card; a plain JPEG with no JFIF header converts exactly the same way.
Reads the photo's EXIF orientation data and stores the output upright, so a portrait phone photo doesn't come back sideways. The rest of the EXIF data, including location, is dropped.
Optionally resizes the decoded pixels to your chosen preset or custom size — never upscaling — then re-encodes them as a TIFF with a pure-JavaScript TIFF encoder: little-endian header, one IFD per image, LZW, Deflate, PackBits or no compression, and the DPI you chose written as XResolution and YResolution tags. Your original file is never modified.

What makes this converter different

The converters that top the results for this search mostly upload your files to a server (XConvert, Zamzar, Convertio and FreeConvert all convert server-side, and XConvert's compression choice and resize come at the cost of sending your photos away), and the one dedicated client-side rival we found, Picflow, is thin — browser-based batch conversion with no compression choice, no multi-page combine and no EXIF handling stated. This page is the only dedicated JFIF-to-TIFF page we found that combines a batch of 20 files with a ZIP download, a genuine compression choice (LZW by default, Deflate or PackBits, or uncompressed), DPI tags from 72 to 600, a multi-page TIFF combine mode, EXIF rotation handling, JFIF header detection, resize presets, and a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to, no daily limits, no account and no watermark.

When is TIFF the right choice for a JFIF?

When the destination demands it: print shops and scanning bureaus that ask for TIFF, archives that store images losslessly, and layout software (InDesign, QuarkXPress and their peers) that places TIFFs at a stated DPI. TIFF is also the format for multi-page scans — one file, one page per image. That is exactly the situation Chrome and Edge create: they save downloads as .jfif, and the print shop, scanner or archive on the other end wants .tif. For anything else — sharing, web, storage — keep the JFIF or use JFIF to PNG instead and keep the smaller file.

Files are checked by their contents, not their name: a JPEG saved as .txt still converts, because the FF D8 FF header is what matters, while a PNG renamed to .jfif is refused with a pointer to the matching converter. A corrupt JPEG is refused by its header, and a truncated JPEG — one that ends before its image data finishes — is refused once the whole file is read, with a per-file error explaining what happened.

Honest limitations

No quality recovery

JPEG throws away detail when it compresses. A TIFF holds the same decoded pixels, losslessly — it cannot put back what JPEG discarded. Blocky artefacts in the JFIF stay blocky in the TIFF.

TIFFs are much larger than JFIFs

Expect roughly 20× the size for an uncompressed TIFF of a photo, less with LZW or Deflate. A 300-DPI A4 scan is about 26 MB uncompressed. Every file shows its size multiple honestly, and the batch bar shows the total before you download anything.

Resizing is lossy

Resizing resamples the decoded pixels, so detail is lost — the TIFF only preserves the resized pixels losslessly. Keep Original when quality matters most, and remember a resize never upscales: a small image stays small.

8-bit RGB only

Output is 8-bit RGB — no 16-bit, no CMYK, no alpha channel. A 16-bit or CMYK source is flattened to 8-bit RGB on decode, because that is what the browser decoder hands over.

Multi-page TIFFs are not universal

Multi-page TIFFs open in most viewers, but some old software shows only the first page. If the destination is old or unknown, send one TIFF per file instead.

DPI is only a tag

The DPI you pick never changes the pixels — it only records how large the image prints. A 72-DPI tag on a 4000-pixel photo still prints large; the pixels are what they are.

Metadata is stripped

Camera metadata (EXIF, including location) is dropped on re-encode. The orientation tag is read and applied first, so the output is stored upright. There is no text layer, no OCR, and nothing searchable is added.

Frequently asked questions

Do my JFIF files get uploaded anywhere?

No. Your browser decodes the JFIF natively and the TIFF encoder runs entirely in your browser, so your file data never leaves the device. The only third-party requests are the site's own analytics, which count page views. You can verify it in your browser's Network tab, or disconnect from the internet after the page loads — conversion still works.

What is a JFIF file — and is it different from a JPG?

A JFIF file IS a JPEG: JFIF is the header (the APP0 segment) that Chrome, Edge and many cameras write at the start of an ordinary JPEG — the same bytes as a .jpg, only the extension differs. A TIFF cannot wrap those bytes the way a PDF can, so converting means decoding the JPEG and re-storing the pixels losslessly as a TIFF. That also means a TIFF cannot restore detail the JPEG threw away when the photo was saved: it holds exactly the pixels your browser decoded, and only stops further loss.

Should I choose LZW, Deflate, PackBits or no compression?

LZW is the default and the right choice for almost everything: it is lossless, it shrinks photos and line art well, and it is the prepress standard every print shop and layout program reads. Deflate is also lossless and usually makes the smallest files of the four — pick it when file size matters and the destination is modern software. PackBits is a simpler lossless RLE format for very old software that does not understand LZW or Deflate. Uncompressed stores every pixel as 3 bytes with no compression at all — the largest files, useful only when the destination cannot decode any compression.

What happens to EXIF data and photo orientation?

EXIF metadata, including location, is dropped on re-encode — the TIFF carries no camera data at all, only dimensions and the DPI tags you chose. The EXIF orientation tag is the exception: it is read before encoding and applied, so a phone photo stored sideways comes out upright in the TIFF. Rotated photos are re-encoded upright, which is lossy; upright files keep their original pixels. Greyscale JFIFs stay greyscale in the pixels, stored as equal red, green and blue values.

What is a multi-page TIFF and when should I combine files?

A multi-page TIFF is one file holding several images, one per page — the format scanners and archives use for a document of many pages. Choose the combine mode when the JFIFs belong together as one document, for example the pages of a scan, and keep one TIFF per file when each photo is separate. Multi-page TIFFs open in most viewers, but some old software shows only the first page.

Can I resize my images while converting?

Yes. Choose Original to keep every pixel, 50% or 25% to halve or quarter each side, a width preset (1920, 1280 or 800 pixels), or a custom width and height with the aspect lock on — locked, the image fits inside your width and height without stretching; unlocked, it is stretched to exactly that size. Resizing never upscales: a smaller image stays small. Resizing resamples the pixels, so it is lossy — keep Original when quality matters most.

Why is the TIFF so much bigger than the JFIF?

JFIF compresses photos lossily to a fraction of their raw size, while TIFF stores the decoded pixels losslessly — even Deflate only compresses them, it never throws detail away. A 1920x1080 photo is about 6 MB as an uncompressed TIFF and often under 300 KB as a JFIF — roughly 20 times larger, less with LZW or Deflate. This tool shows the original and TIFF size for every file, with the size multiple, so the trade-off is never hidden. JPEG has no transparency, so there is nothing transparent to preserve, and the TIFF carries no metadata beyond the DPI tags you chose.