JPG to TIFF converter
Convert JPG images to TIFF format
Print shops, journals and imaging systems ask for TIFF because it is predictable and because it does not re-compress anything. Converting a JPEG to it satisfies the request without pretending to improve the picture: the artifacts the camera or the export baked in are copied across pixel for pixel, now stored uncompressed. The file written here is the conservative baseline variant - little-endian, RGB, eight bits per channel, one strip, no compression - which is what the widest range of software accepts without a word of complaint.
Key facts about JPG to TIFF converter
| Variant produced | Baseline TIFF with ten directory tags, byte order II, RGB photometric interpretation and one strip for the whole image. |
|---|---|
| Compression tag | Set to 1, meaning none. LZW, Deflate, PackBits and JPEG-in-TIFF are not offered by this encoder. |
| Quality relationship | Storing a JPEG uncompressed does not undo its compression - what you get is a large, exact copy of a previously compressed photograph. |
| Channels and depth | Three 8-bit samples per pixel. No alpha sample is written, which costs nothing here since JPEG has no transparency. |
| Predictable length | 134 bytes of header and tags plus three bytes per pixel, so a 4000x3000 photo is always 36,000,134 bytes. |
| Colour space | Plain 8-bit sRGB. No ICC profile is embedded and no CMYK separation is produced, so a press vendor expecting CMYK will need a conversion step. |
| Resolution | No XResolution or YResolution tag is written, so a layout program will fall back to its own default dpi assumption. |
| Pages | A single image file directory. Multi-page TIFF, layers and high-bit-depth scans are outside what this page writes. |
| Opens natively in | Photoshop, InDesign, macOS Preview, Windows Photos, GIMP and the scanning and prepress software that asked for TIFF in the first place. |
What happens to your file
Since no browser exposes a TIFF encoder, the page builds the file itself: after the JPEG is decoded and drawn, the canvas pixel array is stripped of its alpha bytes and packed into RGB triples, and a DataView writes the eight-byte file header and the ten tags ahead of that block before it is wrapped in a Blob. Your photograph is processed entirely in this tab, which also means the EXIF block with any GPS coordinates is dropped rather than forwarded - the TIFF contains pixels only.
About this tool
- 1
Add JPG or HEIC files
Both are accepted; an iPhone HEIC is decoded to JPEG data in the tab first and then written out as TIFF.
- 2
Leave the dimensions alone unless told otherwise
Print and submission requirements are usually expressed in pixels or dpi, so only use a resize preset when you know the target.
- 3
Convert
The pixel packing is a straightforward loop, so even large camera files finish in a moment - the size of the download is the notable part.
- 4
Check it opens
Open the .tif in Preview or Photoshop before sending it on; both read this variant directly.
| Input and output | Takes .jpg and .jpeg only (image/jpeg) and returns .tiff with the image/tiff type; any other extension is refused before decoding. |
|---|---|
| Conversion path | JPG to TIFF runs in three steps: an <img> element decodes the JPEG, baseline or progressive, in the browser; the pixels land on a 2D canvas in this tab; then getImageData feeds a baseline IFD writer that assembles the file in page memory. |
| Browser support | The JPEG side decodes in every browser ever shipped, while writing the TIFF needs nothing from the browser, the directory being written in the page. |
| Controls for this pair | No quality slider, TIFF not being a lossy target here, so the max-dimension presets from 3840 down to 200 px are the only way to hold the TIFF down in size against the JPG. |
| Batch, caps and naming | Twenty JPG files per run at 500 MB each; one result downloads as a single TIFF, several as converted-tiff-files.zip, zipped by JSZip 3.10 in page memory. |
| Device ceiling | The canvas caps it: past roughly 16,384 px a side Chromium refuses the bitmap and iPhone Safari gives up sooner, so an oversized JPG fails before any TIFF bytes exist. |
- If your recipient specified LZW or ZIP compression inside the TIFF, this file will not meet that requirement, because it is written uncompressed.
- A TIFF made from a JPEG is only as good as the JPEG - when the original raw or PSD is still around, export the TIFF from there instead.
- Twenty camera photos converted at once can approach a gigabyte, so convert in smaller groups if your disk or upload link is tight.
- Browsers will not preview the result in a tab; use a desktop viewer to confirm the file before handing it over.
- Meeting a publisher, print vendor or competition rule that names TIFF as the accepted format.
- Importing photographs into prepress or layout software that treats TIFF as its native placed image.
- Supplying uncompressed frames to a scientific or measurement application that does not read JPEG.
Related tools
View allNeed the opposite? Try TIFF to JPG
Works well with this4
Other JPG tools12
Updated