Image MIME Reference
FITS
Flexible Image Transport System
image/fits
VS
High-Throughput JPEG 2000 Codestream
image/jphc
HTJ2K-Codestream
A complete technical comparison of Flexible Image Transport System 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 | FITS | HTJ2K-Codestream |
|---|---|---|
| Transparency (Alpha) | ✕ No | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | Yes |
| HDR Support | Yes | Yes |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
Flexible Image Transport System
image/fits
Extension
.fits.fit.fts
Container
FITS
Compression
Uncompressed / Tile Compressed (Rice, GZIP)
Algorithm
UncompressedRiceGZIPHcompress
Color Depth
8-bit, 16-bit, 32-bit, 64-bit (Float/Double)
Developed by
IAU FITS Working Group / NASA
Released
1981
Magic Bytes
53 49 4D 50 4C 45 20 20 3D 20
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
Browser Support Comparison
| Browser | FITS | HTJ2K-Codestream |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
FITS
FITS Strengths
- The undisputed global standard for archiving and sharing astronomical data
- Self-documenting: Headers are written in plain ASCII, ensuring data is readable decades later regardless of software
- Supports incredibly high dynamic range, N-dimensional arrays, and complex binary tables
Limitations
- No support in standard consumer software or web browsers
- Uncompressed raw FITS files from modern telescopes can be excessively large
- Does not use standard metadata models like EXIF or XMP, requiring specialized parsers
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
FITS
Use FITS when…
- Astronomy & Astrophysics
- Space Telescope Data (Hubble, JWST)
- Scientific Data Archiving
- Spectroscopy
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems