Why TIFF exists and why scans use it
TIFF = professional archives. JPG = everyone else.
TIFF is the standard for professional scans, but huge and not universally readable. Convert to JPG instantly, drop into any document, email, or chat. Bulk, browser-based, no upload.
Three steps, fully local, including multi-page TIFFs.
Drag TIFF or TIF files (up to 100 at once). Multi-page TIFFs (typical for scanned documents) are supported, each page becomes a separate JPG.
92% is the default sweet spot, visually identical to source. Drop to 85% for storage-critical use, raise to 95% for archival.
Single page TIFF → single JPG. Multi-page TIFF → folder of pages numbered sequentially, packed in a ZIP. Average savings: 90-95%.
TIFF is the gold standard for archives. JPG is what the rest of the world reads.
Multi-page TIFF (common for scanned documents) is split into individual JPGs, numbered sequentially. Drop a 50-page contract scan, get 50 JPG pages back in a ZIP.
TIFFs are typically 10-30 MB per page (uncompressed); JPGs are 200-800 KB at the same visible quality. Massive savings for archives, email, and storage.
92% default for invisible loss. Adjust between 60-100% for thumbnail-grade or archival-grade outputs.
Scanned documents, legal, medical, financial, never leave your browser. WebAssembly decoding verifiable in DevTools.
Even a 50 MB TIFF converts in 1-2 seconds. Bulk of 100 files completes in seconds, no upload, no server queue.
Free forever. Output JPG drops straight into Word, PowerPoint, email, or any tool that reads JPG.
When TIFF is right, when it's overkill, and how to bridge the gap.
TIFF = professional archives. JPG = everyone else.
Sharing, web upload, scan-then-email, archive compression, these all need JPG.
Lossless requirements = keep TIFF or convert to PNG, not JPG.
Scanned documents = highly sensitive. Convert locally, always.
Quick answers about the tool