← Back to MIME types
MIME Type
image/avif
ImageModern high-efficiency image MIME type based on the AV1 codec.
MIME type reference, HTTP example, browser usage, common mistakes, and related content.
What is the image/avif MIME type?
The MIME type image/avif is used to tell browsers, APIs, and servers how a file or response body should be interpreted.
MIME stands for Multipurpose Internet Mail Extensions, and MIME types are now a standard part of HTTP responses and web content delivery.
When a browser or client receives a response with image/avif, it uses that information to decide how the content should be processed, rendered, downloaded, or executed.
Example
Content-Type: image/avif
HTTP example
HTTP/1.1 200 OK Content-Type: image/avif Content-Length: 1256
Common file extensions
.avif
Common use cases
- High-performance image delivery
- Modern responsive websites
- Image optimization pipelines
Common mistakes
- Using the wrong MIME type for the file being served
- Returning text/plain instead of image/avif
- Forgetting required parameters like charset when relevant
- Using a deprecated MIME type in older server configurations
- Serving assets with a mismatched Content-Type header, causing browser parsing issues
How browsers use it
Browsers use the Content-Type response header to decide how a response should be handled. For example, HTML is rendered as a page, CSS is parsed as styles, JavaScript is executed as script, and images are displayed visually. If the MIME type is incorrect, the browser may refuse to load the file correctly or may treat it as plain text or a download instead.
Browser support
Supported in major modern browsers, but you should still verify support requirements for older enterprise environments.
Developer note
Excellent compression, but browser and toolchain support should still be checked in some workflows.