NIfTI neuroimaging recovery

A NIfTI file can fail because its header, gzip stream, image offset, dimensions, or voxel payload is damaged.

NIfTI data can be stored in one NII file, a compressed NII.GZ, or a paired HDR and IMG set. A damaged header or truncated compressed stream can block normal loading even when some voxel data remains present.

Understand the symptom

The header defines dimensions, datatype, voxel offset, scaling, orientation, and coordinate transforms.

WHY

What is happening

NIfTI supports a single header-plus-data file or a dual HDR/IMG representation. If dimensions, datatype, endianness, voxel offset, qform, sform, or gzip boundaries are wrong, readers can reject the file or misinterpret an otherwise present payload.

What you may see

Symptoms that change the recovery path.

01

File is not a valid NIfTI image

The signature, header length, datatype, or stream may be unreadable.

02

Unexpected dimensions

Header values may not match the acquired volume.

03

Orientation is incorrect

qform, sform, affine, or sidecar context may be damaged.

04

Gunzip ends unexpectedly

The compressed stream may be truncated before all voxel bytes.

Protect the source

Actions that can make the situation worse.

01

Guessing dimensions can create false data

Use acquisition evidence and matching series.

02

Recompression changes evidence

Keep the original byte stream and checksum.

03

Partial volumes can look plausible

Validate slices, voxel count, datatype, and transforms.

Do this now

Safe steps before evaluation.

01

Copy every representation

Keep NII, compressed sources, HDR/IMG pairs, sidecars, and derived outputs.

02

Record expected geometry

Note matrix, voxel sizes, datatype, volume count, orientation, and scanner series.

03

Preserve acquisition context

Retain DICOM source, BIDS metadata, transforms, scripts, and pipeline logs.

04

Image unstable media

Protect the source before repeated decompression or conversion.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Container and header review

NEPFOSYS identifies format, compression, byte order, header fields, and available payload.

02

Copy-based extraction

Readable voxels and metadata are recovered without overwriting the source.

03

Scientific validation

Dimensions, datatype, slice order, transforms, checksums, and priority volumes are compared with acquisition evidence.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Is NII.GZ a different image format?

It is a gzip-compressed NIfTI file; both compression and NIfTI structure must be valid.

Can a damaged header be reconstructed?

Sometimes, when expected geometry and matching acquisition evidence are available, but reconstructed values must be documented and validated.

Should I convert it to another format first?

No. Preserve the source before any conversion because a failed reader may omit or reinterpret data.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case