“JPEG”的意思、由来-开放百科全书

JPEG compression is used in a number of image file formats. JPEG/Exif is the most common image format used by digital cameras and other photographic image capture devices; along with JPEG/JFIF, it is the most common format for storing and transmitting photographic images on the World Wide Web.^[3] These format variations are often not distinguished, and are simply called JPEG.

The term "JPEG" is an initialism/acronym for the Joint Photographic Experts Group, which created the standard. The MIME media type for JPEG is image/jpeg, except in older Internet Explorer versions, which provides a MIME type of image/pjpeg when uploading JPEG images.^[4] JPEG files usually have a filename extension of .jpg or .jpeg.

JPEG/JFIF supports a maximum image size of 65,535×65,535 pixels,^[5] hence up to 4 gigapixels for an aspect ratio of 1:1.

JPEG standard

"JPEG" stands for Joint Photographic Experts Group, the name of the committee that created the JPEG standard and also other still picture coding standards. The "Joint" stood for ISO TC97 WG8 and CCITT SGVIII. In 1987, ISO TC 97 became ISO/IEC JTC1 and, in 1992, CCITT became ITU-T. Currently on the JTC1 side, JPEG is one of two sub-groups of ISO/IEC Joint Technical Committee 1, Subcommittee 29, Working Group 1 (ISO/IEC JTC 1/SC 29/WG 1) – titled as Coding of still pictures.^[6]^[7]^[8] On the ITU-T side, ITU-T SG16 is the respective body. The original JPEG Group was organized in 1986,^[9] issuing the first JPEG standard in 1992, which was approved in September 1992 as ITU-T Recommendation T.81^[10] and, in 1994, as ISO/IEC 10918-1.

The JPEG standard specifies the codec, which defines how an image is compressed into a stream of bytes and decompressed back into an image, but not the file format used to contain that stream.^[11]

The Exif and JFIF standards define the commonly used file formats for interchange of JPEG-compressed images.

JPEG standards are formally named as Information technology – Digital compression and coding of continuous-tone still images. ISO/IEC 10918 consists of the following parts:

Typical usage

The JPEG compression algorithm operates at its best on photographs and paintings of realistic scenes with smooth variations of tone and color. For web usage, where reducing the amount of data used for an image is important for responsive presentation, JPEG's compression benefits make JPEG popular. JPEG/Exif is also the most common format saved by digital cameras.

However, JPEG is not well suited for line drawings and other textual or iconic graphics, where the sharp contrasts between adjacent pixels can cause noticeable artifacts. Such images are better saved in a lossless graphics format such as TIFF, GIF, PNG, or a raw image format. The JPEG standard includes a lossless coding mode, but that mode is not supported in most products.

As the typical use of JPEG is a lossy compression method, which reduces the image fidelity, it is inappropriate for exact reproduction of imaging data (such as some scientific and medical imaging applications and certain technical image processing work).

JPEG is also not well suited to files that will undergo multiple edits, as some image quality is lost each time the image is recompressed, particularly if the image is cropped or shifted, or if encoding parameters are changed – see digital generation loss for details. To prevent image information loss during sequential and repetitive editing, the first edit can be saved in a lossless format, subsequently edited in that format, then finally published as JPEG for distribution.

JPEG compression

JPEG uses a lossy form of compression based on the discrete cosine transform (DCT). This mathematical operation converts each frame/field of the video source from the spatial (2D) domain into the frequency domain (a.k.a. transform domain). A perceptual model based loosely on the human psychovisual system discards high-frequency information, i.e. sharp transitions in intensity, and color hue. In the transform domain, the process of reducing information is called quantization. In simpler terms, quantization is a method for optimally reducing a large number scale (with different occurrences of each number) into a smaller one, and the transform-domain is a convenient representation of the image because the high-frequency coefficients, which contribute less to the overall picture than other coefficients, are characteristically small-values with high compressibility. The quantized coefficients are then sequenced and losslessly packed into the output bitstream. Nearly all software implementations of JPEG permit user control over the compression ratio (as well as other optional parameters), allowing the user to trade off picture-quality for smaller file size. In embedded applications (such as miniDV, which uses a similar DCT-compression scheme), the parameters are pre-selected and fixed for the application.

The compression method is usually lossy, meaning that some original image information is lost and cannot be restored, possibly affecting image quality. There is an optional lossless mode defined in the JPEG standard. However, this mode is not widely supported in products.

There is also an interlaced progressive JPEG format, in which data is compressed in multiple passes of progressively higher detail. This is ideal for large images that will be displayed while downloading over a slow connection, allowing a reasonable preview after receiving only a portion of the data. However, support for progressive JPEGs is not universal. When progressive JPEGs are received by programs that do not support them (such as versions of Internet Explorer before Windows 7)^[16] the software displays the image only after it has been completely downloaded.

There are also many medical imaging, traffic and camera applications that create and process 12-bit JPEG images both grayscale and color. 12-bit JPEG format is included in an Extended part of the JPEG specification. The libjpeg codec supports 12-bit JPEG and there even exists a high-performance version.^[17]

Lossless editing

A number of alterations to a JPEG image can be performed losslessly (that is, without recompression and the associated quality loss) as long as the image size is a multiple of 1 MCU block (Minimum Coded Unit) (usually 16 pixels in both directions, for 4:2:0 chroma subsampling). Utilities that implement this include:

Blocks can be rotated in 90-degree increments, flipped in the horizontal, vertical and diagonal axes and moved about in the image. Not all blocks from the original image need to be used in the modified one.

The top and left edge of a JPEG image must lie on an 8 × 8 pixel block boundary, but the bottom and right edge need not do so. This limits the possible lossless crop operations, and also prevents flips and rotations of an image whose bottom or right edge does not lie on a block boundary for all channels (because the edge would end up on top or left, where – as aforementioned – a block boundary is obligatory).

Rotations where the image is not a multiple of 8 or 16, which value depends upon the chroma subsampling, are not lossless. Rotating such an image causes the blocks to be recomputed which results in loss of quality.^[18]

When using lossless cropping, if the bottom or right side of the crop region is not on a block boundary, then the rest of the data from the partially used blocks will still be present in the cropped file and can be recovered. It is also possible to transform between baseline and progressive formats without any loss of quality, since the only difference is the order in which the coefficients are placed in the file.

Furthermore, several JPEG images can be losslessly joined together, as long as they were saved with the same quality and the edges coincide with block boundaries.

JPEG files

The file format known as "JPEG Interchange Format" (JIF) is specified in Annex B of the standard. However, this "pure" file format is rarely used, primarily because of the difficulty of programming encoders and decoders that fully implement all aspects of the standard and because of certain shortcomings of the standard:

