Image MIME Reference
JXL
JPEG XL
image/jxl
VS
Truevision TGA (Legacy MIME Alias)
image/x-tga
TGA
A complete technical comparison of JPEG XL and Truevision TGA (Legacy MIME Alias) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
JXL wins on browser support
Feature Support
| Feature | JXL | TGA |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | Yes | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
JPEG XL
image/jxl
Extension
.jxl
Container
ISOBMFF / JPEG XL Codestream
Compression
Lossy (VarDCT) / Lossless (Modular)
Algorithm
VarDCT (Variable block-size DCT)Modular (Predictive coding for lossless)
Color Depth
8-bit, 10-bit, 12-bit, 16-bit, 32-bit (Float)
Developed by
Joint Photographic Experts Group (JPEG)
Released
2021
Magic Bytes
FF 0A (Codestream) / 00 00 00 0C 4A 58 4C 20 0D 0A 87 0A (Container)
Truevision TGA (Legacy MIME Alias)
image/x-tga
Extension
.tga.icb.vda.vst
Container
Truevision TGA Footer/Header
Compression
Uncompressed / Run-Length Encoding (RLE)
Algorithm
NoneRLE
Color Depth
8-bit (Grayscale or Indexed), 16-bit (High Color), 24-bit (True Color), 32-bit (True Color with Alpha Channel)
Developed by
Truevision Inc.
Released
1984
Magic Bytes
54 52 55 45 56 49 53 49 4F 4E 2D 58 46 49 4C 45 2E 00 (At the end of the file)
Browser Support Comparison
| Browser | JXL | TGA |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✓ 17+
|
✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
JXL
JXL Strengths
- Capable of losslessly recompressing legacy JPEG files, saving ~20% space while retaining perfect byte-for-byte restorability
- Highly superior progressive decoding (Saliency-driven), allowing recognizable images to load extremely fast on slow connections
- Outperforms WebP and competes favorably with AVIF, especially at high-fidelity settings and for complex textures/photography
- Royalty-free with an open-source reference implementation (libjxl)
Limitations
- Google's removal of JXL support from Chrome severely hindered its adoption as a universal web standard
- Lack of hardware decoding chips compared to video-derived codecs like AVIF (AV1)
- File parsing logic is complex due to the split between raw codestreams and ISOBMFF containers
TGA
TGA Strengths
- Incredibly simple byte layout allows developers to write custom loaders and exporters in a few dozen lines of code, bypassing the need for heavy external libraries
- Native support for 8-bit alpha channels ensures flawless transparency masking for real-time 3D rendering
- Fast, predictable RLE decoding requires almost no CPU overhead compared to DEFLATE (PNG) or DCT (JPEG)
Limitations
- RLE compression is relatively weak by modern standards, resulting in large file sizes
- Lacks a standard magic byte header at the beginning of the file, making file-sniffing unreliable for older v1.0 files
- Zero support in web browsers; must be converted to PNG or WebP for web delivery
When to choose which format
JXL
Use JXL when…
- High-End Web Delivery (via Safari/Polyfills)
- HDR Photography
- Legacy JPEG Archiving
- Digital Art & Image Storage
TGA
Use TGA when…
- Video Game 3D Textures and Materials
- 3D Rendering and Animation Sequences
- Legacy Video Production Workflows