QRix
Move a photo into the lossless container that print shops, archives and submission systems ask for.
Loading the image workspace…
The usual reason to convert a JPG to TIFF is that something downstream demands it: a printer's prepress checklist, an academic submission portal, a records system, a legal e-filing tool. TIFF's appeal to those systems is that it is lossless and boringly stable, so a file archived today opens identically in twenty years. Be clear about what the conversion does and does not do. It stops any further degradation — every JPG re-save compounds compression artifacts, and moving to TIFF ends that cycle — but it cannot restore detail the original JPG already discarded. You are freezing the image where it is, not improving it. The output is an uncompressed baseline TIFF, so a 2 MB JPG typically becomes 20–30 MB. Since JPG carries no transparency, the file is written as straightforward RGB.
No. Detail already lost to JPG compression cannot be recovered. It prevents further loss from future edits and saves, which is the actual benefit.
The TIFF is uncompressed while the JPG was heavily compressed. A 10–15× increase is normal and expected by the workflows that require TIFF.
Yes. It is a standard baseline TIFF — correct header, tag directory and 8-bit RGB pixel data — not a renamed JPG.
None. The decoded JPG pixels are written into the TIFF exactly as they are.
It's free, private and works right in your browser — no signup, no watermark.