Skip to main content

TIFF to JPG converter

Convert TIFF images to JPG format

No watermarkFree & unlimited
All processing happens in your browser. No data is sent to any server.

This is the pair where file size collapses. An uncompressed baseline TIFF stores three literal bytes per pixel; JPEG throws away detail your eye is poor at noticing and typically lands one to two orders of magnitude smaller. The page parses the TIFF with its own reader, paints the pixels onto a canvas, fills the canvas with white first so nothing transparent turns black, and hands the result to the JPEG encoder built into your browser at the quality you pick on the slider. The trade is permanent: JPEG is lossy and there is no route back to the original data.

Key facts about TIFF to JPG converter

Key facts about TIFF to JPG converter
Quality controlA slider from 30 to 100 in steps of 5, defaulting to 90. It maps straight onto the browser JPEG encoder.
Typical size deltaA 5.93 MB 1920x1080 uncompressed TIFF lands near 400 to 700 KB at quality 90, and under 150 KB at 60.
TransparencyJPEG has no alpha, so the canvas is painted white before drawing. Transparent areas become white, never black.
Source requirementThe TIFF must be uncompressed. LZW, PackBits, Deflate and JPEG-in-TIFF sources are refused with a message.
Greyscale scansRead correctly, including WhiteIsZero, but written as three-channel JPEG, so slightly larger than a true grey export.
Chroma handlingThe browser encoder applies its own subsampling. Fine red or blue text on a light ground softens first.
MetadataNo EXIF is written by the canvas encoder: no capture date, no camera model, no orientation flag, no ICC profile.
PagesOnly the first image directory in the TIFF is read, so a multi-page scan yields one JPEG.
Bit depth8 bits per sample only. Convert a 16-bit scan down in your editor first or the pixels decode as noise.
BatchUp to twenty scans per run; more than one result is offered as a ZIP built in the page with JSZip.
Opens natively inEverything: phones, email clients, CMS uploaders, printers, and every social platform that rejects TIFF.

What happens to your file

The scan is turned into an ArrayBuffer and decoded by the baseline TIFF parser inside this page, so no image data is posted anywhere. The pixels then live briefly in a canvas element before canvas.toBlob asks your browser to produce JPEG bytes, still entirely on your machine. There is no account, no queue and no temporary copy on a server, which also means there is nothing to delete afterwards: closing the tab discards both the decoded buffer and the encoded blob.

About this tool

  1. 1

    Load the TIFF

    Drag a .tif or .tiff onto the panel or click to browse. The converter also accepts a batch of scans.

  2. 2

    Set the quality

    Move the slider between 30 and 100. Ninety is a safe default; the estimate underneath moves as you drag.

  3. 3

    Cap the dimensions if needed

    Choose a longest-edge preset, from 4K down to a 200 px thumbnail, or leave it on Original.

  4. 4

    Convert

    Each file is decoded, drawn onto a white canvas and encoded. A comparison view shows before and after sizes.

  5. 5

    Save

    Download the .jpg, or take the whole batch as one ZIP if you converted several scans together.

Specs & compatibility
Input and outputTakes .tiff and .tif only (image/tiff) and returns .jpg with the image/jpeg type; any other extension is refused before decoding.
Conversion pathTIFF to JPG runs in three steps: the page's own baseline parser reads the IFD and rebuilds the pixels, because no browser decodes TIFF; the pixels land on a 2D canvas in this tab; then canvas.toBlob with the image/jpeg type returns the finished file.
Browser supportThe TIFF side needs no browser support at all, only a baseline uncompressed source, because LZW, Deflate and JPEG-in-TIFF files stop with an error, while writing the JPG is just as universal, since every canvas implementation encodes JPEG.
Controls for this pairA 30 to 100 quality slider (steps of five, default 90) drives the JPG encode, max-dimension presets from 3840 down to 200 px resize the TIFF first, and the strip-metadata toggle is moot on this pair.
Batch, caps and namingTwenty TIFF files per run at 500 MB each; one result downloads as a single JPG, several as converted-jpg-files.zip, zipped by JSZip 3.10 in page memory.
Device ceilingThe canvas caps it: past roughly 16,384 px a side Chromium refuses the bitmap and iPhone Safari gives up sooner, so an oversized TIFF fails before any JPG bytes exist.
  • Try quality 80 before you reach for 90. On scanned photographs the difference is usually invisible at 100 percent zoom while the file is about a third smaller.
  • Text-heavy documents are the wrong fit for JPEG at any setting, because ringing appears along sharp black edges. Use the PNG target for scanned text instead.
  • Resize and compress in the same pass. Dropping a 4000 px scan to Full HD before encoding saves far more bytes than any slider move.
  • Since no orientation tag is written, rotate the image before converting if your scanner recorded it sideways. A viewer has nothing left to auto-rotate by.
  • Keep the TIFF as your master copy. Every further JPEG save compounds the loss, and the discarded detail cannot be recovered from the JPEG.
  • Cut a 40 MB archival scan down to something an email attachment limit or a web form will actually accept.
  • Prepare photographs delivered by a studio as TIFF for a blog, a listing or a product catalogue upload.
  • Produce lightweight proof copies of a scanned collection while the uncompressed originals stay on the drive.
Usually between ten and forty times smaller. An uncompressed TIFF is fixed at three bytes per pixel regardless of content, while JPEG size depends on detail: a smooth studio portrait compresses far harder than a textured landscape. At quality 90 a Full HD scan that occupied almost 6 MB typically settles between 400 and 700 KB.
For anything that will be looked at rather than edited, 80 to 90 is the practical band. Below 70 you start to see blocking in flat gradients such as skies and studio backdrops; above 95 the file grows quickly with almost no visible gain. The slider moves in steps of five so it is easy to try two settings and compare.
Because the canvas is deliberately filled with white before the image is drawn on this target. JPEG has no alpha channel, so transparency has to become some colour, and white is the safer choice for documents and product shots. If you need a specific background colour, composite it in an editor before converting.
No. The JPEG is produced by re-encoding canvas pixels, and that path writes image data only. Capture date, camera and lens details, GPS coordinates, the orientation flag and any embedded colour profile are all absent from the output. For sharing scans this is usually welcome, but copy anything you need out of the TIFF beforehand.
Yes, up to twenty per run. They are processed one after another with a progress bar for the batch, each using the same quality and size settings. When more than one file finishes, the download button packs the results into a ZIP that is assembled in the page rather than on a server.
Almost always this is compression. Scanner software often defaults to LZW, and this reader handles only the uncompressed baseline layout, so it stops with a clear message instead of producing garbage. Open the file in any editor and save it again with compression set to None, then convert.

Related tools

View all

Need the opposite? Try JPG to TIFF

Updated

We use anonymous analytics to improve ToolChamp. No personal data is stored or sold. Privacy Policy