Convert HEIC to TIFF
HEIC is efficient for a phone library, but editing and archival systems often ask for TIFF instead. This route decodes the HEVC-backed image on the server and writes a TIFF copy with the same dimensions. It is a practical handoff, not a time machine: TIFF can protect the decoded pixels from another lossy save, but it cannot restore detail already removed by the HEIC encoder.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeDrop your HEIC file here, or click to browse
Up to 50 MB. Deleted automatically after 30 minutes.
What it does
- TIFF output for editors, print workflows and archive intake
- Server-side HEVC decoding for devices and browsers with limited support
- Original image dimensions retained
- No watermark and no sign-up
How to use HEIC to TIFF
- 1
Add the HEIC
Upload the camera original when possible, rather than a preview exported from a messaging app. The source quality sets the ceiling for the TIFF that follows.
- 2
Convert to TIFF
The server decodes the HEVC image and writes the primary raster image to a TIFF. The dimensions stay the same, while the output is normally much larger than the phone-friendly source.
- 3
Check the receiving specification
Open the TIFF in the intended editor or archive. Confirm its required color profile, bit depth, resolution metadata, compression and maximum size; a TIFF extension alone does not satisfy every intake checklist.
How it works
The upload is decoded by the server's HEVC-capable image path and then written as a TIFF raster. HEIC and TIFF are different encodings, so the server must read the compressed source and create a new file; renaming the extension cannot make an editor understand the bytes. The output keeps the source dimensions and represents the decoded image as a single TIFF image.
The server boundary is practical rather than ornamental. HEIC is a container around HEVC image compression, and decoder support depends on the operating system, device, browser build, and licensing choices made by the software vendor. A recent phone can open its own camera files while an older desktop utility reports an unknown format. Moving the decode to a known server environment makes the handoff more predictable, though a damaged or unusual source can still fail.
TIFF as an editing copy
TIFF is common in retouching, print, scanning, and image interchange because the container can describe several color modes, channel depths, profiles, and compression strategies. That makes it easier for a receiving application to accept a working file than a phone-oriented HEIC. The output is especially useful before an editor performs several saves that would otherwise keep re-encoding a lossy delivery format.
Do not read that as a promise of layers, CMYK, 16-bit samples, or a profile that the source did not contain. This conversion carries the decoded image into TIFF; it does not invent a print master or infer the exact requirements of a particular press, editor, or archive. If the next workflow supplied a technical checklist, compare the file with that checklist separately.
The archival question
TIFF is widely accepted in preservation work, but archival quality is a specification rather than a filename. A repository may reject a file because of its color space, bit depth, compression, embedded profile, missing capture metadata, or unsupported dimensions. A larger TIFF can also create storage and transfer costs that the intake system has planned around differently.
Keep the HEIC until the TIFF passes inspection and the project decides which one is the source of record. The HEIC may contain camera metadata or a compact untouched capture that is valuable even when TIFF is the required access or editing derivative. For a Live Photo or a file with depth information, retain the associated motion and sidecar assets as well; a flat TIFF cannot hold that whole experience.
Size and quality expectations
The TIFF will often be several times larger than the HEIC because a phone codec is optimized for compact library storage while TIFF favors predictable image workflows. That size increase is normal. It does not mean pixels were added, and it does not make a 12 megapixel photograph more detailed than the HEIC from which it was decoded. Use the TIFF where editing or intake compatibility pays for the storage, and retain the efficient HEIC for ordinary library or delivery use when appropriate.
Examples
An iPhone photo entering retouching
The TIFF gives an editor a stable working copy that will not add another HEIC compression pass on every save. It is not sharper than the phone original, and the HEIC should remain available as the untouched camera source.
A museum intake with a documented TIFF requirement
The conversion meets the container part of the handoff, but the repository still needs its own checks for profile, bit depth, metadata and compression. Passing a file named TIFF is not the same as passing an archive specification.
Frequently asked questions
Why does this conversion need a server?
HEIC normally contains HEVC-compressed image data, and HEVC decoder support is uneven across browsers, operating systems, and installed image libraries. A device may show the photo in its own camera app while an upload page or editor cannot decode the same file. The server provides the decoder path and performs the raster-to-TIFF handoff without asking the visitor's browser to understand the camera codec.
Is the TIFF a lossless version of the HEIC?
TIFF encoding can preserve every pixel produced by the HEIC decoder, but that does not restore information discarded when the HEIC was made. Fine texture, subtle color differences, and compression artifacts already present in the camera file remain in the decoded image. Think of the TIFF as a lossless working copy from this point forward, not as a higher-quality reconstruction of the original scene.
Is TIFF good for editing and archival storage?
It is often a better editing or interchange container than HEIC because many professional applications understand TIFF's color and compression options. Archival acceptance is more specific: a repository may require a profile, channel depth, embedded metadata, resolution tags, or a particular compression choice. Inspect the output against that repository's written specification before calling it a preservation master.
What happens to Live Photo motion and camera extras?
This route produces a single raster TIFF, so it is the still image rather than a Live Photo package containing motion. Depth maps, portrait masks, and other sidecar layers do not become separate editable TIFF layers here. Keep the phone original and its associated assets when those computational photography details matter to the project.