Reference Formats
TGA
Truevision's early-1980s raster format, one of the first to support an alpha channel, still used today mainly as a texture and render-output format in games and VFX pipelines.
Extension
.tga
Full name
Truevision Graphics Adapter / Targa File Format
Introduced
1984 (original specification, with AT&T EPICenter and Island Graphics); Version 2.0 (alpha channel, extension area) in 1989
Vendor
Truevision Inc. (now part of Avid Technology)
What is inside the container
TGA supports lossless RLE compression (similar to PackBits) or uncompressed storage, at practical color depths of 8, 15, 16, 24, or 32 bits with an alpha channel of up to 15 bits. Its metadata mechanism is the proprietary TGA 2.0 'extension area' — author name, comments, timestamp, job ID, software version, gamma value — rather than standard EXIF, IPTC, or XMP, and it has no documented ICC color profile support, which limits its color-management usefulness in a modern DAM.
How to open it
For archives
Do not use TGA as a DAM long-term master unless the asset genuinely originates from a game or VFX production pipeline where TGA is the native format (textures, render passes). Otherwise convert to TIFF or PNG for archival, since TGA lacks ICC color management and standardized EXIF/IPTC/XMP metadata, limiting both searchability and color-accurate long-term reuse.
TGA was defined in 1984 (with input from AT&T EPICenter and Island Graphics) to give Truevision’s TARGA and VISTA graphics cards — among the first IBM-PC-compatible cards capable of true color — a matching file format. Version 2.0, released in 1989, added the alpha channel and the extension-area metadata block, making TGA one of the earliest formats to support transparency at all, well before PNG or GIF offered anything comparable.
TGA survives today almost entirely inside game and VFX production pipelines, where it remains a standard texture and render-output format supported natively by tools like Unreal Engine, Unity, Photoshop, and GIMP. In a DAM context, this means TGA assets are typically production intermediates — textures, render passes, mattes — rather than finished deliverables, and the DAM’s job is usually to catalog and version them within a larger asset pipeline rather than serve them as public-facing content.
The metadata challenge is real: TGA’s proprietary extension area (author, timestamp, software ID, gamma) is not EXIF, IPTC, or XMP, so a DAM ingesting TGA files needs an explicit mapping strategy for those fields — or has to fall back on sidecar files and database metadata rather than embedded extraction — to keep production assets searchable at the same level a JPEG or TIFF would be.
Frequently asked
Should a DAM use TGA as a long-term master format?
Only if the asset genuinely originates from a game or VFX production pipeline where TGA is the native format, such as textures or render passes. Otherwise convert to TIFF or PNG for archival, since TGA lacks ICC color management and standardized EXIF/IPTC/XMP metadata.
What metadata can a TGA file carry?
TGA's metadata mechanism is the proprietary TGA 2.0 'extension area' — author name, comments, timestamp, job ID, software version, gamma value — rather than standard EXIF, IPTC, or XMP, and it has no documented ICC color profile support.
How does a DAM handle TGA's metadata on ingest?
It needs an explicit mapping strategy for the proprietary extension-area fields, or has to fall back on sidecar files and database metadata rather than standard embedded extraction, to keep production assets searchable.
Where is TGA still commonly used today?
Almost entirely inside game and VFX production pipelines, where it remains a standard texture and render-output format supported natively by tools like Unreal Engine, Unity, Photoshop, and GIMP.
Is TGA compression lossy or lossless?
Lossless — TGA supports RLE compression similar to PackBits, or uncompressed storage.
What color depths and transparency does TGA support?
Practical color depths of 8, 15, 16, 24, or 32 bits, with an alpha channel of up to 15 bits.
Why is TGA historically significant?
It was one of the first raster formats to support an alpha channel, added in Version 2.0 in 1989, well before PNG or GIF offered comparable transparency.
Why is TGA a poor color-management fit for a modern DAM?
It has no documented ICC color profile support, which limits color-accurate long-term reuse — converting to TIFF or PNG for archival preserves both metadata and proper color management.
Sources
- TGA was originally defined in 1984 with input from AT&T EPICenter and Island Graphics; Version 2.0 in 1989 added the alpha channel and extension area. checked 2026-08-07 — Wikipedia: Truevision TGA