Convert TIFF to JPG

Drop a TIFF below and get a JPG you can email, upload or print. JPG is already selected. Files go up to 16 MB as a guest, 32 MB with a free account and 90 MB on a paid plan, which is where big scans usually need to be. Free. No account, no watermark.

  • JPG already selected
  • TIF and TIFF accepted
  • Colour profiles converted

Balance between the image quality and compression

Output format

Auto tries every format your image can be saved as and gives you the smallest one

Resize

Change the width, height or scale of every image you upload

Original Dimensions Percentage
px
px

Set one side to keep the proportions, or both for an exact size.

Percentage
%

Size limit

Fit every image under a file size, for a form or a site with an upload limit

Any size Under a size
KB

Saved as JPG, WebP or AVIF. When quality alone can't get there, the image is made smaller to fit.

How the size limit works

Responsive image set

Pro

The image at several widths, with a srcset to paste into your page, so each screen loads the size it needs

One size Responsive set
px

Up to 8 widths, each in the format and at the level of the result. A width wider than the image stops at its own width, so nothing is enlarged.

How responsive sizes work

Keep EXIF Keeps details such as the camera, the date and the location in each file. Leave it off to remove them and save space.
Write alt text with AI Describes each image for screen readers and search engines, and suggests a file name
Alt text language
No language matches
English
Spanish
French
German
Italian
Portuguese
Dutch
Polish
Swedish
Turkish
Russian
Ukrainian
Arabic
Persian
Hebrew
Hindi
Indonesian
Vietnamese
Thai
Japanese
Korean
Simplified Chinese
Traditional Chinese
Rename files Downloads take the suggested name instead of the one you uploaded

Pro
Uploading a zip comes with Pro: the browser opens it and uploads its images in the folders they sat in, and the zip of the results keeps them. On your plan, unzip it and drop the images here. How folders and zips work

Up to 16 MB per image PNG, JPG, WEBP, GIF, HEIC, TIFF, or a ZIP of them on a paid plan

Guests get 10 images a day, 10 left today. A free account gets 40 a day and 7 days of Pro.

Upload a folder, or a zip

Pro

Pick a folder and every image in it uploads, with the folders inside it, and Download Selected gives them back in the same folders. A zip of images dropped on the box works the same way, opened in your browser.

How folders and zips work

Auto-start
On, each image starts compressing as soon as it uploads. Off, images wait in the box so you can check the settings, then start together.
Delete this image?
The image and its optimized copy will be removed from storage. This cannot be undone.

Rename this image
Choose the name the optimized image downloads with. Its format stays the same.

Uploaded as

Rename the selected images
Each image gets this name and a number, counted in the order they were uploaded. Their formats stay the same.

Share this image
AI alt text
Alt text

Paste it into the alt attribute of the image on your page.

Choose the compression level that suits your images
Level What it promises What happens Pick it when
Lossless
Not one pixel changes in a JPEG, PNG or GIF The file is repacked, never re-encoded. JPEGs get an optimised Huffman table and progressive scan, PNGs a tighter deflate pass, GIFs a lossless gifsicle run. A lossy WebP has no repack step, so it is re-encoded at the highest quality the level allows. A sideways phone JPEG is rotated losslessly on the way through and keeps its colour profile. The one exception to the promise is a PNG or WebP tagged with a wide-gamut profile such as Display P3: its colours are converted to sRGB, so the values change but the picture doesn't. Logos, line art, anything you'll edit again, or when the file is evidence.
Smart
No visible change, targets 40 dB PSNR and a perceptual score of 70 A quality search runs per image and stops at the lowest quality that still clears the PSNR target. That answer is then scored on the SSIMULACRA 2 scale, because an average over every pixel lets a mostly flat picture through at a quality its detail doesn't deserve, and when it falls under 70 the search moves back up until it doesn't. Photos and graphics end up at different qualities because they need different ones; an image that cannot reach the targets inside the quality ceiling is encoded at the ceiling. Almost everything on a website. This is the default for a reason.
Ultra
Smallest file, targets 34 dB PSNR and a perceptual score of 50 The same two-stage search with lower targets. Fine texture softens a little; edges and text stay sharp. Thumbnails, backgrounds, email images, anything shown small or blurred anyway.
None
No compression at all Only the resize, conversion or metadata setting you chose is applied. Without a resize or a conversion every pixel comes back as it was: the file only loses its metadata, and with Keep EXIF on it comes back byte for byte. You only wanted to resize or convert, and quality is someone else's decision.

Measured, not estimated

What TIFF to JPG saved on two photographs

An uncompressed TIFF stores three bytes for every pixel and nothing smarter, so almost any JPG of it is tiny by comparison.

Sample Original Smart Ultra
Landscape, uncompressed TIFF 1800 by 1200 6.2 MB TIFF 555 KB 91.2% smaller 317 KB 95% smaller
Cafe interior, uncompressed TIFF 1800 by 1200 6.2 MB TIFF 90 KB 98.6% smaller 75 KB 98.8% smaller

Two showcase photographs, 1800 by 1200, written as uncompressed TIFFs and converted by the pipeline your upload goes through. A TIFF saved with LZW or ZIP compression starts smaller, so it saves a smaller share.

Why convert

TIFF is for archives, not for sending

Scanners, cameras and print workflows produce TIFFs because TIFF loses nothing. That's right for a master file and wrong for nearly everything else. A single A4 scan at 300 dpi runs to 25 MB. Browsers won't display it, and most upload forms reject it.

Because a TIFF is a lossless source, Iminify has the full picture to work from. Smart searches for the lowest JPG quality that still matches your image, up to a ceiling of 90, and writes it with jpegli as a progressive JPG.

Mind the limits on big scans. A guest upload stops at 16 MB and every plan stops at 64 megapixels. A 600 dpi A4 scan is about 35 megapixels, which fits, but its file may not unless it was saved with compression.

What survives

What a TIFF keeps on its way to JPG

  • Colours, CMYK included

    A CMYK or wide-gamut TIFF is converted to sRGB through its profile, so a print file doesn't come out with inverted or washed-out colour.

  • EXIF, when you switch it on

    Camera TIFFs carry EXIF. It's stripped by default and carried into the JPG when Keep EXIF is on.

  • Pages after the first

    A multi-page TIFF, such as a scanned document, is converted as its first page only. Split it first if you need them all.

  • Transparency and layers

    JPG has no alpha channel, so transparent areas are flattened onto white. Layers from an editor are merged.

When not to

When to keep the TIFF

  • It's your master scan or a file going to a print shop. Keep it, and convert a copy.
  • It's a multi-page document. You want a PDF, not a JPG, and Iminify doesn't make those.
  • It's line art or text. A PNG or a lossless WebP keeps the edges clean where a JPG leaves ringing; pick one from the full tool.

How to

TIFF to JPG in three steps

  1. 1

    Drop your TIFF

    Both .tif and .tiff are accepted. There's no preview of the original, because browsers can't draw TIFF.

  2. 2

    Resize if it's a scan

    A 300 dpi scan is far bigger than a screen needs. Set a width under Size and it happens in the same pass.

  3. 3

    Download the JPG

    The result does preview, so check it before you download.

Questions

TIFF to JPG questions

Next

From the blog

What we've measured so far

We run the encoders on real photos and screenshots and publish the numbers: when WebP beats AVIF, what quality 80 means in each encoder, and how many kilobytes an image on a web page should weigh.

All posts
Bar chart of file sizes for a photo at four print sizes, 8x10 to 24x36. PNG bars run from 11.3 to 70.6 MB and JPEG bars from 1.4 to 6.5 MB, with a dashed line at Etsy's 20 MB limit.

How many pixels does an AI print need? 300 per inch, and at 16x20 our PNG is over Etsy's download limit

The usual answer is 300 pixels per inch of print: 2400 x 3000 for an 8x10, 4800 x 6000 for a 16x20, 7200 x 10800 for a 24x36. A square Midjourney 8.2 HD image is 2048 x 2048 and a square Gemini 4K image is 4096 x 4096, so neither reaches a 16x20 at that rate without more pixels. (Shops write DPI. Here it means pixels per inch of print.) From a 4K Gemini picture we made 16x20 files of 4800 x 6000 pixels: the PNG is 35.8 MB, over Etsy's 20 MB per file for digital downloads, and the JPEG is 3.6 MB.

7 min read
Two rows of seven squares, one per test post. After the default wp media regenerate, four squares are red and read 404 and three read 200; after --skip-delete and the rewrite, all seven read 200.

Convert your existing WordPress images to WebP without a plugin: what regenerate breaks

On a WordPress 7.1.4 test site, one filter and wp media regenerate turned the resized copies WordPress makes of five full-colour (4:4:4) photographs into WebP files with 62.5% of the JPEG copies' bytes. All 25 WebP copies, five sizes of each photograph, also scored lower. The filter and regenerate also left four of our seven test posts pointing at copies WP-CLI had just deleted, and took the srcset off all seven inserted images that had one. The version below leaves no address broken and gives six of those seven their srcset back: the filter, regenerate with one flag, and a rewrite that changes an address only where a WebP exists. The recipe as printed needs WP-CLI and a shell on the server.

8 min read
Bar chart of bytes Chrome downloaded at phone size for five 4K JPEGs on a Next.js static export page: 55.2 MB as they are, 10.2 MB as Smart JPG at full size, 1.29 MB at 1200 px wide, 767 KB through next-image-export-optimizer.

Next.js static export images: the default loader breaks them and unoptimized ships the original

We built a page with five photographs in a Next.js 16.4.3 App Router app, set output: 'export', left the image settings alone, and next build finished with exit code 0. In Chrome none of the five images loaded: every src pointed at /_next/image, an endpoint a static export doesn't contain. Setting images: { unoptimized: true } fixes that, and the export then serves the file you put in public/. Chrome at phone size downloaded 2.4 MB for five 1800 px photographs, and 55.2 MB when the same page held five 4K Gemini JPEGs. This post compares that flag, next-image-export-optimizer and resizing the files first by what Chrome downloaded at phone size and at desktop size. The table is in the second section, and the choice we'd make follows the three options.

7 min read

Turn your TIFF into a JPG

JPG is already selected. Add a resize if it's a scan, and download a file you can send.