Add your HEIF file
Drop one or more .heif 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 .heif image to .tga 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 .heif image to .tga re-encodes the pixels for a different balance of size, quality, and support. A .heif file uses the High Efficiency Image File Format, a codec-agnostic container standard rather than a single compression scheme. Where .heic specifically means HEVC-coded content, the .heif extension signals the general container, which can in principle wrap HEVC, AV1, or even JPEG payloads along with sequences and derived images.
A .tga file is a Truevision TARGA raster image, one of the earliest formats built for true-color graphics with an alpha channel. Long after its video-hardware origins faded, .tga remains a staple texture format in game development pipelines and 3D tools because it is simple, lossless, and alpha-capable. For this route the practical draw is trivially simple to parse, with decades of stable tooling and reliable 32-bit RGBA storage without compression surprises — balanced against photographic content compresses poorly compared with PNG, let alone WebP, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .heif, the extension alone does not reveal the codec inside, so a given .heif file may or may not decode on a given device. Switching to .tga buys you trivially simple to parse, with decades of stable tooling, which is why it is the better fit for game textures and sprite sheets, where engines have imported TGA for decades. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | HEIF image (.heif) | Targa image (.tga) |
|---|---|---|
| Format type | Lossy — discards detail it judges invisible to shrink files | Lossless — every pixel or sample is preserved exactly |
| How it stores data | iSO BMFF box structure: items, item properties, and item references describe images declaratively | stores 8-bit grayscale, 16-bit, 24-bit, or 32-bit pixels, the last carrying an 8-bit alpha channel |
| Strongest at | container-level workflows that need bursts, brackets, or multi-resolution imagery in one file | game textures and sprite sheets, where engines have imported TGA for decades |
| Weak spot | the extension alone does not reveal the codec inside, so a given .heif file may or may not decode on a given device | photographic content compresses poorly compared with PNG, let alone WebP |
Drop one or more .heif 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 .tga in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if TGA 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 TGA file. Outputs keep the original filename with the .tga extension.
No new loss is introduced — since heif is lossy-oriented and tga is lossless-oriented, everything the .heif file still contains is carried over exactly. What was already discarded by the original lossy encode cannot be recovered, though; converting to .tga does not "restore" quality.
Yes — the .heif 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.
Game engines (Unity, Unreal), 3D suites (Blender, Maya, 3ds Max), and professional editors like Photoshop and GIMP all read and write TGA. Consumer software largely ignores it: browsers will not render it and stock Windows/macOS viewers need plugins, so distribution outside content pipelines means converting to PNG first.
Larger, sometimes much larger. A lossless .tga must store every pixel or sample the decoder produced, without the perceptual shortcuts .heif used. Use this route for editing headroom, not for saving space.
In .heif, eXIF and XMP are first-class metadata items in the container, with ICC profiles or CICP parameters describing color; what survives conversion depends on the tool, not the format. 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.