(7FE0,0010)
Pixel Data
Keyword: PixelData
A data stream of the pixel samples that comprise the Image. The order of pixels is left to right, top to bottom. The encoding follows the Transfer Syntax.
Tag Attributes
- Tag ID
- (7FE0,0010)
- Compact
- 7FE00010
- Keyword
- PixelData
- VR
- OB/OW — Other Byte or Other Word
- VM
- 1
- Required
- Type 1C — required when a condition applies
- PS3.15
- Not listed in PS3.15 Table E.1-1
- Retired
- No
Defined in
What Pixel Data contains
Pixel Data holds the image itself. Everything needed to decode it comes from other attributes: Rows, Columns, Samples per Pixel, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Photometric Interpretation and, for multi-frame images, Number of Frames.
How it is stored depends on the transfer syntax. In native encoding the pixels follow each other row by row, left to right and top to bottom, frame after frame. In encapsulated encoding (JPEG, JPEG-LS, JPEG 2000, RLE and others) the value has an undefined length and is a series of fragments, starting with a Basic Offset Table item that may be empty.
Pixel Data is Type 1C: required unless the pixels are referenced through Pixel Data Provider URL (0028,7FE0) instead, as in JPIP-based transfer.
Usually the largest element of the file. Encapsulated (compressed) pixel data always has VR OB and undefined length. Native pixel data has VR OW, or OB or OW when Bits Allocated is 8 or less in an explicit VR transfer syntax.
Group 7FE0 holds the pixel data itself.
Value format: OB/OW (Other Byte or Other Word), VM 1
(7FE0,0010) PixelData has Value Representation OB/OW (Other Byte or Other Word) and Value Multiplicity 1, which means exactly one value.
OB — Other Byte
A string of bytes whose content is defined by the transfer syntax. Byte order does not apply.
- Length
- 2³²−2 bytes maximum, always an even number of bytes
- Characters
- Binary.
OW — Other Word
A stream of 16-bit words.
- Length
- 2³²−2 bytes maximum
- Characters
- Binary. Byte order follows the transfer syntax.
What the value holds
Native (uncompressed): Rows × Columns × Samples per Pixel × (Bits Allocated ÷ 8) × Number of Frames bytes, padded to an even length. Encapsulated (compressed): undefined length, a Basic Offset Table item, then one or more fragments per frame.
Where PixelData appears
| Defined in | Type | Meaning |
|---|---|---|
| Image Pixel ModulePS3.3 C.7.6.3 | 1C | Required, with a value, when its condition applies, and absent otherwise.Required if Pixel Data Provider URL (0028,7FE0) is not present. |
A module lists the attributes an object must or may carry. Many IODs (CT Image, MR Image, Secondary Capture and others) include the same module, and an IOD-specific module can make an attribute stricter than the general one.
De-identification (PS3.15)
Pixel Data is not listed in PS3.15 Table E.1-1, so the Basic Application Level Confidentiality Profile gives no specific action for it.
Not listed in Table E.1-1 because it is not an identifying attribute, but its content can show burned-in text or recognisable features: see Burned In Annotation (0028,0301).
To see how de-identification changes your own files, try the free DICOM Anonymizer, which runs in the browser and uploads nothing.
In archives and migrations
Copying an object without changing its transfer syntax copies Pixel Data bit for bit, so a byte comparison of a sample of migrated objects is a strong check. Converting between lossless syntaxes changes the bytes but not the decoded pixel values, so compare decoded pixels instead.
Common errors and how to fix them
The image decodes as noise or diagonal stripes
Rows, Columns, Bits Allocated or Samples per Pixel do not describe the pixel data as stored. Compare the expected native length with the actual length to find which value is wrong.
The file ends early
A truncated transfer or copy. Request the object again from the source; the pixels cannot be repaired from the header.
Troubleshooting: For native pixel data the length must match Rows × Columns × Samples per Pixel × Bits Allocated ÷ 8 × Number of Frames. A shorter value means a truncated file or transfer; a different layout means the header and the pixels disagree.
Check a file in seconds with the free DICOM Validator: it reads the header in your browser, lists the tags with their values, and flags missing or malformed key attributes.
Pixel Data: frequently asked questions
What is DICOM tag (7FE0,0010) Pixel Data?
A data stream of the pixel samples that comprise the Image. The order of pixels is left to right, top to bottom. The encoding follows the Transfer Syntax. Pixel Data holds the image itself. Everything needed to decode it comes from other attributes: Rows, Columns, Samples per Pixel, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Photometric Interpretation and, for multi-frame images, Number of Frames.
What VR and VM does Pixel Data (7FE0,0010) have?
(7FE0,0010) PixelData has Value Representation OB/OW (Other Byte or Other Word) and Value Multiplicity 1, which means exactly one value. A string of bytes whose content is defined by the transfer syntax. Byte order does not apply. Maximum length: 2³²−2 bytes maximum, always an even number of bytes.
Is Pixel Data (7FE0,0010) required?
In the Image Pixel Module (PS3.3 C.7.6.3) it is Type 1C: required, with a value, when its condition applies, and absent otherwise. Required if Pixel Data Provider URL (0028,7FE0) is not present.
How is Pixel Data handled when de-identifying DICOM files?
Pixel Data is not listed in PS3.15 Table E.1-1, so the Basic Application Level Confidentiality Profile gives no specific action for it. Not listed in Table E.1-1 because it is not an identifying attribute, but its content can show burned-in text or recognisable features: see Burned In Annotation (0028,0301).
How do I troubleshoot Pixel Data (7FE0,0010)?
For native pixel data the length must match Rows × Columns × Samples per Pixel × Bits Allocated ÷ 8 × Number of Frames. A shorter value means a truncated file or transfer; a different layout means the header and the pixels disagree.
Check PixelData in your files
The free DICOM Validator lists every header tag and flags problems. Files stay in your browser.
Open DICOM Validator →Remove patient data before sharing
The free DICOM Anonymizer applies a de-identification profile in your browser, with no upload.
Open DICOM Anonymizer →Sources
Checked against the DICOM standard, release 2026d. Module Types, query keys and de-identification actions come from these tables: