Drop your JFIF file into the picker and our encoder produces a TIFF output tuned for web delivery: quality factor 80 by default (a Lighthouse sweet-spot), correct color space, and an Accept-aware fallback you can ship behind a `<picture>` element alongside the original JFIF.
Will TIFF actually be smaller than JFIF?
+
Almost always when going from PNG / JPG / TIFF into WebP or AVIF: expect 25-50% smaller than JPG at the same visual quality, 60-90% smaller than PNG. Going the other way (WebP / AVIF back to TIFF = PNG / JPG) typically grows the file because you are leaving a more modern codec for an older one — useful for compatibility, not size.
Does JFIF to TIFF preserve transparency / alpha?
+
Transparency survives when TIFF supports alpha (PNG, WebP, AVIF, GIF, TIFF, SVG). Converting to JPG flattens the alpha channel onto white — if you need transparency on the modern web target WebP or AVIF instead of TIFF.
Can I keep my color profile (sRGB / Display P3) going from JFIF to TIFF?
+
Yes for TIFF formats that store ICC profiles (PNG, JPG, WebP, AVIF, TIFF). Modern wide-gamut profiles like Display P3 round-trip through WebP and AVIF; sRGB profiles round-trip through every common TIFF. If TIFF cannot store a profile, output is tagged sRGB to keep browsers from guessing.
What lossy vs lossless quality settings does the TIFF encoder support?
+
Lossy TIFF (WebP / AVIF / JPG) accepts a quality 1-100, default 80. Lossless TIFF (PNG / WebP lossless / TIFF) does not take a quality dial — every pixel is preserved. WebP and AVIF are the only formats that can do either, which is why they are ideal TIFF targets when source JFIF mixes photos and graphics.
Will the TIFF version look identical to the JFIF on a Retina display?
+
At quality 80+ on WebP / AVIF the difference is invisible to anyone but a trained eye even at 3x device pixel ratio. Photos compress slightly more visibly than line art; if your JFIF is screenshots or UI mockups, push quality to 90 or use a lossless TIFF.
Does JFIF to TIFF keep animation frames?
+
Animated JFIF (animated WebP, GIF, APNG) survives only when TIFF is also animation-aware (animated WebP, GIF, APNG). Converting an animated JFIF to a static TIFF (PNG, JPG, AVIF still) yields just the first frame — use a dedicated animation converter if you need to keep all frames.
Will EXIF camera metadata survive JFIF to TIFF?
+
Yes by default when both JFIF and TIFF support EXIF (JPG, PNG, WebP, TIFF, HEIC). Camera fields (ISO, shutter, lens, GPS) are copied through. Use the "strip metadata" option if you are publishing to the web and want to drop GPS coordinates before TIFF leaves your browser.
Can I batch convert a folder of JFIF files to TIFF?
+
Yes — drop multiple JFIF files at once and they encode in parallel. Free accounts: 100 MB per file. Pro accounts get more parallel workers and bigger per-file caps, so a 200-image gallery typically finishes in well under two minutes.
Are my JFIF files private during TIFF conversion?
+
Yes — uploaded JFIF files are processed in isolated workers and deleted within minutes. No human reviews the pixels, no copy is retained, no third party gets a feed. See /privacy/ for the precise retention window.
How do I serve the TIFF with a JFIF fallback on my site?
+
Use a `<picture>` element: `<picture><source srcset="image.TIFF" type="image/TIFF"><img src="image.JFIF" alt=""></picture>`. Browsers that understand TIFF fetch the smaller file; older browsers fall back to JFIF. WebP is supported in 96%+ of installed browsers, AVIF in 90%+.
Why is my TIFF file unexpectedly bigger / smaller than I expected?
+
A JFIF that is already heavily compressed (low-quality JPG) often grows when re-encoded into a lossless TIFF (PNG / TIFF). A high-bitrate lossless JFIF (PNG / TIFF) often shrinks 60-90% when going to a lossy modern TIFF (WebP / AVIF). Image content matters too — photos compress very differently from line art and screenshots.