TIFF to JPG Converter Online — Aldus TIFF 6.0 (1992) to JPEG via Browser-Native Decode (Safari)

TIFF to JPG Converter — Honest About Browser TIFF Support

Convert TIFF (Tag Image File Format, Aldus TIFF Revision 6.0 finalised 3 June 1992 by Steve Carlsen at Aldus Corporation; copyright transferred to Adobe Systems after Adobe acquired Aldus in 1994) to JPG (ITU-T Recommendation T.81 / ISO/IEC 10918-1:1994, 18 September 1992). The conversion runs locally via WHATWG Canvas drawImage + HTMLCanvasElement.toBlob('image/jpeg', quality), trading TIFF's lossless storage for JPEG's perceptually-tuned compression — typical photographic 1920×1080 TIFF (~6-25 MB depending on compression scheme) lands at 200-500 KB JPG at quality 85. Critical browser limitation — TIFF native decoding is sparse in 2026. Safari decodes TIFF natively via macOS Quartz / CoreGraphics integration. Chrome, Firefox, and Chromium-based Edge do NOT decode TIFF natively — the source fails to load in those browsers. The tool delegates to the browser's built-in HTMLImageElement decoder, so it works on Safari and fails elsewhere. For TIFF conversion in non-Safari browsers, use a desktop tool (Preview on macOS, GIMP, IrfanView) to convert TIFF to PNG first, then run that PNG through this tool's chain. Files never leave the device.

How to convert TIFF to JPG

Drop a .tiff or .tif file onto the tool or click to browse. Critical — works on Safari only. Chrome, Firefox, and Chromium Edge fail to load TIFF natively.
If you're on a non-Safari browser and the source fails to load, convert your TIFF to PNG first using a desktop tool (macOS Preview, GIMP, IrfanView, ImageMagick) and run the PNG through the png-to-jpg path instead.
On Safari: pick a JPG quality level. 85 is the standard web sweet spot per ITU-T T.81 Annex K; 90+ approaches visually lossless; below 70 produces visible 8×8 blocking and ringing.
The tool runs Canvas drawImage (decoded TIFF → canvas at native dimensions) → toBlob('image/jpeg', quality). Multi-page TIFFs only render the first page.
Download the JPG. The original TIFF stays on disk untouched — files never leave the device.

Common use cases

