Exchangeable image file format (officially Exif, according to JEIDA/JEITA/CIPA specifications) is a standard that specifies formats for s, sound, and ancillary tags used by digital cameras (including smartphones), scanners and other systems handling image and sound files recorded by digital cameras. The specification uses the following existing encoding formats with the addition of specific metadata tags: JPEG lossy coding for compressed image files, TIFF Rev. 6.0 (RGB or YCbCr) for uncompressed image files, and RIFF WAV for audio files (linear PCM or ITU-T G.711 μ-law PCM for uncompressed audio data, and IMA-ADPCM for compressed audio data). It does not support JPEG 2000 or GIF encoded images. This standard consists of the Exif image file specification and the Exif audio file specification.
Background
Exif is supported by almost all digital camera manufacturers.
The metadata tags defined in the Exif standard cover a broad spectrum: Camera settings: This includes static information such as the camera model and make, and information that varies with each image such as orientation (rotation), aperture, shutter speed, focal length, metering mode, and ISO speed information Image metrics: Pixel dimensions, resolution, colorspace, and filesize Date and time information, digital cameras will record the current (local) date and time set on the device and save this in the metadata Location information A thumbnail for previewing the picture on the camera's LCD screen, in file managers, or in photo manipulation software Descriptions Copyright information
Version history
The Japan Electronic Industries Development Association (JEIDA) produced the initial definition of Exif. Version 2.1 of the specification is dated 12 June 1998. JEITA established Exif version 2.2 (a.k.a. "Exif Print"), dated 20 February 2002 and released in April 2002. Version 2.21 (with Adobe RGB support) is dated 11 July 2003, but was released in September 2003 following the release of DCF 2.0. Version 2.3 was released on 26 April 2010, and revised to 2.31 in July 2013 and revised to 2.32 on 17 May 2019, was jointly formulated by JEITA and CIPA. The latest version, 3.0, was released in May 2023, and brings, among other things, support for UTF-8 to allow text data in non-ASCII encoding.
+VersionsVersionRelease dateChanges1.0October 1995Established basic tag definitions1.1May 1997Added tags and operating specifications2.0November 1997Added sRGB color space, GPS and compressed thumbnails2.1December 1998Added DCF interoperability tags2.2April 2002Applied ExifPrint2.21September 2003Corrections and some additions2.21 (unified version)September 2009More corrections2.3April 2010Added revised ISO tags and lens information2.3 (revised)December 2012Corrections2.31July 2016Added time zone tags and shooting situation tags2.32May 2019Added composite image tags3.0May 2023Added UTF-8 data type3.0December 2024Changed GPSAltitudeRef definition3.1January 2026Added 7 new tags Added new values for new light source into LightSource Tag. Revised some contents in Annex K following MPF specification revision in 2025. Added the explanation of original preservation image and created a new section and consolidated the Tag Description Level and additional provisions in Annex K.2.13.
Technical The Exif tag structure is borrowed from TIFF files. On several image specific properties, there is a large overlap between the tags defined in the TIFF, Exif, TIFF/EP, and DCF standards. For descriptive metadata, there is an overlap between Exif, IPTC Information Interchange Model and XMP info, which also can be embedded in a JPEG file. The Metadata Working Group has guidelines on mapping tags between these standards.
When Exif is employed for JPEG files, the Exif data are stored in one of JPEG's defined utility Application Segments, the APP1 (segment marker 0xFFE1), which in effect holds an entire TIFF file within. When Exif is employed in TIFF files (also when used as "an embedded TIFF file" mentioned earlier), the TIFF Private Tag 0x8769 defines a sub-Image File Directory (IFD) that holds the Exif specified TIFF Tags. In addition, Exif also defines a Global Positioning System sub-IFD using the TIFF Private Tag 0x8825, holding location information, and an "Interoperability IFD" specified within the Exif sub-IFD, using the Exif tag 0xA005.
Formats specified in Exif standard are defined as folder structures that are based on Exif-JPEG and recording formats for memory. When these formats are used as Exif/DCF files together with the DCF specification (for better interoperability among devices of different types), their scope shall cover devices, recording media, and application software that handle them.
Geolocation
The Exif format has standard tags for location information. , many cameras and mobile phones have a built-in GPS receiver that stores the location information in the Exif header when a picture is taken. Some other cameras have a separate GPS receiver that fits into the flash connector or hot shoe. Recorded GPS data can also be added to any digital photograph on a computer, either by correlating the time stamps of the photographs with a GPS record from a hand-held GPS receiver or manually by using a map or mapping software. Some cameras can be paired with cellphones to provide the geolocation. The process of adding geographic information to a photograph is known as geotagging. Photo-sharing communities like Panoramio, locr or Flickr equally allow their users to upload geocoded pictures or to add geolocation information online.
Program support Exif data are embedded within the image file itself. While many recent image manipulation programs recognize and preserve Exif data when writing to a modified image, this is not the case for most older programs. Many image gallery programs also recognise Exif data and optionally display it alongside the images.
Software libraries, such as libexif for C and Adobe XMP Toolkit or Exiv2 for C++, Metadata Extractor for Java, PIL/Pillow for Python, LEADTOOLS or ExifTool for Perl, parse Exif data from files and read/write Exif tag values.
Problems
Technical The Exif format has a number of drawbacks, mostly relating to its use of legacy file structures.
The derivation of Exif from the TIFF file structure using offset pointers in the files means that data can be spread anywhere within a file, which means that software is likely to corrupt any pointers or corresponding data that it does not decode/encode. For this reason most image editors damage or remove the Exif metadata to some extent upon saving. The standard defines a MakerNote tag, which allows camera manufacturers to place any custom format metadata in the file. This is used increasingly by camera manufacturers to store camera settings not listed in the Exif standard, such as shooting modes, post-processing settings, serial number, focusing modes, etc. As the tag contents are proprietary and manufacturer-specific, it can be difficult to retrieve this information from an image or to properly preserve it when rewriting an image. Manufacturers can encrypt portions of the information; for example, some Nikon cameras encrypt the detailed lens data in the MakerNote data. Exif is very often used in images created by scanners, but the standard makes no provisions for any scanner-specific information. Photo manipulation software sometimes fails to update the embedded thumbnail after an editing operation, possibly causing the user to inadvertently publish compromising information. For example, someone might blank out a licence registration plate of a car (for privacy concerns), only to have the thumbnail not be updated, meaning the information is still visible. Exif metadata are restricted in size to 64 kB in JPEG images because according to the specification this information must be contained within a single JPEG APP1 segment. Although the FlashPix extensions allow information to span multiple JPEG APP2 segments, these extensions are not commonly used. This has prompted some camera manufacturers to develop non-standard techniques for storing the large preview images used by some digital cameras for LCD review. These non-standard extensions are commonly lost if a user re-saves the image using image editor software, possibly rendering the image incompatible with the original camera that created it. (In 2009, CIPA released the Multi Picture Object specification which addresses this deficiency and provides a standard way to store large previews in JPEG images.) Prior to version 2.31 (July 2016) there was no way to record time zone information for an image, resulting in ambiguity. For example, a camera might record the "DateTimeOriginal" value using its local time zone, but a program reading the file later could mistakenly interpret that time as UTC. There is no standard field to record readouts of a camera's accelerometers or inertial navigation system. Such data could help to establish the relationship between the image sensor's XYZ coordinate system and the gravity vector (i.e., which way is down in this image). It could also establish relative camera positions or orientations in a sequence of photos. Some software records this information using the GPSImgDirection tag along with custom GPSPitch and GPSRoll tags. The XResolution and YResolution tags provide the number of pixels per length unit for the width and height of the image, respectively. (The length unit itself is specified by the tag ResolutionUnit.) By default, these tags in combination are set to 72 pixels per inch (ppi). These tags were inherited from the TIFF 6.0 standard and are required even though for images produced by digital cameras, image resolution values such as ppi are meaningless.
Privacy and security
Since the Exif tag contains metadata about the photo, it can pose a privacy problem. For example, a photo taken with a GPS-enabled camera can reveal the exact location and time it was taken, and the unique ID number of the device - this is all done by default - often without the user's knowledge. Many users may be unaware that their photos are tagged by default in this manner, or that specialist software may be required to remove the Exif tag before publishing. For example, a whistleblower, journalist or political dissident relying on the protection of anonymity to allow them to report malfeasance by a corporate entity, criminal, or government may therefore find their safety compromised by this default data collection.
While some services will automatically sanitise EXIF data from images, other services do not consider exposing the tags as an issue. For example, Github will preserve all tags including location. When contacted to raise the issue of potential PII being exposed, a user was directed to raise a feature request instead.
In June 2003, the TV host Cat Schwartz shared cropped photographs of herself on her personal blog unadvertedly containing hidden Exif thumbnail images showing the uncropped image, including her bared breasts. At that moment, the program used to crop them, Photoshop, did not remove or replace EXIF thumbnails, creating a privacy risk.
In December 2012, anti-virus businessman John McAfee was arrested in Guatemala while fleeing from alleged persecution in neighboring Belize. Vice magazine had published an exclusive interview on their website with McAfee "on the run" that included a photo of McAfee with a Vice reporter taken with a phone that had geotagged the image. The photo's metadata included GPS coordinates locating McAfee in Guatemala, and he was captured two days later. McAfee later claimed to have edited the Exif data from his phone to provide a false location.
According to documents leaked by Edward Snowden, the NSA is targeting Exif information under the XKeyscore program.