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

Drop JPG photos below — get a TIFF per file with LZW 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 / PackBits / uncompressed
Batch up to 20 files + ZIP
Multi-page TIFF combine + DPI tags to 600

Add your JPG files

Drag & drop JPG files here

or browse your files · you can also paste from clipboard (Ctrl+V)

Your browser decodes JPG natively — no decoder download, no waiting. EXIF rotation is applied, so phone photos come out upright.

No files yet. Everything stays on this device. Downloads start instantly.

TIFF settings

Output

One TIFF per file Each JPG becomes its own TIFF. Combine into one multi-page TIFF All JPGs become pages of a single TIFF, in list order.

Compression

LZW — lossless Best compression, the print standard. Default. PackBits — lossless Simple RLE for very old software that cannot read LZW. None — uncompressed Every pixel stored raw. Largest files.

Lossless: the decoded pixels are preserved exactly, whatever you pick.

DPI tag

72 DPIScreen use. 150 DPIDrafts, large prints. 300 DPIThe print standard. 600 DPIHigh-resolution print.

DPI is only a tag — it never changes the pixels, it tells print shops how large the image prints.

LZW is the faithful default. Lossless compression, the prepress standard — the same pixels as the JPG, stored without further loss.
Much larger than the JPG. A 1920×1080 photo is about 6 MB as an uncompressed TIFF and often under 300 KB as a JPG. Every file shows its size multiple honestly.
DPI tags are written, pixels are not resized. 72 / 150 / 300 / 600 DPI is recorded as XResolution and YResolution in inches.
EXIF orientation is applied, metadata is dropped. Phone photos stored sideways come out upright; camera data, including location, is stripped on re-encode.
Converting cannot restore detail. JPEG discarded it when the photo was saved; the TIFF holds the same pixels, only bigger.
Settings apply when files convert. Choose before adding files, or press Convert again after changing them.
25 MB per file, 20 per batch. No daily limit and no account — most JPGs are well under 5 MB.

Need a smaller file instead? Convert JPG to PNG — same privacy, lossless quality for photos.

Privacy you can verify, not just trust

Most online JPG 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 JPG 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 JPG 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 JPG to TIFF without uploading it

Every "free" online JPG 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 JPG here, your browser:

Decodes the JPG natively — every browser includes a JPG decoder, so there is no decoder file to download and no waiting for a library to load.
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.
Re-encodes the pixels as a TIFF with a pure-JavaScript TIFF encoder — little-endian header, one IFD per image, LZW, 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, coverters.com and jpg.now all convert server-side, and jpg.now caps free conversions at 10 a day), and the client-side ones we found are thin — one offers a quality slider only, with no compression choice, no DPI tags and no multi-page mode. This page is the only dedicated JPG-to-TIFF page we found that combines a batch of 20 files with a ZIP download, a genuine compression choice (LZW by default, PackBits or uncompressed), DPI tags from 72 to 600, a multi-page TIFF combine mode, EXIF rotation handling, 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 JPG?

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. For anything else — sharing, web, storage — keep the JPG or use JPG 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 .jpg is refused with a pointer to the matching converter. A corrupt or truncated JPEG is refused at decode time, 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 JPG stay blocky in the TIFF.

TIFFs are much larger than JPGs

Expect roughly 20× the size for an uncompressed TIFF of a photo, less with LZW. 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.

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 JPG files get uploaded anywhere?

No. Your browser decodes the JPG 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.

Will converting JPG to TIFF improve the quality?

No. JPEG throws away detail when it compresses a photo, and no converter can put it back. The TIFF holds exactly the pixels your browser decoded from the JPG — the same picture, losslessly stored. Converting to TIFF only stops further loss: unlike saving as JPG again, re-saving a TIFF never degrades the pixels.

Should I choose LZW, 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. PackBits is a simpler lossless RLE format for very old software that does not understand LZW. Uncompressed stores every pixel as 3 bytes with no compression at all — the largest files, useful only when the destination cannot decode either compression.

Which DPI should I choose?

DPI is only a tag — it never changes the pixels, it tells print shops and layout software how large the image prints. 72 DPI is for screen use, 150 DPI is fine for drafts and large prints, 300 DPI is the print standard, and 600 DPI is for high-resolution print work. A 300-DPI A4 scan is 2480 x 3508 pixels, about 26 MB uncompressed, so LZW matters at high DPI.

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 JPGs 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.

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. Greyscale JPGs stay greyscale in the pixels, stored as equal red, green and blue values.

Why is the TIFF so much bigger than the JPG?

JPG compresses photos lossily to a fraction of their raw size, while TIFF stores the decoded pixels losslessly — even LZW 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 JPG — roughly 20 times larger, less with LZW. This tool shows the original and TIFF size for every file, with the size multiple, so the trade-off is never hidden.