MajwareMAJWARE
File Meta

(0002,0010)

Transfer Syntax UID

Keyword: TransferSyntaxUID

Identifies the transfer syntax used to encode the data set that follows the File Meta Information: byte order, explicit or implicit VR, and whether Pixel Data is native or compressed.

Tag Attributes

Tag ID
(0002,0010)
Compact
00020010
Keyword
TransferSyntaxUID
VR
UI — Unique Identifier (UID)
VM
1
Required
Type 1 — required, with a value
PS3.15
Not listed in PS3.15 Table E.1-1
Retired
No

Defined in

File Meta Information

What Transfer Syntax UID contains

Transfer Syntax UID tells a reader three things about the data set that follows the File Meta header: the byte order (little or big endian), whether each element states its VR explicitly, and how Pixel Data is encoded, either native or compressed with JPEG, JPEG-LS, JPEG 2000, RLE or another scheme.

It is a File Meta element, so it exists only in files. On the network the transfer syntax is agreed for each presentation context during association negotiation, and the receiver records the syntax it actually stores in its own File Meta header. The same image can therefore show different transfer syntaxes in different archives.

Implicit VR Little Endian (1.2.840.10008.1.2) is the default transfer syntax that every DICOM implementation supports on the network.

One of the most important elements of a DICOM file: a reader cannot interpret anything after the File Meta header without it. The File Meta header itself is always Explicit VR Little Endian, whatever this value says.

Group 0002 is the File Meta Information defined in PS3.10. It sits at the start of every DICOM file, is always encoded in Explicit VR Little Endian, and is not part of the data set that is sent over the network.

Value format: UI (Unique Identifier (UID)), VM 1

(0002,0010) TransferSyntaxUID has Value Representation UI (Unique Identifier (UID)) and Value Multiplicity 1, which means exactly one value.

UI — Unique Identifier (UID)

A globally unique identifier made of numeric components separated by periods, for example 1.2.840.10008.1.2.1. An odd-length value is padded with one trailing NULL byte.

Length
64 bytes maximum
Characters
The digits 0–9 and the period.

Example value

1.2.840.10008.1.2.1

Format mistakes to avoid

  • A component may not start with a zero unless it is the single digit 0, so 1.2.03 is invalid.
  • Letters, spaces and values longer than 64 bytes are invalid.

Common values

ValueMeaning
1.2.840.10008.1.2Implicit VR Little Endian — the default transfer syntax
1.2.840.10008.1.2.1Explicit VR Little Endian
1.2.840.10008.1.2.1.99Deflated Explicit VR Little Endian
1.2.840.10008.1.2.2Explicit VR Big Endian (retired)
1.2.840.10008.1.2.4.50JPEG Baseline (Process 1) — lossy
1.2.840.10008.1.2.4.51JPEG Extended (Process 2 & 4) — lossy
1.2.840.10008.1.2.4.57JPEG Lossless, Non-Hierarchical (Process 14)
1.2.840.10008.1.2.4.70JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14, Selection Value 1)
1.2.840.10008.1.2.4.90JPEG 2000 Image Compression (Lossless Only)
1.2.840.10008.1.2.4.91JPEG 2000 Image Compression (lossless or lossy)
1.2.840.10008.1.2.5RLE Lossless

Where TransferSyntaxUID appears

Defined inTypeMeaning
File Meta InformationPS3.10 Table 7.1-11Required, 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)

Transfer Syntax UID 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

Decide before a migration whether objects are copied in their original transfer syntax or converted. A lossless conversion changes the encoding but not the pixel values; a lossy one changes the pixels, must set Lossy Image Compression (0028,2110) to 01 and gives the copy a new SOP Instance UID.

Common errors and how to fix them

  • A file will not open

    The declared transfer syntax does not match the encoding, for example a file written in implicit VR but labelled explicit. Re-export it from the source, or rewrite the header with a tool that re-encodes the data set.

  • The receiver rejects images

    Sender and receiver share no transfer syntax for that SOP Class. Let the sender convert to a syntax the receiver accepted, such as the default Implicit VR Little Endian, or add the syntax on the receiver.

  • Images look blocky after a transfer

    A lossy transfer syntax was used somewhere on the way. Check Lossy Image Compression (0028,2110) in the received image.

Troubleshooting: Over the network the transfer syntax is agreed for each presentation context during association negotiation; this element is not sent. If a receiver does not accept the syntax a file uses, the sender has to convert the data set to one the receiver accepted, for example Explicit VR Little Endian. Inside a file, a value that does not match the actual encoding makes the file unreadable.

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.

Transfer Syntax UID: frequently asked questions

What is DICOM tag (0002,0010) Transfer Syntax UID?

Identifies the transfer syntax used to encode the data set that follows the File Meta Information: byte order, explicit or implicit VR, and whether Pixel Data is native or compressed. Transfer Syntax UID tells a reader three things about the data set that follows the File Meta header: the byte order (little or big endian), whether each element states its VR explicitly, and how Pixel Data is encoded, either native or compressed with JPEG, JPEG-LS, JPEG 2000, RLE or another scheme.

What VR and VM does Transfer Syntax UID (0002,0010) have?

(0002,0010) TransferSyntaxUID has Value Representation UI (Unique Identifier (UID)) and Value Multiplicity 1, which means exactly one value. A globally unique identifier made of numeric components separated by periods, for example 1.2.840.10008.1.2.1. An odd-length value is padded with one trailing NULL byte. Maximum length: 64 bytes maximum.

Is Transfer Syntax UID (0002,0010) required?

In the File Meta Information (PS3.10 Table 7.1-1) it is Type 1: required, and it must have a value.

How is Transfer Syntax UID handled when de-identifying DICOM files?

Transfer Syntax UID 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 Transfer Syntax UID (0002,0010)?

Over the network the transfer syntax is agreed for each presentation context during association negotiation; this element is not sent. If a receiver does not accept the syntax a file uses, the sender has to convert the data set to one the receiver accepted, for example Explicit VR Little Endian. Inside a file, a value that does not match the actual encoding makes the file unreadable.

Check TransferSyntaxUID 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 File Meta tags