Initializing... drag & drop files here
Supports: TIFF, TIF
.tif/.tiff images. Batch conversion is supported, and multi-page TIFFs will be flattened to the first page or split into one JFIF per page depending on the source..jfif file (byte-identical to a .jpg — see FAQ below). No sign-up, no watermark, no email required.TIFF (Tagged Image File Format) is the de-facto archival format for scanners, prepress, geospatial data, and medical imaging — single files routinely run 50–500 MB because the format supports uncompressed pixels, LZW/ZIP lossless compression, 16-bit channels, layers, alpha, and embedded color profiles. JFIF (JPEG File Interchange Format) is the standardized container that wraps JPEG-compressed bitmap data with resolution, aspect ratio, and color-space markers. The original JFIF 1.02 specification was an informal document published in 1992; it was later codified as ITU-T T.871 (2011) and ISO/IEC 10918-5 (2013). In practice JFIF and JPG are the same file format with a different extension; converting from TIFF gives you a portable, 10–50× smaller image that opens everywhere.
.jfif instead of .jpg depending on the Windows MIME registry. Outputting JFIF on purpose avoids extension mismatches when feeding pipelines that expect .jfif.| Property | TIFF | JFIF |
|---|---|---|
| Full name | Tagged Image File Format | JPEG File Interchange Format |
| Compression | None, LZW, ZIP, JPEG, PackBits, CCITT (lossless options) | JPEG (lossy DCT) |
| Typical size (8MP photo) | 20–50 MB uncompressed, 6–15 MB LZW | 1–4 MB at "Very High" quality |
| Color depth | 1 / 8 / 16 / 32-bit per channel | 8-bit per channel |
| Layers / alpha | Yes (layers, alpha, masks) | No |
| Multi-page support | Yes | No (single image per file) |
| Browser support | None natively (Chrome, Firefox, Edge, Safari) | All browsers since 1990s (rendered as JPEG) |
| Best for | Archival, prepress, scanning, medical imaging, GIS | Web, email, social sharing, general photos |
| MIME type | image/tiff | image/jpeg |
| Standard | TIFF 6.0 (Adobe, 1992) | ITU-T T.871 (2011) / ISO/IEC 10918-5 (2013); original informal JFIF 1.02 spec: 1992 |
| Extension | What it is | When you see it |
|---|---|---|
.jpg |
The 3-character DOS/Windows-friendly form of JPEG | Most common; default on cameras, phones, most software |
.jpeg |
Full 4-character form, identical bytes to .jpg |
macOS / older Unix workflows, some pro cameras |
.jfif |
JPEG bytes wrapped in the JFIF container with resolution/aspect/color markers | Chrome "Save image as…" on Windows; some scanner output |
.jpe |
Rare DOS-era variant | Legacy archives only |
All four contain JPEG-compressed bitmap data. Renaming .jfif to .jpg works in 100% of cases. The wrapper differs only in the metadata segment immediately after the start-of-image marker. (See also JFIF to JPG if you need the reverse rename-and-rewrap.)
Starting with Chrome 68 (July 2018), Chrome on Windows consults the HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg registry key to decide the extension. On many Windows installs that key's "Extension" value is .jfif rather than .jpg, so Chrome writes .jfif. You can edit the registry value to .jpg and restart Chrome — or just rename the file. Both extensions hold identical JPEG bytes.
Yes. JFIF registers as MIME type image/jpeg and is recognized as a JPEG by Photoshop, Affinity Photo, macOS Preview, Windows Photos, GIMP, IrfanView, and every web browser. If an app refuses to open a .jfif, rename the extension to .jpg — the file bytes don't change.
JFIF uses JPEG compression, which is lossy, so yes — some quality is lost compared to an uncompressed or LZW-compressed TIFF. At "Very High" (the default) the loss is typically not visible to the eye for photographs; for line art, text scans, screenshots, and images with sharp edges or large flat color areas, you'll see JPEG ringing and blockiness. For those, consider TIFF to PNG (lossless) instead.
Multi-page TIFFs (common in fax archives and scanned documents) cannot fit into a single JFIF because JFIF holds one image per file. The converter handles this by either flattening to the first page or splitting into one JFIF per page — check the output count after conversion.
JFIF is 8-bit-per-channel RGB or grayscale with no alpha and no layers. Alpha is composited against a white background by default (configurable in advanced options). Layers are flattened. 16-bit channels are quantized to 8-bit — that's a one-way conversion, so keep the original TIFF as your archival master.
Almost always much smaller. An uncompressed 24-bit color TIFF holds roughly 3 bytes per pixel before metadata; the same image at "Very High" JPEG quality typically averages 0.2–0.5 bytes per pixel — a 6–15× reduction. LZW-compressed TIFFs of photographic content still see 4–8× shrinkage, and pure black-and-white CCITT scans may shrink less (or grow, if the source was already heavily compressed).
Yes. In Advanced Options, switch from "Quality Preset" to "Specific file size" and enter a target in KB or MB. With Auto Scale on, the converter will adjust dimensions to hit the size while preserving maximum quality. For an exact percentage of the original, use "Target file size (%)" instead.
Functionally identical — TIFF to JPG produces the same bytes with a .jpg extension. Pick JFIF only when the downstream pipeline specifically expects that extension (some scanner workflows, some Windows-saved files) or when matching what Chrome's "Save image as" already produces. For everything else, .jpg has wider out-of-the-box compatibility.
JFIF can't do either. For lossless conversion from TIFF use TIFF to PNG (lossless, supports alpha) or TIFF to WebP (smaller than PNG, lossless mode available). If you only need to shrink the TIFF without changing format, try the TIFF compressor.