Free webp to jpg
Image MIME Reference
FITS

Flexible Image Transport System

image/fits
VS

Khronos Texture 2.0

image/ktx2
KTX2

A complete technical comparison of Flexible Image Transport System and Khronos Texture 2.0 — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature FITS KTX2
Transparency (Alpha) ✕ No Yes
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
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
Full FITS reference →
Khronos Texture 2.0
image/ktx2
Extension
.ktx2
Container KTX 2.0
Compression Basis Universal (ETC1S / UASTC) / Zstandard (zstd) Supercompression / Uncompressed
Algorithm
ETC1SUASTCZstandard (zstd)Raw GPU Formats (ASTC, BCn)
Color Depth 8-bit, 16-bit, 32-bit (Float)
Developed by Khronos Group
Released 2021
Magic Bytes
AB 4B 54 58 20 32 30 BB 0D 0A 1A 0A
Full KTX2 reference →

Browser Support Comparison

Browser FITS KTX2
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE 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
KTX2

KTX2 Strengths

  • Universal hardware compatibility: write once, transcode anywhere to the target GPU's preferred format (ASTC, BC7, PVRTC, etc.)
  • Drastically reduces transmission size over networks thanks to Basis Universal and Zstandard supercompression
  • Seamless integration with the glTF ecosystem for optimized 3D asset delivery
Limitations
  • Requires WebAssembly (Wasm) decoders and JavaScript loaders for web viewing, increasing initial application payload slightly
  • Encoding textures into high-quality Basis Universal UASTC can be computationally intensive and slow
  • Zero support in traditional 2D image viewers or native OS previews

When to choose which format

FITS
Use FITS when…
  • Astronomy & Astrophysics
  • Space Telescope Data (Hubble, JWST)
  • Scientific Data Archiving
  • Spectroscopy
KTX2
Use KTX2 when…
  • glTF 3D Models (KHR_texture_basisu)
  • WebGPU and WebGL Applications
  • Game Engines (Unity, Unreal, Godot)
  • Augmented and Virtual Reality (AR/VR)
Share this comparison