Minimum unique abbreviation of option is acceptable. You may use double hyphens instead of single hyphen to denote options. You may use white space in place of the equals sign to separate an option name from its value.
This program is part of Netpbm.
jpegtopnm converts JFIF images to PPM or PGM images.
By default, jpegtopnm expects the input stream to contain one JFIF image and produces one PGM or PPM image as output. It fails if the input stream is empty.
But with the -multiple option, jpegtopnm reads JFIF images sequentially from the input stream and writes one PPM or PGM image to the output stream for each JFIF input. If the input stream is empty, so is the output.
The input stream is the filename you specify or, if you don't specify filename, Standard Input. The output stream is Standard Output.
If a JFIF input image is of the grayscale variety, jpegtopnm generates a PGM image. Otherwise, it generates a PPM image.
Before Netpbm 10.11 (October 2002), jpegtopnm did not have the multiple image stream capability. From 10.11 through 10.22, Netpbm always behaved as if you specified -multiple. Starting with Netpbm 10.23 (July 2004), Netpbm's default behavior went back to the pre-10.11 behavior and the new -multiple option selected the 10.12 behavior. The reason for the reversion was that there were discovered in the world files that contain JFIF images followed by something other than another JFIF image. The producers of these files expect them to work with any JFIF interpreter because most JFIF interpreters just stop reading the file after the first JFIF image.
jpegtopnm uses the Independent JPEG Group's JPEG library to interpret the input file. See http://www.ijg.org for information on the library.
"JFIF" is the correct name for the image format commonly known as "JPEG." Strictly speaking, JPEG is a method of compression. The image format using JPEG compression that is by far the most common is JFIF. There is also a subformat of TIFF that uses JPEG compression.
EXIF is an image format that is a subformat of JFIF (to wit, a JFIF file that contains an EXIF header as an APP1 marker). jpegtopnm handles EXIF.
JFIF files can have either 8 bits per sample or 12 bits per sample. The 8 bit variety is by far the most common. There are two versions of the IJG JPEG library. One reads only 8 bit files and the other reads only 12 bit files. You must link the appropriate one of these libraries with jpegtopnm. Ordinarily, this means the library is in your shared library search path when you run jpegtopnm.
jpegtopnm generates output with either one byte or two bytes per sample depending on whether the JFIF input has either 8 bits or 12 bits per sample. You can use pamdepth to reduce a two-byte-per-sample file to a one-byte-per-sample file if you need to.
If the JFIF file uses the CMYK or YCCK color space, the input does not actually contain enough information to know what color each pixel is. To know what color a pixel is, one would have to know the properties of the inks to which the color space refers. jpegtopnm interprets the colors using the common transformation which assumes all the inks are simply subtractive and linear.
See the jpegtopnm manual for information on how images lose quality when you convert to and from JFIF.
These options tell jpegtopnm which version of the CMYK or YCCK color space the image uses. If you specify neither, jpegtopnm tries to figure it out on its own. In the present version, it doesn't try very hard at all: It just assumes the Photoshop version, since Photoshop and its emulators seem to be the main source of CMYK and YCCK images. But with experience of use, future versions might be more sophisticated.
If the JFIF image does not indicate that it is CMYK or YCCK, these options have no effect.
If you don't use the right one of these options, the symptom is output that looks like a negative.
This option was added in Netpbm 9.19 (September 2001).
jpegtopnm writes the contents of the EXIF header byte-for-byte, starting with the two byte length field (which length includes those two bytes).
You can use this file as input to pnmtojpeg to insert an identical EXIF header into a new JFIF image.
If there is no EXIF header, jpegtopnm writes two bytes of binary zero and nothing else.
An EXIF header takes the form of a JFIF APP1 marker. Only the first such marker within the JFIF header counts.
This option was added in Netpbm 9.19 (September 2001).
This option was new in Netpbm 10.23 (July 2004).
Without this option, some invalid input causes jpegtopnm to fail, and what output it produces is undefined. With -repair such invalid input causes jpegtopnm to succeed instead.
But note that there are some forms of invalid input that always cause jpegtopnm to fail and others that always cause it to salvage image information and succeed.
One particular case where -repair makes a difference is the common case that the file is truncated somewhere after the JFIF header. Without -repair, that always causes a failure; with -repair it always causes success. Because the image information is laid out generally top to bottom in the JFIF stream, the image jpegtopnm produces in this case has the proper image contents at the top, but the bottom is padded with gray.
This option was new in Netpbm 10.38.0 (March 2007). Before that, jpegtopnm always fails in the cases in question.
This example converts the color JFIF file foo.jpg to a PPM file named foo.ppm:
jpegtopnm foo.jpg >foo.ppm
Use pamscale to change the dimensions of the resulting image.
Use ppmtopgm to convert a color JFIF file to a grayscale PGM file.
You can easily use these converters together. E.g.:
jpegtopnm foo.jpg | ppmtopgm | pamscale .25 >foo.pgm
-dct fast and/or -nosmooth gain speed at a small sacrifice in quality.
If you are fortunate enough to have very fast floating point hardware, -dct float may be even faster than -dct fast. But on most machines -dct float is slower than -dct int; in this case it is not worth using, because its theoretical accuracy advantage is too small to be significant in practice.
Another program, djpeg, is similar. djpeg is maintained by the Independent JPEG Group and packaged with the JPEG library which jpegtopnm uses for all its JPEG work. Because of that, you may expect it to exploit more current JPEG features. Also, since you have to have the library to run jpegtopnm, but not vice versa, cjpeg may be more commonly available.
On the other hand, djpeg does not use the NetPBM libraries to generate its output, as all the NetPBM tools such as jpegtopnm do. This means it is less likely to be consistent with all the other programs that deal with the NetPBM formats. Also, the command syntax of jpegtopnm is consistent with that of the other Netpbm tools, unlike djpeg.
ppm, pgm, pnmtojpeg, pnmquant, pamscale, ppmtopgm, ppmdither, pamdepth,
djpeg man page, cjpeg man page, jpegtran man page, rdjpgcom man page, wrjpgcom man page, jhead man page
Wallace, Gregory K. "The JPEG Still Picture Compression Standard", Communications of the ACM, April 1991 (vol. 34, no. 4), pp. 30-44.
jpegtopnm and this manual were derived in large part from djpeg, by the Independent JPEG Group. The program is otherwise by Bryan Henderson on March 19, 2000.