The JPEG File Interchange Format (JFIF) is an image file format standard published as ITU-T Recommendation T.871 and ISO/IEC 10918-5. It defines supplementary specifications for the container format that contains the image data encoded with the JPEG algorithm. The base specifications for a JPEG container format are defined in Annex B of the JPEG standard, known as JPEG Interchange Format (JIF). JFIF builds over JIF to solve some of JIF's limitations, including unnecessary complexity, component sample registration, resolution, aspect ratio, and color space. Because JFIF is not the original JPG standard, one might expect another MIME type. However, it is still registered as "image/jpeg" (indicating its primary data format rather than the amended information).
JFIF is mutually incompatible with the newer Exchangeable image file format (Exif).
JFIF defines a number of details that are left unspecified by the JPEG Part 1 standard (ISO/IEC 10918-1, ITU-T Recommendation T.81.)[1]
JPEG allows multiple components (such as Y, Cb, and Cr) to have different resolutions, but it does not define how those differing sample arrays (which render bitmaps) should be aligned. This pixel-producing information is rendered with the expectation of indicating rectangles by their centroid, rather than being pixel data directly, or being 'first corner and flood', etc. which is uncommon.
The JPEG standard does not include any method of coding the resolution or aspect ratio of an image. JFIF provides resolution or aspect ratio information using an application segment extension to JPEG. It uses Application Segment #0, with a segment header consisting of the null-terminated string spelling "JFIF" in ASCII followed by a byte equal to 0, and specifies that this must be the first segment in the file, hence making it simple to recognize a JFIF file. Exif images recorded by digital cameras generally do not include this segment, but typically comply in all other respects with the JFIF standard.
The JPEG standard used for the compression coding in JFIF files does not define which color encoding is to be used for images. JFIF defines the color model to be used: either Y for greyscale, or YCbCr derived from RGB color primaries as defined in CCIR 601 (now known as Rec. ITU-R BT.601), except with a different "full range" scaling of the Y, Cb and Cr components. Unlike the "studio range" defined in CCIR 601, in which black is represented by Y=16 and white by Y=235 and values outside of this range are available for signal processing "headroom" and "footroom", JFIF uses all 256 levels of the 8-bit representation, so that Y=0 for black and Y=255 for peak white. The RGB color primaries defined in JFIF via CCIR 601 also differ somewhat from what has become common practice in newer applications (e.g., they differ slightly from the color primaries defined in sRGB). Moreover, CCIR 601 (before 2007) did not provide a precise definition of the RGB color primaries; it relied instead on the underlying practices of the television industry.
Color interpretation of a JFIF image may be improved by embedding an ICC profile, colorspace metadata, or an sRGB tag, and using an application that interprets this information.
A JFIF file consists of a sequence of markers or marker segments (for details refer to JPEG, Syntax and structure). The markers are defined in part 1 of the JPEG Standard. Each marker consists of two bytes: an FF byte followed by a byte which is not equal to 00 or FF and specifies the type of the marker. Some markers stand alone, but most indicate the start of a marker segment that contains data bytes according to the following pattern:
FF ''xx'' ''s1'' ''s2'' ''[data bytes]''
The bytes s1 and s2 are taken together to represent a big-endian 16-bit integer specifying the length of the following "data bytes" plus the 2 bytes used to represent the length. In other words, s1 and s2 specify the number of the following data bytes as
256 ⋅ s1+s2-2
According to part 1 of the JPEG standard, applications can use APP marker segments and define an application specific meaning of the data. In the JFIF standard, the following APP marker segments are defined:
They are described below.
The JFIF standard requires that the JFIF APP0 marker segment immediately follows the SOI marker. If a JFIF extension APP0 marker segment is used, it must immediately follow the JFIF APP0 marker segment. So a JFIF file will have the following structure:
| JFIF file structure | |||
|---|---|---|---|
| Segment | Code | Description | |
| SOI | FF D8 | Start of Image | |
| JFIF-APP0 | FF E0 ''s1'' ''s2'' 4A 46 49 46 00 ... | see below | |
| JFXX-APP0 | FF E0 ''s1'' ''s2'' 4A 46 58 58 00 ... | optional, see below | |
| … additional marker segments (for example SOF, DHT, COM) | |||
| SOS | FF DA | Start of Scan | |
| compressed image data | |||
| EOI | FF D9 | End of Image | |
In the mandatory JFIF APP0 marker segment the parameters of the image are specified. Optionally an uncompressed thumbnail can be embedded.
| JFIF APP0 marker segment | |||
|---|---|---|---|
| Field | Size (bytes) | Description | |
| APP0 marker | 2 | FF E0 | |
| Length | 2 | Length of segment excluding APP0 marker | |
| Identifier | 5 | 4A 46 49 46 00 = "JFIF" in ASCII, terminated by a null byte | |
| JFIF version | 2 | First byte for major version, second byte for minor version (01 02 for 1.02) | |
| Density units | 1 | Units for the following pixel density fields
| |
| Xdensity | 2 | Horizontal pixel density. Must not be zero | |
| Ydensity | 2 | Vertical pixel density. Must not be zero | |
| Xthumbnail | 1 | Horizontal pixel count of the following embedded RGB thumbnail. May be zero | |
| Ythumbnail | 1 | Vertical pixel count of the following embedded RGB thumbnail. May be zero | |
| Thumbnail data | 3 × n | Uncompressed 24 bit RGB (8 bits per color channel) raster thumbnail data in the order R0, G0, B0, ... Rn-1, Gn-1, Bn-1; with n = Xthumbnail × Ythumbnail | |
Immediately following the JFIF APP0 marker segment may be a JFIF extension APP0 marker segment. This segment may only be present for JFIF versions 1.02 and above. It allows to embed a thumbnail image in 3 different formats.
| JFIF extension APP0 marker segment | |||
|---|---|---|---|
| Field | Size (bytes) | Description | |
| APP0 marker | 2 | FF E0 | |
| Length | 2 | Length of segment excluding APP0 marker | |
| Identifier | 5 | 4A 46 58 58 00 = "JFXX" in ASCII, terminated by a null byte | |
| Thumbnail format | 1 | Specifies what data format is used for the following embedded thumbnail:
| |
| Thumbnail data | variable | Depends on the thumbnail format, see below | |
The thumbnail data depends on the thumbnail format as follows:
| Thumbnail stored using JPEG encoding | |||
|---|---|---|---|
| Field | Size (bytes) | Description | |
| SOI | 2 | FF D8 | |
| variable | Must be JIF format using YCbCr or just Y, and must not contain JFIF or JFXX segments | ||
| EOI | 2 | FF D9 | |
| Thumbnail stored using one byte per pixel | |||
|---|---|---|---|
| Field | Size (bytes) | Description | |
| Xthumbnail | 1 | Horizontal pixel count of the following embedded thumbnail. Must not be zero | |
| Ythumbnail | 1 | Vertical pixel count of the following embedded thumbnail. Must not be zero | |
| Thumbnail palette | 768 | 256 palette entries, each containing a 24 bit RGB color value | |
| Thumbnail data | n | One byte per pixel containing the index of the color within the palette,with n = Xthumbnail × Ythumbnail | |
| Thumbnail stored using three byte per pixel | |||
|---|---|---|---|
| Field | Size (bytes) | Description | |
| Xthumbnail | 1 | Horizontal pixel count of the following embedded thumbnail. Must not be zero | |
| Ythumbnail | 1 | Vertical pixel count of the following embedded thumbnail. Must not be zero | |
| Thumbnail data | 3 × n | Uncompressed 24 bit RGB (8 bits per color channel) raster thumbnail data in the order R0, G0, B0, ... Rn-1, Gn-1, Bn-1; with n = Xthumbnail × Ythumbnail | |
The newer Exchangeable image file format (Exif) is comparable to JFIF, but the two standards are mutually incompatible. This is because both standards specify that their particular application segment (APP0 for JFIF, APP1 for Exif) must immediately follow the SOI marker. In practice, many programs and digital cameras produce files with both application segments included. This will not affect the image decoding for most decoders, but poorly designed JFIF or Exif parsers may not recognise the file properly.
JFIF is compatible with Adobe Photoshop's JPEG "Information Resource Block" extensions, and IPTC Information Interchange Model metadata, since JFIF does not preclude other application segments, and the Photoshop extensions are not required to be the first in the file. However, Photoshop generally saves CMYK buffers as four-component "Adobe JPEGs" that are not conformant with JFIF. Since these files are not in a YCbCr color space, they are typically not decodable by Web browsers and other Internet software.
Development of the JFIF document was led by Eric Hamilton of C-Cube Microsystems, and agreement on the first version was established in late 1991 at a meeting held at C-Cube involving about 40 representatives of various computer, telecommunications, and imaging companies. Shortly afterwards, a minor revision was published — JFIF 1.01. For nearly 20 years, the latest version available was v1.02, published September 1, 1992.[2]
In 1996, RFC 2046 specified that the image format used for transmitting JPEG images across the Internet should be JFIF. The MIME type of "image/jpeg" must be encoded as JFIF. In practice, however, virtually all Internet software can decode any baseline JIF image that uses Y or YCbCr components, whether it is JFIF compliant or not.
As time went by, C-Cube was restructured (and eventually devolved into Harmonic, LSI Logic, Magnum Semiconductor, Avago Technologies, Broadcom, and GigOptix, GigPeak, etc), and lost interest in the document, and the specification had no official publisher until it was picked up by Ecma International and the ITU-T/ISO/IEC Joint Photographic Experts Group around 2009 to avoid it being lost to history and provide a way to formally cite it in standard publications and improve its editorial quality. It was published by ECMA in 2009 as Technical Report number 98 to avoid loss of the historical record,[3] and it was formally standardized by ITU-T in 2011 as its Recommendation T.871[4] and by ISO/IEC in 2013 as ISO/IEC 10918-5,[5] The newer publications included editorial improvements but no substantial technical changes.