Free webp to jpg
Image MIME Reference
Apple-ICNS

Apple Icon Image

image/x-icns
VS

High-Throughput JPEG 2000 Codestream

image/jphc
HTJ2K-Codestream

A complete technical comparison of Apple Icon Image and High-Throughput JPEG 2000 Codestream — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature Apple-ICNS HTJ2K-Codestream
Transparency (Alpha) Yes Yes
Animation Support ✕ No ✕ No
Progressive Loading ✕ No Yes
HDR Support ✕ No Yes
EXIF Metadata ✕ No ✕ No
ICC Color Profile Yes ✕ No
Apple Icon Image
image/x-icns
Extension
.icns
Container Chunk-based (OSType Header)
Compression Uncompressed (Legacy) / PNG (Modern) / JPEG 2000 (Modern)
Algorithm
NoneDeflate (via embedded PNG)Wavelet (via embedded JP2)
Color Depth 1-bit (Monochrome), 4-bit, 8-bit, 24-bit (RGB), 32-bit (RGBA)
Developed by Apple Inc.
Released 2001
Magic Bytes
69 63 6E 73
Full Apple-ICNS reference →
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
Full HTJ2K-Codestream reference →

Browser Support Comparison

Browser Apple-ICNS HTJ2K-Codestream
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
Apple-ICNS

Apple-ICNS Strengths

  • Seamlessly handles multi-resolution scaling on macOS, perfectly serving both standard and high-DPI (Retina) displays from a single asset
  • Modern versions efficiently embed standard PNG files, making it much easier to parse the high-resolution layers than the legacy raw pixel formats
Limitations
  • Strictly bound to the Apple ecosystem; completely useless natively on Windows, Linux, or the Web
  • The internal chunking structure is notoriously messy, utilizing dozens of different undocumented, legacy OSType tags spanning 20+ years of Apple history
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

When to choose which format

Apple-ICNS
Use Apple-ICNS when…
  • macOS Application Bundles (.app)
  • macOS Folder Customization
  • Apple Disk Image (.dmg) Styling
HTJ2K-Codestream
Use HTJ2K-Codestream when…
  • Medical Imaging Pipelines
  • Geospatial Data Streaming
  • Digital Cinema
  • Embedded Systems
Share this comparison