Image MIME Reference
HTJ2K-Codestream
High-Throughput JPEG 2000 Codestream
image/jphc
VS
Windows Icon (Legacy MIME)
image/x-icon
ICO
A complete technical comparison of High-Throughput JPEG 2000 Codestream and Windows Icon (Legacy MIME) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
ICO wins on browser support
Feature Support
| Feature | HTJ2K-Codestream | ICO |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| 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
Windows Icon (Legacy MIME)
image/x-icon
Extension
.ico
Container
ICO Directory Structure
Compression
Uncompressed (DIB/BMP) / Deflate (Embedded PNG)
Algorithm
NoneDeflate (via PNG)
Color Depth
1-bit, 4-bit, 8-bit, 24-bit (True Color), 32-bit (RGBA)
Developed by
Microsoft Corporation
Released
1985
Magic Bytes
00 00 01 00
Browser Support Comparison
| Browser | HTJ2K-Codestream | ICO |
|---|---|---|
Chrome
|
✕ |
✓ 1
|
Firefox
|
✕ |
✓ 1
|
Safari
|
✕ |
✓ 1
|
Edge
|
✕ |
✓ 12
|
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
ICO
ICO Strengths
- Universally supported by every web browser in existence for website favicons
- Packs multiple resolutions into a single file, eliminating the need to serve different files for the taskbar vs. the desktop
- Modern support for embedded PNGs (since Windows Vista) allows for excellent 32-bit transparency (alpha channels) and drastically reduced file sizes
Limitations
- Internal file structure is convoluted due to decades of legacy cruft, such as the requirement for BMP data to lack a standard file header but double the height property for an archaic XOR/AND mask
- Larger file size compared to a single optimized PNG or SVG, as it literally stores the same image multiple times at different scales
- The MIME type landscape is highly fragmented (x-icon vs. vnd.microsoft.icon), causing occasional caching or strict-MIME validation errors on restrictive servers
When to choose which format
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems
ICO
Use ICO when…
- Website Favicons (favicon.ico)
- Windows Application Executable Icons (.exe)
- Desktop Shortcut Icons