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

Adobe Photoshop Native, long-standing TGA import/export support

GIMP Built-in TGA import/export plug-in

Game engines / VFX tools Universally supported as a texture format in tools like Unreal Engine and Unity

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?

TGA textures remain common in real-time 3D pipelines: game engines like Unreal Engine and Unity import them directly for sprites, UI elements, and material maps, and 3D/VFX render passes are often output as TGA sequences because the format is simple and fast to parse. Editing tools such as Photoshop and GIMP still support TGA import/export for this reason, but outside game and VFX production it has largely been replaced by PNG, TIFF, or EXR.

Is TGA compression lossy or lossless?

TGA compression is always lossless. Pixel data can be stored raw or compressed with RLE (run-length encoding), similar to PackBits, which shortens runs of identical pixels without discarding any values. There is no lossy option and no chroma subsampling, unlike JPEG. RLE compresses simple images with flat color areas—icons, sprites, line art—well, but does little for noisy photographic content, where files stay close to raw size.

What color depths and transparency does TGA support?

TGA supports pixel depths of 8, 15, 16, 24, or 32 bits per pixel in practice, even though the format header allows values up to 255. The 8-bit mode is typically indexed color or grayscale; 24-bit is truecolor RGB with no alpha. Transparency comes via an alpha channel of up to 8 bits, giving full RGBA support at 32 bits per pixel, or a single transparency bit in 16-bit mode.

Why is TGA historically significant?

TGA was one of the first widely used raster formats to include a native alpha channel, added in version 2.0 in 1989, years before formats like PNG standardized transparency. Originally created in 1984 for Truevision's TARGA graphics and video-capture boards, its simple, easy-to-parse structure—raw or RLE-compressed pixel data plus a compact header—made it a natural fit for early 3D rendering and game engines, cementing its role in graphics pipelines for decades.

Why is TGA a poor color-management fit for a modern DAM?

TGA has no documented support for embedded ICC color profiles, the mechanism TIFF, PNG, and JPEG use to preserve consistent color across devices and software. Its only color-related metadata is a single gamma value stored in the proprietary TGA 2.0 extension area, alongside author, comments, and job ID fields—not standardized EXIF, IPTC, or XMP. Without an ICC profile, a DAM cannot guarantee accurate color reproduction, so archival conversion to TIFF or PNG is recommended.

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