OpenEXR image recovery

An OpenEXR can contain readable scanline or tile chunks even when one offset, part, level, or data block is damaged.

OpenEXR stores headers, channels, data windows, offset tables, scanline or tile chunks, and optional multipart or deep data. Corruption may affect one frame, chunk, channel group, part, or mip level rather than an entire sequence.

Understand the symptom

Each part has a header, offset table, and pixel chunks.

WHY

What is happening

OpenEXR documentation distinguishes scanline, tiled, multipart, multiresolution, and deep-data chunks. Recovery must use the declared windows, channels, compression, part type, and chunk coordinates rather than assuming one flat RGB image.

What you may see

Symptoms that change the recovery path.

01

Cannot read chunk

A referenced scanline, tile, or compressed data block is damaged.

02

Missing channel or layer

Header definitions and stored chunk content may disagree.

03

One frame fails in a sequence

Damage may be limited to a single file or storage region.

04

Wrong crop or image dimensions

Display window, data window, or tile-level metadata may be corrupt.

Protect the source

Actions that can make the situation worse.

01

Flattening discards channels

RGBA export can lose depth, masks, IDs, and deep data.

02

Sequence renumbering hides missing frames

Preserve original frame IDs and gaps.

03

Replacing a header can misinterpret pixels

Windows, sampling, compression, and channel types must match.

Do this now

Safe steps before evaluation.

01

Freeze the complete sequence

Keep every frame, checksum, name, timestamp, and directory relationship.

02

Record expected structure

List parts, channels, windows, compression, tiles, levels, and frame range.

03

Collect render context

Preserve scene version, renderer, color pipeline, logs, and farm manifests.

04

Image failing storage

Protect media before reading every large frame repeatedly.

NEPFOSYS process

How a data-first evaluation proceeds.

01

EXR structure review

NEPFOSYS maps headers, parts, channels, offset tables, chunks, windows, and readable ranges.

02

Selective chunk extraction

Recoverable channels and chunks are written to new files without modifying originals.

03

Sequence validation

Frame range, dimensions, channels, sample pixels, metadata, and production expectations are checked.

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.

Can one damaged EXR chunk leave other pixels readable?

Yes. OpenEXR is chunk-oriented, but the exact effect depends on file type and metadata integrity.

Should I convert EXR to PNG?

Not before preservation; PNG cannot retain many EXR channels, data types, or deep samples.

Can a neighboring frame replace the header?

It can provide evidence, but headers may vary by window, channels, parts, and render settings.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case