Several additional standards have evolved to address these issues. The first of these, released in 1992, was the JPEG File Interchange Format (or JFIF), followed in recent years by Exchangeable image file format (Exif) and ICC color profiles. Both of these formats use the actual JIF byte layout, consisting of different markers, but in addition, employ one of the JIF standard's extension points, namely the application markers: JFIF uses APP0, while Exif uses APP1. Within these segments of the file that were left for future use in the JIF standard and are not read by it, these standards add specific metadata.

Thus, in some ways, JFIF is a cut-down version of the JIF standard in that it specifies certain constraints (such as not allowing all the different encoding modes), while in other ways, it is an extension of JIF due to the added metadata. The documentation for the original JFIF standard states:^[19]

Image files that employ JPEG compression are commonly called "JPEG files", and are stored in variants of the JIF image format. Most image capture devices (such as digital cameras) that output JPEG are actually creating files in the Exif format, the format that the camera industry has standardized on for metadata interchange. On the other hand, since the Exif standard does not allow color profiles, most image editing software stores JPEG in JFIF format, and also includes the APP1 segment from the Exif file to include the metadata in an almost-compliant way; the JFIF standard is interpreted somewhat flexibly.^[20]

Strictly speaking, the JFIF and Exif standards are incompatible, because each specifies that its marker segment (APP0 or APP1, respectively) appear first. In practice, most JPEG files contain a JFIF marker segment that precedes the Exif header. This allows older readers to correctly handle the older format JFIF segment, while newer readers also decode the following Exif segment, being less strict about requiring it to appear first.

JPEG filename extensions

The most common filename extensions for files employing JPEG compression are .jpg and .jpeg, though .jpe, .jfif and .jif are also used. It is also possible for JPEG data to be embedded in other file types – TIFF encoded files often embed a JPEG image as a thumbnail of the main image; and MP3 files can contain a JPEG of cover art in the ID3v2 tag.

Color profile

Many JPEG files embed an ICC color profile (color space). Commonly used color profiles include sRGB and Adobe RGB. Because these color spaces use a non-linear transformation, the dynamic range of an 8-bit JPEG file is about 11 stops; see gamma curve.

Syntax and structure

A JPEG image consists of a sequence of segments, each beginning with a marker, each of which begins with a 0xFF byte, followed by a byte indicating what kind of marker it is. Some markers consist of just those two bytes; others are followed by two bytes (high then low), indicating the length of marker-specific payload data that follows. (The length includes the two bytes for the length, but not the two bytes for the marker.) Some markers are followed by entropy-coded data; the length of such a marker does not include the entropy-coded data. Note that consecutive 0xFF bytes are used as fill bytes for padding purposes, although this fill byte padding should only ever take place for markers immediately following entropy-coded scan data (see JPEG specification section B.1.1.2 and E.1.2 for details; specifically "In all cases where markers are appended after the compressed data, optional 0xFF fill bytes may precede the marker").

Within the entropy-coded data, after any 0xFF byte, a 0x00 byte is inserted by the encoder before the next byte, so that there does not appear to be a marker where none is intended, preventing framing errors. Decoders must skip this 0x00 byte. This technique, called byte stuffing (see JPEG specification section F.1.2.3), is only applied to the entropy-coded data, not to marker payload data. Note however that entropy-coded data has a few markers of its own; specifically the Reset markers (0xD0 through 0xD7), which are used to isolate independent chunks of entropy-coded data to allow parallel decoding, and encoders are free to insert these Reset markers at regular intervals (although not all encoders do this).

There are other Start Of Frame markers that introduce other kinds of JPEG encodings.

Since several vendors might use the same APPn marker type, application-specific markers often begin with a standard or vendor name (e.g., "Exif" or "Adobe") or some other identifying string.

At a restart marker, block-to-block predictor variables are reset, and the bitstream is synchronized to a byte boundary. Restart markers provide means for recovery after bitstream error, such as transmission over an unreliable network or file corruption. Since the runs of macroblocks between restart markers may be independently decoded, these runs may be decoded in parallel.

JPEG codec example

Although a JPEG file can be encoded in various ways, most commonly it is done with JFIF encoding. The encoding process consists of several steps:

The decoding process reverses these steps, except the quantization because it is irreversible. In the remainder of this section, the encoding and decoding processes are described in more detail.

Encoding

Many of the options in the JPEG standard are not commonly used, and as mentioned above, most image software uses the simpler JFIF format when creating a JPEG file, which among other things specifies the encoding method. Here is a brief description of one of the more common methods of encoding when applied to an input that has 24 bits per pixel (eight each of red, green, and blue). This particular option is a lossy data compression method.

Color space transformation

First, the image should be converted from RGB into a different color space called {{YCbCr}} (or, informally, YCbCr). It has three components Y', C_B and C_R: the Y' component represents the brightness of a pixel, and the C_B and C_R components represent the chrominance (split into blue and red components). This is basically the same color space as used by digital color television as well as digital video including video DVDs, and is similar to the way color is represented in analog PAL video and MAC (but not by analog NTSC, which uses the YIQ color space). The {{YCbCr}} color space conversion allows greater compression without a significant effect on perceptual image quality (or greater perceptual image quality for the same compression). The compression is more efficient because the brightness information, which is more important to the eventual perceptual quality of the image, is confined to a single channel. This more closely corresponds to the perception of color in the human visual system. The color transformation also improves compression by statistical decorrelation.

A particular conversion to {{YCbCr}} is specified in the JFIF standard, and should be performed for the resulting JPEG file to have maximum compatibility. However, some JPEG implementations in "highest quality" mode do not apply this step and instead keep the color information in the RGB color model,^[23] where the image is stored in separate channels for red, green and blue brightness components. This results in less efficient compression, and would not likely be used when file size is especially important.

Downsampling

Due to the densities of color- and brightness-sensitive receptors in the human eye, humans can see considerably more fine detail in the brightness of an image (the Y' component) than in the hue and color saturation of an image (the Cb and Cr components). Using this knowledge, encoders can be designed to compress images more efficiently.

The transformation into the {{YCbCr}} color model enables the next usual step, which is to reduce the spatial resolution of the Cb and Cr components (called "downsampling" or "chroma subsampling"). The ratios at which the downsampling is ordinarily done for JPEG images are 4:4:4 (no downsampling), 4:2:2 (reduction by a factor of 2 in the horizontal direction), or (most commonly) 4:2:0 (reduction by a factor of 2 in both the horizontal and vertical directions). For the rest of the compression process, Y', Cb and Cr are processed separately and in a very similar manner.

Block splitting

After subsampling, each channel must be split into 8×8 blocks. Depending on chroma subsampling, this yields Minimum Coded Unit (MCU) blocks of size 8×8 (4:4:4 – no subsampling), 16×8 (4:2:2), or most commonly 16×16 (4:2:0). In video compression MCUs are called macroblocks.

If the data for a channel does not represent an integer number of blocks then the encoder must fill the remaining area of the incomplete blocks with some form of dummy data. Filling the edges with a fixed color (for example, black) can create ringing artifacts along the visible part of the border;

repeating the edge pixels is a common technique that reduces (but does not necessarily completely eliminate) such artifacts, and more sophisticated border filling techniques can also be applied.

Discrete cosine transform

Next, each 8×8 block of each component (Y, Cb, Cr) is converted to a frequency-domain representation, using a normalized, two-dimensional type-II discrete cosine transform (DCT), see Citation 1 in discrete cosine transform. The DCT is sometimes referred to as "type-II DCT" in the context of a family of transforms as in discrete cosine transform, and the corresponding inverse (IDCT) is denoted as "type-III DCT".

Before computing the DCT of the 8×8 block, its values are shifted from a positive range to one centered on zero. For an 8-bit image, each entry in the original block falls in the range

. The midpoint of the range (in this case, the value 128) is subtracted from each entry to produce a data range that is centered on zero, so that the modified range is

. This step reduces the dynamic range requirements in the DCT processing stage that follows.

If we perform this transformation on our matrix above, we get the following (rounded to the nearest two digits beyond the decimal point):

Note the top-left corner entry with the rather large magnitude. This is the DC coefficient (also called the constant component), which defines the basic hue for the entire block. The remaining 63 coefficients are the AC coefficients (also called the alternating components).^[24] The advantage of the DCT is its tendency to aggregate most of the signal in one corner of the result, as may be seen above. The quantization step to follow accentuates this effect while simultaneously reducing the overall size of the DCT coefficients, resulting in a signal that is easy to compress efficiently in the entropy stage.

The DCT temporarily increases the bit-depth of the data, since the DCT coefficients of an 8-bit/component image take up to 11 or more bits (depending on fidelity of the DCT calculation) to store. This may force the codec to temporarily use 16-bit numbers to hold these coefficients, doubling the size of the image representation at this point; these values are typically reduced back to 8-bit values by the quantization step. The temporary increase in size at this stage is not a performance concern for most JPEG implementations, since typically only a very small part of the image is stored in full DCT form at any given time during the image encoding or decoding process.

Quantization

The human eye is good at seeing small differences in brightness over a relatively large area, but not so good at distinguishing the exact strength of a high frequency brightness variation. This allows one to greatly reduce the amount of information in the high frequency components. This is done by simply dividing each component in the frequency domain by a constant for that component, and then rounding to the nearest integer. This rounding operation is the only lossy operation in the whole process (other than chroma subsampling) if the DCT computation is performed with sufficiently high precision. As a result of this, it is typically the case that many of the higher frequency components are rounded to zero, and many of the rest become small positive or negative numbers, which take many fewer bits to represent.

The elements in the quantization matrix control the compression ratio, with larger values producing greater compression. A typical quantization matrix (for a quality of 50% as specified in the original JPEG Standard), is as follows:

where

is the unquantized DCT coefficients;

is the quantization matrix above; and

is the quantized DCT coefficients.

Using this quantization matrix with the DCT coefficient matrix from above results in:

For example, using −415 (the DC coefficient) and rounding to the nearest integer

Notice that most of the higher-frequency elements of the sub-block (i.e., those with an x or y spatial frequency greater than 4) are compressed into zero values.

Entropy coding

Entropy coding is a special form of lossless data compression. It involves arranging the image components in a "zigzag" order employing run-length encoding (RLE) algorithm that groups similar frequencies together, inserting length coding zeros, and then using Huffman coding on what is left.

The JPEG standard also allows, but does not require, decoders to support the use of arithmetic coding, which is mathematically superior to Huffman coding. However, this feature has rarely been used, as it was historically covered by patents requiring royalty-bearing licenses, and because it is slower to encode and decode compared to Huffman coding. Arithmetic coding typically makes files about 5–7% smaller.

The previous quantized DC coefficient is used to predict the current quantized DC coefficient. The difference between the two is encoded rather than the actual value. The encoding of the 63 quantized AC coefficients does not use such prediction differencing.

The zigzag sequence for the above quantized coefficients are shown below. (The format shown is just for ease of understanding/viewing.)

If the i-th block is represented by

and positions within each block are represented by

where

and

, then any coefficient in the DCT image can be represented as

. Thus, in the above scheme, the order of encoding pixels (for the {{mvar|i}}-th block) is

and so on.

This encoding mode is called baseline sequential encoding. Baseline JPEG also supports progressive encoding. While sequential encoding encodes coefficients of a single block at a time (in a zigzag manner), progressive encoding encodes similar-positioned batch of coefficients of all blocks in one go (called a scan), followed by the next batch of coefficients of all blocks, and so on. For example, if the image is divided into N 8×8 blocks

, then a 3-scan progressive encoding encodes DC component,

for all blocks, i.e., for all

, in first scan. This is followed by the second scan which encoding a few more components (assuming four more components, they are

, still in a zigzag manner) coefficients of all blocks (so the sequence is:

), followed by all the remained coefficients of all blocks in the last scan.

Once all similar-positioned coefficients have been encoded, the next position to be encoded is the one occurring next in the zigzag traversal as indicated in the figure above. It has been found that baseline progressive JPEG encoding usually gives better compression as compared to baseline sequential JPEG due to the ability to use different Huffman tables (see below) tailored for different frequencies on each "scan" or "pass" (which includes similar-positioned coefficients), though the difference is not too large.

In the rest of the article, it is assumed that the coefficient pattern generated is due to sequential mode.

In order to encode the above generated coefficient pattern, JPEG uses Huffman encoding. The JPEG standard provides general-purpose Huffman tables; encoders may also choose to generate Huffman tables optimized for the actual frequency distributions in images being encoded.

The process of encoding the zig-zag quantized data begins with a run-length encoding explained below, where:

The run-length encoding works by examining each non-zero AC coefficient {{mvar|x}} and determining how many zeroes came before the previous AC coefficient. With this information, two symbols are created:

Both RUNLENGTH and SIZE rest on the same byte, meaning that each only contains four bits of information. The higher bits deal with the number of zeroes, while the lower bits denote the number of bits necessary to encode the value of {{mvar|x}}.

This has the immediate implication of Symbol 1 being only able store information regarding the first 15 zeroes preceding the non-zero AC coefficient. However, JPEG defines two special Huffman code words. One is for ending the sequence prematurely when the remaining coefficients are zero (called "End-of-Block" or "EOB"), and another when the run of zeroes goes beyond 15 before reaching a non-zero AC coefficient. In such a case where 16 zeroes are encountered before a given non-zero AC coefficient, Symbol 1 is encoded "specially" as: (15, 0)(0).

The overall process continues until "EOB"{{snd}} denoted by (0, 0){{snd}} is reached.

(The first value in the matrix, −26, is the DC coefficient; it is not encoded the same way. See above.)

From here, frequency calculations are made based on occurrences of the coefficients. In our example block, most of the quantized coefficients are small numbers that are not preceded immediately by a zero coefficient. These more-frequent cases will be represented by shorter code words.

Compression ratio and artifacts

The resulting compression ratio can be varied according to need by being more or less aggressive in the divisors used in the quantization phase. Ten to one compression usually results in an image that cannot be distinguished by eye from the original. A compression ratio of 100:1 is usually possible, but will look distinctly artifacted compared to the original. The appropriate level of compression depends on the use to which the image will be put.

Those who use the World Wide Web may be familiar with the irregularities known as compression artifacts that appear in JPEG images, which may take the form of noise around contrasting edges (especially curves and corners), or "blocky" images. These are due to the quantization step of the JPEG algorithm. They are especially noticeable around sharp corners between contrasting colors (text is a good example, as it contains many such corners). The analogous artifacts in MPEG video are referred to as mosquito noise, as the resulting "edge busyness" and spurious dots, which change over time, resemble mosquitoes swarming around the object.^[25]^[26]

These artifacts can be reduced by choosing a lower level of compression; they may be completely avoided by saving an image using a lossless file format, though this will result in a larger file size. The images created with ray-tracing programs have noticeable blocky shapes on the terrain. Certain low-intensity compression artifacts might be acceptable when simply viewing the images, but can be emphasized if the image is subsequently processed, usually resulting in unacceptable quality. Consider the example below, demonstrating the effect of lossy compression on an edge detection processing step.

Some programs allow the user to vary the amount by which individual blocks are compressed. Stronger compression is applied to areas of the image that show fewer artifacts. This way it is possible to manually reduce JPEG file size with less loss of quality.

Since the quantization stage always results in a loss of information, JPEG standard is always a lossy compression codec. (Information is lost both in quantizing and rounding of the floating-point numbers.) Even if the quantization matrix is a matrix of ones, information will still be lost in the rounding step.

Decoding

Taking the DCT coefficient matrix (after adding the difference of the DC coefficient back in)

and taking the entry-for-entry product with the quantization matrix from above results in

which closely resembles the original DCT coefficient matrix for the top-left portion.

The next step is to take the two-dimensional inverse DCT (a 2D type-III DCT), which is given by:

Rounding the output to integer values (since the original had integer values) results in an image with values (still shifted down by 128)

This is the decompressed subimage. In general, the decompression process may produce values outside the original input range of

. If this occurs, the decoder needs to clip the output values so as to keep them within that range to prevent overflow when storing the decompressed image with the original bit depth.

The decompressed subimage can be compared to the original subimage (also see images to the right) by taking the difference (original − uncompressed) results in the following error values:

The error is most noticeable in the bottom-left corner where the bottom-left pixel becomes darker than the pixel to its immediate right.

Required precision

The encoding description in the JPEG standard does not fix the precision needed for the output compressed image. However, the JPEG standard (and the similar MPEG standards) includes some precision requirements for the decoding, including all parts of the decoding process (variable length decoding, inverse DCT, dequantization, renormalization of outputs); the output from the reference algorithm must not exceed:

These assertions are tested on a large set of randomized input images, to handle the worst cases. The former IEEE 1180–1990 standard contained some similar precision requirements. The precision has a consequence on the implementation of decoders, and it is critical because some encoding processes (notably used for encoding sequences of images like MPEG) need to be able to construct, on the encoder side, a reference decoded image. In order to support 8-bit precision per pixel component output, dequantization and inverse DCT transforms are typically implemented with at least 14-bit precision in optimized decoders.

Effects of JPEG compression

JPEG compression artifacts blend well into photographs with detailed non-uniform textures, allowing higher compression ratios. Notice how a higher compression ratio first affects the high-frequency textures in the upper-left corner of the image, and how the contrasting lines become more fuzzy. The very high compression ratio severely affects the quality of the image, although the overall colors and image form are still recognizable. However, the precision of colors suffer less (for a human eye) than the precision of contours (based on luminance). This justifies the fact that images should be first transformed in a color model separating the luminance from the chromatic information, before subsampling the chromatic planes (which may also use lower quality quantization) in order to preserve the precision of the luminance plane with more information bits.

Sample photographs

For information, the uncompressed 24-bit RGB bitmap image below (73,242 pixels) would require 219,726 bytes (excluding all other information headers). The filesizes indicated below include the internal JPEG information headers and some metadata. For highest quality images (Q=100), about 8.25 bits per color pixel is required. On grayscale images, a minimum of 6.5 bits per pixel is enough (a comparable Q=100 quality color information requires about 25% more encoded bits). The highest quality image below (Q=100) is encoded at nine bits per color pixel, the medium quality image (Q=25) uses one bit per color pixel. For most applications, the quality factor should not go below 0.75 bit per pixel (Q=12.5), as demonstrated by the low quality image. The image at lowest quality uses only 0.13 bit per pixel, and displays very poor color. This is useful when the image will be displayed in a significantly scaled-down size. A method for creating better quantization matrices for a given image quality using PSNR instead of the Q factor is described in Minguillón & Pujol (2001).^[27]

The medium quality photo uses only 4.3% of the storage space required for the uncompressed image, but has little noticeable loss of detail or visible artifacts. However, once a certain threshold of compression is passed, compressed images show increasingly visible defects. See the article on rate–distortion theory for a mathematical explanation of this threshold effect. A particular limitation of JPEG in this regard is its non-overlapped 8×8 block transform structure. More modern designs such as JPEG 2000 and JPEG XR exhibit a more graceful degradation of quality as the bit usage decreases – by using transforms with a larger spatial extent for the lower frequency coefficients and by using overlapping transform basis functions.

Lossless further compression

From 2004 to 2008, new research emerged on ways to further compress the data contained in JPEG images without modifying the represented image.^[28]^[29]^[30]^[31] This has applications in scenarios where the original image is only available in JPEG format, and its size needs to be reduced for archiving or transmission. Standard general-purpose compression tools cannot significantly compress JPEG files.

Typically, such schemes take advantage of improvements to the naive scheme for coding DCT coefficients, which fails to take into account:

Some standard but rarely used options already exist in JPEG to improve the efficiency of coding DCT coefficients: the arithmetic coding option, and the progressive coding option (which produces lower bitrates because values for each coefficient are coded independently, and each coefficient has a significantly different distribution). Modern methods have improved on these techniques by reordering coefficients to group coefficients of larger magnitude together;^[28] using adjacent coefficients and blocks to predict new coefficient values;^[30] dividing blocks or coefficients up among a small number of independently coded models based on their statistics and adjacent values;^[29]^[30] and most recently, by decoding blocks, predicting subsequent blocks in the spatial domain, and then encoding these to generate predictions for DCT coefficients.^[31]

Typically, such methods can compress existing JPEG files between 15 and 25 percent, and for JPEGs compressed at low-quality settings, can produce improvements of up to 65%.^[30]^[31]

A freely available tool called packJPG^[32] is based on the 2007 paper "Improved Redundancy Reduction for JPEG Files."

Derived formats for stereoscopic 3D

JPEG Stereoscopic

JPS is a stereoscopic JPEG image used for creating 3D effects from 2D images. It contains two static images, one for the left eye and one for the right eye; encoded as two side-by-side images in a single JPG file.

JPEG Stereoscopic (JPS, extension .jps) is a JPEG-based format for stereoscopic images.^[33]^[34] It has a range of configurations stored in the JPEG APP3 marker field, but usually contains one image of double width, representing two images of identical size in cross-eyed (i.e. left frame on the right half of the image and vice versa) side-by-side arrangement. This file format can be viewed as a JPEG without any special software, or can be processed for rendering in other modes.

JPEG Multi-Picture Format

JPEG Multi-Picture Format (MPO, extension .mpo) is a JPEG-based format for storing multiple images in a single file. It contains two or more JPEG files concatenated together.^[35]^[36] It also defines a JPEG APP2 marker segment for image description. Various devices use it to store 3D images, such as Fujifilm FinePix Real 3D W1, HTC Evo 3D, JVC GY-HMZ1U AVCHD/MVC extension camcorder, Nintendo 3DS, Panasonic Lumix DMC-TZ20, DMC-TZ30, DMC-TZ60, DMC-TS4 (FT4), and Sony DSC-HX7V. Other devices use it to store "preview images" that can be displayed on a TV.

In the last few years, due to the growing use of stereoscopic images, much effort has been spent by the scientific community to develop algorithms for stereoscopic image compression.^[37]^[38]

Patent issues

In 2002, Forgent Networks asserted that it owned and would enforce patent rights on the JPEG technology, arising from a patent that had been filed on October 27, 1986, and granted on October 6, 1987 ({{US patent|4698672}}). The announcement created a furor reminiscent of Unisys' attempts to assert its rights over the GIF image compression standard.

The JPEG committee investigated the patent claims in 2002 and were of the opinion that they were invalidated by prior art.^[39] Others also concluded that Forgent did not have a patent that covered JPEG.^[40] Nevertheless, between 2002 and 2004 Forgent was able to obtain about US$105 million by licensing their patent to some 30 companies. In April 2004, Forgent sued 31 other companies to enforce further license payments. In July of the same year, a consortium of 21 large computer companies filed a countersuit, with the goal of invalidating the patent. In addition, Microsoft launched a separate lawsuit against Forgent in April 2005.^[41] In February 2006, the United States Patent and Trademark Office agreed to re-examine Forgent's JPEG patent at the request of the Public Patent Foundation.^[42] On May 26, 2006 the USPTO found the patent invalid based on prior art. The USPTO also found that Forgent knew about the prior art, yet it intentionally avoided telling the Patent Office. This makes any appeal to reinstate the patent highly unlikely to succeed.^[43]

Forgent also possesses a similar patent granted by the European Patent Office in 1994, though it is unclear how enforceable it is.^[44]

As of October 27, 2006, the U.S. patent's 20-year term appears to have expired, and in November 2006, Forgent agreed to abandon enforcement of patent claims against use of the JPEG standard.^[45]

The JPEG committee has as one of its explicit goals that their standards (in particular their baseline methods) be implementable without payment of license fees, and they have secured appropriate license rights for their JPEG 2000 standard from over 20 large organizations.

Beginning in August 2007, another company, Global Patent Holdings, LLC claimed that its patent ({{US patent|5,253,341}}) issued in 1993, is infringed by the downloading of JPEG images on either a website or through e-mail. If not invalidated, this patent could apply to any website that displays JPEG images. The patent was under reexamination by the U.S. Patent and Trademark Office from 2000-2007; in July 2007, the Patent Office revoked all of the original claims of the patent but found that an additional claim proposed by Global Patent Holdings (claim 17) was valid.^[46] Global Patent Holdings then filed a number of lawsuits based on claim 17 of its patent.

In its first two lawsuits following the reexamination, both filed in Chicago, Illinois, Global Patent Holdings sued the Green Bay Packers, CDW, Motorola, Apple, Orbitz, Officemax, Caterpillar, Kraft and Peapod as defendants. A third lawsuit was filed on December 5, 2007 in South Florida against ADT Security Services, AutoNation, Florida Crystals Corp., HearUSA, MovieTickets.com, Ocwen Financial Corp. and Tire Kingdom, and a fourth lawsuit on January 8, 2008 in South Florida against the Boca Raton Resort & Club. A fifth lawsuit was filed against Global Patent Holdings in Nevada. That lawsuit was filed by Zappos.com, Inc., which was allegedly threatened by Global Patent Holdings, and sought a judicial declaration that the '341 patent is invalid and not infringed.

Global Patent Holdings had also used the '341 patent to sue or threaten outspoken critics of broad software patents, including Gregory Aharonian^[47] and the anonymous operator of a website blog known as the "Patent Troll Tracker."^[48] On December 21, 2007, patent lawyer Vernon Francissen of Chicago asked the U.S. Patent and Trademark Office to reexamine the sole remaining claim of the '341 patent on the basis of new prior art.^[49]

On March 5, 2008, the U.S. Patent and Trademark Office agreed to reexamine the '341 patent, finding that the new prior art raised substantial new questions regarding the patent's validity.^[50] In light of the reexamination, the accused infringers in four of the five pending lawsuits have filed motions to suspend (stay) their cases until completion of the U.S. Patent and Trademark Office's review of the '341 patent. On April 23, 2008, a judge presiding over the two lawsuits in Chicago, Illinois granted the motions in those cases.^[51] On July 22, 2008, the Patent Office issued the first "Office Action" of the second reexamination, finding the claim invalid based on nineteen separate grounds.^[52] On Nov. 24, 2009, a Reexamination Certificate was issued cancelling all claims.

Beginning in 2011 and continuing as of early 2013, an entity known as Princeton Digital Image Corporation,^[53] based in Eastern Texas, began suing large numbers of companies for alleged infringement of {{US patent|4813056}}. Princeton claims that the JPEG image compression standard infringes the '056 patent and has sued large numbers of websites, retailers, camera and device manufacturers and resellers. The patent was originally owned and assigned to General Electric. The patent expired in December 2007, but Princeton has sued large numbers of companies for "past infringement" of this patent. (Under U.S. patent laws, a patent owner can sue for "past infringement" up to six years before the filing of a lawsuit, so Princeton could theoretically have continued suing companies until December 2013.) As of March 2013, Princeton had suits pending in New York and Delaware against more than 55 companies. General Electric's involvement in the suit is unknown, although court records indicate that it assigned the patent to Princeton in 2009 and retains certain rights in the patent.^[54]

Implementations

A very important implementation of a JPEG codec is the free programming library libjpeg of the Independent JPEG Group. It was first published in 1991 and was key for the success of the standard.^[55] This library or a direct derivative of it is used in countless applications. Recent versions introduce proprietary extension not compatible with ISO/IEC standards.

In March 2017, Google released the open source project Guetzli, which trades off a much longer encoding time for better appearance and smaller file size (similar to what Zopfli does for PNG and other lossless data formats).^[56]

ISO/IEC Joint Photography Experts Group maintains a reference software implementation which can encode both base JPEG (ISO/IEC 10918-1 and 18477-1) and JPEG XT extensions (ISO/IEC 18477 Parts 2 and 6-9), as well as JPEG-LS (ISO/IEC 14495).^[57]

JPEG XT

JPEG XT (ISO/IEC 18477) was published in June 2015; it extends base JPEG format with support for higher integer bit depths (up to 16 bit), high dynamic range imaging and floating-point coding, lossless coding, and alpha channel coding. Extensions are backward compatible with the base JPEG/JFIF file format and 8-bit lossy compressed image. JPEG XT uses an extensible file format based on JFIF. Extension layers are used to modify the JPEG 8-bit base layer and restore the high-resolution image. Existing software is forward compatible and can read the JPEG XT binary stream, though it would only decode the base 8-bit layer.^[58]

JPEG XL

Since August 2017, JTC1/SC29/WG1 issued a series of draft calls for proposals on JPEG XL{{snd}} the next generation image compression standard with substantially better compression efficiency (60% improvement) comparing to JPEG.^[59] The standard is expected to follow still image compression performance shown by HEVC HM, Daala and WebP. The core requirements include support for very high-resolution images (at least 40 MP), 8–10 bits per component, RGB/YCbCr/ICtCp color encoding, animated images, alpha channel coding, Rec.709 color space (sRGB) and gamma function (2.4-power), Rec.2100 wide color gamut color space (Rec.2020) and high dynamic range transfer functions (PQ and HLG), and high-quality compression of synthetic images, such as bitmap fonts and gradients. The standard should also offer higher bit depths (12–16 bit integer and floating point), additional color spaces and transfer functions (such as Log C from Arri), embedded preview images, lossless alpha channel encoding, image region coding, and low-complexity encoding. Any patented technologies would be licensed on a royalty-free basis. The proposals were submitted by September 2018, with current target publication date in October 2019.^[60]

See also

References

1. ^{{cite web|url=http://www.collinsdictionary.com/dictionary/english/jpeg|title=Definition of "JPEG"|work=Collins English Dictionary|accessdate=2013-05-23}}
2. ^{{cite techreport |url=https://ntrs.nasa.gov/search.jsp?R=19920024689 |author1=Haines, Richard F. |author2=Chuang, Sherry L. |title=The effects of video compression on acceptability of images for monitoring life sciences experiments |number=NASA-TP-3239, A-92040, NAS 1.60:3239 |institution=NASA |date=1 July 1992 |access-date=2016-03-13 |quote=The JPEG still-image-compression levels, even with the large range of 5:1 to 120:1 in this study, yielded equally high levels of acceptability}}
3. ^{{cite web|url=http://httparchive.org/interesting.php#imageformats|title=HTTP Archive - Interesting Stats|website=httparchive.org|access-date=2016-04-06}}
4. ^MIME Type Detection in Internet Explorer: Uploaded MIME Types (msdn.microsoft.com)
5. ^{{cite web|url=http://www.jpeg.org/public/jfif.pdf|title=Wayback Machine|date=3 September 2014|website=Web.archive.org|accessdate=16 October 2017|deadurl=bot: unknown|archiveurl=https://web.archive.org/web/20140903080533/http://www.jpeg.org/public/jfif.pdf|archivedate=3 September 2014|df=}}
6. ^{{cite web |url=http://kikaku.itscj.ipsj.or.jp/sc29/29w12901.htm |title=ISO/IEC JTC 1/SC 29/WG 1 – Coding of Still Pictures (SC 29/WG 1 Structure) |author=ISO/IEC JTC 1/SC 29 |date=2009-05-07 |accessdate=2009-11-11 |deadurl=yes |archiveurl=https://web.archive.org/web/20131231055215/http://kikaku.itscj.ipsj.or.jp/sc29/29w12901.htm |archivedate=2013-12-31 |df= }}
7. ^¹{{cite web |url=http://kikaku.itscj.ipsj.or.jp/sc29/29w42901.htm |title=Programme of Work, (Allocated to SC 29/WG 1) |author=ISO/IEC JTC 1/SC 29 |accessdate=2009-11-07 |deadurl=yes |archiveurl=https://web.archive.org/web/20131231012300/http://kikaku.itscj.ipsj.or.jp/sc29/29w42901.htm |archivedate=2013-12-31 |df= }}
8. ^{{cite web |url=http://www.iso.org/iso/standards_development/technical_committees/list_of_iso_technical_committees/iso_technical_committee.htm?commid=45316 |title=JTC 1/SC 29 – Coding of audio, picture, multimedia and hypermedia information |author=ISO |accessdate=2009-11-11}}
9. ^¹{{cite web | url=http://www.jpeg.org/jpeg/index.html | title=Joint Photographic Experts Group, JPEG Homepage | author=JPEG | accessdate=2009-11-08}}
10. ^{{cite web |url=http://www.itu.int/rec/T-REC-T.81 |title=T.81 : Information technology – Digital compression and coding of continuous-tone still images – Requirements and guidelines| website=Itu.int|accessdate=2009-11-07}}
11. ^{{cite book | title = JPEG still image data compression standard | edition = 3rd |author1=William B. Pennebaker |author2=Joan L. Mitchell|author2-link=Joan L. Mitchell | publisher = Springer | year = 1993 | isbn = 978-0-442-01272-4 | page = 291 | url = https://books.google.com/books?id=AepB_PZ_WMkC&pg=PA291&dq=JPEG+%22did+not+specify+a+file+format%22&lr=&num=20&as_brr=0&ei=VHXySui8JYqukASSssWzAw#v=onepage&q=JPEG%20%22did%20not%20specify%20a%20file%20format%22&f=false }}
12. ^{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_tc_browse.htm?commid=45316 |title=JTC 1/SC 29 – Coding of audio, picture, multimedia and hypermedia information |author=ISO | accessdate=2009-11-07}}
13. ^{{cite web|url=https://www.loc.gov/preservation/digital/formats/fdd/fdd000019.shtml|title=SPIFF, Still Picture Interchange File Format |publisher= Library of Congress |access-date=2018-07-31 |archive-url=https://web.archive.org/web/20180731093543/https://www.loc.gov/preservation/digital/formats/fdd/fdd000019.shtml |archive-date=2018-07-31 |dead-url=no}}
14. ^{{cite press|url=http://www.jpeg.org/newsrel25.html |title=JPEG XR enters FDIS status: JPEG File Interchange Format (JFIF) to be standardized as JPEG Part 5 |author=JPEG |date=2009-04-24 |accessdate=2009-11-09 |deadurl=yes |archiveurl=https://web.archive.org/web/20091008041637/http://www.jpeg.org/newsrel25.html |archivedate=2009-10-08 |df= }}
15. ^{{cite web|url=http://www.ecma-international.org/publications/techreports/E-TR-098.htm|year=2009|title=JPEG File Interchange Format (JFIF)|accessdate=2011-08-01|work=ECMA TR/98 1st ed.|publisher=Ecma International}}
16. ^{{cite web | url = http://msdn.microsoft.com/en-us/library/ee720036(v=vs.85).aspx | title = Progressive Decoding Overview | accessdate = 2012-03-23 | work = Microsoft Developer Network | publisher = Microsoft}}
17. ^{{Cite web | last = Fastvideo | title = 12-bit JPEG encoder on GPU |date = January 2018| url = http://www.fastcompression.com/products/jpeg/12-bit-jpeg-codec.htm | accessdate = 2018-01-16}}
18. ^{{cite web|url=http://petapixel.com/2012/08/14/why-you-should-always-rotate-original-jpeg-photos-losslessly/|title=Why You Should Always Rotate Original JPEG Photos Losslessly|date=|website=Petapixel.com|access-date=16 October 2017}}
19. ^{{cite web| url = http://www.w3.org/Graphics/JPEG/jfif3.pdf| title = JFIF File Format as PDF| format = PDF}}
20. ^{{cite web|url=http://www.faqs.org/faqs/jpeg-faq/part1/|title=JPEG image compression FAQ|author=Tom Lane|date=1999-03-29|accessdate=2007-09-11}} (q. 14: "Why all the argument about file formats?")
21. ^{{cite web | url = http://www.digicamsoft.com/itu/itu-t81-36.html | title = ISO/IEC 10918-1 : 1993(E) p.36 }}
22. ^{{cite web | url = http://apodeline.free.fr/DOC/libjpeg/libjpeg-3.html | title = Advanced Features: Compression parameter selection | work = Using the IJG JPEG Library | author = Thomas G. Lane. }}
23. ^{{Cite book|url=https://books.google.com/books?id=bYxMVVzdV80C&lpg=PA53&ots=jINS_TrM1X&dq=A%20particular%20conversion%20to%20Y%E2%80%B2CBCR%20is%20specified%20in%20the%20JFIF%20standard,%20and%20should%20be%20performed%20for%20the%20resulting%20JPEG%20file%20to%20have%20maximum%20compatibility.&pg=PA53#v=onepage&q=A%20particular%20conversion%20to%20Y%E2%80%B2CBCR%20is%20specified%20in%20the%20JFIF%20standard,%20and%20should%20be%20performed%20for%20the%20resulting%20JPEG%20file%20to%20have%20maximum%20compatibility.%20A%20particular%20conversion%20to%20Y%E2%80%B2CBCR%20is%20specified%20in%20the%20JFIF%20standard,%20and%20should%20be%20performed%20for%20the%20resulting%20JPEG%20file%20to%20have%20maximum%20compatibility.%20%20A%20particular%20conversion%20to%20Y%E2%80%B2CBCR%20is%20specified%20in%20the%20JFIF%20standard,%20and%20should%20be%20performed%20for%20the%20resulting%20JPEG%20file%20to%20have%20maximum%20compatibility.%20&f=false|title=E - Learning Modules: Dlr Associates Series|last=Ryan|first=Dan|date=2012-06-20|publisher=AuthorHouse|isbn=9781468575200|language=en}}
24. ^{{cite web|url=http://forum.doom9.org/showthread.php?p=184647#post184647|title=DC / AC Frequency Questions - Doom9's Forum|website=forum.doom9.org|accessdate=16 October 2017}}
25. ^¹Phuc-Tue Le Dinh and Jacques Patry. Video compression artifacts and MPEG noise reduction. Video Imaging DesignLine. February 24, 2006. Retrieved May 28, 2009.
26. ^"3.9 mosquito noise: Form of edge busyness distortion sometimes associated with movement, characterized by moving artifacts and/or blotchy noise patterns superimposed over the objects (resembling a mosquito flying around a person's head and shoulders)."ITU-T Rec. P.930 (08/96) Principles of a reference impairment system for video {{webarchive|url=https://web.archive.org/web/20100216033245/http://eu.sabotage.org/www/ITU/P/P0930e.pdf |date=2010-02-16 }}
27. ^{{cite journal|author=Julià Minguillón, Jaume Pujol|title=JPEG standard uniform quantization error modeling with applications to sequential and progressive operation modes|journal=Electronic Imaging|date=April 2001|volume=10|number=2|pages=475–485|url=http://hdl.handle.net/10609/6263|accessdate=2016-06-10}}
28. ^¹I. Bauermann and E. Steinbacj. Further Lossless Compression of JPEG Images. Proc. of Picture Coding Symposium (PCS 2004), San Francisco, US, December 15–17, 2004.
29. ^¹N. Ponomarenko, K. Egiazarian, V. Lukin and J. Astola. Additional Lossless Compression of JPEG Images, Proc. of the 4th Intl. Symposium on Image and Signal Processing and Analysis (ISPA 2005), Zagreb, Croatia, pp. 117–120, September 15–17, 2005.
30. ^¹²³M. Stirner and G. Seelmann. Improved Redundancy Reduction for JPEG Files. Proc. of Picture Coding Symposium (PCS 2007), Lisbon, Portugal, November 7–9, 2007
31. ^¹²Ichiro Matsuda, Yukio Nomoto, Kei Wakabayashi and Susumu Itoh. Lossless Re-encoding of JPEG images using block-adaptive intra prediction. Proceedings of the 16th European Signal Processing Conference (EUSIPCO 2008).
32. ^{{cite web|url=http://www.elektronik.htw-aalen.de/packjpg/ |title=Latest Binary Releases of packJPG: V2.3a |date=January 3, 2008 |deadurl=yes |archiveurl=https://web.archive.org/web/20090123232605/http://www.elektronik.htw-aalen.de/packjpg/ |archivedate=January 23, 2009 |df= }}
33. ^{{cite web |authors=J. Siragusa, D. C. Swift |url=http://vrex.com/developer/sterdesc.pdf |title=General Purpose Stereoscopic Data Descriptor |work=VRex, Inc., Elmsford, New York, US |date=1997 |archiveurl=https://web.archive.org/web/20111030182549/http://vrex.com/developer/sterdesc.pdf |archivedate=2011-10-30}}
34. ^Tim Kemp, JPS files
35. ^{{cite web|url=http://www.cipa.jp/std/documents/e/DC-007_E.pdf |title=Multi-Picture Format |format=PDF |date=2009 |accessdate=2015-12-30}}
36. ^{{citation |url=http://www.mtbs3d.com/phpbb/viewtopic.php?f=3&t=4124&start=15 |title=MPO2Stereo: Convert Fujifilm MPO files to JPEG stereo pairs|website=Mtbs3d.com|accessdate=12 January 2010}}
37. ^{{citation |url=http://iplab.dmi.unict.it/publication/503 |title=A new fast matching method for adaptive compression of stereoscopic images|author1=Alessandro Ortis |author2=Sebastiano Battiato |publisher=SPIE - Three-Dimensional Image Processing, Measurement (3DIPM), and Applications 2015|accessdate=30 April 2015}}
38. ^{{citation |url=http://iplab.dmi.unict.it/publication/49 |title=Adaptive Compression of Stereoscopic Images|author1=Alessandro Ortis |author2=Francesco Rundo |author3=Giuseppe Di Giore |author4=Sebastiano Battiato |publisher=International Conference on Image Analysis and Processing (ICIAP) 2013|accessdate=30 April 2015}}
39. ^{{cite web |url=http://www.jpeg.org/newsrel1.html |title=Concerning recent patent claims |website=Jpeg.org |date=2002-07-19 |accessdate=2011-05-29 |deadurl=yes |archiveurl=https://web.archive.org/web/20070714232941/http://www.jpeg.org/newsrel1.html |archivedate=2007-07-14 |df= }}
40. ^{{cite web|url=http://www.algovision-luratech.com/company/news/patentquarrel.jsp?OnlineShopId=164241031081525276 |title=JPEG and JPEG2000 – Between Patent Quarrel and Change of Technology |accessdate=2017-04-16 |deadurl=bot: unknown |archiveurl=https://web.archive.org/web/20040817154508/http://www.algovision-luratech.com/company/news/patentquarrel.jsp?OnlineShopId=164241031081525276 |archivedate=August 17, 2004 |df= }}
41. ^{{cite web|title=Graphics patent suit fires back at Microsoft|publisher=CNET News|first=Dawn|last=Kawamoto|date=April 22, 2005|url=http://news.cnet.com/2100-1025_3-5681112.html|accessdate=2009-01-28}}
42. ^{{cite web |title=Trademark Office Re-examines Forgent JPEG Patent |website=Publish.com |date=February 3, 2006 |url=http://www.publish.com/c/a/Graphics-Tools/Trademark-Office-Reexamines-Forgent-JPEG-Patent/ |accessdate=2009-01-28 }}
43. ^{{cite web |title=USPTO: Broadest Claims Forgent Asserts Against JPEG Standard Invalid |website=Groklaw.net |date=May 26, 2006 |url=http://www.groklaw.net/article.php?story=20060526105754880 |accessdate=2007-07-21 }}
44. ^{{cite web|url=http://gauss.ffii.org/PatentView/EP266049 |title=Coding System for Reducing Redundancy |website=Gauss.ffii.org |date= |accessdate=2011-05-29}}
45. ^{{cite web |title=JPEG Patent Claim Surrendered |publisher=Public Patent Foundation |date=November 2, 2006 |url=http://www.pubpat.org/jpegsurrendered.htm |accessdate=2006-11-03 }}
46. ^Ex Parte Reexamination Certificate for U.S. Patent No. 5,253,341 {{webarchive |url=https://web.archive.org/web/20080602141045/http://www.uspto.gov/web/patents/patog/week30/OG/html/1320-4/US05253341-20070724.html |date=June 2, 2008 }}
47. ^{{cite web|author=Workgroup |url=http://eupat.ffii.org/pikta/xrani/rozmanith/index.en.html |title=Rozmanith: Using Software Patents to Silence Critics |website=Eupat.ffii.org |date= |accessdate=2011-05-29 |deadurl=yes |archiveurl=https://web.archive.org/web/20110716123228/http://eupat.ffii.org/pikta/xrani/rozmanith/index.en.html |archivedate=2011-07-16 |df= }}
48. ^{{cite web|url=http://www.law.com/jsp/article.jsp?id=1196762670106 |title=A Bounty of $5,000 to Name Troll Tracker: Ray Niro Wants To Know Who Is saying All Those Nasty Things About Him |website=Law.com |date= |accessdate=2011-05-29}}
49. ^{{cite web|last=Reimer |first=Jeremy |url=https://arstechnica.com/news.ars/post/20080205-hunting-trolls-uspto-asked-to-reexamine-broad-image-patent.html |title=Hunting trolls: USPTO asked to reexamine broad image patent |website=Arstechnica.com |date=2008-02-05 |accessdate=2011-05-29}}
50. ^U.S. Patent Office – Granting Reexamination on 5,253,341 C1
51. ^{{cite web|url=http://www.techdirt.com/articles/20080427/143205960.shtml |title=Judge Puts JPEG Patent On Ice |website=Techdirt.com |date=2008-04-30 |accessdate=2011-05-29}}
52. ^{{cite web|url=http://techdirt.com/articles/20080731/0337491852.shtml |title=JPEG Patent's Single Claim Rejected (And Smacked Down For Good Measure) |website=Techdirt.com |date=2008-08-01 |accessdate=2011-05-29}}
53. ^{{cite web|author=Workgroup |url=http://www.princetondigitalimage.com/ |title=Princeton Digital Image Corporation Home Page |date= |accessdate=2013-05-01}}
54. ^{{cite web|author=Workgroup |url=http://patentlaw.jmbm.com/2013/04/hps-motion-to-dismiss-for-lack.html/ |archive-url=https://web.archive.org/web/20160309142416/http://patentlaw.jmbm.com/2013/04/hps-motion-to-dismiss-for-lack.html |dead-url=yes |archive-date=2016-03-09 |title=Article on Princeton Court Ruling Regarding GE License Agreement |date= |accessdate=2013-05-01 }}
55. ^{{cite web|url=http://jpeg.org/jpeg|title=Overview of JPEG|website=jpeg.org|accessdate=2017-10-16}}
56. ^{{cite web|url=https://research.googleblog.com/2017/03/announcing-guetzli-new-open-source-jpeg.html|title=Announcing Guetzli: A New Open Source JPEG Encoder|website=Research.googleblog.com|accessdate=16 October 2017}}
57. ^{{cite web|url=https://jpeg.org/jpegxt/software.html|title=JPEG - JPEG XT|website=jpeg.org}}
58. ^{{cite web|url=https://jpeg.org/jpegxt/|title=JPEG - JPEG XT|website=jpeg.org}}
59. ^{{cite web|url=https://jpeg.org/items/20180423_cfp_jpeg_xl.html|title=JPEG - Next-Generation Image Compression (JPEG XL) Final Draft Call for Proposals|website=Jpeg.org|accessdate=29 May 2018}}
60. ^{{cite web|url=https://jpeg.org/downloads/jpegxl/jpegxl-cfp.pdf|format=PDF|title=N79010 Final Call for Proposals for a Next-Generation Image Coding Standard (JPEG XL) |work=ISO/IEC JTC 1/SC 29/WG 1 (ITU-T SG16)|accessdate=29 May 2018}}