Add your HDR file
Drop one or more .hdr files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Converting a .hdr image to .tiff re-encodes the pixels for a different balance of size, quality, and support. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Converting a .hdr image to .tiff re-encodes the pixels for a different balance of size, quality, and support. An .hdr file is a Radiance RGBE image, the original high-dynamic-range raster format. Each pixel stores three 8-bit mantissas and one shared 8-bit exponent, so 32 bits per pixel cover a luminance range no ordinary 8-bit format can express. It is still the everyday container for the HDRI environment maps used to light 3D scenes.
A .tiff file is a Tagged Image File Format raster, the long-standing archival and prepress standard for images that must not lose a single bit. Its tag-based structure lets one .tiff hold multiple pages, layers of metadata, and pixel formats from 1-bit fax scans to 32-bit floating-point channels. For this route the practical draw is losslessly preserves any bit depth and color space you throw at it and decades of stability make it the safest long-term archival bet — balanced against files are huge — often 10x a visually identical JPEG, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .hdr, only about 1 percent precision per channel, and the shared exponent hurts saturated colours. Switching to .tiff buys you losslessly preserves any bit depth and color space you throw at it, which is why it is the better fit for archival masters for museums, libraries, and digitization projects. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | Radiance HDR image (.hdr) | TIFF image (.tiff) |
|---|---|---|
| Format type | Lossy — discards detail it judges invisible to shrink files | Lossless — every pixel or sample is preserved exactly |
| How it stores data | rGBE encoding: three 8-bit mantissas plus one shared 8-bit exponent, 32 bits per pixel | structured as Image File Directories (IFDs) of numbered tags, allowing multiple images per file |
| Strongest at | hDRI environment maps and sky domes for image-based lighting in Blender, Unreal, Unity and V-Ray | archival masters for museums, libraries, and digitization projects |
| Weak spot | only about 1 percent precision per channel, and the shared exponent hurts saturated colours | files are huge — often 10x a visually identical JPEG |
| Metadata | the text header carries EXPOSURE, GAMMA, PRIMARIES, SOFTWARE and free-form comment lines. There is no EXIF, XMP or ICC profile block, and this converter's raster outputs do not carry the header lines across | eXIF is itself structured as TIFF tags, so TIFF holds it natively, alongside XMP packets, IPTC records, ICC profiles, and GeoTIFF georeferencing tags |
Drop one or more .hdr files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .tiff in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if TIFF is selectable, the route is real and validated.
Press Convert. Decoding and re-encoding happen on your device using the browser's native image pipeline and hand-tuned encoders.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid TIFF file. Outputs keep the original filename with the .tiff extension.
No new loss is introduced — since hdr is lossy-oriented and tiff is lossless-oriented, everything the .hdr file still contains is carried over exactly. What was already discarded by the original lossy encode cannot be recovered, though; converting to .tiff does not "restore" quality.
Yes — the .hdr file is processed inside your browser tab and never uploaded. Decoding and re-encoding happen on your device using the browser's native image pipeline and hand-tuned encoders. Close the tab and the file is gone from memory.
Every serious image editor, scanner driver, and DTP application on Windows, macOS, and Linux reads TIFF, and both major OSes preview it natively. Web browsers are the gap: Chrome, Firefox, and Edge will download rather than display a .tiff, so web delivery always requires conversion to PNG, JPEG, or WebP.
Larger, sometimes much larger. A lossless .tiff must store every pixel or sample the decoder produced, without the perceptual shortcuts .hdr used. Use this route for editing headroom, not for saving space.
In .hdr, the text header carries EXPOSURE, GAMMA, PRIMARIES, SOFTWARE and free-form comment lines. There is no EXIF, XMP or ICC profile block, and this converter's raster outputs do not carry the header lines across. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.