Image MIME Reference
FST-Image
FAST Search & Transfer Image
image/vnd.fst
VS
High-Throughput JPEG 2000 Codestream
image/jphc
HTJ2K-Codestream
A complete technical comparison of FAST Search & Transfer 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 | FST-Image | HTJ2K-Codestream |
|---|---|---|
| Transparency (Alpha) | ✕ No | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | Yes |
| HDR Support | ✕ No | Yes |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
FAST Search & Transfer Image
image/vnd.fst
Extension
.fst
Container
Proprietary FAST Container
Compression
Proprietary
Algorithm
Unknown (Proprietary FAST encoding)
Color Depth
Unknown
Developed by
FAST Search & Transfer ASA (Arild Fuldseth)
Released
2000
Magic Bytes
Unknown (Proprietary)
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 | FST-Image | HTJ2K-Codestream |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
FST-Image
FST-Image Strengths
- Historically served as an optimized, compressed format for FAST's early multimedia and live streaming engines over constrained late-1990s bandwidth
Limitations
- Completely obsolete and non-functional in modern software ecosystems
- Undocumented, closed-source binary structure with zero support in modern image processing libraries
- Shares its file extension with several other distinct file types (such as FL Studio state files or FAST Search dictionaries), leading to easy misidentification
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
FST-Image
Use FST-Image when…
- Historical FAST Enterprise Search Indexing
- Legacy Proprietary Multimedia Streaming (late 1990s)
- Internal Media Transmission
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems