Photo-style JPEG
- Input
- 13,991 byte JPG at 640×480 with a gradient background and a white label drawn into the pixels.
- Output
- 234,942 byte TIFF at 640×480, RGB, tiff_adobe_deflate. The file was much larger and kept JPEG-era artifacts.
JPG to TIFF moves a decoded JPEG photo into a TIFF container, often increasing size without recovering detail lost by JPEG.
From real runs
| Element | Result | What happens |
|---|---|---|
| Dimensions | Kept | The 640×480 JPEG wrote a 640×480 TIFF, so no resize happened with default options. |
| File size | Changed | The 13,991 byte source expanded to a 234,942 byte TIFF using tiff_adobe_deflate compression. |
| Color mode | Kept | The output opened as RGB TIFF, matching the decoded JPEG color mode from the source photo. |
| JPEG artifacts | Kept | Block noise and softened detail already in the JPEG are stored faithfully inside the TIFF pixels. |
| Transparency | Lost | A JPEG source has no alpha channel, so the TIFF output remains fully opaque RGB imagery. |
| Resolution metadata | Changed | The inspected TIFF reported 1×1 dpi, so this conversion should not be used to assert scan resolution. |
The 640×480 JPEG wrote a 640×480 TIFF, so no resize happened with default options.
The 13,991 byte source expanded to a 234,942 byte TIFF using tiff_adobe_deflate compression.
The output opened as RGB TIFF, matching the decoded JPEG color mode from the source photo.
Block noise and softened detail already in the JPEG are stored faithfully inside the TIFF pixels.
A JPEG source has no alpha channel, so the TIFF output remains fully opaque RGB imagery.
The inspected TIFF reported 1×1 dpi, so this conversion should not be used to assert scan resolution.
We converted our JPEG sample (42 KB) with Image engine on 2026-10-20. It took 43 ms and produced a 145 KB TIFF file, 3.4× larger than the input. The engine raised 1 warning, listed below.
Input · sample.jpg · 42 KB
1200 × 800 px, baseline
Output · sample.tif · 145 KB
1200 × 800 px, deflate
JPG to TIFF does not make a photographed page searchable. Use Deep Read or OCR before relying on text inside the converted TIFF.
ImageMagick 7
magick photo.jpg -compress Zip photo.tiffThe command changes the container and compression method, not the damage already introduced by JPEG encoding.
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=jpg&to=tiff.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.jpg" -F "from=jpg" -F "to=tiff" \
-F 'options={"dpi":96}' \
--output output.tif| Key | Applies to | Type | Default |
|---|---|---|---|
| dpi | Reading JPEG | number | 96 |
No. It stores the decoded JPEG pixels in TIFF, including artifacts and blur that were already present.
TIFF deflate stores RGB pixels differently from JPEG's lossy photo compression. Our 13,991 byte JPG became 234,942 bytes.
No. JPEG starts opaque, and the tested TIFF output opened as RGB with no alpha channel.