image/jpeg
JPEG remains the default for photos and rich imagery where small file sizes matter more than transparency or perfect edge fidelity.
How teams usually encounter it
This page maps the media type to the file extensions and delivery behaviors developers usually care about: browser parsing, upload validation, cache correctness, and asset handling.
Compression signal
image/jpeg is usually already compressed or stored in a binary-heavy format, so extra transfer compression tends to help less.
Server config snippets
Use these when a server is missing the right extension-to-MIME mapping or you want the expected header to survive a proxy, CDN, or custom asset bucket setup.
types {
image/jpeg jpeg jpg;
}AddType image/jpeg .jpeg .jpgMagic bytes / file signature
When you need to validate uploads or investigate a mislabeled file, the signature often starts with FF D8 FF.
Operational shortcut
If a browser downloads this asset instead of rendering it correctly, check the response header first, then verify the extension mapping on your origin and edge cache. .jpeg is the fastest sanity check for teammates reviewing the file outside the app.
Related image types
image/png
PNG is the go-to raster format for screenshots, UI assets, and graphics that need sharp edges or transparent backgrounds.
.pngimage/gif
GIF is still used for simple animations and low-color graphics where compatibility matters more than compression efficiency.
.gifimage/webp
WebP is a web delivery format tuned for lighter images, often replacing PNG or JPEG when modern browser support is acceptable.
.webpimage/avif
AVIF targets aggressive image compression for the modern web, trading older compatibility for smaller payloads and strong visual quality.
.avifimage/svg+xml
SVG serves vector artwork and interface icons as text-based markup, which keeps graphics crisp and scriptable at any size.
.svgimage/vnd.microsoft.icon
ICO packages one or more favicon sizes in a format browsers and desktop systems still expect for app and site icons.
.ico