Image Codec vs Container

A codec defines how image information is encoded and decoded. A container defines how encoded items, metadata, timing, profiles, previews, or multiple images are organized in a file. The terms overlap in everyday speech but answer different questions.

Comparison

Concept	Primary job	Example question
Codec	Compress and reconstruct image data	How are pixels represented?
Container	Package coded items and related information	How are images and metadata arranged?
File format	Define the complete interoperable file	What must a conforming reader understand?

Examples

JPEG commonly refers to a coding family and its familiar still-image file interchange. AVIF stores AV1-coded image items in an ISO Base Media File Format-derived container. HEIC is a HEIF-family container commonly carrying HEVC-coded images. TIFF is a flexible tagged format able to represent different organizations and compressions. ICO packages one or more icon images, which may use PNG-backed frames.

Why the distinction matters

An application may understand the container but lack the codec required for a particular item. Two files with the same broad container family may use different compatible brands or features. A converter must validate both structure and decodability rather than infer complete support from the extension.

Common mistakes

Assuming every HEIF file is the same as every HEIC file.
Calling a container lossless without naming the codec and mode.
Believing a new extension changes the codec.
Assuming container support guarantees animation, metadata, or every profile.

Capability questions to ask

Can the application parse the container?
Can it decode the specific codec and profile?
Does it support every required item, frame, or page?
Will it retain color and metadata needed by the workflow?
Can it encode the requested output, or only decode input?

This vocabulary prevents misleading statements such as “HEIF is supported” when only one still-image codec and no sequences are implemented.