HDF 4.4.0

Release Information

| Version | HDF 4.4.0 | | Release Date | 9/1/2026 |

  | Additional Release Information | [Release Notes](https://github.com/HDFGroup/hdf4/blob/hdf4.4.0/release_docs/RELEASE.txt) | | Compatibility Reports for 4.4.0 vs 4.3.1 | [C library](https://support.hdfgroup.org/releases/hdf4/v4_4/v4_4_0/downloads/hdf4.4.0-vs-hdf4.3.1-interface_compatibility_report.html) | | [Java library](https://support.hdfgroup.org/releases/hdf4/v4_4/v4_4_0/downloads/hdf4.4.0-vs-hdf4.3.1-java-interface_compatibility_report.html) ## Downloads #### NOTE: Applications that were created with HDF4 releases 3.x and earlier will need to be modified to use the safe version of Vgetname, Vgetclass, and Vinquire introduced in 4.0 release. Refer to the Breaking changes section in the [RELEASE.txt](https://github.com/HDFGroup/hdf4/blob/hdf4.4.0/release_docs/RELEASE.txt) for details. | File | Type | | ----- | ---- | --------------------- | | [hdf4.4.0.tar.gz](https://github.com/HDFGroup/hdf4/releases/download/hdf4.4.0/hdf4.4.0.tar.gz) | Source release | | [hdf4.4.0.zip](https://github.com/HDFGroup/hdf4/releases/download/hdf4.4.0/hdf4.4.0.zip) | Source release | | [Ready to use Binaries](https://github.com/HDFGroup/hdf4/releases/tag/hdf4.4.0) | Pre-built binary distributions for Unix and Windows | | [sha256](https://github.com/HDFGroup/hdf4/releases/download/hdf4.4.0/hdf4.4.0.sha256sums.txt) | Checksum file | Please refer to [Build Instructions](https://github.com/HDFGroup/hdf4/blob/hdf4.4.0/release_docs/INSTALL) for building with either CMake or Autotools. #### Known Problems: o Users should also be aware that, as in previous releases, Fortran on 64-bit platforms is generally not expected to work and should be considered unsupported in most configurations. While some compiler and platform combinations may work, these cases should be viewed as exceptions rather than the norm. o Valgrind may report "Conditional jump or move depends on uninitialised value(s)" in JPEG-related test comparisons when the library is built against SIMD-enabled libjpeg-turbo. This is a documented false positive caused by Valgrind mis-tracking libjpeg-turbo's SSE2 color-space conversion code, not an actual bug in HDF4. It does not occur when built/run with SIMD disabled (JSIMD_FORCENONE=1). See the libjpeg-turbo README, "SIMD Extensions" section at: https://github.com/libjpeg-turbo/libjpeg-turbo/blob/main/README.md#memory-debugger-pitfalls for details.