Free online converter for converting files to TGA.
We ensure quality, convenience, and support for all formats.
| Data type | Image |
| MIME type | image/x-tga |
| Developer | Truevision, Inc. |
| Primary use cases | Textures and assets in game development/3D rendering; interchange in graphics pipelines; simple archival of RGBA bitmaps |
TGA (TARGA) is a simple raster image format known for straightforward structure, optional lossless RLE compression, and common support for 24/32-bit images including alpha.
| Data type | Image |
| MIME type | image/x-tga |
| Compression | Optional lossless RLE |
| Color depth | Commonly 8-bit (indexed or grayscale), 16-bit (usually 5-5-5 with 1 attribute bit), 24-bit (8-8-8), and 32-bit (8-8-8 plus 8-bit alpha/attribute). Some tools may also encounter 15-bit variants. |
| Color space | Primarily RGB/RGBA (with optional alpha/attribute bits), also grayscale and indexed color via palette; pixel byte order is commonly BGR(A) in practice |
| Transparency support | Yes |
| Animation support | No |
| EXIF / Metadata support | No |
| Metadata | Limited. TGA supports an Image ID field; TGA 2.0 extension area can store basic metadata (author/software/date-time/comments), a thumbnail (postage stamp), and color correction table. No standard Exif and typically no ICC profile support. |
| Structure type | Header + optional ID/color map + pixel data (packed) + optional footer/extension area (v2.0) |
| Standard / Specification | Truevision TGA File Format Specification (v2.0, 1989) |
| Typical file size | Often relatively large: uncompressed 24-bit is ~3 bytes/pixel, 32-bit is ~4 bytes/pixel; RLE can help for flat-color areas but may not reduce photographic images much |
| Year introduced | 1984 |
The TGA file format offers several advantages that make it suitable for common use cases.
The TGA file format has certain limitations that may affect its use in specific scenarios.
TGA images are widely supported and can be viewed on most devices and platforms.
Treat as untrusted input: malformed headers or RLE streams can trigger bugs in decoders; validate dimensions and expected data size before processing
Technically proprietary, but the specification is widely available and generally considered safe to implement; no widely enforced licensing/patent constraints in modern use