Image MIME Reference
HTJ2K-Codestream
High-Throughput JPEG 2000 Codestream
image/jphc
VS
PiCture eXchange
image/x-pcx
PCX
A complete technical comparison of High-Throughput JPEG 2000 Codestream and PiCture eXchange — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | HTJ2K-Codestream | PCX |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
High-Throughput JPEG 2000 Codestream
image/jphc
Extension
.jhc
Container
None (Raw Codestream)
Compression
Lossy / Lossless
Algorithm
High-Throughput JPEG 2000 (HTJ2K)
Color Depth
8-bit, 16-bit, 32-bit, 38-bit
Developed by
Joint Photographic Experts Group (JPEG)
Released
2019
Magic Bytes
FF 4F FF 51
PiCture eXchange
image/x-pcx
Extension
.pcx
Container
ZSoft Proprietary Header (128 bytes)
Compression
Run-Length Encoding (RLE)
Algorithm
ZSoft RLE
Color Depth
1-bit (Monochrome), 4-bit (16 colors), 8-bit (256 colors), 24-bit (True Color)
Developed by
ZSoft Corporation
Released
1985
Magic Bytes
0A (followed by version, e.g., 0A 05 01 08)
Browser Support Comparison
| Browser | HTJ2K-Codestream | PCX |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
HTJ2K-Codestream
HTJ2K-Codestream Strengths
- Extremely fast encoding and decoding capabilities due to the parallelizable block coder
- Minimal file overhead since it lacks container headers and metadata
- Ideal for streaming applications or embedded systems where parsing a full container is unnecessary
Limitations
- Lacks standard metadata support (like EXIF, XMP, or ICC color profiles) since there is no container structure
- Zero native web browser compatibility
- Difficult to distinguish from standard JPEG 2000 codestreams without deeply parsing the internal marker segments
PCX
PCX Strengths
- Incredibly simple RLE algorithm makes it very fast to decode, which was historically vital for early 3D video game engines
- Retains crisp, lossless pixel data suitable for pixel art and interface assets
- Well-documented and highly supported by older desktop publishing and image editing software
Limitations
- Extremely inefficient compression by modern standards, producing large file sizes compared to PNG
- Lacks modern imaging features such as alpha channel transparency, EXIF metadata, and color profiles
- Zero support in web browsers; must be converted to PNG for web use
When to choose which format
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems
PCX
Use PCX when…
- MS-DOS and Early Windows Graphics
- 1990s Video Game Assets (Textures, UI)
- Retro Computing Archival