MajwareMAJWARE
Pixel Data

(7FE0,0008)

Float Pixel Data

Keyword: FloatPixelData

Pixel data stored as 32-bit floating-point values instead of integers.

Tag Attributes

Tag ID
(7FE0,0008)
Compact
7FE00008
Keyword
FloatPixelData
VR
OF — Other Float
VM
1
Required
Type 1 — required, with a value
PS3.15
Not listed in PS3.15 Table E.1-1
Retired
No

Defined in

Floating Point Image Pixel Module

What Float Pixel Data contains

Used by IODs such as the Parametric Map for quantitative values (T1 maps, ADC maps and similar). The Floating Point Image Pixel Module drops Bits Stored, High Bit and Pixel Representation, which do not apply to floats.

Group 7FE0 holds the pixel data itself.

Value format: OF (Other Float), VM 1

(7FE0,0008) FloatPixelData has Value Representation OF (Other Float) and Value Multiplicity 1, which means exactly one value.

OF — Other Float

A stream of 32-bit IEEE 754 floating-point numbers.

Length
2³²−4 bytes maximum
Characters
Binary. Byte order follows the transfer syntax.

What the value holds

Binary: one 32-bit IEEE 754 float per pixel. Bits Allocated is 32 and Photometric Interpretation is MONOCHROME2.

Where FloatPixelData appears

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

Float 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.

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

Pixel Data is the bulk of every object. A migration that keeps the transfer syntax copies it bit for bit; one that recompresses it changes its encoding, and a lossy recompression also changes the pixel values themselves.

Common errors and how to fix them

Troubleshooting: A viewer that supports only integer Pixel Data (7FE0,0010) cannot show it. Check the viewer's conformance statement for the Parametric Map Storage SOP Class.

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.

Float Pixel Data: frequently asked questions

What is DICOM tag (7FE0,0008) Float Pixel Data?

Pixel data stored as 32-bit floating-point values instead of integers.

What VR and VM does Float Pixel Data (7FE0,0008) have?

(7FE0,0008) FloatPixelData has Value Representation OF (Other Float) and Value Multiplicity 1, which means exactly one value. A stream of 32-bit IEEE 754 floating-point numbers. Maximum length: 2³²−4 bytes maximum.

Is Float Pixel Data (7FE0,0008) required?

In the Floating Point Image Pixel Module (PS3.3 C.7.6.24) it is Type 1: required, and it must have a value.

How is Float Pixel Data handled when de-identifying DICOM files?

Float 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.

How do I troubleshoot Float Pixel Data (7FE0,0008)?

A viewer that supports only integer Pixel Data (7FE0,0010) cannot show it. Check the viewer's conformance statement for the Parametric Map Storage SOP Class.

Check FloatPixelData 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 Pixel Data tags