Reference Guide

Photo Metadata Glossary

Complete definitions for 200+ metadata fields. Every term explained two ways: technical precision for professionals, plain language for everyone else. Search any field instantly.

EXIF Core Fields 24 terms

Fundamental image properties recorded by every digital camera. These fields describe the basic technical characteristics of your photo file—dimensions, format, orientation, and file information.

ImageWidth

Tag 0x0100 EXIF

The number of pixels across your photo horizontally. If your image is 4000 pixels wide, that means there are 4000 tiny dots of color from left to right edge. Combined with height, this tells you the total resolution.

Why you'd care: Bigger numbers mean you can print larger or crop more aggressively without your image looking pixelated. Social media platforms often compress or resize based on these dimensions.

Specifies the horizontal pixel count of the primary image. Stored in the zeroth IFD (Image File Directory) as part of baseline TIFF structure. For JPEG files, this may differ from the actual image dimensions stored in the Start of Frame marker if metadata was modified without re-encoding the pixel data.

Tag ID
0x0100 (256)
Data Type
SHORT (3) or LONG (4)
Count
1
Standard
TIFF 6.0, EXIF 2.32
Some editing tools update pixel data but forget to update this tag, causing mismatches. Always verify against actual decoded dimensions when precision matters.

ImageHeight

Tag 0x0101 EXIF

The number of pixels from top to bottom of your photo. A 3000-pixel height means 3000 rows of colored dots stacked vertically. Together with width, this determines your image's total megapixel count.

Why you'd care: Aspect ratio (width vs height) affects how your photo fits different screens and print sizes. Portrait photos are taller than wide; landscapes are wider than tall.

Specifies the vertical pixel count of the primary image. Like ImageWidth, stored in IFD0 as baseline TIFF metadata. Multiply by ImageWidth to calculate total pixel count (megapixels when divided by one million).

Tag ID
0x0101 (257)
Data Type
SHORT (3) or LONG (4)
Count
1
Standard
TIFF 6.0, EXIF 2.32

Make

Tag 0x010F EXIF

The company that made your camera or phone. Values like "Apple", "Canon", "Sony", or "Samsung" appear here. Every device leaves this brand fingerprint in your photos automatically.

Why you'd care: Useful for organizing photos by device. Also reveals what equipment you use to anyone viewing your photo's metadata—which may or may not be information you want public.

Records the manufacturer of the image capture device as a null-terminated ASCII string. Written by camera firmware at capture time. Format and capitalization vary by manufacturer—Canon uses "Canon", Apple uses "Apple", some use all caps.

Tag ID
0x010F (271)
Data Type
ASCII (2)
Count
Variable (null-terminated)
Standard
TIFF 6.0, EXIF 2.32
Combined with Model and SerialNumber, can uniquely identify a specific camera unit. Forensic investigators use this for device attribution.

Model

Tag 0x0110 EXIF

The specific camera or phone model that took the photo. Examples: "iPhone 15 Pro Max", "Canon EOS R5", "NIKON Z8". More specific than the manufacturer name—tells you exactly which device was used.

Why you'd care: Photographers compare shots from different cameras. Stock photo buyers sometimes filter by equipment. It also reveals your device to anyone examining your photos.

Contains the device model name or number as ASCII text. Format is manufacturer-dependent—Apple includes color variants ("iPhone 15 Pro Max"), Canon uses marketing names ("Canon EOS R5"). May include internal codenames on some devices.

Tag ID
0x0110 (272)
Data Type
ASCII (2)
Count
Variable (null-terminated)
Standard
TIFF 6.0, EXIF 2.32

Orientation

Tag 0x0112 EXIF

Tells software how to rotate your photo for correct display. When you hold your phone sideways, the camera records this so apps know to show the image right-side-up. Without it, your vertical selfies might appear sideways.

Why you'd care: Ever had a photo appear rotated wrong on a website? The site might be ignoring this tag. Understanding orientation helps troubleshoot display issues.

Indicates the viewing orientation relative to pixel data. Uses values 1-8 representing combinations of rotation (0°, 90°, 180°, 270°) and mirroring. The accelerometer in smartphones writes this at capture time. Pixel data stays in sensor orientation; display software applies the transform.

Tag ID
0x0112 (274)
Data Type
SHORT (3)
Count
1
Values
1-8 (1=normal, 3=180°, 6=90° CW, 8=90° CCW)
Standard
TIFF 6.0, EXIF 2.32
Values 2, 4, 5, 7 include horizontal mirroring—rare in photography but possible with front-facing cameras or manual manipulation.

XResolution

Tag 0x011A EXIF

A number (usually 72 or 300) indicating the suggested print density—how many pixels should fit in one inch when printed. Higher numbers mean finer detail. Most cameras default to 72, but this doesn't limit your actual print options.

Why you'd care: This is mainly a hint for printing software. Your actual print quality depends on total pixels divided by print size—this tag alone doesn't determine sharpness.

Horizontal display/print resolution in units specified by ResolutionUnit (typically pixels per inch). Stored as RATIONAL for precision. Most cameras write 72 (legacy screen PPI) or 300 (print standard). Doesn't affect actual pixel count—purely advisory for rendering software.

Tag ID
0x011A (282)
Data Type
RATIONAL (5)
Count
1
Common Values
72/1, 300/1, 96/1
Standard
TIFF 6.0, EXIF 2.32

YResolution

Tag 0x011B EXIF

Same concept as XResolution but for the vertical direction. Almost always matches XResolution (square pixels). Together they suggest how densely your photo should be printed.

Why you'd care: If these don't match (rare), your image might appear stretched when printed. Usually not something to worry about—cameras set both identically.

Vertical display/print resolution, paired with XResolution. Non-square pixel ratios (XResolution ≠ YResolution) are technically possible but extremely rare in photography—more common in video/broadcast legacy formats.

Tag ID
0x011B (283)
Data Type
RATIONAL (5)
Count
1
Standard
TIFF 6.0, EXIF 2.32

ResolutionUnit

Tag 0x0128 EXIF

Specifies whether resolution numbers are measured in inches or centimeters. Almost always set to "inches" (value 2), giving you DPI (dots per inch). This is just the measuring stick—doesn't change your actual image.

Why you'd care: Rarely matters for everyday use. Just know that "72 DPI" means 72 pixels per inch, not per centimeter.

Defines the unit for XResolution and YResolution values. Virtually all digital cameras use value 2 (inches). Value 3 (centimeters) is technically valid but uncommon. Value 1 (no unit) means resolution values have no real-world meaning.

Tag ID
0x0128 (296)
Data Type
SHORT (3)
Count
1
Values
1 = None, 2 = Inch, 3 = Centimeter
Standard
TIFF 6.0, EXIF 2.32

Software

Tag 0x0131 EXIF

Records what software last touched your image. Fresh from camera, this shows firmware version ("Ver.1.2.0"). After editing, it might show "Adobe Photoshop 25.0" or "Lightroom 7.1". Tells you if and how a photo was processed.

Why you'd care: Reveals your editing workflow to others. Forensic analysts check this to determine if an image was manipulated. Some photographers remove it before sharing to keep their process private.

Contains the name and version of software that created or last modified the file. Initially populated with camera firmware identifier; overwritten by editing applications on save. Format is software-dependent—no standard structure.

Tag ID
0x0131 (305)
Data Type
ASCII (2)
Count
Variable (null-terminated)
Standard
TIFF 6.0, EXIF 2.32
This tag alone doesn't prove an image is unedited—sophisticated editing can preserve or restore original values. Use with other forensic indicators.

DateTime

Tag 0x0132 EXIF

When the image file was last changed. If you've never edited the photo, this matches when you took it. After any save operation, it updates to show when you last modified it. Different from the original capture time.

Why you'd care: Helps track your editing history. If DateTime differs from DateTimeOriginal, the photo has been resaved at some point.

File modification timestamp in format "YYYY:MM:DD HH:MM:SS". Updated by any software that resaves the file. Located in IFD0, distinct from DateTimeOriginal (ExifIFD) which preserves capture time. No timezone information in standard format.

Tag ID
0x0132 (306)
Data Type
ASCII (2)
Count
20 (fixed length including null)
Format
YYYY:MM:DD HH:MM:SS
Standard
TIFF 6.0, EXIF 2.32

Artist

Tag 0x013B EXIF

The name of the person who created the image. You can set this in your camera's menu so every photo automatically includes your name. This is your credit line embedded in the file itself.

Why you'd care: Establishes authorship. If your photos spread online, your name stays embedded. Stock photo services often read this field for automatic crediting.

Records the image creator's name. Can be preset in camera settings (Canon: Owner Name; Nikon: Artist) so it's written automatically at capture. Multiple artists can be separated by semicolons, though support varies.

Tag ID
0x013B (315)
Data Type
ASCII (2)
Count
Variable (null-terminated)
Standard
TIFF 6.0, EXIF 2.32
Syncs with IPTC Creator/By-line and XMP dc:creator in metadata-aware workflows.

ImageDescription

Tag 0x010E EXIF

A text field where you can describe what's in the photo—like a caption. "Sunset at Big Sur, California" or "Family reunion, June 2024". Most cameras leave this empty; it's typically added during editing or organization.

Why you'd care: Helps you find photos later by searching descriptions. Also useful for accessibility—screen readers can read this to describe images to visually impaired users.

Free-form text describing the image subject. Rarely populated by cameras at capture time; typically written by cataloging software or manual entry. Limited to ASCII in original TIFF spec, though many tools handle UTF-8.

Tag ID
0x010E (270)
Data Type
ASCII (2)
Count
Variable
Standard
TIFF 6.0, EXIF 2.32
Often synced with IPTC Caption and XMP dc:description. May contain voice memos transcribed by some smartphone cameras.

DateTimeOriginal

Tag 0x9003 EXIF

The exact date and time you pressed the shutter button. This is the "real" timestamp—when the photo was actually taken. Unlike DateTime (which changes on edit), this stays locked to the capture moment.

Why you'd care: This is what your photo app uses to sort pictures chronologically. It's also how you prove when a photo was actually taken—important for legal evidence or journalism.

Immutable timestamp recording when the original image data was generated. For a photo, this is shutter actuation time. For scanned film, it should be the original exposure date if known. Stored in ExifIFD, not IFD0.

Tag ID
0x9003 (36867)
Data Type
ASCII (2)
Count
20
Format
YYYY:MM:DD HH:MM:SS
Standard
EXIF 2.32
Companion tags SubSecTimeOriginal and OffsetTimeOriginal can add sub-second precision and timezone. Critical for forensic timeline analysis.

DateTimeDigitized

Tag 0x9004 EXIF

When the image became a digital file. For digital cameras, this matches DateTimeOriginal (same instant). For scanned film photos, it's when you scanned them—which could be decades after the original shot.

Why you'd care: Mostly matters for scanned photos. If you scan old family photos from 1985, DateTimeOriginal would show 1985, but DateTimeDigitized shows 2024 (when scanned).

Records when the image was stored as digital data. For direct digital capture, equals DateTimeOriginal. Becomes distinct when digitizing analog sources—film scanning, video frame capture, or document imaging.

Tag ID
0x9004 (36868)
Data Type
ASCII (2)
Count
20
Format
YYYY:MM:DD HH:MM:SS
Standard
EXIF 2.32

ColorSpace

Tag 0xA001 EXIF

Defines which "palette" of colors your photo uses. sRGB is the web standard—colors look consistent on most screens. Adobe RGB contains more colors (especially greens and blues) but needs special software to display correctly.

Why you'd care: Use sRGB for sharing online. Adobe RGB photos might look dull on regular monitors if the software doesn't handle the conversion. Most phones shoot sRGB automatically.

Indicates the color space of the image data. Value 1 means sRGB; value 65535 (0xFFFF) means "uncalibrated" and typically indicates Adobe RGB or another wide-gamut space. The actual ICC profile provides precise color characterization.

Tag ID
0xA001 (40961)
Data Type
SHORT (3)
Count
1
Values
1 = sRGB, 65535 = Uncalibrated
Standard
EXIF 2.32
The "uncalibrated" value is a workaround since EXIF predates widespread ICC profile usage. Check embedded ICC profile for actual color space when this tag shows 65535.

ExifVersion

Tag 0x9000 EXIF

Shows which version of the EXIF standard your camera used. Most modern cameras write "0232" (version 2.32) or "0231" (2.31). Higher versions can store more types of information, but basic data is backward compatible.

Why you'd care: Rarely matters in practice. Old cameras might show "0220" (2.2) or earlier. It's mainly useful for developers determining which tags are valid in a file.

Four-byte ASCII string indicating EXIF specification version. Written as "0232" for EXIF 2.32 (2019), "0231" for 2.31 (2016), etc. Determines which tags are valid and their interpretation. Stored as UNDEFINED type, not null-terminated.

Tag ID
0x9000 (36864)
Data Type
UNDEFINED (7)
Count
4
Common Values
"0230", "0231", "0232"
Standard
EXIF 2.32

BitsPerSample

Tag 0x0102 EXIF

How many shades each color channel can represent. Standard photos use 8 bits (256 shades per channel = 16.7 million colors total). RAW files and professional images may use 12, 14, or 16 bits for smoother gradients and more editing flexibility.

Why you'd care: Higher bit depth means smoother color transitions and more room to adjust brightness without banding. 8-bit is fine for finished photos; 16-bit is better for heavy editing.

Specifies the number of bits per color component. For RGB images, this is typically "8, 8, 8" (24-bit total) or "16, 16, 16" (48-bit). The array length matches SamplesPerPixel. Grayscale images have a single value.

Tag ID
0x0102 (258)
Data Type
SHORT (3)
Count
SamplesPerPixel
Common Values
[8, 8, 8], [16, 16, 16]
Standard
TIFF 6.0, EXIF 2.32

Compression

Tag 0x0103 EXIF

How the image data is squeezed to save space. Value "6" means JPEG compression (most common—small files but loses some quality). Value "1" means no compression (huge files but perfect quality). There are also lossless options in between.

Why you'd care: JPEG is fine for sharing. For archival or heavy editing, uncompressed or lossless formats preserve every detail. Each re-save of a JPEG loses a tiny bit more quality.

Identifies the compression scheme applied to image data. In JPEG files, this primarily describes the embedded thumbnail's compression within the EXIF block. The main image compression is defined by the JPEG structure itself.

Tag ID
0x0103 (259)
Data Type
SHORT (3)
Count
1
Values
1 = None, 6 = JPEG, 7 = JPEG (new), 8 = Deflate
Standard
TIFF 6.0, EXIF 2.32

PixelXDimension

Tag 0xA002 EXIF

Another width measurement, but specifically for the "valid" image area after any cropping or processing applied in-camera. Usually matches ImageWidth, but can differ if your camera did in-camera editing.

Why you'd care: Most people can ignore this—it matches ImageWidth 99% of the time. It's mainly a technical detail for software to handle edge cases correctly.

Valid width of meaningful image data when stored in an uncompressed format or when the file format doesn't record dimensions elsewhere. In JPEG files, this should match the SOF (Start of Frame) dimensions. Required in ExifIFD when using compressed data.

Tag ID
0xA002 (40962)
Data Type
SHORT (3) or LONG (4)
Count
1
Standard
EXIF 2.32

PixelYDimension

Tag 0xA003 EXIF

The valid height of your image's data—typically identical to ImageHeight. Exists as a partner to PixelXDimension for consistency in the EXIF specification.

Why you'd care: Like its horizontal counterpart, this usually matches ImageHeight and doesn't require your attention unless you're debugging dimension mismatches.

Valid height of meaningful image data, paired with PixelXDimension. Together they define the actual image dimensions independent of the file's container format. Used by decoders when TIFF dimension tags might be stale or missing.

Tag ID
0xA003 (40963)
Data Type
SHORT (3) or LONG (4)
Count
1
Standard
EXIF 2.32

UserComment

Tag 0x9286 EXIF

A flexible note field for any text you want to attach to a photo. Unlike ImageDescription, this field properly supports international characters (Japanese, Arabic, emoji). Some cameras use it for voice memo transcriptions.

Why you'd care: Good place to add personal notes about a photo that won't conflict with professional captioning. Some cameras automatically fill this with voice memos or scene analysis.

Stores user-defined comments with explicit character encoding. First 8 bytes indicate encoding: "ASCII\0\0\0", "JIS\0\0\0\0\0", "UNICODE\0", or "\0\0\0\0\0\0\0\0" (undefined). Solves ImageDescription's ASCII limitation.

Tag ID
0x9286 (37510)
Data Type
UNDEFINED (7)
Count
Variable
Encoding
First 8 bytes define character set
Standard
EXIF 2.32

HostComputer

Tag 0x013C EXIF

The computer or device where the image was created or processed. For smartphone photos, this often contains the phone model. For scanned images, it might show the computer that ran the scanner software.

Why you'd care: Another breadcrumb revealing which devices touched your photo. Similar to Make/Model but focuses on the processing system rather than capture device.

Records the computer system used to create the image file. In modern workflow, often duplicates or complements Make/Model. Originally intended for workstation identification in publishing environments.

Tag ID
0x013C (316)
Data Type
ASCII (2)
Count
Variable
Standard
TIFF 6.0

Photography Settings 89 terms

Camera settings recorded at the moment of capture. Exposure, aperture, ISO, focus, flash, and metering data that tells the complete story of how your photo was made.

ExposureTime

Tag 0x829A EXIF

How long your camera's sensor was exposed to light—basically how long the "shutter was open." Displayed as fractions like 1/250 (fast) or whole seconds like 2" (slow).

Why you'd care: Fast shutter speeds freeze action (sports, birds). Slow speeds create motion blur (waterfalls, light trails). Knowing what worked helps you repeat success.

Stored as a RATIONAL type (two unsigned 32-bit integers forming numerator/denominator). A value of 1/250 is stored as {1, 250}. Long exposures use values like {30, 1} for 30 seconds. Camera firmware typically records the value used, not the metered value.

Tag ID
0x829A (33434)
Data Type
RATIONAL (5)
Count
1
Unit
Seconds
Standard
EXIF 2.32
Related to ShutterSpeedValue (APEX format) which stores the same data differently. Both should represent identical actual exposure duration.

FNumber

Tag 0x829D EXIF

How wide your lens opening was. Think of it like your eye's pupil—lower numbers (f/1.8) mean bigger opening, more light, blurrier backgrounds. Higher numbers (f/16) mean smaller opening, less light, everything sharp.

Why you'd care: Low f-numbers create that dreamy portrait blur (bokeh). High f-numbers keep landscapes sharp front-to-back. This tells you exactly what depth-of-field you achieved.

Represents lens aperture as the f-stop value, mathematically defined as the ratio of focal length to entrance pupil diameter. Stored as RATIONAL to allow precise fractional values (e.g., f/5.6 stored as {56, 10}).

Tag ID
0x829D (33437)
Data Type
RATIONAL (5)
Count
1
Range
Typically f/0.95–f/64
Standard
EXIF 2.32, TIFF/EP
ApertureValue stores the same information in APEX units. Both are recorded; FNumber is human-readable while ApertureValue enables computational exposure calculations.

ISOSpeedRatings

Tag 0x8827 EXIF

How sensitive your camera was to light. Low numbers (100-400) give clean images in bright light. High numbers (3200+) let you shoot in dim conditions but add grainy "noise" to your photos.

Why you'd care: Explains why some photos look grainy—you probably needed high ISO for the lighting. Modern cameras handle ISO 6400+ beautifully; older ones struggle past 1600.

Records sensor sensitivity per ISO 12232 standard. Originally named after film speed conventions (ASA/ISO). Modern cameras implement ISO through analog gain amplification and digital processing. May record multiple values for expanded ISO ranges.

Tag ID
0x8827 (34855)
Data Type
SHORT (3)
Count
Any (typically 1-2)
Range
Typically 50–409600
Standard
EXIF 2.32
EXIF 2.3+ added PhotographicSensitivity as the preferred tag. Legacy ISOSpeedRatings remains for compatibility. Dual ISO cameras may record base and expansion values.

ExposureProgram

Tag 0x8822 EXIF

What mode dial setting you used—Auto, Manual, Aperture Priority (A/Av), Shutter Priority (S/Tv), or a scene mode. Shows how much control you had over the exposure.

Why you'd care: Helps you remember what approach worked. "That sunset was shot in Aperture Priority at f/8"—useful for recreating successful shots.

Enumerated value indicating the exposure control mode active during capture. Values 0-8 are defined by EXIF standard; manufacturer-specific scene modes typically appear in MakerNotes rather than here.

Tag ID
0x8822 (34850)
Data Type
SHORT (3)
Count
1
Values
0=Not defined, 1=Manual, 2=Normal program, 3=Aperture priority, 4=Shutter priority, 5=Creative program, 6=Action program, 7=Portrait mode, 8=Landscape mode
Standard
EXIF 2.32

MeteringMode

Tag 0x9207 EXIF

How your camera measured light to determine exposure. "Spot" measures one small area, "Center-weighted" prioritizes the middle, "Matrix/Evaluative" analyzes the whole scene intelligently.

Why you'd care: If a photo came out too bright or dark, check metering mode. Backlit subjects often need spot metering; landscapes work well with matrix/evaluative.

Indicates the metering algorithm used to determine exposure. Most modern cameras default to multi-pattern/evaluative metering with machine learning enhancements, though this is recorded generically as "Pattern" (5).

Tag ID
0x9207 (37383)
Data Type
SHORT (3)
Count
1
Values
0=Unknown, 1=Average, 2=Center-weighted average, 3=Spot, 4=Multi-spot, 5=Pattern, 6=Partial, 255=Other
Standard
EXIF 2.32

Flash

Tag 0x9209 EXIF

Whether the flash fired, and how it was configured. Tells you if the photo used flash, if red-eye reduction was on, and whether the flash was automatic, forced, or suppressed.

Why you'd care: Explains harsh shadows or washed-out faces. Also useful for understanding why some indoor shots look natural (no flash) versus artificial (flash fired).

Bitfield encoding multiple flash-related flags in a single SHORT value. Bit 0 indicates fired status; additional bits encode return detection, mode (auto/compulsory/suppressed), red-eye reduction, and function presence.

Tag ID
0x9209 (37385)
Data Type
SHORT (3)
Count
1
Bit 0
Flash fired (0=No, 1=Yes)
Bits 1-2
Return detection (0=No strobe return function, 2=Return not detected, 3=Return detected)
Bits 3-4
Mode (0=Unknown, 1=Compulsory firing, 2=Compulsory suppression, 3=Auto)
Bit 5
Flash function present (0=Yes, 1=No flash function)
Bit 6
Red eye reduction (0=No, 1=Yes)
Standard
EXIF 2.32
Common values: 0=No flash, 1=Flash fired, 16=Flash off (compulsory), 24=Auto mode no flash, 25=Auto mode flash fired.

FocalLength

Tag 0x920A EXIF

How zoomed in your lens was, measured in millimeters. Lower numbers (18mm) give wide-angle views that capture more scene. Higher numbers (200mm) zoom in tight on distant subjects.

Why you'd care: Helps you remember what zoom setting captured that perfect shot. "That bird was at 400mm"—now you know what reach you needed.

Records the actual focal length of the lens in millimeters at capture time. For zoom lenses, reflects the specific setting used. Does not account for sensor crop factor—see FocalLengthIn35mmFilm for equivalent field of view.

Tag ID
0x920A (37386)
Data Type
RATIONAL (5)
Count
1
Unit
Millimeters
Standard
EXIF 2.32

WhiteBalance

Tag 0xA403 EXIF

Whether your camera automatically adjusted colors for the lighting (Auto), or you set it manually. Affects whether whites look truly white or have a warm/cool color cast.

Why you'd care: Explains odd color tints. Indoor photos under fluorescent lights often look green; tungsten bulbs cast orange. Correct white balance fixes this.

Simple flag indicating automatic versus manual white balance selection. The specific color temperature or preset used is found in LightSource or manufacturer-specific MakerNotes. RAW files retain original sensor data regardless of this setting.

Tag ID
0xA403 (42035)
Data Type
SHORT (3)
Count
1
Values
0=Auto, 1=Manual
Standard
EXIF 2.32

LightSource

Tag 0x9208 EXIF

What type of lighting your camera thought it was under—daylight, cloudy, shade, tungsten bulbs, fluorescent tubes, or flash. This determines how colors are balanced.

Why you'd care: If your photo has strange color casts, check this field. "Daylight" white balance indoors under tungsten lights will make everything look orange.

Specifies the light source (illuminant) used for white balance calculation. Values correspond to standard illuminants defined by the CIE (International Commission on Illumination). Custom Kelvin temperatures use value 255.

Tag ID
0x9208 (37384)
Data Type
SHORT (3)
Count
1
Key Values
0=Unknown, 1=Daylight, 2=Fluorescent, 3=Tungsten, 4=Flash, 9=Fine weather, 10=Cloudy, 11=Shade, 17-24=Various fluorescent types, 255=Other
Standard
EXIF 2.32

ExposureBiasValue

Tag 0x9204 EXIF

How much you told the camera to adjust its automatic exposure—typically shown as +1, -0.7, etc. Positive values make photos brighter; negative values make them darker.

Why you'd care: Common technique: "+1 EV for snow scenes" keeps snow white instead of gray. Knowing your compensation helps replicate successful exposure decisions.

Records the exposure compensation applied relative to the metered exposure, measured in APEX exposure value (EV) units. One EV equals one stop of exposure adjustment. Stored as SRATIONAL to support fractional negative values.

Tag ID
0x9204 (37380)
Data Type
SRATIONAL (10)
Count
1
Range
Typically -5.0 to +5.0 EV
Unit
APEX EV (stops)
Standard
EXIF 2.32

ShutterSpeedValue

Tag 0x9201 EXIF

Another way to record shutter speed—the same information as ExposureTime, but stored in a mathematical format cameras use internally for exposure calculations.

Why you'd care: You'll usually look at ExposureTime instead (shows familiar values like 1/250). This exists for technical completeness and software that needs precise calculations.

Shutter speed expressed in APEX (Additive System of Photographic Exposure) units, where Tv = -log₂(ExposureTime). This logarithmic format enables simple addition for exposure calculations: Ev = Av + Tv - Sv.

Tag ID
0x9201 (37377)
Data Type
SRATIONAL (10)
Count
1
Formula
Tv = -log₂(ExposureTime in seconds)
Example
1/250s → Tv ≈ 7.97
Standard
EXIF 2.32

ApertureValue

Tag 0x9202 EXIF

The same aperture information as FNumber, stored in a different mathematical format. Like ShutterSpeedValue, this exists for technical exposure calculations.

Why you'd care: Most people look at FNumber instead (shows familiar f/2.8, f/8, etc.). Software uses this field for automated exposure analysis.

Aperture in APEX units, where Av = 2 × log₂(FNumber). The logarithmic scale means each increment of 1 represents one stop of exposure change, enabling simple arithmetic for exposure calculations.

Tag ID
0x9202 (37378)
Data Type
RATIONAL (5)
Count
1
Formula
Av = 2 × log₂(FNumber)
Example
f/5.6 → Av ≈ 4.97
Standard
EXIF 2.32

BrightnessValue

Tag 0x9203 EXIF

How bright the scene was when your camera metered it. Higher numbers mean brighter conditions (sunny day), lower numbers mean darker (dimly lit room).

Why you'd care: Gives context about shooting conditions. A great photo at BV -1 (dim) required different skills than the same composition at BV 10 (bright sun).

Scene brightness measured by the camera's meter, expressed in APEX Bv units (approximately log₂ of luminance). This is the metered value before any exposure compensation. Value of 0xFFFFFFFF indicates unknown.

Tag ID
0x9203 (37379)
Data Type
SRATIONAL (10)
Count
1
Typical Range
-4 (candlelit) to +15 (bright snow)
Unit
APEX Bv
Standard
EXIF 2.32

MaxApertureValue

Tag 0x9205 EXIF

The widest your lens can open (its "fastest" aperture) at the focal length used. A lens marked f/2.8 might only achieve f/4 when fully zoomed in—this field tells you the actual maximum.

Why you'd care: Helps identify your lens capabilities. "Fast" lenses (f/1.4, f/2.8) excel in low light and create better background blur than slower kit lenses (f/3.5-5.6).

Records the maximum (widest) aperture available at the focal length used for capture, in APEX units. For variable-aperture zoom lenses, this reflects the maximum aperture at the specific focal length, not the lens's widest specification.

Tag ID
0x9205 (37381)
Data Type
RATIONAL (5)
Count
1
Formula
FNumber = √(2^Av)
Example
Av 2.97 ≈ f/2.8
Standard
EXIF 2.32

SubjectDistance

Tag 0x9206 EXIF

How far your camera focused—the distance to your main subject in meters. Helps you understand if you were shooting close-up portraits or distant landscapes.

Why you'd care: Useful for macro photography where precise distances matter, or figuring out how close you got to wildlife. Many cameras estimate this from lens focus position.

Estimated distance to the focused subject in meters. Derived from lens focus position, phase-detection AF data, or depth sensors. Accuracy varies significantly—some cameras don't populate this field at all. Value 0xFFFFFFFF means infinity focus.

Tag ID
0x9206 (37382)
Data Type
RATIONAL (5)
Count
1
Unit
Meters
Special Values
0=Unknown, 0xFFFFFFFF=Infinity
Standard
EXIF 2.32

ExposureMode

Tag 0xA402 EXIF

Whether the camera set exposure automatically, you set it manually, or you used bracketing (taking multiple shots at different exposures for HDR or to ensure a good exposure).

Why you'd care: Differentiates between fully automatic shooting and deliberate exposure choices. "Auto Bracket" indicates an HDR set or exposure insurance shots.

Indicates the exposure setting method at capture time. Distinguishes between camera-determined exposure (Auto), photographer-set exposure (Manual), and exposure bracketing sequences. Complements ExposureProgram which describes the specific program mode.

Tag ID
0xA402 (42034)
Data Type
SHORT (3)
Count
1
Values
0=Auto exposure, 1=Manual exposure, 2=Auto bracket
Standard
EXIF 2.32

DigitalZoomRatio

Tag 0xA404 EXIF

Whether your camera used digital zoom (cropping and enlarging electronically) and by how much. A value of 2.0 means the image was digitally magnified 2x beyond optical zoom.

Why you'd care: Digital zoom reduces image quality since it's just cropping and enlarging pixels. A ratio above 1.0 explains why a distant photo looks softer or pixelated.

Records the digital zoom factor applied at capture time as a ratio. Value of 1.0 means no digital zoom; 2.0 means 2x digital magnification. Zero or absent indicates digital zoom wasn't used. Modern smartphones may record crop factors from multi-lens switching here.

Tag ID
0xA404 (42036)
Data Type
RATIONAL (5)
Count
1
Range
0 (none) to 10+ (heavy digital zoom)
Standard
EXIF 2.32

FocalLengthIn35mmFilm

Tag 0xA405 EXIF

A standardized focal length that lets you compare zoom levels across different cameras. "50mm equivalent" means the same field of view whether you're using a phone, compact camera, or professional DSLR.

Why you'd care: Makes comparison meaningful. "24mm equivalent" is always wide-angle, "85mm equivalent" is always portrait-length, regardless of what camera you used.

Equivalent focal length assuming a 35mm full-frame sensor (36×24mm). Calculated by multiplying actual focal length by the crop factor. Stored as integer millimeters. A 50mm lens on APS-C (1.5x crop) yields 75mm equivalent.

Tag ID
0xA405 (42037)
Data Type
SHORT (3)
Count
1
Unit
Millimeters (35mm equivalent)
Special Value
0=Unknown
Standard
EXIF 2.32

SceneCaptureType

Tag 0xA406 EXIF

What type of scene your camera thought it was shooting—standard, landscape, portrait, or night scene. Some cameras detect this automatically; others record your mode dial selection.

Why you'd care: Shows what processing your camera applied. "Landscape" typically boosts saturation and sharpness; "Portrait" smooths skin tones; "Night" adjusts for darkness.

Indicates the scene classification used for image processing optimization. Values reflect either manual mode selection or camera scene detection algorithms. Affects in-camera JPEG processing; RAW files preserve original data regardless.

Tag ID
0xA406 (42038)
Data Type
SHORT (3)
Count
1
Values
0=Standard, 1=Landscape, 2=Portrait, 3=Night scene
Standard
EXIF 2.32

GainControl

Tag 0xA407 EXIF

How much your camera amplified the signal from its sensor. "High Gain Up" means the camera boosted sensitivity significantly, which often introduces noise but allows shooting in darker conditions.

Why you'd care: Related to ISO—high gain explains grainy images. Useful for understanding image quality tradeoffs your camera made automatically.

Qualitative indicator of sensor amplification level. Relates to ISO sensitivity but provides categorical rather than numeric information. Useful for understanding relative signal boosting without exposing proprietary gain algorithms.

Tag ID
0xA407 (42039)
Data Type
SHORT (3)
Count
1
Values
0=None, 1=Low gain up, 2=High gain up, 3=Low gain down, 4=High gain down
Standard
EXIF 2.32

Contrast

Tag 0xA408 EXIF

The contrast level applied to your image—how much difference there is between light and dark areas. "Soft" preserves shadow detail; "Hard" creates punchier, more dramatic images.

Why you'd care: Explains why some photos look flat (low contrast) while others pop (high contrast). This setting affects in-camera JPEGs; RAW files let you adjust later.

Records the contrast processing setting applied by camera firmware during JPEG generation. Affects the tone curve applied to image data. RAW files retain linear data regardless of this setting.

Tag ID
0xA408 (42040)
Data Type
SHORT (3)
Count
1
Values
0=Normal, 1=Soft, 2=Hard
Standard
EXIF 2.32

Saturation

Tag 0xA409 EXIF

How vivid or muted colors appear in your photo. "Low" creates more subtle, pastel-like colors; "High" makes colors pop and appear more vibrant—sometimes unrealistically so.

Why you'd care: Explains oversaturated "postcard colors" or muted film-like tones. Many smartphones default to high saturation for eye-catching shots.

Records the color saturation processing level applied during in-camera JPEG rendering. Affects chroma intensity without altering luminance. RAW files preserve original color data for custom processing.

Tag ID
0xA409 (42041)
Data Type
SHORT (3)
Count
1
Values
0=Normal, 1=Low saturation, 2=High saturation
Standard
EXIF 2.32

Sharpness

Tag 0xA40A EXIF

How much edge enhancement was applied to make details appear crisper. "Soft" gives a gentler look good for portraits; "Hard" emphasizes edges and texture—sometimes creating unnatural halos.

Why you'd care: Over-sharpening creates crunchy, unnatural-looking images with visible halos around edges. This setting reveals why some photos look "processed."

Indicates the level of unsharp mask or similar edge-enhancement processing applied during JPEG conversion. Excessive sharpening introduces ringing artifacts. Professional workflows typically use minimal in-camera sharpening, preferring RAW processing.

Tag ID
0xA40A (42042)
Data Type
SHORT (3)
Count
1
Values
0=Normal, 1=Soft, 2=Hard
Standard
EXIF 2.32

SubjectDistanceRange

Tag 0xA40C EXIF

A category describing roughly how far away your subject was: macro (very close), close-up (near), distant (far), or unknown. Simpler than the exact SubjectDistance measurement.

Why you'd care: Quick indicator of shooting context. "Macro" means you were capturing tiny details; "Distant view" suggests landscapes or far-off subjects.

Categorical classification of focus distance. Often derived from lens focus position or AF system data. Less precise than SubjectDistance but more reliably populated across cameras. May influence camera scene optimization.

Tag ID
0xA40C (42044)
Data Type
SHORT (3)
Count
1
Values
0=Unknown, 1=Macro, 2=Close view, 3=Distant view
Standard
EXIF 2.32

SensingMethod

Tag 0xA217 EXIF

What type of image sensor captured your photo. Most cameras today use "one-chip color area sensors"—a single sensor with a colored filter over each pixel to capture red, green, and blue.

Why you'd care: Mostly historical interest. Three-chip sensors (separate sensors for R/G/B) appear in professional video cameras; trilinear sensors in flatbed scanners.

Describes the image sensor type and configuration. Value 2 (one-chip color area) is standard for Bayer-pattern CMOS/CCD sensors. Foveon X3 sensors may report differently. Values 7 and 8 typically indicate scanning-type sensors.

Tag ID
0xA217 (41495)
Data Type
SHORT (3)
Count
1
Values
1=Not defined, 2=One-chip color area sensor, 3=Two-chip color area sensor, 4=Three-chip color area sensor, 5=Color sequential area sensor, 7=Trilinear sensor, 8=Color sequential linear sensor
Standard
EXIF 2.32

FileSource

Tag 0xA300 EXIF

Whether the image came from a digital camera, a scanner, or another type of device. Almost all photos from cameras and phones will say "DSC" (Digital Still Camera).

Why you'd care: Mainly helps distinguish scanned photos from native digital captures. Useful when working with mixed archives of digitized film and digital originals.

Single-byte indicator of image source hardware category. Value 3 (DSC) is nearly universal for digital cameras and smartphones. Scanners should write 1-2 but compliance varies. Custom or unknown sources may use 0.

Tag ID
0xA300 (41728)
Data Type
UNDEFINED (7)
Count
1
Values
0=Other, 1=Film scanner, 2=Reflection print scanner, 3=DSC (Digital Still Camera)
Standard
EXIF 2.32

SceneType

Tag 0xA301 EXIF

Whether this is a directly-photographed image or something else. Value 1 means "directly photographed"—the camera pointed at a real scene and captured it. This is what virtually all photos are.

Why you'd care: Could theoretically distinguish real photos from composites or CGI, but in practice this field is rarely updated even for heavily processed images.

Indicates whether the image was captured directly from a scene. Value 1 is the only defined value and indicates direct photography. Intended to distinguish from synthetic or composite images, but lacks reliable implementation for modified images.

Tag ID
0xA301 (41729)
Data Type
UNDEFINED (7)
Count
1
Values
1=Directly photographed
Standard
EXIF 2.32

CustomRendered

Tag 0xA401 EXIF

Whether your camera applied special processing—like art filters, HDR, or other effects. "Normal" means standard processing; "Custom" indicates some special effect was applied in-camera.

Why you'd care: Explains unusual-looking images. If metadata shows "Custom" rendering, the camera itself created that dreamy/dramatic/vintage look—not post-processing software.

Binary flag indicating whether non-standard image processing was applied. Does not specify what processing was used—that information may be in MakerNotes. HDR, panorama stitching, and art filters typically set value 1.

Tag ID
0xA401 (42033)
Data Type
SHORT (3)
Count
1
Values
0=Normal process, 1=Custom process
Standard
EXIF 2.32

SensitivityType

Tag 0x8830 EXIF

Which ISO measurement standard your camera used. There are actually several ways to measure ISO sensitivity—this tells you which one applies to the ISO number in your photo's data.

Why you'd care: Usually you can ignore this—ISO 800 means roughly the same thing across cameras. This matters mainly to engineers and standardization enthusiasts.

Specifies which ISO 12232 sensitivity measurement method was used. SOS (Standard Output Sensitivity) and REI (Recommended Exposure Index) are most common. Different methods can yield different ISO numbers for identical exposure behavior.

Tag ID
0x8830 (34864)
Data Type
SHORT (3)
Count
1
Values
0=Unknown, 1=SOS, 2=REI, 3=ISO, 4=SOS + ISO, 5=REI + ISO, 6=SOS + REI, 7=SOS + REI + ISO
Standard
EXIF 2.32

FlashEnergy

Tag 0xA20B EXIF

How powerful the flash was when it fired, measured in a standard unit of light output. Higher numbers mean more light was dumped onto the scene. Rarely recorded by consumer cameras.

Why you'd care: Professional studio equipment might record this for lighting reproducibility. Most cameras don't fill in this field even when flash is used.

Records strobe energy at capture time in BCPS (Beam Candle Power Seconds). Primarily used by studio flash systems and scientific imaging. Consumer camera flashes rarely populate this field. Not the same as guide number.

Tag ID
0xA20B (41483)
Data Type
RATIONAL (5)
Count
1
Unit
BCPS (Beam Candle Power Seconds)
Standard
EXIF 2.32

SubjectArea

Tag 0x9214 EXIF

Where in the frame your camera's autofocus locked on. This tells you which part of the image was considered the "main subject"—useful for understanding focus decisions.

Why you'd care: Helps debug focus issues. If your subject is blurry but the background is sharp, checking SubjectArea reveals where the camera actually focused.

Specifies the main subject location as pixel coordinates. Encoding varies by count: 2 values = center point (X, Y); 3 values = circle (X, Y, diameter); 4 values = rectangle (X, Y, width, height). Coordinates are relative to full sensor area, not cropped output.

Tag ID
0x9214 (37396)
Data Type
SHORT (3)
Count
2, 3, or 4
Format
[X, Y] or [X, Y, diameter] or [X, Y, width, height]
Standard
EXIF 2.32

SubjectLocation

Tag 0xA214 EXIF

The exact pixel coordinates of your main subject within the image—where the camera detected or you selected the primary focus point. Shown as X and Y pixel positions.

Why you'd care: Useful for analysis of focus point selection. If every photo has the subject dead-center, you might want to explore the rule of thirds more.

Records the main subject location as X, Y pixel coordinates within the image. Unlike SubjectArea which can describe regions, this field specifies only a point location. Origin (0, 0) is top-left corner of the image.

Tag ID
0xA214 (41492)
Data Type
SHORT (3)
Count
2
Format
[X column, Y row]
Standard
EXIF 2.32

FocalPlaneXResolution

Tag 0xA20E EXIF

How densely packed the pixels are on your camera's sensor—how many pixels fit per unit of physical sensor area. Higher density means smaller individual pixels.

Why you'd care: Combined with megapixel count, reveals sensor size. Small sensors with high density have tiny pixels that may perform worse in low light than large sensors with fewer pixels.

Records the sensor's horizontal pixel density as pixels per FocalPlaneResolutionUnit. Combined with image dimensions, enables calculation of actual sensor dimensions. FocalPlaneYResolution provides the vertical complement.

Tag ID
0xA20E (41486)
Data Type
RATIONAL (5)
Count
1
Unit
Per FocalPlaneResolutionUnit (0xA210)
Standard
EXIF 2.32
Sensor width (mm) = ImageWidth / FocalPlaneXResolution × (25.4 if unit=inch). Use FocalPlaneYResolution (0xA20F) for height calculation.

ImageUniqueID

Tag 0xA420 EXIF

A unique code assigned to identify this specific image, like a serial number. Helps distinguish between different photos even if they have identical filenames or capture times.

Why you'd care: Useful for photo management software to track images across renames and copies. However, many cameras don't generate this field, and it's not universally unique.

32-character hexadecimal identifier intended to uniquely identify the image. Generation method is manufacturer-specific and may incorporate serial numbers, timestamps, or random values. Not guaranteed globally unique across all cameras.

Tag ID
0xA420 (42016)
Data Type
ASCII (2)
Count
33 (32 hex digits + null terminator)
Format
128-bit value as hexadecimal string
Standard
EXIF 2.32

Gamma

Tag 0xA500 EXIF

A value describing how brightness levels in the image file map to actual display brightness. Most images use a value around 2.2, which matches typical computer monitors.

Why you'd care: Usually handled automatically by software. If images look too dark or washed out across devices, incorrect gamma interpretation might be the cause.

Records the gamma coefficient of the image, describing the relationship between encoded pixel values and light intensity. Value 2.2 is standard for sRGB. Value 1.0 indicates linear gamma (no encoding). Rarely populated by cameras; typically assumed to be sRGB-compatible.

Tag ID
0xA500 (42240)
Data Type
RATIONAL (5)
Count
1
Typical Values
1.0 (linear), 1.8 (older Mac), 2.2 (sRGB), 2.4 (Rec. 709)
Standard
EXIF 2.32

OffsetTime

Tag 0x9010 EXIF

Your timezone when the photo was taken, shown as an offset from UTC (like +05:30 for India or -08:00 for Pacific US). This makes the capture time globally precise, not just "local time."

Why you'd care: Critical for sorting travel photos correctly. Without timezone, a photo taken at "10 PM" in Tokyo appears earlier than one taken at "3 PM" in London, even though Tokyo was first.

Records the timezone offset for the DateTime tag (ModifyDate). Format is ±HH:MM relative to UTC. Added in EXIF 2.31 to address the historic ambiguity of EXIF timestamps. Three related tags exist: OffsetTime (ModifyDate), OffsetTimeOriginal (DateTimeOriginal), OffsetTimeDigitized.

Tag ID
0x9010 (36880)
Data Type
ASCII (2)
Count
7
Format
±HH:MM
Example
-08:00, +05:30, +00:00
Standard
EXIF 2.31+

SubSecTime

Tag 0x9290 EXIF

Fractions of a second for the capture time—the part after the decimal point. Normal timestamps only go down to seconds; this adds precision like .250 (quarter second) or .083 (one-twelfth second).

Why you'd care: Essential for sorting burst-mode photos taken in the same second. Without subsecond precision, 12 photos per second all show identical timestamps.

Provides sub-second precision for the DateTime tag. Stored as an ASCII string representing decimal fractions (e.g., "123" means .123 seconds). Related tags SubSecTimeOriginal and SubSecTimeDigitized provide precision for their respective timestamps.

Tag ID
0x9290 (37520)
Data Type
ASCII (2)
Count
Variable
Format
Decimal digits (e.g., "250" for .250 seconds)
Related
SubSecTimeOriginal (0x9291), SubSecTimeDigitized (0x9292)
Standard
EXIF 2.32

InteroperabilityIndex

Tag 0x0001 EXIF

A code indicating which compatibility standard the image follows. "R98" means it's a standard JPEG that any EXIF-aware software can read; "R03" indicates DCF Option File (typically thumbnail or special format).

Why you'd care: You can usually ignore this—it's mainly for software compatibility verification. Almost all camera JPEGs use "R98" standard interoperability.

Identifies the interoperability rule to which the file conforms, stored in the Interoperability IFD. R98 indicates ExifR98 (standard JPEG with sRGB), R03 indicates DCF option file (non-standard colorspace or thumbnail). Part of DCF (Design rule for Camera File system) specification.

Tag ID
0x0001 (1) in Interoperability IFD
Data Type
ASCII (2)
Count
4
Values
"R98" (ExifR98, sRGB JPEG), "R03" (DCF Option File), "THM" (DCF Thumbnail)
Standard
DCF 2.0, EXIF 2.32

GPS & Location 27 terms

Geographic coordinates, altitude, direction, and timing data embedded by GPS-enabled devices. These fields can pinpoint exactly where and when a photo was taken—often to within a few meters.

Privacy Warning: GPS metadata can reveal sensitive locations—your home address, workplace, children's schools, or daily routines. Consider removing this data before sharing photos publicly.

GPSLatitude

Tag 0x0002 GPS

Your north-south position on Earth when the photo was taken. Combined with longitude, this pinpoints exactly where you were standing—sometimes accurate to within 3 meters with modern smartphones.

Why you'd care: Lets you see on a map exactly where each photo was taken. Great for travel memories, but reveals your physical location to anyone who examines the file.
Privacy: Can reveal your home address, workplace, or frequented locations. Remove before sharing photos online, especially of children or your residence.

Stores latitude as three RATIONAL values representing degrees, minutes, and seconds (DMS format). Requires GPSLatitudeRef to indicate North or South hemisphere. Some implementations use decimal degrees with minutes and seconds as zero.

Tag ID
0x0002 (2)
Data Type
RATIONAL (5)
Count
3
Format
[degrees, minutes, seconds]
Standard
EXIF 2.32 (GPS IFD)
Accuracy varies: dedicated GPS receivers achieve 3-5m, smartphones 3-15m depending on conditions. Indoor locations may be significantly less accurate or derived from WiFi triangulation.

GPSLatitudeRef

Tag 0x0001 GPS

A simple indicator—"N" for north of the equator, "S" for south. Works together with GPSLatitude to form a complete position. Without this, the latitude number would be ambiguous.

Why you'd care: Essential companion to latitude coordinates. If you're editing GPS data manually, forgetting this tag would make your location unreadable.

Single ASCII character indicating latitude hemisphere. "N" for northern hemisphere (positive latitude), "S" for southern hemisphere (negative latitude). Must be present when GPSLatitude is recorded.

Tag ID
0x0001 (1)
Data Type
ASCII (2)
Count
2 (including null)
Values
"N" or "S"
Standard
EXIF 2.32 (GPS IFD)

GPSLongitude

Tag 0x0004 GPS

Your east-west position on Earth. Together with latitude, this creates an exact point on the map. The Prime Meridian (through Greenwich, London) divides East from West longitudes.

Why you'd care: The other half of your location coordinates. Latitude alone only tells you how far north/south—longitude completes the picture to give your exact spot.
Privacy: Combined with latitude, creates precise coordinates that can be plotted on any map service. Even a single photo can reveal your home location if taken there.

Stores longitude as three RATIONAL values in degrees, minutes, seconds format. Requires GPSLongitudeRef for East/West designation. Range: 0° to 180° (with reference indicating direction from Prime Meridian).

Tag ID
0x0004 (4)
Data Type
RATIONAL (5)
Count
3
Format
[degrees, minutes, seconds]
Standard
EXIF 2.32 (GPS IFD)

GPSLongitudeRef

Tag 0x0003 GPS

Indicates whether the longitude is "E" (east of the Prime Meridian) or "W" (west). Americas are West; Europe, Africa, Asia, and Australia are primarily East.

Why you'd care: Without this single letter, the longitude number is meaningless. Getting it wrong would place your photo on the wrong side of the planet.

Single ASCII character for longitude hemisphere. "E" indicates positive longitude (east of Greenwich), "W" indicates negative longitude (west). Forms a required pair with GPSLongitude tag.

Tag ID
0x0003 (3)
Data Type
ASCII (2)
Count
2
Values
"E" or "W"
Standard
EXIF 2.32 (GPS IFD)

GPSAltitude

Tag 0x0006 GPS

How high you were above (or below) sea level when taking the photo, measured in meters. At the beach it's near 0; in Denver it's around 1,600; on a mountaintop it could be 4,000+.

Why you'd care: Adds a third dimension to your location. Helpful for hiking and travel photos to remember elevations. Also tells whether you were on a high floor of a building.

Altitude in meters, stored as RATIONAL for fractional precision. Reference datum (above/below sea level) is specified by GPSAltitudeRef. Consumer GPS altitude accuracy is typically ±10-20m, significantly less precise than horizontal positioning.

Tag ID
0x0006 (6)
Data Type
RATIONAL (5)
Count
1
Units
Meters
Standard
EXIF 2.32 (GPS IFD)
GPS altitude uses WGS84 ellipsoid, which can differ from local mean sea level by up to 100m in some regions. Barometric altimeters on phones may provide corrections.

GPSAltitudeRef

Tag 0x0005 GPS

Indicates whether the altitude is above sea level (normal, value 0) or below sea level (rare, value 1). Unless you're photographing from a submarine or the Dead Sea, this is almost always 0.

Why you'd care: Usually not—it's almost always "above sea level." Only relevant in unusual situations like underwater photography or locations below sea level.

Single byte indicating altitude reference. Value 0 means altitude is above sea level; value 1 means below sea level. Default is 0 when not specified. Required when GPSAltitude is present.

Tag ID
0x0005 (5)
Data Type
BYTE (1)
Count
1
Values
0 = Above sea level, 1 = Below sea level
Standard
EXIF 2.32 (GPS IFD)

GPSTimeStamp

Tag 0x0007 GPS

The time from GPS satellites when your location was recorded—always in UTC (Coordinated Universal Time), regardless of your local timezone. GPS time comes from atomic clocks in space, so it's extremely accurate.

Why you'd care: More accurate than your camera's internal clock. Useful for synchronizing photos from multiple cameras or verifying exact timing for events.

UTC time from GPS fix, stored as three RATIONAL values for hours, minutes, and seconds. GPS time derives from satellite atomic clocks, accurate to nanoseconds. May differ from DateTimeOriginal if camera clock isn't synced.

Tag ID
0x0007 (7)
Data Type
RATIONAL (5)
Count
3
Format
[hours, minutes, seconds] in UTC
Standard
EXIF 2.32 (GPS IFD)
Combined with GPSDateStamp for complete UTC timestamp. GPS time is always UTC—does not observe daylight saving time.

GPSDateStamp

Tag 0x001D GPS

The date component from GPS data, always in UTC timezone. Because of timezone differences, this might show a different date than your local time—if you take a photo at 11 PM in New York, the GPS date might show tomorrow's date (UTC is 5 hours ahead).

Why you'd care: The GPS date is timezone-neutral, making it reliable for synchronizing international travel photos or correlating with other GPS logs.

Date of GPS fix in UTC, formatted as "YYYY:MM:DD". Paired with GPSTimeStamp for complete UTC datetime. May differ from DateTimeOriginal's local date due to timezone offset, especially near midnight.

Tag ID
0x001D (29)
Data Type
ASCII (2)
Count
11
Format
YYYY:MM:DD
Standard
EXIF 2.32 (GPS IFD)

GPSSpeed

Tag 0x000D GPS

How fast you were moving when the photo was taken. Useful for action shots while driving, cycling, skiing, or flying. The unit (mph, km/h, or knots) is specified separately.

Why you'd care: Fun data for sports and travel photos. "I took this at 65 mph!" Some dash cams and action cameras record this automatically.

GPS-derived speed of movement at capture time. Units specified by GPSSpeedRef tag. Calculated from position changes between GPS fixes, so accuracy depends on fix interval and conditions.

Tag ID
0x000D (13)
Data Type
RATIONAL (5)
Count
1
Units
Per GPSSpeedRef: K=km/h, M=mph, N=knots
Standard
EXIF 2.32 (GPS IFD)

GPSSpeedRef

Tag 0x000C GPS

Tells you what unit the GPSSpeed value is measured in: "K" for kilometers per hour, "M" for miles per hour, or "N" for nautical miles per hour (knots). Check this before interpreting the speed number.

Why you'd care: A speed of "60" could mean very different things depending on the unit. Always check this companion tag to interpret GPSSpeed correctly.

Single character defining GPSSpeed units. Default is "K" (kilometers/hour) if not specified. Aviation and marine equipment may use "N" (nautical miles/hour, knots).

Tag ID
0x000C (12)
Data Type
ASCII (2)
Count
2
Values
"K" = km/h, "M" = mph, "N" = knots
Standard
EXIF 2.32 (GPS IFD)

GPSImgDirection

Tag 0x0011 GPS

The compass direction your camera was pointing when you took the photo—0° is North, 90° is East, 180° is South, 270° is West. Recorded by your phone's digital compass or magnetometer.

Why you'd care: Helps identify what you photographed without a clear landmark. "This was shot facing northeast" can help locate a building or mountain in the frame.

Camera heading in degrees (0-360) when image was captured. Reference type (true north vs magnetic north) specified by GPSImgDirectionRef. Derived from device magnetometer; accuracy affected by magnetic interference.

Tag ID
0x0011 (17)
Data Type
RATIONAL (5)
Count
1
Range
0.00 to 359.99 degrees
Standard
EXIF 2.32 (GPS IFD)
Phone compass accuracy is typically ±5-15°. Metal objects, buildings, and electromagnetic interference can cause significant deviation.

GPSImgDirectionRef

Tag 0x0010 GPS

Specifies whether the image direction is measured against true north ("T") or magnetic north ("M"). True north points to the geographic North Pole; magnetic north points where a compass needle points, which shifts over time.

Why you'd care: The difference is usually small (a few degrees) but matters for precise navigation. Most modern phones calculate and store true north.

Reference for GPSImgDirection bearing. "T" = true (geographic) north; "M" = magnetic north. Smartphones typically apply magnetic declination correction and report true north.

Tag ID
0x0010 (16)
Data Type
ASCII (2)
Count
2
Values
"T" = True North, "M" = Magnetic North
Standard
EXIF 2.32 (GPS IFD)

GPSTrack

Tag 0x000F GPS

The compass direction you were traveling when the photo was taken—not where the camera was pointed, but which way you were moving. Different from GPSImgDirection if you took a photo while facing sideways.

Why you'd care: Useful for tracking movement during road trips or hikes. Combined with speed, tells the complete story of your motion at capture time.

Direction of GPS receiver movement in degrees (0-360). Distinct from GPSImgDirection which records camera pointing direction. Calculated from successive position fixes, so requires movement to be accurate.

Tag ID
0x000F (15)
Data Type
RATIONAL (5)
Count
1
Range
0.00 to 359.99 degrees
Standard
EXIF 2.32 (GPS IFD)

GPSTrackRef

Tag 0x000E GPS

Whether GPSTrack is measured relative to true north ("T") or magnetic north ("M"). Same concept as GPSImgDirectionRef but for your movement direction instead of camera pointing direction.

Why you'd care: Only matters if you need precise directional accuracy. Most users can ignore this detail.

Reference for GPSTrack bearing. "T" = true north; "M" = magnetic north. GPS-derived track is inherently referenced to true north; magnetic is used with traditional compasses.

Tag ID
0x000E (14)
Data Type
ASCII (2)
Count
2
Values
"T" or "M"
Standard
EXIF 2.32 (GPS IFD)

GPSMapDatum

Tag 0x0012 GPS

The coordinate system used for the GPS data—almost always "WGS-84", the global standard used by GPS satellites and mapping services like Google Maps. It defines the shape of Earth used for calculations.

Why you'd care: Usually you don't—WGS-84 is the universal standard. Only matters when working with specialized survey data or very old coordinate systems.

Geodetic datum for GPS coordinates. "WGS-84" (World Geodetic System 1984) is the GPS native datum and nearly universal. Historical data might use local datums (NAD27, ED50) which can differ by hundreds of meters.

Tag ID
0x0012 (18)
Data Type
ASCII (2)
Count
Variable
Common Value
"WGS-84"
Standard
EXIF 2.32 (GPS IFD)
Using coordinates without knowing the datum can introduce positioning errors up to 1km in extreme cases. Modern GPS always outputs WGS-84.

GPSDestLatitude

Tag 0x0014 GPS

The latitude of your subject (what you photographed), not where you were standing. Rarely used in consumer photography—it's designed for cases where you're photographing something at a known different location.

Why you'd care: Most consumer photos don't include this. It's more relevant for surveying, aviation, or photographing distant landmarks with known coordinates.

Latitude of the subject/destination point, formatted identically to GPSLatitude. Used with GPSDestLatitudeRef, GPSDestLongitude, and GPSDestLongitudeRef to specify subject location distinct from camera position.

Tag ID
0x0014 (20)
Data Type
RATIONAL (5)
Count
3
Format
[degrees, minutes, seconds]
Standard
EXIF 2.32 (GPS IFD)

GPSDestLongitude

Tag 0x0016 GPS

The longitude of your subject, paired with GPSDestLatitude. Together they mark the location of what you photographed, separate from where the camera was positioned.

Why you'd care: Specialized use case—most photos only record where the photographer stood, not where they were looking.

Longitude of subject/destination point in standard DMS format. Completes the destination coordinate pair with GPSDestLatitude. Rarely populated in consumer photography equipment.

Tag ID
0x0016 (22)
Data Type
RATIONAL (5)
Count
3
Standard
EXIF 2.32 (GPS IFD)

GPSDestBearing

Tag 0x0018 GPS

The compass direction from where you stood to what you photographed. If you're at a lookout point photographing a mountain to your east, this would be around 90 degrees.

Why you'd care: Can help identify distant subjects. Similar to GPSImgDirection but specifically describes the bearing to the subject rather than where the camera faced.

Bearing from camera position to destination/subject in degrees. Can be calculated from coordinates or measured directly. Reference direction (true/magnetic) specified by GPSDestBearingRef.

Tag ID
0x0018 (24)
Data Type
RATIONAL (5)
Count
1
Range
0.00 to 359.99 degrees
Standard
EXIF 2.32 (GPS IFD)

GPSDestDistance

Tag 0x001A GPS

How far away the subject of your photo was from where you stood. Useful when photographing distant landmarks—"That mountain is 15 kilometers away." Units are specified separately.

Why you'd care: Provides context for landscape and wildlife photos. "The elephant was 200 meters away" tells the story better than just GPS coordinates.

Distance from camera position to subject/destination. Can be calculated from coordinate pairs or measured directly (e.g., by rangefinder). Units specified by GPSDestDistanceRef.

Tag ID
0x001A (26)
Data Type
RATIONAL (5)
Count
1
Units
Per GPSDestDistanceRef
Standard
EXIF 2.32 (GPS IFD)

GPSProcessingMethod

Tag 0x001B GPS

How your device figured out where you were. "GPS" means satellite-based (most accurate). "CELLID" means estimated from cell towers. "WLAN" means derived from WiFi networks. Some devices use combinations.

Why you'd care: Explains accuracy variations. Pure GPS is usually accurate to 3-5 meters. WiFi/cell tower methods might be off by 20-100 meters or more.

Text string identifying the positioning method. Standard values: "GPS", "CELLID", "WLAN", or combinations like "GPS/CELLID". First 8 bytes indicate character encoding (as with UserComment). Device-dependent implementation.

Tag ID
0x001B (27)
Data Type
UNDEFINED (7)
Count
Variable
Common Values
"GPS", "CELLID", "WLAN", "MANUAL"
Standard
EXIF 2.32 (GPS IFD)
A-GPS (Assisted GPS) uses cell network to speed satellite acquisition but still provides satellite-grade accuracy. May appear as "GPS" or "GPS/CELLID".

GPSDOP

Tag 0x000B GPS

A quality score for the GPS reading—lower is better. Values under 2 are excellent; 2-5 is good; over 5 suggests the coordinates may be less accurate. It measures how well-positioned the satellites were overhead.

Why you'd care: Helps you know how much to trust the location data. A high DOP in a canyon or dense city means the coordinates might be off by more than usual.

Dilution of Precision—a unitless quality metric where lower values indicate better satellite geometry. PDOP (position), HDOP (horizontal), or VDOP (vertical) may be stored; exact type is often unspecified.

Tag ID
0x000B (11)
Data Type
RATIONAL (5)
Count
1
Quality Scale
<2 excellent, 2-5 good, 5-10 moderate, >10 poor
Standard
EXIF 2.32 (GPS IFD)
DOP reflects satellite constellation geometry, not absolute accuracy. Multiply DOP by receiver's base accuracy (typically 3m) for error estimate.

GPSSatellites

Tag 0x0008 GPS

Information about the GPS satellites used to calculate your position. Might include how many satellites were visible or their individual signal strengths. More satellites generally means better accuracy.

Why you'd care: Mostly for GPS enthusiasts. A count of 8+ satellites usually means excellent fix quality. Fewer than 4 means the position might be unreliable.

Free-form ASCII text describing satellites used for the position fix. Format varies by manufacturer—may include satellite count, PRN codes, elevations, azimuths, or SNR values. No standardized structure.

Tag ID
0x0008 (8)
Data Type
ASCII (2)
Count
Variable
Standard
EXIF 2.32 (GPS IFD)

GPSStatus

Tag 0x0009 GPS

Whether the GPS was actively tracking ("A" for active) or still searching for satellites ("V" for void/invalid). If this shows "V", the coordinates might be old or estimated.

Why you'd care: Tells you if the GPS had a real fix or was guessing. "A" means solid lock; "V" means the location might be from a previous fix or interpolated.

GPS receiver status at time of fix. "A" indicates active measurement (valid fix); "V" indicates void/invalid (receiver searching or using dead reckoning). Derived from NMEA sentence status flags.

Tag ID
0x0009 (9)
Data Type
ASCII (2)
Count
2
Values
"A" = Active, "V" = Void
Standard
EXIF 2.32 (GPS IFD)

GPSMeasureMode

Tag 0x000A GPS

Whether the GPS calculated a 2D fix (latitude and longitude only) or a 3D fix (latitude, longitude, and altitude). 3D is better and requires at least 4 satellites; 2D only needs 3 but can't determine height.

Why you'd care: If the altitude seems wrong, check this—a 2D fix means the altitude is either unavailable or estimated, not measured.

GPS measurement dimensionality. "2" = 2D fix (latitude/longitude only, 3 satellites minimum); "3" = 3D fix (full position including altitude, 4+ satellites). Affects altitude reliability.

Tag ID
0x000A (10)
Data Type
ASCII (2)
Count
2
Values
"2" = 2D, "3" = 3D
Standard
EXIF 2.32 (GPS IFD)

GPSVersionID

Tag 0x0000 GPS

The version of the GPS metadata format used in this file—almost always "2.3.0.0" for modern cameras. Like a format identifier that tells software how to interpret the other GPS tags.

Why you'd care: You probably don't—it's just a technical detail ensuring GPS data is read correctly. Current standard has been stable for years.

Version of the GPSInfoIFD. Four bytes representing major.minor.revision.build. Current version is 2.3.0.0 (bytes: 2, 3, 0, 0). Must be first tag in GPS IFD to enable proper parsing.

Tag ID
0x0000 (0)
Data Type
BYTE (1)
Count
4
Current Value
[2, 3, 0, 0]
Standard
EXIF 2.32 (GPS IFD)

IPTC Metadata 48 terms

Professional metadata standard developed by the International Press Telecommunications Council. Creator credits, captions, keywords, copyright, and contact information used by news agencies and stock photo services.

ObjectName

IIM 2:05 IPTC

A short reference name for your image—like giving a file a nickname that describes what's in it. News agencies use this to quickly identify photos in their systems.

Why you'd care: Helps you find specific photos later. Stock photo sites use this as the image title that buyers see in search results.

Short textual identifier assigned to the object by the creator, functioning as a unique reference within the provider's system. Distinct from the headline (which is for publication) and caption (which describes content). Limited to 64 characters per IPTC IIM specification.

Dataset
2:05
Data Type
Text
Max Length
64 characters
Standard
IPTC IIM 4.2

Urgency

IIM 2:10 IPTC

A 1-8 scale showing how quickly this image needs to be processed or published. News agencies use this to prioritize breaking news photos over feature stories.

Why you'd care: Mostly relevant if you work in news photography. A "1" means "flash—stop the presses" while an "8" means "whenever you get around to it."

Editorial priority indicator on a scale of 1 (most urgent) to 8 (least urgent), with 5 representing normal urgency. Originally designed for wire service workflows to prioritize transmission order. Value 0 is reserved, and 9 indicates user-defined priority.

Dataset
2:10
Data Type
Digits
Value Range
1-8 (0 reserved, 9 user-defined)
Standard
IPTC IIM 4.2

Category

IIM 2:15 IPTC

A three-letter code identifying the subject area—like "SPO" for sports, "WAR" for war/conflict, or "FIN" for finance. Think of it as a filing system for news photos.

Why you'd care: This legacy field is mostly replaced by Keywords, but you might still see it in older images from news agencies.

Three-character alphabetic code identifying the subject matter according to provider's classification scheme. Originally used ANPA codes (American Newspaper Publishers Association). Now largely deprecated in favor of Subject Reference codes, though still supported for backward compatibility.

Dataset
2:15
Data Type
Alpha (3 chars)
Max Length
3 characters
Standard
IPTC IIM 4.2 (deprecated)

SupplementalCategories

IIM 2:20 IPTC

Additional category codes to further classify an image beyond the main category. If the main Category is "SPO" (sports), supplemental might specify "basketball" or "NBA Finals."

Why you'd care: Like Category, this is a legacy field. Modern workflows use Keywords and Subject Reference instead.

Repeatable field containing additional subject classification codes that supplement the primary Category. Each instance can be up to 32 characters. Now deprecated in favor of Subject Reference (2:12), which uses standardized IPTC NewsCodes.

Dataset
2:20
Data Type
Text
Max Length
32 characters each
Repeatable
Yes
Standard
IPTC IIM 4.2 (deprecated)

Keywords

IIM 2:25 IPTC

Searchable words or phrases describing what's in your photo—like hashtags, but embedded in the file itself. "sunset," "beach," "California," "vacation" would all be separate keywords.

Why you'd care: This is how stock photo buyers find your images. Good keywording can be the difference between selling photos and having them sit unseen. Also helps you find photos in your own library years later.

Repeatable field for individual words or short phrases describing the intellectual content. Each keyword should be atomic (one concept per keyword). Forms the primary discovery mechanism for image databases. Maps to dc:subject in XMP. Controlled vocabularies are recommended for consistency.

Dataset
2:25
Data Type
Text
Max Length
64 characters each
Repeatable
Yes (unlimited)
Standard
IPTC IIM 4.2, XMP dc:subject

SpecialInstructions

IIM 2:40 IPTC

Notes to photo editors about how to handle this image. "EMBARGO until 9am EST" or "Do not crop" or "Model release on file." Think of it as a sticky note attached to your photo.

Why you'd care: Essential for professional workflows. If you have usage restrictions, release information, or handling requirements, this is where they go.

Free-text field for editorial handling instructions that travel with the image through production workflows. Common uses include embargo dates, cropping restrictions, sensitivity warnings, and model/property release status. Content should be actionable instructions, not descriptive metadata.

Dataset
2:40
Data Type
Text
Max Length
256 characters
Standard
IPTC IIM 4.2

DateCreated

IIM 2:55 IPTC

The date when the intellectual content was created—typically when you pressed the shutter. For a scan of a 1960s photo, this would be 1960s, not the scan date.

Why you'd care: Distinguishes when the actual photo was taken from when the file was digitized. Important for historical images and archival work.

Designates the date the intellectual content was created. Per IPTC definition, this is explicitly the date of content creation, not file creation or modification. Stored as CCYYMMDD (8 digits). Should be combined with TimeCreated (2:60) for complete temporal specification. Maps to photoshop:DateCreated in XMP.

Dataset
2:55
Data Type
Digits
Format
CCYYMMDD (e.g., 20240315)
Standard
IPTC IIM 4.2

TimeCreated

IIM 2:60 IPTC

The time of day when the photo was taken, paired with DateCreated to give the complete moment. Includes timezone information so editors know exactly when events occurred.

Why you'd care: Critical for news photography where the exact moment matters—"Was this photo taken before or after the announcement?"

Time component corresponding to DateCreated, indicating when the intellectual content was created. Format includes optional timezone offset from UTC. Combined with DateCreated, provides complete ISO 8601-compatible timestamp for content creation moment.

Dataset
2:60
Data Type
Digits
Format
HHMMSS±HHMM (e.g., 143022+0100)
Standard
IPTC IIM 4.2

Byline

IIM 2:80 IPTC

The photographer's name—who actually pressed the shutter. This is your credit line that appears under published photos: "Photo by Jane Smith."

Why you'd care: Essential for getting credited for your work. Stock agencies, news organizations, and publications pull this field to display photographer credits.

Contains the name(s) of the creator(s) of the intellectual content. Repeatable for multiple creators. Maps to dc:creator in XMP Dublin Core. Should contain individual names, not organization names (use Credit for organization attribution). Format typically "Surname, Firstname" for consistent sorting.

Dataset
2:80
Data Type
Text
Max Length
32 characters each
Repeatable
Yes
Standard
IPTC IIM 4.2, XMP dc:creator

BylineTitle

IIM 2:85 IPTC

The photographer's job title or role—"Staff Photographer," "Freelance," "Chief Photographer," or "Contributing Photographer." Accompanies the Byline for fuller attribution.

Why you'd care: Adds professional context to your credit. "Photo by Jane Smith, Chief Photographer" sounds more authoritative than just a name alone.

Contains the job title or position of the creator(s) identified in Byline. Should describe their role at time of creation, not their current position. Maps to photoshop:AuthorsPosition in XMP. Multiple titles correspond positionally to multiple Byline entries.

Dataset
2:85
Data Type
Text
Max Length
32 characters
Standard
IPTC IIM 4.2

City

IIM 2:90 IPTC

The city where the photo was taken—"New York," "London," or "Tokyo." This is a text location, not GPS coordinates, so it's human-readable and searchable.

Why you'd care: Helps editors and stock photo buyers find images from specific locations. Someone searching for "Paris photos" will find yours if this field is filled in.

Identifies the city of content origin per IPTC location hierarchy (Sublocation → City → State/Province → Country). Use official city name, not colloquial names. For non-urban locations, use the nearest named municipality. Maps to photoshop:City in XMP.

Dataset
2:90
Data Type
Text
Max Length
32 characters
Standard
IPTC IIM 4.2

Sublocation

IIM 2:92 IPTC

The specific place within a city—"Central Park," "Eiffel Tower," "Madison Square Garden," or "Westminster Abbey." More precise than just the city name.

Why you'd care: Adds context that makes your photos more discoverable and valuable. "Louvre Museum, Paris" is more useful than just "Paris."

Most specific element of the IPTC location hierarchy. Can be a landmark, venue, named area, or street address. Should identify a recognizable location narrower than city level. Maps to Iptc4xmpCore:Location in XMP. For unnamed locations, consider leaving empty rather than using GPS coordinates.

Dataset
2:92
Data Type
Text
Max Length
32 characters
Standard
IPTC IIM 4.2

Province-State

IIM 2:95 IPTC

The state, province, or region where the photo was taken—"California," "Ontario," "Bavaria," or "New South Wales." The administrative level between city and country.

Why you'd care: Disambiguates cities with common names. There are cities named "Springfield" in many U.S. states—the state tells you which one.

Primary administrative subdivision of the country—typically a state, province, territory, or region. Use official names, not abbreviations. For countries without administrative subdivisions, this field may be omitted. Maps to photoshop:State in XMP.

Dataset
2:95
Data Type
Text
Max Length
32 characters
Standard
IPTC IIM 4.2

Country-PrimaryLocationCode

IIM 2:100 IPTC

A standardized two or three-letter code for the country—"US" for United States, "GB" for Great Britain, "JP" for Japan. Computers use these codes for consistent international sorting.

Why you'd care: Ensures your photos are correctly categorized regardless of language. "Deutschland" and "Germany" both map to "DE."

ISO 3166-1 alpha-3 country code indicating location of content origin. Provides unambiguous, language-independent country identification. Should be used together with Country-PrimaryLocationName for human readability. Maps to Iptc4xmpCore:CountryCode in XMP.

Dataset
2:100
Data Type
Alpha
Length
3 characters (ISO 3166-1 alpha-3)
Standard
IPTC IIM 4.2, ISO 3166-1

Country-PrimaryLocationName

IIM 2:101 IPTC

The full, readable country name—"United States," "United Kingdom," "Japan." The human-friendly version of the country code.

Why you'd care: Makes your photos searchable by country name. More intuitive for browsing than country codes.

Full name of the country depicted in the content. Use official English name per ISO 3166-1 or UN standards. Should always be accompanied by Country-PrimaryLocationCode for machine processing. Maps to photoshop:Country in XMP.

Dataset
2:101
Data Type
Text
Max Length
64 characters
Standard
IPTC IIM 4.2

OriginalTransmissionReference

IIM 2:103 IPTC

Originally a wire service routing code, now commonly used as a job number or client reference. "Wedding-Smith-2024" or "Client123-Project456" helps track which project a photo belongs to.

Why you'd care: Handy for organizing photos by assignment or project. When a client asks for "those photos from the Johnson shoot," this field helps you find them.

Originally designated for wire transmission routing codes; now repurposed as a general job/project identifier. IPTC Photo Metadata Standard recommends using this for job tracking, purchase order numbers, or client references. Maps to photoshop:TransmissionReference in XMP.

Dataset
2:103
Data Type
Text
Max Length
32 characters
Standard
IPTC IIM 4.2

Headline

IIM 2:105 IPTC

A short, publishable summary of the image—like a newspaper headline. "President Signs Climate Bill" or "Sunset Over Golden Gate Bridge." Intended for publication, not just internal use.

Why you'd care: Stock agencies often display this as the image title. A compelling headline makes your photo more likely to be licensed.

A brief synopsis of the content, suitable for publication. Should be concise and journalistically styled. Distinct from ObjectName (internal reference) and Caption (detailed description). Maps to photoshop:Headline in XMP. Limited to 256 characters, though shorter headlines are more effective.

Dataset
2:105
Data Type
Text
Max Length
256 characters
Standard
IPTC IIM 4.2

Credit

IIM 2:110 IPTC

The organization or person to credit when publishing—"Reuters," "Getty Images," or "Jane Smith Photography." This is often the agency or company name, separate from the individual photographer.

Why you'd care: If you work through an agency, this should show the agency name. Combined with Byline, it creates credits like "AP Photo/John Doe."

Identifies who should be credited when the image is published. Typically contains the content provider (agency, archive, or organization) rather than the individual creator. When both exist, publications often format as "Credit/Byline." Maps to photoshop:Credit in XMP.

Dataset
2:110
Data Type
Text
Max Length
32 characters
Standard
IPTC IIM 4.2

Source

IIM 2:115 IPTC

Where the image originally came from—the original owner or supplier. For a wire photo, this might be "AFP" even if you got it from Getty. It's the chain of custody for images.

Why you'd care: Helps track image provenance, especially for archived or redistributed images. Useful for verifying authenticity.

Identifies the original owner or creator of the intellectual content. Distinguished from Credit (who to attribute when publishing) and Copyright (legal rights holder). Represents the earliest known source in the distribution chain. Maps to photoshop:Source in XMP.

Dataset
2:115
Data Type
Text
Max Length
32 characters
Standard
IPTC IIM 4.2

Caption-Abstract

IIM 2:120 IPTC

A detailed description of what's in the image—who, what, where, when, why. This is the full story behind the photo, often used as the caption printed beneath it in publications.

Why you'd care: A well-written caption dramatically increases stock photo sales and helps with accessibility. Search engines and screen readers use this to understand your image.

Textual description of the content, providing the who/what/where/when/why for news photos or detailed descriptions for other imagery. Can be used as photo caption for publication. Should be written in complete sentences. Maps to dc:description in XMP. No practical length limit, though 2000 characters is typical maximum.

Dataset
2:120
Data Type
Text
Max Length
2000 characters
Standard
IPTC IIM 4.2, XMP dc:description

Writer-Editor

IIM 2:122 IPTC

Who wrote the caption—not the photographer, but the person who penned the description. In news organizations, this is often a different person than the one who took the photo.

Why you'd care: Accountability. If there's ever a question about caption accuracy, this identifies who was responsible for the description.

Identifies the person who wrote, edited, or corrected the Caption-Abstract field. Provides accountability for caption content separate from the image creator. Repeatable for multiple contributors. Maps to photoshop:CaptionWriter in XMP.

Dataset
2:122
Data Type
Text
Max Length
32 characters each
Repeatable
Yes
Standard
IPTC IIM 4.2

ReleaseDate

IIM 2:30 IPTC

The earliest date when this image can be published—an embargo date. If set to next Monday, editors know they can't use the photo until then.

Why you'd care: Used for planned announcements, product launches, or events where timing matters. Prevents accidental early publication.

Designates the earliest date the provider intends the object to be used. Often used for embargo enforcement in news workflows. Format matches DateCreated (CCYYMMDD). Should be paired with ReleaseTime for precise embargo management.

Dataset
2:30
Data Type
Digits
Format
CCYYMMDD
Standard
IPTC IIM 4.2

ReleaseTime

IIM 2:35 IPTC

The exact time when the embargo lifts—paired with ReleaseDate for precise control. "9:00 AM EST on Monday" is clearer than just "Monday."

Why you'd care: For time-sensitive releases where hour-level precision matters. Commonly used for earnings announcements or political news.

Time component of earliest intended use date. Includes timezone offset for unambiguous international coordination. Combined with ReleaseDate provides complete embargo timestamp. Format: HHMMSS±HHMM.

Dataset
2:35
Data Type
Digits
Format
HHMMSS±HHMM
Standard
IPTC IIM 4.2

ExpirationDate

IIM 2:37 IPTC

The date after which this image shouldn't be used anymore—a "kill date." Common for time-limited campaigns, seasonal content, or licensed images with usage windows.

Why you'd care: Prevents outdated or rights-expired images from being accidentally republished. Essential for managing licensed content libraries.

Designates the latest date the provider intends the object to be used. After this date, the object should be removed from active use. Commonly used for time-limited rights or content that becomes stale. Format: CCYYMMDD.

Dataset
2:37
Data Type
Digits
Format
CCYYMMDD
Standard
IPTC IIM 4.2

ExpirationTime

IIM 2:38 IPTC

The exact time when usage rights end—paired with ExpirationDate. "Midnight GMT on December 31st" for precise rights management.

Why you'd care: For contracts with specific time-based expiration. Less commonly used than ExpirationDate alone, but available when precision is needed.

Time component of latest intended use date. Provides hour/minute precision when date-level granularity is insufficient. Combined with ExpirationDate for complete expiration timestamp.

Dataset
2:38
Data Type
Digits
Format
HHMMSS±HHMM
Standard
IPTC IIM 4.2

FixtureIdentifier

IIM 2:22 IPTC

An identifier for recurring features or series—like "Daily Weather Map" or "Weekly Fashion" or "Olympics-2024." Groups related images that appear regularly.

Why you'd care: Mainly used by news services for standing features. Helps editors find images for regular sections or ongoing coverage.

Identifies editorial content that recurs regularly. Used by wire services to route content to appropriate destinations automatically based on standing requests. Limited to 32 alphanumeric characters.

Dataset
2:22
Data Type
Text
Max Length
32 characters
Standard
IPTC IIM 4.2

EditStatus

IIM 2:07 IPTC

Workflow status indicator—"Draft," "Approved," "Final," or "Published." Tracks where an image is in the editorial pipeline.

Why you'd care: Useful in team environments to know if an image is ready to use or still needs review. Prevents premature publication.

Status of the object within the editorial workflow. Provider-defined values indicate review/approval state. Not standardized across organizations—each outlet may define their own status values. Maximum 64 characters.

Dataset
2:07
Data Type
Text
Max Length
64 characters
Standard
IPTC IIM 4.2

ObjectCycle

IIM 2:75 IPTC

Which edition the image is intended for—morning (a), afternoon (p), or both (b). A holdover from when newspapers had multiple daily editions.

Why you'd care: Mostly historical. Today's 24/7 news cycle makes this less relevant, but you might see it in archived images from print-era workflows.

Single-character code indicating intended publication cycle: 'a' (morning), 'p' (afternoon/evening), 'b' (both). Legacy field from print newspaper workflows with multiple daily editions. Largely obsolete in digital publishing.

Dataset
2:75
Data Type
Alpha
Values
a, p, b
Standard
IPTC IIM 4.2 (legacy)

SubjectReference

IIM 2:12 IPTC

A standardized code classifying what the image is about—using the IPTC Subject NewsCodes taxonomy. More precise than free-form keywords because everyone uses the same codes.

Why you'd care: News organizations and wire services rely on these codes to route content automatically. Learning the system helps if you work in photojournalism.

Structured reference to IPTC Subject NewsCodes, a standardized taxonomy of 1,400+ subject matter concepts. Format: IPR:SubjectCode:SubjectName:SubjectMatter:SubjectDetail. Enables automated routing and precise categorization across news systems. Replaces deprecated Category field.

Dataset
2:12
Data Type
Text (structured)
Format
IPR:XXXXXXXX:Name:Matter:Detail
Repeatable
Yes
Standard
IPTC IIM 4.2, IPTC NewsCodes

DigitalCreationDate

IIM 2:62 IPTC

When the digital file was created—as opposed to when the intellectual content was created. For a scan of a 1960s photo, DateCreated is 1960s but DigitalCreationDate is when you scanned it.

Why you'd care: Helps distinguish original photography dates from digitization dates. Important for archives, historical images, and scanned film.

Date when the digital representation was created. For born-digital content, matches DateCreated. For digitized content, indicates scan/digitization date. Enables tracking of both intellectual creation and digital asset creation timelines. Format: CCYYMMDD.

Dataset
2:62
Data Type
Digits
Format
CCYYMMDD
Standard
IPTC IIM 4.2

DigitalCreationTime

IIM 2:63 IPTC

The time of day when the digital file was created—paired with DigitalCreationDate. Less commonly used than the date alone.

Why you'd care: Provides complete digitization timestamp when batch processing archival materials and you need to track exactly when each scan occurred.

Time component corresponding to DigitalCreationDate. Combined provides complete ISO 8601-compatible timestamp for digital asset creation. Format includes optional timezone offset.

Dataset
2:63
Data Type
Digits
Format
HHMMSS±HHMM
Standard
IPTC IIM 4.2

OriginatingProgram

IIM 2:65 IPTC

The software that created or last modified the IPTC data—"Adobe Photoshop," "Photo Mechanic," or "Lightroom." Shows which program was used to manage the metadata.

Why you'd care: Helpful for troubleshooting when metadata looks wrong. Knowing the originating software can explain formatting quirks or missing fields.

Identifies the software that created or last modified the IPTC metadata. Not the camera software—that's in EXIF Software tag. Records the application used for metadata entry/editing. Typically combined with ProgramVersion.

Dataset
2:65
Data Type
Text
Max Length
32 characters
Standard
IPTC IIM 4.2

ProgramVersion

IIM 2:70 IPTC

Version number of the software identified in OriginatingProgram—"25.0" or "2024.1" or "6.0." Helps pinpoint exactly which software release created the metadata.

Why you'd care: Useful for diagnosing metadata issues. A known bug in a specific software version might explain corrupted fields.

Version number corresponding to OriginatingProgram. Format varies by vendor—may be numeric, semantic versioning, or build number. Together with OriginatingProgram, provides complete software identification.

Dataset
2:70
Data Type
Text
Max Length
10 characters
Standard
IPTC IIM 4.2

ImageType

IIM 2:130 IPTC

Describes the color/component characteristics—black & white, color, CMYK, etc. A two-character code indicating what kind of image data is present.

Why you'd care: Legacy field from wire services. Today's software can detect color characteristics automatically, but you might see this in archived images.

Two-character code describing image components. First character indicates number of components (0-4), second indicates color type (W=monochrome, Y=yellow component, M=magenta, C=cyan, K=black, R=red, G=green, B=blue). Legacy field from wire transmission era.

Dataset
2:130
Data Type
Text (coded)
Length
2 characters
Standard
IPTC IIM 4.2 (legacy)

ImageOrientation

IIM 2:131 IPTC

Whether the image is landscape (horizontal), portrait (vertical), or square. A single letter code: L, P, or S.

Why you'd care: Helps in searches when you need a specific shape. "I need a vertical photo for this magazine cover."

Single-character code indicating aspect ratio: P (portrait/vertical), L (landscape/horizontal), S (square). Determined by comparing pixel dimensions. Note: This is different from EXIF Orientation (rotation)—this is purely about aspect ratio.

Dataset
2:131
Data Type
Alpha
Values
P, L, S
Standard
IPTC IIM 4.2

LanguageIdentifier

IIM 2:135 IPTC

The language used in textual metadata—"en" for English, "de" for German, "ja" for Japanese. Tells readers what language the caption and other text fields are written in.

Why you'd care: Important for international distribution. Helps systems route images to appropriate language desks or audiences.

ISO 639:1988 two or three-letter language code indicating the language of textual metadata (caption, headline, keywords). Enables language-aware search and routing in multilingual systems. Format: 2-3 character ISO 639 code.

Dataset
2:135
Data Type
Alpha
Length
2-3 characters
Standard
IPTC IIM 4.2, ISO 639

Contact

IPTC Extension IPTC

How to reach the creator or rights holder—may include email, phone, website, or mailing address. Embedded right in the photo so potential buyers can find you.

Why you'd care: Makes it easy for people who want to license your work to contact you. Essential for freelance photographers looking for business.

Structured contact information for the creator(s) or maintainer(s). In IPTC Core/Extension, this is a complex type with multiple fields: Address, City, State/Province, Postal Code, Country, Phone(s), Email(s), Website(s). Maps to Iptc4xmpCore:CreatorContactInfo in XMP.

Standard
IPTC Photo Metadata Standard
XMP Mapping
Iptc4xmpCore:CreatorContactInfo
Structure
Bag of ContactInfo
Fields
Address, City, Region, PostalCode, Country, Phone, Email, Website

ContentLocationCode

IIM 2:26 IPTC

ISO country code indicating where the content was created. Similar to Country-PrimaryLocationCode but can be repeated for images showing multiple countries.

Why you'd care: For photos taken at borders or depicting multiple countries. Most users will only need Country-PrimaryLocationCode.

ISO 3166-1 country code(s) indicating location(s) depicted in or relevant to the content. Repeatable field—unlike Country-PrimaryLocationCode which is singular. Enables tagging content relevant to multiple geographic locations.

Dataset
2:26
Data Type
Alpha
Length
3 characters (ISO 3166-1 alpha-3)
Repeatable
Yes
Standard
IPTC IIM 4.2, ISO 3166-1

ContentLocationName

IIM 2:27 IPTC

Full name of location(s) depicted in the image, paired with ContentLocationCode. Human-readable complement to the country code.

Why you'd care: Rarely needed—most photographers use the standard City/State/Country fields instead.

Full text name corresponding to ContentLocationCode. Repeatable field allowing multiple location names. Each ContentLocationName should correspond positionally to a ContentLocationCode entry. Maximum 64 characters per entry.

Dataset
2:27
Data Type
Text
Max Length
64 characters each
Repeatable
Yes
Standard
IPTC IIM 4.2

IntellectualGenre

IPTC Core IPTC

The editorial nature of the content—"Current," "Analysis," "Feature," "Profile," or "Opinion." Tells editors what kind of story this image supports.

Why you'd care: Helps news organizations route images appropriately. A profile photo goes to different editors than breaking news.

Describes the intellectual or editorial character of the content using IPTC Genre NewsCodes. Examples: "Current," "Analysis," "Archive," "Background," "Feature," "Obituary," "Opinion." Distinct from subject matter (what it's about) vs. editorial treatment (how it's presented).

Standard
IPTC Photo Metadata Standard
XMP Mapping
Iptc4xmpCore:IntellectualGenre
Data Type
Text
Vocabulary
IPTC Genre NewsCodes

Scene

IPTC Core IPTC

What type of scene is depicted using IPTC Scene codes—"headshot," "general view," "action," "performing," "press conference," etc. Describes how the subject is shown.

Why you'd care: Helps photo buyers find specific compositions. Someone needing a "headshot" can filter out action shots and landscapes.

Describes what type of visual scene is depicted using IPTC Scene NewsCodes. Six-digit codes covering scene types: aerial, close-up, couple, exterior, full length, group, half length, headshot, interior, night scene, off-beat, panoramic, performing, portrait, etc. Repeatable field.

Standard
IPTC Photo Metadata Standard
XMP Mapping
Iptc4xmpCore:Scene
Data Type
Text (6-digit codes)
Vocabulary
IPTC Scene NewsCodes
Repeatable
Yes

PersonInImage

IPTC Extension IPTC

Names of people visible in the photo—separate from the photographer (Byline). "Barack Obama," "Taylor Swift," or "John Smith, CEO."

Why you'd care: Makes people searchable. Essential for news photos, event photography, and stock images featuring identifiable individuals.
Privacy: Contains names of depicted individuals. May require consent depending on jurisdiction and usage context.

Names of persons depicted in the image. Distinct from Byline (creator) and CaptionWriter (metadata author). Repeatable field for multiple subjects. In IPTC Extension, can be enhanced with PersonInImageWithDetails providing identifier, name, and optional description per person.

Standard
IPTC Photo Metadata Extension
XMP Mapping
Iptc4xmpExt:PersonInImage
Data Type
Text
Repeatable
Yes (bag of names)

Event

IPTC Extension IPTC

The event where the photo was taken—"Super Bowl LVIII," "Oscars 2024," "G20 Summit," or "Smith-Jones Wedding." Names the specific occasion or happening.

Why you'd care: Groups all photos from the same event together. Makes finding event-specific images much easier than searching by date alone.

Identifies the event at which the photo was taken. Free-text field describing the specific occasion. More granular than Keywords—captures the particular event rather than general topic. Maps to Iptc4xmpExt:Event in XMP.

Standard
IPTC Photo Metadata Extension
XMP Mapping
Iptc4xmpExt:Event
Data Type
Text (langAlt)
Localizable
Yes (language alternatives)

ModelAge

Plus:ModelAge IPTC/PLUS

Age of the model(s) at the time the photo was taken. Important for legal compliance and appropriate usage—especially for distinguishing minors from adults.

Why you'd care: Stock agencies often require this for images with recognizable people. Helps buyers ensure appropriate use and legal compliance.

Age(s) of human model(s) in years at time of capture. Part of PLUS (Picture Licensing Universal System) schema adopted by IPTC. Repeatable for multiple models. Essential for legal compliance in jurisdictions with age-specific restrictions. Integer values only.

Standard
PLUS Coalition / IPTC Extension
XMP Mapping
plus:ModelAge
Data Type
Integer
Repeatable
Yes (bag of integers)

ModelReleaseStatus

Plus:ModelReleaseStatus IPTC/PLUS

Whether you have legal permission from people in the photo to use their likeness commercially. "Unlimited Model Release," "Limited Release," "No Release," or "Not Applicable."

Why you'd care: Determines how the photo can be used. Without a release, commercial use of recognizable people is legally risky. Stock agencies require this information.

Indicates model release status using PLUS controlled vocabulary: MR-NON (No release), MR-NAP (Not applicable—no people), MR-UMR (Unlimited model release), MR-LMR (Limited/restricted). Essential for licensing workflow compliance.

Standard
PLUS Coalition / IPTC Extension
XMP Mapping
plus:ModelReleaseStatus
Data Type
Closed Choice
Values
MR-NON, MR-NAP, MR-UMR, MR-LMR

PropertyReleaseStatus

Plus:PropertyReleaseStatus IPTC/PLUS

Whether you have permission to use recognizable property—buildings, artwork, branded items, pets—commercially. Similar to model releases but for things instead of people.

Why you'd care: Some properties (like the Eiffel Tower at night, or Disney buildings) have usage restrictions. This field documents whether you have clearance.

Indicates property release status using PLUS controlled vocabulary: PR-NON (No release), PR-NAP (Not applicable—no recognizable property), PR-UPR (Unlimited property release), PR-LPR (Limited/restricted). Covers buildings, artwork, trademarks, pets, and other distinctive property.

Standard
PLUS Coalition / IPTC Extension
XMP Mapping
plus:PropertyReleaseStatus
Data Type
Closed Choice
Values
PR-NON, PR-NAP, PR-UPR, PR-LPR

RegistryID

IPTC Extension IPTC

A unique identifier issued by an image registry service—like a social security number for photos. Used to track and verify image authenticity across the internet.

Why you'd care: Helps protect against unauthorized use by linking your photo to a permanent registry. Services like ISCC or ContentAuthenticity use this approach.

Structured identifier from an image registry, containing both the registry organization identifier and the item ID issued by that registry. Enables persistent identification across systems and over time. Supports multiple registry entries per image.

Standard
IPTC Photo Metadata Extension
XMP Mapping
Iptc4xmpExt:RegistryId
Structure
RegOrgId (URI) + RegItemId (text)
Repeatable
Yes

UsageTerms

XMP Rights IPTC

Human-readable licensing terms—how the image can be used. "Creative Commons Attribution 4.0," "Editorial Use Only," or "Contact owner for licensing."

Why you'd care: Tells users what they can and can't do with your photo. Clear usage terms prevent misunderstandings and protect your rights.

Free-form text describing licensing and usage terms in human-readable language. More detailed than CopyrightNotice—can include full license names, restrictions, or instructions. Maps to xmpRights:UsageTerms in XMP. Localizable via langAlt for multiple languages.

Standard
IPTC Photo Metadata Standard
XMP Mapping
xmpRights:UsageTerms
Data Type
Text (langAlt)
Localizable
Yes

WebStatement

XMP Rights IPTC

A URL linking to your full copyright or licensing statement online. Points to a webpage with complete terms, contact info, or licensing portal.

Why you'd care: When your full licensing terms don't fit in metadata fields, link to a webpage. Makes it easy for users to find complete information about using your work.

URL referencing a web page with copyright ownership and usage rights information. Should be a persistent URL. For Creative Commons licenses, typically points to the specific license deed (e.g., creativecommons.org/licenses/by/4.0/).

Standard
IPTC Photo Metadata Standard
XMP Mapping
xmpRights:WebStatement
Data Type
URL

XMP Extended 55 terms

Adobe's Extensible Metadata Platform—a flexible framework that can store ratings, labels, editing history, custom properties, and much more. The modern choice for complex metadata workflows.

dc:creator

Dublin Core XMP

Your name as the photographer or artist who made the image. This is the XMP equivalent of the EXIF Artist field.

Why you'd care: Establishes authorship and gets your name embedded in the file. When photos spread online, your creator credit stays with them.

Ordered array of entities primarily responsible for making the resource. In photo contexts, typically the photographer. From Dublin Core Metadata Element Set. Maps to IPTC Creator (Byline) for interoperability.

Namespace
http://purl.org/dc/elements/1.1/
Data Type
Ordered array of ProperName
Standard
Dublin Core, XMP 1.0
IPTC Sync
Creator (2:80 Byline)

dc:description

Dublin Core XMP

A detailed caption or description of what's in the photo. Tell the story behind the image—who, what, where, when, why.

Why you'd care: Search engines index this text, making your photos findable. Stock agencies use it to understand what your image depicts.

Language-alternative array for textual descriptions of the resource content. Supports multiple languages through the xml:lang attribute. Primary storage location for image captions in XMP-aware workflows.

Namespace
http://purl.org/dc/elements/1.1/
Data Type
Lang Alt (language alternative)
Standard
Dublin Core, XMP 1.0
IPTC Sync
Description (2:120 Caption-Abstract)

dc:title

Dublin Core XMP

A short, catchy title for your image—like naming a painting. Not the filename, but a proper title like "Golden Hour at Half Dome".

Why you'd care: Gives your photo an identity beyond "IMG_4523.jpg". Makes browsing large libraries easier and looks professional in portfolios.

Language-alternative array for the formal name given to the resource. Distinct from filename or technical identifiers. Supports localization for international distribution.

Namespace
http://purl.org/dc/elements/1.1/
Data Type
Lang Alt (language alternative)
Standard
Dublin Core, XMP 1.0
IPTC Sync
Title (2:05 ObjectName)

dc:subject

Dublin Core XMP

Keywords that describe your photo—basically tags. "sunset", "beach", "California", "silhouette". The more relevant tags, the more discoverable your image.

Why you'd care: Keywords are how people find your photos in stock agencies, search engines, and your own catalog. Good keywording = more visibility.

Unordered array of descriptive phrases about the resource's content. Primary XMP storage for keywords, synchronized with IPTC Keywords. No hierarchy—for hierarchical keywords, use lr:hierarchicalSubject.

Namespace
http://purl.org/dc/elements/1.1/
Data Type
Unordered array of Text
Standard
Dublin Core, XMP 1.0
IPTC Sync
Keywords (2:25)

dc:rights

Dublin Core XMP

Your copyright statement—like "© 2024 Jane Smith. All rights reserved." Establishes who owns the image and can license it.

Why you'd care: Without a copyright notice, people might assume your image is free to use. This puts your ownership claim right in the file.

Language-alternative array containing copyright and rights information. Should include copyright symbol, year, and rights holder. Synchronized with IPTC CopyrightNotice and EXIF Copyright.

Namespace
http://purl.org/dc/elements/1.1/
Data Type
Lang Alt (language alternative)
Standard
Dublin Core, XMP 1.0
IPTC Sync
CopyrightNotice (2:116)

dc:format

Dublin Core XMP

The file format—"image/jpeg", "image/png", "image/tiff". Tells software what kind of file this is, independent of the filename extension.

Why you'd care: Mostly automatic. Useful when files get renamed with wrong extensions—the MIME type reveals the true format.

MIME type of the resource following IANA media type conventions. Set automatically by applications. Helps identify resource format independent of file extension.

Namespace
http://purl.org/dc/elements/1.1/
Data Type
MIMEType
Standard
Dublin Core, XMP 1.0
Example
image/jpeg, image/tiff, application/pdf

dc:identifier

Dublin Core XMP

A unique ID for this image—could be your catalog number, a stock agency ID, or a DOI. Think of it like a book's ISBN, but for photos.

Why you'd care: If you sell images or manage a large archive, unique IDs help track licenses and prevent confusion between similar files.

Unambiguous reference to the resource within a given context. Can be a URI, ISBN, DOI, stock photo ID, or any formal identification system. Distinct from xmpMM:DocumentID which tracks file identity across edits.

Namespace
http://purl.org/dc/elements/1.1/
Data Type
Text
Standard
Dublin Core, XMP 1.0
Example
urn:isbn:978-0-123456-78-9, DOI:10.1234/photo.2024

dc:language

Dublin Core XMP

What language the text in your photo is—relevant for images with signs, documents, or text overlays. Uses codes like "en", "es", "ja".

Why you'd care: Helps stock agencies and search engines route your image to the right audience. A photo of Japanese text should be tagged "ja".

Language(s) of the intellectual content using RFC 3066 tags (based on ISO 639). For images, indicates language of visible text content. Uses BCP 47 language tags.

Namespace
http://purl.org/dc/elements/1.1/
Data Type
Unordered array of Locale
Standard
Dublin Core, BCP 47
Example
en-US, fr-CA, zh-Hans

dc:publisher

Dublin Core XMP

Who's responsible for making this image available—could be a stock agency, news wire, or your own business name.

Why you'd care: In editorial workflows, this tracks which organization distributed the image. Less relevant for personal photos.

Entity responsible for making the resource available. In photography, typically the distributing agency or organization rather than the creator. Distinct from dc:creator.

Namespace
http://purl.org/dc/elements/1.1/
Data Type
Unordered array of ProperName
Standard
Dublin Core, XMP 1.0

dc:source

Dublin Core XMP

Where this image originally came from—the original source if this is a derivative or digital copy. Could reference an archive, agency, or original work.

Why you'd care: Important for derivative works and reproductions. Tracks provenance when images are copied or modified from other sources.

Reference to a resource from which the present resource is derived. May use a formal identifier or URI. Supports provenance tracking for derivative works.

Namespace
http://purl.org/dc/elements/1.1/
Data Type
Text
Standard
Dublin Core, XMP 1.0
IPTC Sync
Source (2:115)

dc:type

Dublin Core XMP

What type of resource this is—"Image", "StillImage", "Collection". More about the nature of the file than its subject matter.

Why you'd care: Rarely used for photos specifically. More relevant when managing mixed media collections (photos, videos, audio, documents).

Nature or genre of the resource. Recommended to use DCMI Type Vocabulary terms: Collection, Dataset, Event, Image, InteractiveResource, MovingImage, PhysicalObject, Service, Software, Sound, StillImage, Text.

Namespace
http://purl.org/dc/elements/1.1/
Data Type
Unordered array of open Choice
Standard
Dublin Core, DCMI Type Vocabulary
Example
StillImage, Image

xmp:CreateDate

XMP Core XMP

When the image was originally created—the moment you pressed the shutter. This is the XMP version of EXIF's DateTimeOriginal.

Why you'd care: This date organizes your photos chronologically. It's when the photo was *taken*, not when you edited or exported it.

Date and time the resource was created. For photographs, should match EXIF DateTimeOriginal. Stored in ISO 8601 format with optional timezone. Preserved across format conversions.

Namespace
http://ns.adobe.com/xap/1.0/
Data Type
Date (ISO 8601)
Standard
XMP 1.0
EXIF Sync
DateTimeOriginal (0x9003)

xmp:ModifyDate

XMP Core XMP

When the file was last changed—whether that's pixel editing, metadata updates, or re-exporting. Updates automatically when you save changes.

Why you'd care: Helps track when files were last touched. Useful for finding recently edited images or troubleshooting sync issues.

Date and time the resource was last modified. Updated by applications when file content changes (pixel or metadata). Corresponds to file system modification time in many contexts.

Namespace
http://ns.adobe.com/xap/1.0/
Data Type
Date (ISO 8601)
Standard
XMP 1.0
EXIF Sync
DateTime (0x0132)

xmp:MetadataDate

XMP Core XMP

When the metadata itself was last changed—even if the image pixels weren't touched. Adding keywords? Updating copyright? This timestamp changes.

Why you'd care: Useful for syncing metadata between systems. You can tell if someone added keywords to a file without modifying the actual image.

Date and time any metadata for this resource was last changed. Different from xmp:ModifyDate which tracks resource content changes. Enables efficient metadata synchronization workflows.

Namespace
http://ns.adobe.com/xap/1.0/
Data Type
Date (ISO 8601)
Standard
XMP 1.0

xmp:CreatorTool

XMP Core XMP

What software created this file—"Adobe Photoshop 2024", "Lightroom Classic 13.0", "iPhone 15 Pro". Can be a camera, scanner, or editing software.

Why you'd care: Helps troubleshoot issues by revealing what tools touched the file. Also interesting for forensics or curiosity about someone's workflow.

Name of the first application used to create the resource. For scans, may be the scanner software. For photos, may be the camera model or capture software. Preserved through edits—use xmpMM:History for complete processing chain.

Namespace
http://ns.adobe.com/xap/1.0/
Data Type
AgentName
Standard
XMP 1.0
EXIF Related
Software (0x0131)

xmp:Rating

XMP Core XMP

Your star rating—1 to 5 stars, just like in Lightroom or Photos. Rate your best shots 5 stars to find them easily later.

Why you'd care: The fastest way to sort keepers from rejects. Rating survives exports, so your 5-star picks stay marked even after processing.

User-assigned rating indicating relative quality or importance. Uses integer scale where -1 = rejected, 0 = unrated, 1-5 = star rating. Universally supported by asset management software.

Namespace
http://ns.adobe.com/xap/1.0/
Data Type
Closed Choice of Integer
Range
-1 (rejected) to 5 (★★★★★)
Standard
XMP 1.0

xmp:Label

XMP Core XMP

A color label—Red, Yellow, Green, Blue, Purple. Like colored stickers for your photos. Use them however you want: Red = needs editing, Green = ready to share.

Why you'd care: Another way to organize beyond star ratings. Great for workflow stages like "needs retouching" or "client approved".

Free-form text label for user-defined classification. Typically mapped to colors in applications (Red, Yellow, Green, Blue, Purple) but stored as text. Meaning is user-defined—no standard semantics.

Namespace
http://ns.adobe.com/xap/1.0/
Data Type
Text
Standard
XMP 1.0
Common Values
Red, Yellow, Green, Blue, Purple

xmpRights:Marked

XMP Rights XMP

A simple yes/no flag indicating whether this image is copyrighted. True = copyrighted, False = public domain. Separate from the actual copyright text.

Why you'd care: Makes it clear to anyone viewing metadata that your photo is protected. Some systems use this to trigger copyright warnings.

Boolean indicating whether this is a rights-managed resource. True = copyrighted, False = public domain, absent = unknown. Distinct from copyright notice text—this is a machine-readable rights status flag.

Namespace
http://ns.adobe.com/xap/1.0/rights/
Data Type
Boolean
Standard
XMP 1.0
Values
True (copyrighted), False (public domain)

xmpRights:Owner

XMP Rights XMP

Who owns the copyright—could be you, your employer, or a client who bought all rights. Not necessarily the photographer.

Why you'd care: If you do work-for-hire, the copyright owner is your client, not you. This field makes the legal owner explicit.

Unordered array of legal owners of the resource. May differ from dc:creator (photographer) in work-for-hire situations. Used for rights management and licensing queries.

Namespace
http://ns.adobe.com/xap/1.0/rights/
Data Type
Unordered array of ProperName
Standard
XMP 1.0

xmpRights:UsageTerms

XMP Rights XMP

Plain-language description of how this image can be used. "Editorial use only", "Licensed to Acme Corp through 2025", "CC BY 4.0 Attribution Required".

Why you'd care: Tells anyone who finds your image exactly what they can and can't do with it. Embeds your licensing terms right in the file.

Language-alternative text describing usage rights and restrictions. Human-readable complement to machine-readable license URLs. Supports localization for international distribution.

Namespace
http://ns.adobe.com/xap/1.0/rights/
Data Type
Lang Alt (language alternative)
Standard
XMP 1.0, IPTC Photo Metadata
IPTC Sync
Rights Usage Terms

xmpRights:WebStatement

XMP Rights XMP

A URL pointing to your full copyright or licensing page online. Links to where people can find complete terms, contact info, or buy a license.

Why you'd care: When usage terms are too long to embed, link to a webpage instead. Especially useful for Creative Commons licenses—link directly to the CC deed.

URL referencing a web page with comprehensive rights and licensing information. Should be a persistent URL. For Creative Commons, typically points to the license deed (e.g., creativecommons.org/licenses/by/4.0/).

Namespace
http://ns.adobe.com/xap/1.0/rights/
Data Type
URL
Standard
XMP 1.0, IPTC Photo Metadata
IPTC Sync
Web Statement of Rights

xmpRights:Certificate

XMP Rights XMP

A URL to a certificate proving your copyright registration or other legal documentation. Links to official registration records.

Why you'd care: If you've registered your copyright (which provides legal benefits in the US), this links to the proof. Strengthens your legal position.

URL pointing to a web-accessible certificate documenting rights ownership. Typically links to copyright registration services or blockchain-based provenance records.

Namespace
http://ns.adobe.com/xap/1.0/rights/
Data Type
URL
Standard
XMP 1.0

xmpMM:DocumentID

XMP MM XMP

A unique fingerprint for this image that stays the same even when you make copies or edits. Like a social security number for your file.

Why you'd care: Helps software track that all your edited versions came from the same original. Useful for asset management and avoiding duplicates.

Universally unique identifier for the document. Assigned when the resource is first created and preserved through modifications. Enables tracking of document lineage across edits and format conversions. Uses UUID URN format.

Namespace
http://ns.adobe.com/xap/1.0/mm/
Data Type
URI (UUID URN)
Standard
XMP 1.0
Format
xmp.did:UUID or uuid:UUID

xmpMM:InstanceID

XMP MM XMP

Changes every time you save the file—each save creates a new "instance". While DocumentID stays constant, InstanceID tracks each version.

Why you'd care: Helps identify exactly which version of a file you're looking at. Two files can have the same DocumentID but different InstanceIDs if one was edited.

Identifier that changes with each save operation. Combined with DocumentID, enables tracking specific versions of a resource. Should be updated whenever the file is modified and saved to new state.

Namespace
http://ns.adobe.com/xap/1.0/mm/
Data Type
URI (UUID URN)
Standard
XMP 1.0
Behavior
New UUID on each save

xmpMM:OriginalDocumentID

XMP MM XMP

Points back to the very first file this came from—your original RAW file, even if you've converted to JPEG, then TIFF, then back to JPEG.

Why you'd care: No matter how many times you convert or re-save, this traces back to the original capture. Helps prove authenticity and find source files.

DocumentID of the original resource from which this one was derived. Set when SaveAs creates a new document from an existing one. Enables tracing complete derivation chain back to original capture.

Namespace
http://ns.adobe.com/xap/1.0/mm/
Data Type
URI (UUID URN)
Standard
XMP 1.0
Set When
Save As / Export operation

xmpMM:History

XMP MM XMP

A log of everything that's been done to this file—created, opened, saved, exported. Like a timeline showing the image's journey from camera to final version.

Why you'd care: Reveals the editing history. You can see what software touched the file and when. Useful for forensics or understanding a file's provenance.

Ordered array of ResourceEvent structures documenting high-level actions performed on the resource. Each event records action type, timestamp, software agent, and optional parameters. Comprehensive audit trail for asset management.

Namespace
http://ns.adobe.com/xap/1.0/mm/
Data Type
Ordered array of ResourceEvent
Standard
XMP 1.0
Actions
created, saved, converted, copied, derived

xmpMM:DerivedFrom

XMP MM XMP

References the immediate parent file this one came from. If you exported a JPEG from a PSD, this points to that PSD file.

Why you'd care: Helps track the chain from edited file back to source. Useful when you have multiple versions and need to find the parent file.

ResourceRef structure pointing to the immediate source from which this resource was derived. Contains DocumentID and InstanceID of the parent resource. Enables single-hop provenance tracking.

Namespace
http://ns.adobe.com/xap/1.0/mm/
Data Type
ResourceRef
Standard
XMP 1.0
Contains
documentID, instanceID, fromPart, toPart

xmpMM:Ingredients

XMP MM XMP

Lists all the files that went into making this composite image—like a recipe's ingredient list. References each source photo, texture, or element used.

Why you'd care: Essential for composites. If you combined 10 photos, this tracks all 10 sources. Useful for licensing compliance and recreating your work.

Unordered array of ResourceRef structures listing all resources that contributed to this composite. Each entry identifies a source document and optionally which parts were used. Critical for tracking multi-source derivations.

Namespace
http://ns.adobe.com/xap/1.0/mm/
Data Type
Unordered array of ResourceRef
Standard
XMP 1.0
Use Case
Composite images, collages, layered documents

photoshop:ColorMode

Photoshop XMP

How colors are stored—RGB (for screens), CMYK (for print), Grayscale (black and white), or LAB (device-independent). Most photos are RGB.

Why you'd care: Critical for print. A CMYK file is ready for press, while RGB is for web/screen. Wrong mode = color shifts in final output.

Color model of the document matching Photoshop's internal modes. Integer enumeration: 0=Bitmap, 1=Grayscale, 2=Indexed, 3=RGB, 4=CMYK, 7=Multichannel, 8=Duotone, 9=LAB.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Closed Choice of Integer
Standard
Adobe Photoshop XMP
Values
0-9 (see Photoshop documentation)

photoshop:ICCProfile

Photoshop XMP

The color profile name—"sRGB", "Adobe RGB", "ProPhoto RGB", "Display P3". Defines exactly which colors the RGB numbers represent.

Why you'd care: Same RGB values look different in different color spaces. sRGB is safest for web, Adobe RGB captures more colors for print.

Name of the ICC color profile embedded in or associated with the document. Should match the actual embedded profile. Used by color management systems to interpret color values correctly.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Text
Standard
Adobe Photoshop XMP
Common Values
sRGB IEC61966-2.1, Adobe RGB (1998), ProPhoto RGB

photoshop:DateCreated

Photoshop XMP

The date the intellectual content was created—typically when the photo was taken. Similar to EXIF DateTimeOriginal but in IPTC/Photoshop format.

Why you'd care: This is the date that shows up in many photo management applications. Important for proper chronological organization.

Date the intellectual content was created. Maps to IPTC DateCreated. Distinct from file creation date. Should be synchronized with EXIF DateTimeOriginal for photographs.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Date
Standard
Adobe Photoshop XMP
IPTC Sync
DateCreated (2:55)

photoshop:Headline

Photoshop XMP

A short, attention-grabbing summary of the image—like a newspaper headline. More descriptive than a title, shorter than a caption.

Why you'd care: News agencies display headlines prominently. A compelling headline helps your image get selected and published.

Brief synopsis of the image content. XMP mapping for IPTC Headline (2:105). Intended for quick identification—should be more descriptive than title but briefer than caption.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Text
Standard
Adobe Photoshop XMP
IPTC Sync
Headline (2:105)

photoshop:Credit

Photoshop XMP

The credit line to display when the image is published—"Photo: Jane Smith / Getty Images". Combines photographer and provider information.

Why you'd care: This is the attribution that appears under published photos. Getting it right ensures proper credit for your work.

Credit line to be published with the image. May combine creator and provider names. XMP mapping for IPTC Credit (2:110). Designed for direct use in published photo credits.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Text
Standard
Adobe Photoshop XMP
IPTC Sync
Credit (2:110)

photoshop:City

Photoshop XMP

The city where the photo was taken—"Paris", "Tokyo", "New York". Human-readable location name, not GPS coordinates.

Why you'd care: Helps people find photos by location. Stock photo searches for "New York skyline" match this field.

City of image origin. XMP mapping for IPTC City (2:90). Part of the legacy IPTC location hierarchy (City, State, Country). For new metadata, consider IPTC Extension LocationShown.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Text
Standard
Adobe Photoshop XMP
IPTC Sync
City (2:90)

photoshop:State

Photoshop XMP

The state or province where the photo was taken—"California", "Ontario", "Bavaria". The middle level of the location hierarchy.

Why you'd care: Provides regional context. Combined with city and country, gives complete geographic placement.

Province/state of image origin. XMP mapping for IPTC Province-State (2:95). Part of legacy location hierarchy. Full name preferred over abbreviations.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Text
Standard
Adobe Photoshop XMP
IPTC Sync
Province-State (2:95)

photoshop:Country

Photoshop XMP

The country where the photo was taken—"United States", "Japan", "Germany". Full country name, not ISO codes.

Why you'd care: Top-level geographic categorization. Essential for editorial and stock photography workflows.

Full country name of image origin. XMP mapping for IPTC Country-PrimaryLocationName (2:101). Use full names per ISO 3166-1 rather than codes. Codes go in separate CountryCode field.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Text
Standard
Adobe Photoshop XMP
IPTC Sync
Country-PrimaryLocationName (2:101)

photoshop:TransmissionReference

Photoshop XMP

A job ID or reference number for tracking—"Assignment #12345", "Wedding-Johnson-2024". Your own coding system for organizing work.

Why you'd care: Connects photos to specific jobs or assignments. Invaluable for professional workflows and client billing.

Code representing original transmission reference. Originally for wire service identification, now commonly used as job/assignment identifier. Maps to IPTC OriginalTransmissionReference (2:103).

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Text
Standard
Adobe Photoshop XMP
IPTC Sync
OriginalTransmissionReference (2:103)

photoshop:Instructions

Photoshop XMP

Notes for editors or publishers—"Do not crop", "Embargo until Jan 1", "Editorial use only". Communicates special handling requirements.

Why you'd care: Ensures editors see critical usage restrictions before publishing. Prevents misuse of your images.

Any special instructions or editorial handling notes. Maps to IPTC SpecialInstructions (2:40). Used for embargoes, usage restrictions, or processing notes that must travel with the image.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Text
Standard
Adobe Photoshop XMP
IPTC Sync
SpecialInstructions (2:40)

photoshop:AuthorsPosition

Photoshop XMP

Your job title or role—"Staff Photographer", "Freelance", "Photo Editor". Describes your professional capacity when you made the image.

Why you'd care: Provides professional context. "Staff Photographer, New York Times" carries different weight than just a name.

Title or position of the creator. Maps to IPTC By-lineTitle (2:85). Provides professional context for the creator named in dc:creator/Byline.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Text
Standard
Adobe Photoshop XMP
IPTC Sync
By-lineTitle (2:85)

photoshop:CaptionWriter

Photoshop XMP

Who wrote the caption—might be you, a photo editor, or an agency staffer. Not necessarily the same person who took the photo.

Why you'd care: In newsrooms, photographers shoot and editors caption. This tracks who wrote the description for accountability.

Name of the person who wrote the caption/description. Maps to IPTC Writer-Editor (2:122). Distinct from image creator—used in workflows where captioning is separate from shooting.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Text
Standard
Adobe Photoshop XMP
IPTC Sync
Writer-Editor (2:122)

photoshop:Source

Photoshop XMP

Where this image came from—the original supplier. Could be "Getty Images", "Associated Press", or your own studio name.

Why you'd care: Identifies the original provider, separate from credit line. Important for licensing and sourcing verification.

Original owner or provider of the image. Maps to IPTC Source (2:115). In wire service context, identifies the original transmitting organization. Distinct from Credit which is for publication.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Text
Standard
Adobe Photoshop XMP
IPTC Sync
Source (2:115)

photoshop:Urgency

Photoshop XMP

How urgent this image is on a scale of 1-8, with 1 being most urgent. A legacy field from wire service days when breaking news needed priority handling.

Why you'd care: Mostly obsolete. Some news systems still use it, but xmp:Rating is now more common for importance ranking.

Editorial urgency rating. Maps to IPTC Urgency (2:10). Scale: 1 (most urgent) to 8 (least). Value 0 reserved, 9 means user-defined. Legacy field—consider xmp:Rating for modern workflows.

Namespace
http://ns.adobe.com/photoshop/1.0/
Data Type
Integer
Range
1 (high) to 8 (low)
IPTC Sync
Urgency (2:10)

lr:hierarchicalSubject

Lightroom XMP

Keywords organized in a tree structure—like "Animals|Mammals|Dogs|Golden Retriever". The pipe character shows the hierarchy from general to specific.

Why you'd care: Better organization than flat keywords. When you tag "Golden Retriever", the software knows it's also a Dog, Mammal, and Animal.

Adobe Lightroom's hierarchical keyword format using pipe (|) as delimiter. Each entry shows full path from root to leaf. Enables controlled vocabulary hierarchies. Synchronized to flat dc:subject for compatibility.

Namespace
http://ns.adobe.com/lightroom/1.0/
Data Type
Unordered array of Text
Standard
Adobe Lightroom XMP
Delimiter
| (pipe character)

crs:Version

Camera Raw XMP

Which version of Adobe Camera Raw or Lightroom's processing engine was used—like "15.0". Different versions can render the same settings slightly differently.

Why you'd care: If a photo looks different on another computer, version mismatch might be the cause. Newer versions add features but can change rendering.

Version of Camera Raw that last modified the settings. Critical for ensuring consistent rendering across systems. Format matches ACR version numbers.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Text
Standard
Adobe Camera Raw XMP
Example
15.0, 14.5

crs:ProcessVersion

Camera Raw XMP

The rendering engine generation—newer process versions have better highlight recovery, shadow detail, and color science. Updating can dramatically improve old photos.

Why you'd care: Old photos processed in Process Version 2010 can look much better if updated to 2012 or later. Major image quality improvements.

The demosaic and rendering engine version. Major revisions: 5.0 (2003), 5.7 (2010), 6.7 (2012), 11.0 (2018), 15.0 (2023). Each version changes how sliders affect the image. Upgrading recalculates all settings.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Text
Standard
Adobe Camera Raw XMP
Key Versions
5.0, 5.7, 6.7, 11.0, 15.0

crs:WhiteBalance

Camera Raw XMP

The white balance preset applied in RAW processing—"As Shot", "Daylight", "Cloudy", "Tungsten", or "Custom". Affects the overall color warmth.

Why you'd care: One of the biggest advantages of shooting RAW—you can change white balance after the fact. Fix yellow indoor shots or warm up cold outdoor ones.

White balance preset name. When set to "Custom", uses crs:Temperature and crs:Tint values. Other presets apply predefined temperature/tint combinations based on lighting conditions.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Closed Choice of Text
Standard
Adobe Camera Raw XMP
Presets
As Shot, Auto, Daylight, Cloudy, Shade, Tungsten, Fluorescent, Flash, Custom

crs:Temperature

Camera Raw XMP

Color temperature in Kelvin—lower numbers (3000K) look warm/orange, higher numbers (7000K) look cool/blue. 5500K is roughly daylight.

Why you'd care: The main slider for fixing color casts. Indoor photos too yellow? Lower the temperature. Overcast day too blue? Raise it.

White balance temperature in Kelvin. For RAW files, the actual adjustment value. For rendered files (JPEG/TIFF), relative adjustment from original. Range typically 2000-50000K depending on file type.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Unit
Kelvin
Typical Range
2000-50000

crs:Tint

Camera Raw XMP

Adjusts color between green and magenta—the other half of white balance. Negative values add green, positive adds magenta. Usually fine-tunes after setting temperature.

Why you'd care: Fixes fluorescent lighting's green cast or removes magenta color casts. Works together with Temperature for complete white balance control.

White balance tint adjustment along green-magenta axis. Complements Temperature which adjusts blue-yellow. Negative = more green, Positive = more magenta. Range typically -150 to +150.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
-150 to +150
Neutral
0

crs:Exposure2012

Camera Raw XMP

Overall brightness adjustment in stops—the main "make it brighter or darker" slider. +1.0 doubles the brightness, -1.0 halves it.

Why you'd care: The most impactful single slider. Underexposed photo? Bump it up. Blown highlights? Pull it down. RAW files have amazing latitude here.

Overall exposure adjustment in stops (EV). Uses 2012 process version algorithm targeting midtones primarily. Range -5.0 to +5.0 stops, though practical limits depend on file bit depth and noise.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Real
Range
-5.0 to +5.0
Unit
EV (stops)

crs:Contrast2012

Camera Raw XMP

Makes bright areas brighter and dark areas darker—increases the difference between light and shadow. Adds "punch" to flat images.

Why you'd care: Quick way to add drama. But be careful—too much crushes blacks and clips whites. Subtle adjustments usually work best.

S-curve contrast adjustment primarily affecting midtones. Uses 2012 algorithm which applies gentler adjustment than legacy versions. Operates independently from tone curve.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
-100 to +100
Default
0

crs:Highlights2012

Camera Raw XMP

Controls the brightest parts of your image. Negative values recover blown-out skies and windows. Positive values brighten highlights further.

Why you'd care: Essential for high-contrast scenes. Recovering highlight detail in a bright sky while keeping a darker foreground properly exposed is a game-changer.

Adjustment targeting highlight tones. Negative values recover clipped highlights from RAW data (if available). Uses Process Version 2012 algorithm with improved highlight reconstruction.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
-100 to +100
Default
0

crs:Shadows2012

Camera Raw XMP

Brightens or darkens the shadow areas without affecting highlights. Positive values reveal detail hiding in dark areas.

Why you'd care: Rescue underexposed shadows without washing out the whole image. Perfect for backlit subjects or opening up dark interiors.

Adjustment targeting shadow tones. Positive values lift shadows, potentially revealing noise. Uses Process Version 2012 algorithm with improved shadow separation. Works best with RAW files with good dynamic range.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
-100 to +100
Default
0

crs:Whites2012

Camera Raw XMP

Sets where your brightest white point is—how bright the very brightest pixels become. Positive values push whites brighter, negative pulls them back.

Why you'd care: Controls overall "brightness ceiling". Useful for ensuring pure whites in product photography or preventing highlight clipping in high-key images.

White point adjustment affecting the brightest tones. Sets the mapping of the whitest image values. Different from Highlights which affects a broader range. Typically adjusted with histogram clipping preview.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
-100 to +100
Default
0

crs:Blacks2012

Camera Raw XMP

Sets where your black point is—how dark the very darkest pixels become. Negative values crush blacks deeper, positive lifts them.

Why you'd care: Controls shadow "floor". Want rich, deep blacks for drama? Go negative. Need to see shadow detail? Go positive. Prevents muddy-looking images.

Black point adjustment affecting the darkest tones. Sets the mapping of the blackest image values. Negative values increase black clipping, positive values lift the black point (faded look).

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
-100 to +100
Default
0

crs:Clarity2012

Camera Raw XMP

Adds local contrast and edge definition—makes textures pop without affecting overall exposure. Positive values add punch, negative creates a soft/dreamy look.

Why you'd care: The "gritty landscape" slider. Great for architecture, texture, and dramatic skies. Use negative clarity for soft, flattering portraits.

Midtone local contrast adjustment using a modified unsharp mask algorithm. Affects medium-scale detail without changing overall luminance. Process 2012 version has improved halo control.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
-100 to +100
Default
0

crs:Texture

Camera Raw XMP

Enhances or smooths fine details like skin texture, fabric, or foliage. Positive brings out detail, negative smooths it away. More natural than clarity for many uses.

Why you'd care: The "skin smoother" slider when negative. Great for portraits. Positive values enhance pores and fine details in product/macro photography.

Medium-frequency detail enhancement using machine learning-based algorithm. Operates on smaller scale features than Clarity. Designed specifically to preserve skin texture while being adjustable. Added in 2019.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
-100 to +100
Default
0

crs:Dehaze

Camera Raw XMP

Cuts through haze, fog, and atmospheric murk to reveal hidden detail. Positive values remove haze, negative values add a misty, ethereal effect.

Why you'd care: Magic for hazy landscape shots. Can rescue photos taken on smoggy days. Negative values create dreamy, atmospheric effects intentionally.

Atmospheric haze removal based on dark channel prior algorithm. Estimates atmospheric light and transmission map to recover scene visibility. Can introduce color shifts and artifacts at extreme values.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
-100 to +100
Default
0

crs:Vibrance

Camera Raw XMP

Smart saturation boost—enhances muted colors while protecting already-saturated colors and skin tones. Less likely to make things look radioactive than regular saturation.

Why you'd care: The "safe" color boost slider. Makes blues bluer and greens greener without making skin orange. Go-to for landscapes with people.

Intelligent saturation adjustment that protects skin tones and already-saturated colors. Uses nonlinear response curve—more effect on desaturated colors, less on saturated ones. Prevents clipping in any channel.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
-100 to +100
Default
0

crs:Saturation

Camera Raw XMP

Raw color intensity boost—makes all colors more vivid. Goes from grayscale (-100) through natural (0) to extremely vivid (+100). No intelligence—affects everything equally.

Why you'd care: For dramatic effect or converting to black and white (-100). Most photographers prefer Vibrance for subtle color enhancement.

Linear saturation adjustment affecting all colors equally. At -100 produces complete desaturation. No protection for skin tones or already-saturated colors. Can cause color channel clipping.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
-100 to +100
Default
0

crs:ToneCurvePV2012

Camera Raw XMP

A graph controlling how input tones map to output tones. Pull up the curve to brighten, push down to darken. The classic film-era tool for precise tonal control.

Why you'd care: Ultimate control over contrast. Create an S-curve for punch, lifted blacks for vintage look, or precise adjustments the basic sliders can't achieve.

Point-curve tone mapping stored as coordinate pairs. Applied after Basic panel adjustments. Separate curves available for RGB composite and individual R, G, B channels. Uses Process Version 2012 coordinate system.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Ordered array of Integer pairs
Standard
Adobe Camera Raw XMP
Format
0, 0, 255, 255 (linear default)

crs:GrainAmount

Camera Raw XMP

Adds film-like grain texture to digital images. Higher values = more visible grain. Gives modern digital photos that analog film aesthetic.

Why you'd care: Makes digital look less sterile. Great for black and white photos or when you want a nostalgic, film-era look. Can also hide compression artifacts.

Synthetic film grain intensity. Uses procedural grain generation with Size and Roughness sub-parameters. Applied late in pipeline to avoid interaction with noise reduction. Value 0 = disabled.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Integer
Range
0 to 100
Default
0

crs:HasSettings

Camera Raw XMP

A simple yes/no flag showing whether this image has been processed in Camera Raw or Lightroom. "True" means settings have been applied.

Why you'd care: Helps identify which RAW files you've already worked on. Useful for sorting processed vs. unprocessed images in your catalog.

Boolean flag indicating whether Camera Raw settings have been applied to this resource. True = has develop settings, False = using defaults. Used by Bridge and other applications to filter developed vs. undeveloped files.

Namespace
http://ns.adobe.com/camera-raw-settings/1.0/
Data Type
Boolean
Standard
Adobe Camera Raw XMP
Values
True, False

aux:Lens

Auxiliary XMP

Alternative lens identification field—often more detailed than EXIF LensModel. May include information like focal length range and maximum aperture.

Why you'd care: Provides lens info even when EXIF fields are incomplete. Useful for identifying which lens took a shot when you own multiple similar lenses.

Adobe's auxiliary namespace field for lens identification. Often populated from MakerNotes data that doesn't map cleanly to EXIF LensModel. May contain normalized or enriched lens descriptions.

Namespace
http://ns.adobe.com/exif/1.0/aux/
Data Type
Text
Standard
Adobe XMP
Source
Often derived from MakerNotes

aux:SerialNumber

Auxiliary XMP

Your camera's serial number, as recorded by Adobe software. Like a fingerprint for your specific camera body.

Why you'd care: Can prove you owned the camera that took a photo. Also useful for insurance claims or tracking stolen equipment.

Camera body serial number from Adobe's auxiliary namespace. Often pulled from MakerNotes. May differ from EXIF BodySerialNumber field depending on how camera formats serial data.

Namespace
http://ns.adobe.com/exif/1.0/aux/
Data Type
Text
Standard
Adobe XMP
Privacy
Identifying
Privacy: Can uniquely identify your camera and potentially link all photos taken with it back to you. Consider removing before sharing publicly.

aux:LensSerialNumber

Auxiliary XMP

Your lens's serial number. Uniquely identifies the exact lens used—useful when you own multiple copies of the same lens model.

Why you'd care: If you have calibration issues or need to track which of your 70-200mm lenses took a particular shot. Also valuable for insurance documentation.

Lens serial number from Adobe's auxiliary namespace. Retrieved from lens-to-camera communication (for lenses that report serial) or MakerNotes. Not all lenses report serial numbers electronically.

Namespace
http://ns.adobe.com/exif/1.0/aux/
Data Type
Text
Standard
Adobe XMP
Availability
Depends on lens capabilities
Privacy: Identifies your specific lens and could be used to link photos across different contexts. Remove before sharing if privacy is a concern.

Camera & Lens 16 terms

Device identification fields including camera body details, lens specifications, serial numbers, and firmware versions. These fields can uniquely identify the exact equipment used.

Privacy Note: Serial numbers and owner names can uniquely identify your equipment and potentially link photos back to you personally. Consider removing these fields before sharing photos publicly.

LensModel

Tag 0xA434 EXIF

The name of the lens that took the photo—like "EF 24-70mm f/2.8L II USM" or "Sony FE 85mm f/1.4 GM". Shows exactly which lens you used.

Why you'd care: Perfect for tracking which lens gives you the best results. "All my sharpest portraits are with the 85mm f/1.4"—now you can verify that with data.

Contains the complete lens designation as a text string. Format varies by manufacturer—may include focal length range, maximum aperture, optical stabilization designation, and lens series codes. For adaptered lenses, may be missing or show adapter information instead.

Tag ID
0xA434 (42036)
Data Type
ASCII (2)
Count
Variable
Example
"EF24-70mm f/2.8L II USM"
Standard
EXIF 2.32

LensMake

Tag 0xA433 EXIF

The company that manufactured your lens—Canon, Sigma, Tamron, Sony, Zeiss, etc. May differ from your camera manufacturer if using third-party lenses.

Why you'd care: Tracks which lens brands you're using. Useful for analyzing whether your Canon camera does better with native Canon lenses or adapted Sigma glass.

Records the lens manufacturer as a text string. Should match the actual lens maker, not the camera body maker. Third-party lens manufacturers (Sigma, Tamron, Tokina) should report their own names. Older or manual lenses often leave this field empty.

Tag ID
0xA433 (42035)
Data Type
ASCII (2)
Count
Variable
Example
"SIGMA", "Canon", "TAMRON"
Standard
EXIF 2.32

LensSerialNumber

Tag 0xA435 EXIF

The unique serial number of your lens—the same number printed on the lens barrel. Uniquely identifies your specific lens among all lenses of that model ever made.

Why you'd care: Helps with insurance claims if equipment is stolen. But also links all your photos to a unique piece of equipment, which could be a privacy concern.
Privacy: Serial numbers can link photos to specific equipment owned by you. Remove before sharing publicly if anonymity matters.

Records the lens serial number as reported via the lens-camera communication protocol. Not all lens mounts transmit serial numbers electronically. Manual lenses and some older autofocus lenses lack electronic serial number reporting. Format varies by manufacturer.

Tag ID
0xA435 (42037)
Data Type
ASCII (2)
Count
Variable
Standard
EXIF 2.32

BodySerialNumber

Tag 0xA431 EXIF

Your camera's unique serial number—the same number on the sticker under the battery door. Uniquely identifies your specific camera among millions produced.

Why you'd care: Tracks which of your cameras took each shot (if you own multiple). Essential for insurance documentation. But can also be used to trace photos back to you.
Privacy: Camera serial numbers create a unique fingerprint linking all photos from that camera. Law enforcement and forensic analysts use this for identification. Remove before sharing if privacy matters.

Records the camera body's serial number as stored in firmware. Format varies by manufacturer—some use numeric only, others alphanumeric. This is the EXIF 2.3+ standardized tag; older cameras may store serial numbers only in proprietary MakerNotes.

Tag ID
0xA431 (42033)
Data Type
ASCII (2)
Count
Variable
Standard
EXIF 2.32
Some manufacturers also store serial numbers in manufacturer-specific MakerNotes tags, which may persist even after standard EXIF removal.

CameraOwnerName

Tag 0xA430 EXIF

The name you entered in your camera's settings as the owner. This text appears in every photo you take and identifies you as the equipment owner.

Why you'd care: Useful for proving ownership of images and recovering stolen cameras. But directly reveals your identity in every photo you share.
Privacy: Contains your actual name if configured. Remove before sharing photos if you want to remain anonymous.

User-configurable field set through camera menus. Intended for ownership identification but often used for photographer credits. Character encoding and maximum length vary by camera. Empty by default on most cameras—requires deliberate configuration.

Tag ID
0xA430 (42032)
Data Type
ASCII (2)
Count
Variable
Standard
EXIF 2.32

LensSpecification

Tag 0xA432 EXIF

Technical capabilities of your lens in four numbers: minimum and maximum focal lengths, and maximum apertures at those focal lengths. Tells you "what this lens can do."

Why you'd care: Shows your lens's complete range—like "24-70mm f/2.8" without needing the model name. Useful for understanding lens capabilities from metadata alone.

Four RATIONAL values describing lens optical characteristics: [MinFocalLength, MaxFocalLength, MinFNumberAtMinFL, MinFNumberAtMaxFL]. Prime lenses have identical min/max focal lengths. Constant-aperture zooms have identical f-numbers; variable-aperture zooms differ.

Tag ID
0xA432 (42034)
Data Type
RATIONAL (5)
Count
4
Format
[MinFL, MaxFL, MinF@MinFL, MinF@MaxFL]
Example
[24, 70, 2.8, 2.8] for 24-70mm f/2.8
Standard
EXIF 2.32

InternalSerialNumber

MakerNotes MakerNote

A hidden serial number stored in manufacturer-specific data that may survive even when you think you've removed EXIF data. Often different from the visible BodySerialNumber.

Why you'd care: Important privacy awareness—some cameras embed tracking data deep in proprietary sections that basic EXIF strippers don't remove.
Privacy: Many basic metadata removal tools miss this field. Use comprehensive tools that specifically strip MakerNotes if anonymity is critical.

Manufacturer-proprietary serial number field stored in MakerNotes. Tag location and encoding varies by brand—Canon, Nikon, Sony all use different structures. May contain production batch codes, factory calibration data, or modified serial formats. Not part of official EXIF spec.

Location
MakerNotes (varies by manufacturer)
Canon
Tag 0x00c
Nikon
Tag 0x001d
Sony
Various encrypted tags
Standard
Proprietary

MakerNote

Tag 0x927C EXIF

A catch-all container where camera manufacturers store their own proprietary data—everything from autofocus point information to internal settings that don't fit standard EXIF fields.

Why you'd care: Contains detailed camera-specific information like which AF point was used, lens corrections applied, shutter count, and more. Specialized software can decode this for your camera brand.

UNDEFINED data block containing manufacturer-specific metadata. Structure is entirely proprietary—each brand uses different formats, some encrypted. ExifTool maintains extensive reverse-engineered documentation. Can be several KB in size. Some editors preserve it, others destroy it during saves.

Tag ID
0x927C (37500)
Data Type
UNDEFINED (7)
Count
Variable (often 1000s of bytes)
Standard
EXIF 2.32 (container only; contents proprietary)
MakerNote contents may include: shutter count, AF points used, lens correction profiles, image stabilization data, flash exposure details, scene recognition results, and internal serial numbers.

FirmwareVersion

MakerNotes/Software EXIF

The version of your camera's internal software (firmware) when the photo was taken. Shows whether you were running the latest updates or an older version.

Why you'd care: If you notice quality differences in older photos, check firmware—an update may have improved autofocus, image quality, or fixed bugs affecting your shots.

Firmware information may appear in multiple locations: the standard Software tag (IFD0), manufacturer-specific MakerNotes, or both. Format varies—some show just version numbers, others include build dates or internal codes. Updates can change image processing characteristics.

Common Locations
Software (0x0131), MakerNotes
Data Type
ASCII (2)
Example
"Ver.1.3.2", "Firmware Version 2.10"
Standard
EXIF 2.32 (Software); Proprietary (MakerNotes)

ShutterCount

MakerNotes MakerNote

How many photos your camera has taken since it was manufactured—like an odometer for your camera. High counts mean more wear; shutters have rated lifespans (typically 100,000-500,000 actuations).

Why you'd care: Essential when buying used cameras—a camera with 20,000 shots is less worn than one with 200,000. Also helps track your own shooting volume over time.

Stored in manufacturer-specific MakerNotes, often encrypted or obfuscated. Not all cameras expose this data in EXIF—some require special software or service mode access. Includes mechanical shutter actuations; electronic shutter shots may or may not increment depending on implementation.

Location
MakerNotes (varies by manufacturer)
Nikon
Often in ShutterCount tag
Canon
Often requires special tools
Sony
Encrypted in newer models
Standard
Proprietary

AFPoint

MakerNotes MakerNote

Which autofocus point(s) your camera used to focus on the shot. Shows exactly where in the frame the camera locked focus—whether single-point, zone, or face/eye detection.

Why you'd care: Debug focus misses by seeing where the camera actually focused. If photos are consistently sharp in the wrong place, you can adjust your AF point selection.

Stored in manufacturer-specific MakerNotes with highly varied formats. May include: selected point, active points in zone/wide mode, face detection regions, eye-AF target, confidence scores, and phase-detect vs contrast-detect flags. Critical for focus troubleshooting.

Location
MakerNotes
Format
Varies extensively by manufacturer/model
Data
Point ID, coordinates, or zone information
Standard
Proprietary

CameraProfile

DNG/XMP DNG

The color profile used to interpret your RAW file's colors—like "Camera Standard," "Adobe Portrait," or "Camera Neutral." Different profiles give the same RAW file dramatically different looks.

Why you'd care: Explains why RAW files look different in various software. The profile determines starting colors before any editing—switching profiles changes the entire mood.

Stored in DNG files or XMP sidecars, specifies the color transform matrix and tone curve used for RAW conversion. Adobe Camera RAW uses embedded or looked-up profiles. DCP (DNG Camera Profile) files contain full color matrices, hue/saturation/luminance adjustments, and tone curves.

Namespace
crs (Camera Raw Settings)
XMP Tag
crs:CameraProfile
Values
"Adobe Standard", "Camera Neutral", "Camera Vivid", custom DCP names
Standard
DNG 1.6, Adobe XMP

ImageStabilization

MakerNotes MakerNote

Whether image stabilization was active—the anti-shake technology in your lens or camera body that counteracts hand movement for sharper handheld shots.

Why you'd care: Explains why some slow shutter speed shots came out sharp (IS saved them) or blurry (IS was off or couldn't compensate enough).

Stored in MakerNotes with manufacturer-specific terminology: Canon IS, Nikon VR, Sony SteadyShot/IBIS, etc. May indicate mode (Standard/Active/Off), type (optical/sensor), and sometimes compensation amount achieved. Camera IBIS and lens OIS may be recorded separately.

Location
MakerNotes
Canon
ImageStabilization tag
Nikon
VibrationReduction tag
Sony
SteadyShot / IBISEnabled
Standard
Proprietary

DriveMode

MakerNotes MakerNote

How your camera captured the image—single shot, continuous burst, self-timer, remote trigger, etc. Shows whether you fired one shot or were in spray-and-pray mode.

Why you'd care: Tells you if a great action shot came from skill (single shot) or statistics (burst mode picked the best frame). Also reveals self-timer shots.

Stored in MakerNotes with values for: single shot, continuous low/high, self-timer (various delays), remote control, interval timer, bracketing sequences, etc. Terminology and value encoding varies significantly between manufacturers.

Location
MakerNotes
Typical Values
Single, Continuous, Self-timer (2s/10s), Remote
Standard
Proprietary

SensorSize

Derived Composite

The physical dimensions of your camera's image sensor. "Full frame" (36×24mm) is the largest common size, followed by APS-C (~23×15mm), Micro Four Thirds (~17×13mm), and smaller smartphone sensors.

Why you'd care: Larger sensors generally produce better image quality, especially in low light. Sensor size also affects depth of field—full frame gives more background blur at the same settings.

Not stored directly—must be calculated from FocalPlaneResolution tags, looked up from camera model, or derived from FocalLengthIn35mmFilm ratio. ExifTool and similar tools can calculate sensor dimensions when sufficient data is present.

Full Frame
36 × 24 mm (1.0x crop)
APS-C (Canon)
22.3 × 14.9 mm (1.6x crop)
APS-C (Nikon/Sony)
23.6 × 15.6 mm (1.5x crop)
Micro 4/3
17.3 × 13.0 mm (2.0x crop)
Calculation
ImageWidth ÷ FocalPlaneXResolution × 25.4

Environmental Sensors 6 terms

Ambient conditions recorded by cameras with environmental sensors. Temperature, humidity, pressure, water depth, and acceleration data captured alongside your photos.

AmbientTemperature

Tag 0x9400 EXIF

The air temperature when your photo was taken, measured by a sensor in the camera. Shows whether you were shooting in freezing cold or scorching heat.

Why you'd care: Fascinating context for travel and outdoor photography. "That mountain shot was at -15°C!" Also useful for tracking conditions that affect battery life and camera behavior.

Records ambient temperature from an internal or external sensor. Stored as SRATIONAL allowing negative values. Available on select rugged/outdoor cameras (Olympus TG series, some Nikons). May lag actual conditions due to camera body heat absorption.

Tag ID
0x9400 (37888)
Data Type
SRATIONAL (10)
Count
1
Unit
Degrees Celsius
Standard
EXIF 2.32

Humidity

Tag 0x9401 EXIF

The relative humidity when your photo was taken—how much moisture was in the air, from 0% (bone dry) to 100% (saturated/foggy).

Why you'd care: Adds environmental context to your shots. High humidity can cause hazy atmospherics in landscapes. Also warns about conditions that can cause lens fogging.

Records relative humidity as a percentage. Found on cameras with environmental sensors. May be measured internally or via connected external sensors. Accuracy varies with sensor placement—internal sensors may be affected by camera heat.

Tag ID
0x9401 (37889)
Data Type
RATIONAL (5)
Count
1
Unit
Percent (%)
Range
0–100
Standard
EXIF 2.32

Pressure

Tag 0x9402 EXIF

Atmospheric pressure when the photo was taken. Lower pressure indicates higher altitude or stormy weather; higher pressure suggests sea level or fair weather.

Why you'd care: Provides altitude estimation even without GPS, and documents weather conditions. "That shot was during low pressure at 950 hPa—no wonder the sky looked dramatic."

Records barometric pressure from an internal sensor. Can be used for altitude estimation when combined with reference pressure. Available on select cameras with environmental sensors. Standard sea-level pressure is approximately 1013.25 hPa.

Tag ID
0x9402 (37890)
Data Type
RATIONAL (5)
Count
1
Unit
hPa (hectopascals)
Reference
~1013 hPa at sea level
Standard
EXIF 2.32

WaterDepth

Tag 0x9403 EXIF

How deep underwater you were when shooting—measured in meters below the surface. Only recorded by waterproof cameras and diving housings with depth sensors.

Why you'd care: Essential for scuba and underwater photography. Documents dive depths, helps identify marine life habitats, and provides bragging rights for deep shots.

Records depth below water surface from pressure sensor. Available on waterproof cameras (Olympus TG series, Nikon AW series) and some underwater housings. Calculated from water pressure differential. Negative values indicate above-water altitude equivalent.

Tag ID
0x9403 (37891)
Data Type
SRATIONAL (10)
Count
1
Unit
Meters
Note
Positive = depth, Negative = altitude
Standard
EXIF 2.32

Acceleration

Tag 0x9404 EXIF

The G-force or movement detected by your camera's motion sensor at capture time. Indicates how much the camera was accelerating or being shaken.

Why you'd care: Shows shooting conditions for action photography. High acceleration values explain camera shake blur or confirm stable shooting conditions.

Records accelerometer data at capture time. May be a single magnitude or three-axis vector. Used internally for image stabilization and orientation detection. At rest, reads approximately 1g (9.8 m/s²) due to gravity. Format varies by implementation.

Tag ID
0x9404 (37892)
Data Type
SRATIONAL (10)
Count
1 or 3 (for XYZ)
Unit
mG (milli-G) or m/s²
Standard
EXIF 2.32

CameraElevationAngle

Tag 0x9405 EXIF

How much your camera was tilted up or down from level—measured in degrees. 0° is horizontal, +90° is pointing straight up, -90° is straight down.

Why you'd care: Reveals your shooting angle. Architecture shots at +45° were looking up at buildings; wildlife at -20° means you were shooting downward. Useful for planning repeat shots.

Records the pitch angle (elevation) of the camera relative to horizontal, derived from accelerometer or gyroscope data. Positive values indicate upward tilt; negative values indicate downward. Not the same as roll (horizon level) or compass direction (yaw).

Tag ID
0x9405 (37893)
Data Type
SRATIONAL (10)
Count
1
Unit
Degrees
Range
-90 to +90
Standard
EXIF 2.32

Composite & Advanced 8 terms

Advanced technical fields for composite images, color filter arrays, spectral data, and sensor-specific information. Specialized metadata used in computational photography and RAW processing.

CompositeImage

Tag 0xA460 EXIF

Whether this image was created by combining multiple shots—like HDR (multiple exposures), panorama (stitched images), or computational photography (like Night Mode stacking).

Why you'd care: Reveals if the impressive dynamic range or detail came from in-camera processing rather than a single capture. Important for understanding what your camera actually did.

Indicates whether the image is a composite of multiple captures. Added in EXIF 2.32 to address computational photography where phones/cameras merge multiple frames. When value is 2 (Composite), CompositeImageCount and CompositeImageExposureTimes tags may provide details.

Tag ID
0xA460 (42080)
Data Type
SHORT (3)
Count
1
Values
0=Unknown, 1=Not a Composite, 2=General Composite, 3=Composite with capture times
Standard
EXIF 2.32

CompositeImageCount

Tag 0xA461 EXIF

How many individual photos were combined to create this composite image. A Night Mode shot might stack 30 frames; an HDR might merge 3-5 exposures.

Why you'd care: Reveals the computational effort behind the image. More frames generally means better noise reduction and dynamic range. Also helps explain long processing times.

Two-value array indicating: [total frames captured, frames used in composite]. For example, camera might capture 30 frames but use best 20. Only meaningful when CompositeImage indicates a composite was created.

Tag ID
0xA461 (42081)
Data Type
SHORT (3)
Count
2
Format
[total captured, used in composite]
Standard
EXIF 2.32

CFAPattern

Tag 0xA302 EXIF

The color filter pattern on your camera's sensor—the arrangement of red, green, and blue filters over the pixels that lets it capture color. Most cameras use "Bayer" pattern (RGGB).

Why you'd care: Mostly of interest to technical enthusiasts. Different patterns (Bayer, X-Trans, Quad Bayer) affect how RAW files are processed and can influence moiré patterns.

Describes the geometric pattern of the Color Filter Array on the sensor. Stored as 2-byte width, 2-byte height, followed by pattern values. Standard Bayer is 2×2: [0,1,1,2] representing RGGB. Fujifilm X-Trans uses 6×6 pattern. Critical for RAW demosaicing algorithms.

Tag ID
0xA302 (41730)
Data Type
UNDEFINED (7)
Count
Variable
Format
[width, height, pattern values...]
Values
0=Red, 1=Green, 2=Blue, 3=Cyan, 4=Magenta, 5=Yellow, 6=White
Standard
EXIF 2.32

SpectralSensitivity

Tag 0x8824 EXIF

Technical data about how your camera's sensor responds to different wavelengths of light. Describes the sensor's sensitivity to various colors in precise scientific terms.

Why you'd care: Extremely specialized—only relevant for scientific imaging, color calibration research, or understanding why different cameras render colors differently.

Records spectral sensitivity of each channel per ASTM E1655 standard. Stored as ASCII text defining wavelength bands and response curves. Rarely populated by consumer cameras; primarily used in scientific/industrial imaging where precise color response characterization is required.

Tag ID
0x8824 (34852)
Data Type
ASCII (2)
Count
Variable
Format
Per ASTM E1655
Standard
EXIF 2.32

OECF

Tag 0x8828 EXIF

Opto-Electronic Conversion Function—the mathematical curve describing how your camera converts light intensity into digital values. Like a detailed version of gamma that maps real-world brightness to pixel values.

Why you'd care: Very technical—mainly relevant for scientific imaging or precise color reproduction workflows. Consumer cameras rarely populate this field.

Specifies the relationship between optical input and the resulting image file values. Stored per ISO 14524 as a structured table of columns/rows with stimulus and response values. Enables precise tone reproduction characterization. Almost never populated by consumer equipment.

Tag ID
0x8828 (34856)
Data Type
UNDEFINED (7)
Count
Variable
Format
Per ISO 14524
Standard
EXIF 2.32

SpatialFrequencyResponse

Tag 0xA20C EXIF

Data about how well your camera/lens resolves fine detail at different frequencies—essentially how sharp things get as details get smaller. Related to lens resolution testing (MTF charts).

Why you'd care: Highly technical—used for scientific lens characterization. If you're not testing optics in a lab, you'll never encounter this field populated.

Records the camera/lens system's Modulation Transfer Function (MTF) response. Stored per ISO 12233 format with spatial frequency values and corresponding contrast values for each color channel. Almost never populated by consumer cameras. Used in laboratory characterization.

Tag ID
0xA20C (41484)
Data Type
UNDEFINED (7)
Count
Variable
Format
Per ISO 12233
Standard
EXIF 2.32

DNGVersion

Tag 0xC612 DNG

The version of the DNG (Digital Negative) format used to save this RAW file. DNG is Adobe's open RAW format that many cameras and phones now support natively.

Why you'd care: Newer DNG versions support more features like transparency, HDR gain maps, and semantic masks. Version determines what software can open the file properly.

Four-byte array indicating DNG specification version: [major, minor, patch, patch]. For example, [1, 6, 0, 0] indicates DNG 1.6. Determines available features like floating-point data, ProPhoto RGB, semantic masks, and gain maps. Requires corresponding DNGBackwardVersion for reader compatibility.

Tag ID
0xC612 (50706)
Data Type
BYTE (1)
Count
4
Format
[major, minor, patch, patch]
Current
1.7.0.0 (DNG 1.7)
Standard
Adobe DNG 1.7

NoiseProfile

Tag 0xC761 DNG

Calibration data describing how noisy your camera's sensor is at different brightness levels. Helps RAW processing software apply optimal noise reduction without losing detail.

Why you'd care: Better noise profiles = smarter noise reduction. When present, your RAW converter can more intelligently separate real detail from sensor noise, preserving texture while reducing grain.

Contains coefficients for a per-color-channel noise model: NoiseProfile(level) = sqrt(a + b × level). Two doubles per color plane describe photon shot noise and sensor read noise. Enables optimal Poisson-Gaussian denoising. Calculated from sensor calibration data.

Tag ID
0xC761 (51041)
Data Type
DOUBLE (12)
Count
2 × ColorPlanes
Format
[a, b] coefficients per channel
Model
σ = √(a + b × L)
Standard
Adobe DNG 1.3+

Jump to Category

Learn More About Photo Metadata

Explore our guides to understand how metadata affects your privacy and photography workflow.