MajwareMAJWARE
Image Pixel

(0028,0101)

Bits Stored

Keyword: BitsStored

Number of bits stored for each pixel sample. Must be ≤ Bits Allocated.

Tag Attributes

Tag ID
(0028,0101)
Compact
00280101
Keyword
BitsStored
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

Image Pixel Module

What Bits Stored contains

The number of bits actually used for each sample, within Bits Allocated. 12 bits stored in 16 allocated is common for CT.

Group 0028 describes the pixel matrix and how stored pixel values are turned into displayed values.

Value format: US (Unsigned Short), VM 1

(0028,0101) BitsStored 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

12

Common values

ValueMeaning
88 bits: 256 levels
1010 bits
1212 bits: common for CT
1414 bits
1616 bits: the full allocated word

Where BitsStored appears

Defined inTypeMeaning
Image Pixel ModulePS3.3 C.7.6.31Required, 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)

Bits Stored 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

Troubleshooting: High Bit (0028,0102) must equal Bits Stored − 1. Violation causes incorrect pixel value interpretation.

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.

Bits Stored: frequently asked questions

What is DICOM tag (0028,0101) Bits Stored?

Number of bits stored for each pixel sample. Must be ≤ Bits Allocated.

What VR and VM does Bits Stored (0028,0101) have?

(0028,0101) BitsStored 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 Bits Stored (0028,0101) 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 Bits Stored handled when de-identifying DICOM files?

Bits Stored 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 Bits Stored (0028,0101)?

High Bit (0028,0102) must equal Bits Stored − 1. Violation causes incorrect pixel value interpretation.

Check BitsStored 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:

More Image Pixel tags