Free webp to jpg
Image MIME Reference
HSJ2

JPEG 2000 Image Sequence (Obsolete)

image/hsj2
VS

GIMP Image Format

image/x-xcf
XCF

A complete technical comparison of JPEG 2000 Image Sequence (Obsolete) and GIMP Image Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature HSJ2 XCF
Transparency (Alpha) Yes Yes
Animation Support Yes Yes
Progressive Loading Yes ✕ No
HDR Support Yes Yes
EXIF Metadata Yes Yes
ICC Color Profile Yes Yes
JPEG 2000 Image Sequence (Obsolete)
image/hsj2
Extension
.hsj2
Container HEIF / ISOBMFF (ISO/IEC 15444-16 Obsolete)
Compression Lossy / Lossless
Algorithm
Motion JPEG 2000 (ISO/IEC 15444-3)
Color Depth 8-bit, 10-bit, 12-bit, 16-bit
Developed by ISO/IEC JTC 1 / ITU-T
Released 2019
Magic Bytes
XX XX XX XX 66 74 79 70 68 73 6A 32
Full HSJ2 reference →
GIMP Image Format
image/x-xcf
Extension
.xcf
Container GIMP Hierarchical Chunk Container
Compression None / RLE (Run-Length Encoding) / Zlib / Deflate (In newer GIMP versions)
Algorithm
NoneRLEZlib
Color Depth 8-bit per channel, 16-bit per channel, 32-bit floating point
Developed by Spencer Kimball, Peter Mattis, and the GIMP Development Team
Released 1995
Magic Bytes
67 69 6D 70 20 78 63 66
Full XCF reference →

Browser Support Comparison

Browser HSJ2 XCF
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
HSJ2

HSJ2 Strengths

  • Historically attempted to combine Motion JPEG 2000 sequences with the flexible metadata capabilities of the HEIF container
  • Supported mathematically lossless compression and scalable wavelet decoding
Limitations
  • Officially deprecated by the standardization body (ISO/IEC JTC 1)
  • Completely superseded by image/hej2k, rendering hsj2 files obsolete for any new development or archiving
  • Zero web browser compatibility and negligible modern software support
XCF

XCF Strengths

  • Preserves all non-destructive editing elements, layer hierarchies, masks, and alpha channels across GIMP sessions
  • Open and thoroughly documented specification within the open-source community, allowing third-party tools like Krita and ImageMagick to read project files
  • Reliable magic byte header prevents misidentification
Limitations
  • Massive file sizes because raw, unflattened layer bitmaps and masks are stored directly within the project archive
  • Completely proprietary to the GIMP ecosystem for deep editing; cannot be natively rendered or parsed by web browsers
  • Third-party software supporting XCF may occasionally struggle to render complex text layer adjustments or advanced layer blend modes identically to GIMP

When to choose which format

HSJ2
Use HSJ2 when…
  • Legacy Archival
  • Deprecated Workflows
XCF
Use XCF when…
  • GIMP Native Project Archival
  • Layered Photo Editing and Graphic Design
  • Intermediary Asset Preparation for Export
Share this comparison