TIFF is lossless, alpha, and several images inside a single file. JPEG is lossy compression tuned for human vision, and no alpha channel at all. ImageMagick sits between the two, and this page says exactly what happens to a TIFF file on the way to becoming a JPG one.
What runs when a TIFF file becomes JPG
ImageMagick 6.9.12, on a machine we rent and watch. Your TIFF file is uploaded once, ImageMagick runs once, the JPG comes back, and neither file is kept. TIFF to JPG is one of the 3649 pairs that engine was probed on with a real file, which is why it has a page here and why the pairs the probe could not prove do not.
What survives from the TIFF into the JPG
The pixel dimensions of your TIFF file. The JPG comes out the size the TIFF went in, because nothing on this path resizes anything.
What TIFF to JPG costs you
Transparency. JPG has no alpha channel, so the engine composites your TIFF image onto white before encoding. Without that step ImageMagick lays black underneath, and a transparent TIFF logo comes back as a black rectangle.
Every page of the TIFF but the first. A TIFF file can hold several images in one container; a JPG file holds exactly one.
Exactness. JPG is a lossy encoding, so the file you get back approximates the TIFF you sent. The artefacts appear once and never come out again, which is why converting the JPG back to TIFF afterwards restores nothing.
If a model is going to read the JPG
A JPG file is pixels, and pixels are expensive for a model to read. Handed this JPG, an assistant spends its budget looking at the picture rather than reading it, and it will paraphrase what it thinks it saw. If your TIFF is mostly words, the useful move is to pull the text out of it, not to change which picture format holds it.
TIFF to JPG, measured rather than promised
Running TIFF to JPG against the real engine with a real file, ImageMagick wrote 1,568 bytes of JPG in under a tenth of a second, machine otherwise idle. That is one TIFF file on one day and not an average, which is why the number is given together with the file that produced it.
The TIFF to JPG verdict was reached by a format signature, meaning at least four bytes unique to the format were found at the right offset. Which check was used matters, because they do not all prove the same thing, and a status code of 200 proves nothing whatsoever about whether the JPG file has anything inside it.
The same TIFF file, sent somewhere else
Other outputs the probe measured out of a TIFF file, so the cost of choosing JPG can be read against something. Sizes do not compare across engines, because each family was probed with its own TIFF witness file.
TIFF to PDF: 118,721 bytes in under a tenth of a second, verified by a format signature.
TIFF to PNG: 815 bytes in under a tenth of a second, verified by a format signature.
TIFF to WEBP: 370 bytes in under a tenth of a second, verified by a format signature.
TIFF to GIF: 3,512 bytes in 0.1 seconds, verified by a format signature.
Other ways into JPG, and what they measured
Among the published routes into JPG, TIFF is the tenth largest output of the 13 measured. The witness files differ, so this ranks the probe run and not your document.
AVIF to JPG: 1,705 bytes in under a tenth of a second.
SVG to JPG: 2,483 bytes in under a tenth of a second.
PSD to JPG: 1,568 bytes in under a tenth of a second.
ICO to JPG: 1,568 bytes in under a tenth of a second.
HEIF to JPG: 1,666 bytes in under a tenth of a second.
What we will not pretend about TIFF to JPG
A TIFF file over 25 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
A TIFF to JPG run that passes 30 seconds is killed, and the ImageMagick process is killed with it. A run left behind would sit on one of the machine's two cores until somebody noticed.
No text is read out of the TIFF anywhere on this path. Converting a picture to JPG never turns it into words, whatever the picture happens to contain.
ImageMagick was not saturated at sixteen simultaneous conversions: it held 47.5 a second while latency moved from 0.22 s to 0.34 s, and the service memory did not move off 51 MB. That is the measured headroom behind TIFF to JPG, not a marketing number.
One TIFF file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
TIFF to JPG: what people ask
What actually converts my TIFF file to JPG?
ImageMagick does it, 6.9.12, on a machine we rent and watch. Not a browser trick and not somebody else service: the TIFF file is uploaded once, ImageMagick runs once, the JPG comes back, and neither file is kept afterwards.
How long does TIFF to JPG take?
On the file the probe used, ImageMagick took under a tenth of a second and wrote 1,568 bytes of JPG. That is one real measurement on one real TIFF file, not an average and not a promise about yours: a larger TIFF takes longer, and past 30 seconds the run is stopped.
What do I lose going from TIFF to JPG?
The one to know about first: Transparency. JPG has no alpha channel, so the engine composites your TIFF image onto white before encoding. Without that step ImageMagick lays black underneath, and a transparent TIFF logo comes back as a black rectangle.
Why did my transparent TIFF background turn white in the JPG?
Because JPG has no alpha channel and something has to sit behind the picture. The engine puts white there on purpose. Left to itself ImageMagick puts black, and a transparent TIFF logo comes back as a black rectangle. If you need the transparency, send the TIFF to PNG or WebP instead.
Is TIFF to JPG free?
There is a free allowance every month, and one TIFF to JPG conversion costs half a credit against it. When the allowance runs out the tool says so and stops, rather than quietly handing you a worse JPG.