Preparing scanned documents or artwork for email, web upload or CMS import where TIFF is rejected (most non-print platforms have phased TIFF out as an upload format).
Shrinking TIFF camera exports (some pro cameras still default to TIFF for raw-adjacent capture) for sharing in a format most devices can open.
Converting archived TIFF photo libraries (museums, libraries, scientific archives still use TIFF as the lossless master) into JPG distribution copies for blog or social use.
Reducing the storage footprint of an archived single-page TIFF library before backing it up to cloud storage that charges per GB (multi-page TIFFs need a desktop tool first).
Converting TIFF screenshots from older software (Photoshop's default save format pre-2010 was TIFF for many workflows) to JPG for modern compatibility.

Frequently asked questions

Why does my TIFF fail to load on Chrome / Firefox?

TIFF is not natively decoded by Chrome, Firefox, or Chromium-based Edge — those browsers do not ship a TIFF decoder. Safari decodes TIFF natively via macOS Quartz / CoreGraphics integration (the Image I/O framework shared with Preview and QuickLook), so the tool works on Safari only. For non-Safari browsers, use a desktop tool (macOS Preview, GIMP, IrfanView, or ImageMagick) to convert your TIFF to PNG first, then run that PNG through the png-to-jpg tool. The browser TIFF support gap is a structural limitation, not a bug in the tool.

Does converting TIFF to JPG lose detail?

Yes — JPG is lossy per ITU-T T.81 Annex K's perceptual quantisation tables. At quality 85 or above the loss is usually invisible at normal viewing distances; at quality 60 or below it becomes noticeable on smooth gradients (banding) or sharp edges (ringing, 8×8 block boundaries). For archival or print-adjacent use, stay at quality 90+. TIFF is lossless (in uncompressed, LZW, Deflate, and PackBits modes), so converting to JPG is a one-way trade of fidelity for size. For lossless raster output, convert TIFF to PNG instead via a desktop tool.

Will every TIFF variant work on Safari?

Safari decodes the common TIFF variants via macOS Quartz / CoreGraphics: uncompressed (TIFF Compression tag = 1) at 8-bit and 16-bit per channel, LZW (US Patent 4,558,302 expired 20 June 2003), Deflate, JPEG-in-TIFF, and PackBits. Less common variants may fail: CCITT Fax Group 3 / Group 4 (multi-bit fax compression), exotic colour spaces (CMYK, Lab), and multi-page TIFFs (only the first page renders). Re-export from GIMP or Preview as single-page baseline TIFF if loading fails.

What quality should I pick?

For archival or print-adjacent use (where the TIFF was the lossless master), stay at quality 90+ to preserve detail. For typical web and email use, 80-85 is the best balance of size and visual quality per ITU-T T.81's perceptual model. Below 70 the savings plateau and artefacts start to appear in photographic content. The 1-100 scale is a non-linear quantisation table scaling factor; doubling the number does NOT double the file size.

Is my file uploaded?

No. The decode + canvas draw + JPEG encode all run client-side via WHATWG Canvas drawImage + HTMLCanvasElement.toBlob('image/jpeg', quality). DevTools Network tab shows zero upload requests. Note that on browsers without TIFF decode support (Chrome, Firefox, Chromium Edge), the source fails to load locally and the tool returns an error — no upload happens because no decode happens.

TIFF's compression options + the browser TIFF support gap

TIFF Revision 6.0 (3 June 1992, Steve Carlsen, Aldus Corporation) is a flexible container that stores image data via tagged Image File Directories (IFDs); each IFD can carry uncompressed RGB, LZW (US Patent 4,558,302 expired 20 June 2003 in the US), JPEG-in-TIFF (TIFF Tag 33), Deflate (RFC 1951), CCITT Fax Group 3 / Group 4, PackBits, or other compression schemes. The format supports 8-bit and 16-bit colour depths, CMYK and Lab colour spaces beyond sRGB, multiple pages per file, and metadata-rich tagging — making it the dominant lossless format for scanning, print pre-press, GIS, and scientific imaging. The trade-off is size: a typical 1920×1080 photographic TIFF is 6-10 MB (with LZW or PackBits) or up to 25 MB (uncompressed). JPEG's DCT + chroma subsampling + Huffman pipeline cuts that to 200-500 KB at quality 85, a 10-50× reduction depending on the source's compression. The browser-decode caveat is the practical blocker: Safari's TIFF support comes from macOS Quartz / CoreGraphics integration (the Image I/O framework that QuickLook, Preview, and Safari all share); Chrome, Firefox, and Chromium Edge dropped or never had TIFF support because TIFF is not a web-target format. The tool will appear to fail to load TIFF on those browsers — that's a structural limitation, not a bug. For non-Safari users: Adobe's TIFF spec at adobe.com (post-1994) and Aldus's original 1992 PDF are the authoritative references for converting TIFF to PNG / JPG via desktop tools (Preview, GIMP, IrfanView, ImageMagick all decode every variant the spec defines).

Source TIFF decoded per Aldus TIFF Revision 6.0 (3 June 1992, Steve Carlsen) / Adobe steward post-1994
Safari only — TIFF browser-native decoding via macOS Quartz / CoreGraphics integration
Not supported on Chrome / Firefox / Chromium Edge — these browsers do NOT decode TIFF natively (use a desktop tool to convert TIFF → PNG first)
Adjustable JPEG quality 1-100 mapped to ITU-T T.81 Annex K quantisation tables
Substantial file-size reduction for photographic content — typically 10-50× smaller at quality 85
Output JFIF v1.02 container (Hamilton, C-Cube Microsystems, 1 September 1992) widely accepted by legacy editors and CMS platforms
Browser-side via WHATWG Canvas drawImage + HTMLCanvasElement.toBlob('image/jpeg', quality) — no upload
Operates in sRGB (IEC 61966-2-1:1999) at 8-bit precision; CMYK and Lab TIFFs are converted to sRGB during decode (where supported)

Free. No signup. No file uploads. Ads via AdSense (consent required).

Sources (7)

Carlsen, S. (Aldus Corporation, later Adobe Systems) (1992). TIFF Revision 6.0 Final. Aldus Corporation, 3 June 1992 — Tag Image File Format (TIFF) baseline + extensions; copyright transferred to Adobe Systems after Adobe acquired Aldus on 31 August 1994. TIFF supports uncompressed (Compression tag = 1), LZW (Compression tag = 5), JPEG-in-TIFF (Compression tag = 7), Deflate (Compression tag = 8), PackBits (Compression tag = 32773), CCITT fax (Group 3 / Group 4); multi-page documents; 8-bit and 16-bit colour depths; CMYK and other colour spaces beyond sRGB.
Welch, T. A. (Sperry Corporation, later Unisys) (1985). High speed data compression and decompression apparatus and method (LZW). U.S. Patent 4,558,302, filed 20 June 1983, granted 10 December 1985 — the LZW compression algorithm available to TIFF as Compression tag = 5; the patent expired 20 June 2003 in the US (international counterparts 2004), clearing the legal cloud that had hung over LZW-encoded TIFF and GIF files for the algorithm's patented life.
ITU-T (CCITT) Study Group VIII & ISO/IEC JTC 1/SC 29/WG 10 (JPEG) (1992). Information technology — Digital compression and coding of continuous-tone still images: Requirements and guidelines. ITU-T Recommendation T.81 (18 September 1992) / ISO/IEC 10918-1:1994 — target JPEG baseline DCT bitstream; quality 1–100 maps to Annex K quantisation tables; the practical web/email format that TIFF needs to convert to for sharing.
Hamilton, E. (C-Cube Microsystems) (1992). JPEG File Interchange Format (JFIF) Version 1.02. 1 September 1992 — target de facto JPEG container; APP0 marker, density units, thumbnail handling.
WHATWG (live). HTML Living Standard — HTMLImageElement (browser-native TIFF decoding limitations). html.spec.whatwg.org/#htmlimageelement — TIFF native browser support is sparse: Safari decodes TIFF via macOS Quartz / CoreGraphics integration; Chrome / Firefox / Chromium-based Edge do NOT natively decode TIFF and the tool fails to load the source there. Browsers that do decode handle a subset of TIFF compressions (uncompressed BI_RGB, sometimes LZW, sometimes JPEG-in-TIFF); CCITT fax variants and multi-page TIFFs typically fail.
WHATWG (live). HTML Living Standard — Canvas 2D Context: drawImage() + toBlob('image/jpeg', quality). html.spec.whatwg.org/#dom-context-2d-drawimage + canvas section 4.12.5 — browser conversion mechanism: load TIFF into HTMLImageElement (where supported) → drawImage onto canvas at native dimensions → toBlob('image/jpeg', quality) re-encodes via the browser's built-in JPEG encoder.
International Electrotechnical Commission (IEC) (1999). Multimedia systems and equipment — Colour measurement and management — Part 2-1: Default RGB colour space — sRGB. IEC 61966-2-1:1999 — default 8-bit RGB colour space the Canvas 2D path operates in; TIFF files in CMYK, Lab, or other non-sRGB colour spaces are converted to sRGB by the browser decoder during the load step (where supported).

These are the W3C, ISO/IEC, ITU-T, and IETF specifications the tool implements or builds on. Locate them on w3.org, iso.org, itu.int, or datatracker.ietf.org.