(0028,0103)
Pixel Representation
Keyword: PixelRepresentation
Data representation of pixel samples. 0x0000 = unsigned integer, 0x0001 = 2's complement (signed).
Tag Attributes
- Tag ID
- (0028,0103)
- Compact
- 00280103
- Keyword
- PixelRepresentation
- VR
- US — Unsigned Short
- VM
- 1
- Required
- Type 1 — required, with a value
- PS3.15
- Not listed in PS3.15 Table E.1-1
- Retired
- No
Defined in
What Pixel Representation contains
Pixel Representation says whether stored pixel values are unsigned integers (0) or two's complement signed integers (1). It applies to the Bits Stored bits of each sample, so with 12 bits stored and a value of 1, the High Bit is the sign bit.
A reader must apply it before Rescale Slope and Intercept. Reading signed data as unsigned turns small negative values into very large positive ones, which in CT shows up as air or background displayed bright instead of dark.
CT pixels may be stored either way: unsigned with a Rescale Intercept such as −1024, or signed with negative values stored directly. This attribute tells the reader which, and the reader must apply it before the rescale.
Group 0028 describes the pixel matrix and how stored pixel values are turned into displayed values.
Value format: US (Unsigned Short), VM 1
(0028,0103) PixelRepresentation has Value Representation US (Unsigned Short) and Value Multiplicity 1, which means exactly one value.
US — Unsigned Short
A 16-bit unsigned binary integer, from 0 to 65535.
- Length
- 2 bytes fixed
- Characters
- Binary. Byte order follows the transfer syntax.
Example value
0
Common values
| Value | Meaning |
|---|---|
| 0 | Unsigned integer |
| 1 | Two's complement (signed) integer |
Where PixelRepresentation appears
| Defined in | Type | Meaning |
|---|---|---|
| Image Pixel ModulePS3.3 C.7.6.3 | 1 | Required, and it must have a value. |
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 Representation is not listed in PS3.15 Table E.1-1, so the Basic Application Level Confidentiality Profile gives no specific action for it.
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
Image pixel attributes must stay consistent with the Pixel Data. If images are recompressed during a move (for example to JPEG 2000), the transfer syntax changes and some of these values can change with it, so a lossless copy is the only way to keep them byte-for-byte identical.
Common errors and how to fix them
Negative values come out as large positive numbers
With signed data and Bits Stored smaller than Bits Allocated, the reader must extend the sign from the High Bit to the full word. Check the reader before suspecting the file.
Troubleshooting: CT images displaying with air as bright white (instead of black) is the classic symptom of wrong Pixel Representation (unsigned when signed is needed).
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 Representation: frequently asked questions
What is DICOM tag (0028,0103) Pixel Representation?
Data representation of pixel samples. 0x0000 = unsigned integer, 0x0001 = 2's complement (signed). Pixel Representation says whether stored pixel values are unsigned integers (0) or two's complement signed integers (1). It applies to the Bits Stored bits of each sample, so with 12 bits stored and a value of 1, the High Bit is the sign bit.
What VR and VM does Pixel Representation (0028,0103) have?
(0028,0103) PixelRepresentation has Value Representation US (Unsigned Short) and Value Multiplicity 1, which means exactly one value. A 16-bit unsigned binary integer, from 0 to 65535. Maximum length: 2 bytes fixed.
Is Pixel Representation (0028,0103) required?
In the Image Pixel Module (PS3.3 C.7.6.3) it is Type 1: required, and it must have a value.
How is Pixel Representation handled when de-identifying DICOM files?
Pixel Representation is not listed in PS3.15 Table E.1-1, so the Basic Application Level Confidentiality Profile gives no specific action for it.
How do I troubleshoot Pixel Representation (0028,0103)?
CT images displaying with air as bright white (instead of black) is the classic symptom of wrong Pixel Representation (unsigned when signed is needed).
Check PixelRepresentation 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: