Two-page scanner TIFF
- Input
- 4,544 byte LZW TIFF with an RGB cover page at 300×200 and a grayscale second page at 220×160.
- Output
- 2,529 byte JPG at 300×200. Page one looked correct; page two did not appear anywhere in the converted file.
TIFF to JPG trades scanner and prepress structure for one broadly readable RGB JPEG from the decoded first TIFF frame.
From real runs
| Element | Result | What happens |
|---|---|---|
| First frame pixels | Changed | The 300×200 RGB page from our LZW TIFF became a 2,529 byte JPEG with normal quality-90 compression. |
| Additional frames | Lost | A second 220×160 grayscale frame in the same TIFF was not exported, zipped, or mentioned in the response body. |
| 16-bit tone values | Changed | The 16-bit grayscale TIFF converted to a 653 byte RGB JPEG, so high-bit-depth sample values were quantized. |
| CMYK color | Changed | The 180×120 CMYK proof decoded successfully and wrote a 1,341 byte RGB JPEG instead of preserving CMYK channels. |
| Transparency | Lost | JPEG output is opaque, and any alpha-like TIFF source data must be flattened before the file can be saved. |
| Compression model | Changed | CCITT, LZW, or deflate TIFF compression is replaced by lossy JPEG quantization controlled by the quality option. |
The 300×200 RGB page from our LZW TIFF became a 2,529 byte JPEG with normal quality-90 compression.
A second 220×160 grayscale frame in the same TIFF was not exported, zipped, or mentioned in the response body.
The 16-bit grayscale TIFF converted to a 653 byte RGB JPEG, so high-bit-depth sample values were quantized.
The 180×120 CMYK proof decoded successfully and wrote a 1,341 byte RGB JPEG instead of preserving CMYK channels.
JPEG output is opaque, and any alpha-like TIFF source data must be flattened before the file can be saved.
CCITT, LZW, or deflate TIFF compression is replaced by lossy JPEG quantization controlled by the quality option.
We converted our TIFF sample (19 KB) with Image engine on 2026-10-20. It took 35 ms and produced a 39 KB JPEG file, 2.1× larger than the input. The engine raised 2 warnings, listed below.
Input · sample.tif · 19 KB
1200 × 800 px, deflate
Output · sample.jpg · 39 KB
1200 × 800 px, baseline
TIFF to JPG does not OCR scanner output. A contract page converted this way may be easy to preview, but Deep Read is needed when names, dates, or clauses must become text.
ImageMagick 7
magick scan.tiff[0] -colorspace sRGB -quality 90 scan.jpgThe [0] selector is deliberate; remove it and handle filenames explicitly if you want every TIFF frame.
The HTTP API and the MCP server run the exact engine this page uses (Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=tiff&to=jpg.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.tif" -F "from=tiff" -F "to=jpg" \
-F 'options={"width":0}' \
--output output.jpg| Key | Applies to | Type | Default |
|---|---|---|---|
| width | Writing JPEG | number | 0 |
| height | Writing JPEG | number | 0 |
| fit | Writing JPEG | contain · cover · fill | contain |
| quality | Writing JPEG | number | 90 |
| background | Writing JPEG | string | #ffffff |
| stripMetadata | Writing JPEG | boolean | true |
No. The tested multi-frame TIFF produced one JPG from the first frame. Split the TIFF or choose a document output when page count matters.
The CMYK sample converted to an RGB JPEG. That is convenient for viewing, but it is not a print-ready CMYK deliverable.
Only for visual previews. The tested 16-bit TIFF became an RGB JPEG, so use PNG or TIFF if numeric tonal precision matters.