DICOM Basics using .NET and C# - Transfer Syntax and Compression

Nov 30, 2025

Introduction

This is part of my series of articles on the DICOM standard. In this tutorial, we'll explore DICOM Transfer Syntax, which defines how DICOM data is encoded for storage and transmission. Understanding Transfer Syntax is essential for handling compressed images and ensuring interoperability between systems.

Transfer Syntax determines byte ordering (endianness), VR encoding (implicit/explicit), and pixel data compression. Choosing the right transfer syntax impacts storage efficiency, transmission speed, and image quality.

Prerequisites

Before you begin, ensure you have the following:

A .NET development environment (Visual Studio or Visual Studio Code)
The Fellow Oak DICOM library (fo-dicom) installed via NuGet
Basic understanding of DICOM concepts from previous tutorials
You can find all the code demonstrated in this tutorial on GitHub here

“Simplicity is the final achievement. After one has played a vast quantity of notes, it is simplicity that emerges as the crowning reward of art.” ~ Frédéric Chopin

The Theory Behind Transfer Syntax

Transfer Syntax addresses a fundamental challenge in data exchange: the same logical information can be represented in many different physical formats. DICOM data is abstract until encoded, and Transfer Syntax defines that encoding. Understanding the three components - byte ordering, VR encoding, and compression - reveals why this abstraction is necessary.

Byte ordering (endianness) exists because different processor architectures store multi-byte numbers differently. Intel x86 uses little-endian (least significant byte first), while some older systems used big-endian. DICOM standardized on little-endian for the default Transfer Syntax because it was becoming dominant. Without explicit byte ordering specification, a 16-bit pixel value of 0x0102 could be interpreted as 258 or 513 depending on the reader's assumption.

Implicit vs. Explicit VR trades file size against self-description. Implicit VR requires both sender and receiver to agree on the VR of every tag based on the data dictionary - a 2-byte savings per element but fragile if dictionaries differ. Explicit VR includes the VR in the data stream, making files self-describing and robust to dictionary mismatches. Modern practice strongly favors Explicit VR for interoperability.

From information theory, compression exploits redundancy to reduce size. Medical images have significant redundancy: adjacent pixels often have similar values (spatial redundancy), and certain pixel values occur more frequently (statistical redundancy). Lossless compression exploits these patterns without altering pixel values, achieving typical 2:1 to 4:1 ratios. Lossy compression achieves higher ratios by discarding information the human visual system is less sensitive to.

The choice between lossless and lossy involves clinical and legal considerations, not just technical trade-offs. For diagnostic interpretation, lossless preserves the original acquisition. For teaching files or patient portals where diagnostic quality isn't required, lossy may be acceptable. The Lossy Image Compression attribute (0028,2110) provides traceability, ensuring downstream systems know when data has been irreversibly modified.

JPEG 2000's wavelet compression offers advantages over DCT-based JPEG: better quality at equal compression, support for lossless and lossy in the same codec, and progressive transmission (showing a low-resolution preview while full data loads). The computational cost is higher, but modern hardware handles it well.

Transfer Syntax Components

A Transfer Syntax defines three encoding aspects:

Component	Options	Description
Byte Ordering	Little/Big Endian	LSB or MSB first
VR Encoding	Implicit/Explicit	VR in data or lookup
Compression	Native/Encapsulated	Uncompressed or compressed

Common Transfer Syntaxes

Here are the most commonly used transfer syntaxes:

using System;
using System.Diagnostics;
using FellowOakDicom;

namespace DicomTransferSyntax
{
    public class Program
    {
        public static void Main(string[] args)
        {
            LogToDebugConsole("=== DICOM Transfer Syntax and Compression Demo ===");
            LogToDebugConsole("");

            DemonstrateUncompressedSyntaxes();
            DemonstrateCompressedSyntaxes();
            DemonstrateCompressionComparison();
        }

        private static void DemonstrateUncompressedSyntaxes()
        {
            LogToDebugConsole("--- Uncompressed Transfer Syntaxes ---");
            LogToDebugConsole("");

            LogToDebugConsole("Implicit VR Little Endian (Default):");
            LogToDebugConsole($"  UID: {DicomTransferSyntax.ImplicitVRLittleEndian.UID.UID}");
            LogToDebugConsole("  The default DICOM transfer syntax");
            LogToDebugConsole("  VR must be looked up in data dictionary");
            LogToDebugConsole("");

            LogToDebugConsole("Explicit VR Little Endian:");
            LogToDebugConsole($"  UID: {DicomTransferSyntax.ExplicitVRLittleEndian.UID.UID}");
            LogToDebugConsole("  Widely supported, VR included in data");
            LogToDebugConsole("  Recommended for network transfer");
            LogToDebugConsole("");

            LogToDebugConsole("Explicit VR Big Endian (Retired):");
            LogToDebugConsole($"  UID: {DicomTransferSyntax.ExplicitVRBigEndian.UID.UID}");
            LogToDebugConsole("  Retired in DICOM 2011 (Supplement 131)");
            LogToDebugConsole("  Avoid for new implementations");
        }

        private static void LogToDebugConsole(string message)
        {
            Debug.WriteLine(message);
        }
    }
}

Uncompressed Transfer Syntaxes

Transfer Syntax	UID	Use Case
Implicit VR Little Endian	1.2.840.10008.1.2	Default, legacy systems
Explicit VR Little Endian	1.2.840.10008.1.2.1	Recommended standard
Explicit VR Big Endian	1.2.840.10008.1.2.2	Retired - avoid

Compressed Transfer Syntaxes

DICOM supports various compression schemes:

private static void DemonstrateCompressedSyntaxes()
{
    LogToDebugConsole("--- Compressed Transfer Syntaxes ---");
    LogToDebugConsole("");

    LogToDebugConsole("JPEG Baseline (Lossy):");
    LogToDebugConsole($"  UID: {DicomTransferSyntax.JPEGProcess1.UID.UID}");
    LogToDebugConsole("  8-bit lossy compression");
    LogToDebugConsole("  Good compression ratio (10:1 to 50:1)");
    LogToDebugConsole("");

    LogToDebugConsole("JPEG Lossless:");
    LogToDebugConsole($"  UID: {DicomTransferSyntax.JPEGProcess14SV1.UID.UID}");
    LogToDebugConsole("  Selection Value 1 (Predictor 1)");
    LogToDebugConsole("  Most commonly used lossless (~3:1)");
    LogToDebugConsole("");

    LogToDebugConsole("JPEG 2000 Lossless:");
    LogToDebugConsole($"  UID: {DicomTransferSyntax.JPEG2000Lossless.UID.UID}");
    LogToDebugConsole("  Better compression than JPEG Lossless (~4:1)");
    LogToDebugConsole("  Computationally more expensive");
    LogToDebugConsole("");

    LogToDebugConsole("JPEG 2000 Lossy:");
    LogToDebugConsole($"  UID: {DicomTransferSyntax.JPEG2000Lossy.UID.UID}");
    LogToDebugConsole("  Configurable quality/compression");
    LogToDebugConsole("  Up to 50:1 compression");
    LogToDebugConsole("");

    LogToDebugConsole("JPEG-LS Lossless:");
    LogToDebugConsole($"  UID: {DicomTransferSyntax.JPEGLSLossless.UID.UID}");
    LogToDebugConsole("  Excellent lossless compression");
    LogToDebugConsole("  Fast encoding/decoding");
    LogToDebugConsole("");

    LogToDebugConsole("RLE Lossless:");
    LogToDebugConsole($"  UID: {DicomTransferSyntax.RLELossless.UID.UID}");
    LogToDebugConsole("  Run-Length Encoding");
    LogToDebugConsole("  Simple, widely supported (~2:1)");
}

Compression Comparison

Type	Ratio	Quality	Use Case
None (Native)	1:1	Perfect	Acquisition
RLE Lossless	~2:1	Lossless	Simple images
JPEG Lossless	~3:1	Lossless	General archival
JPEG-LS	~3:1	Lossless	Better compression
JPEG 2000 LL	~4:1	Lossless	Best lossless
JPEG Baseline	~20:1	Lossy	Web viewing
JPEG 2000 Lossy	~50:1	Lossy	High compression

Lossy vs Lossless Compression

Understanding the differences is critical for clinical applications:

private static void DemonstrateCompressionComparison()
{
    LogToDebugConsole("--- Lossy vs Lossless Compression ---");
    LogToDebugConsole("");

    LogToDebugConsole("Lossy Compression:");
    LogToDebugConsole("  - Data is lost during compression");
    LogToDebugConsole("  - Cannot recover original pixel values");
    LogToDebugConsole("  - Much better compression ratios (10:1 to 50:1)");
    LogToDebugConsole("  - Use cases: viewing, archival (with caution)");
    LogToDebugConsole("");

    LogToDebugConsole("Lossy Compression Attributes:");
    LogToDebugConsole("  (0028,2110) Lossy Image Compression = \"01\"");
    LogToDebugConsole("  (0028,2112) Lossy Image Compression Ratio");
    LogToDebugConsole("  (0028,2114) Lossy Image Compression Method");
    LogToDebugConsole("");

    LogToDebugConsole("Lossless Compression:");
    LogToDebugConsole("  - Original data fully recoverable");
    LogToDebugConsole("  - Lower compression ratios (2:1 to 4:1)");
    LogToDebugConsole("  - Required for diagnostic/legal purposes");
    LogToDebugConsole("  - Safe for all clinical use");
}

Working with Transfer Syntax in fo-dicom

Here's how to work with transfer syntax in fo-dicom:

public static void ExamineTransferSyntax(string filePath)
{
    var file = DicomFile.Open(filePath);

    // Get Transfer Syntax from File Meta Information
    var ts = file.FileMetaInfo.TransferSyntax;

    LogToDebugConsole($"Transfer Syntax: {ts.UID.Name}");
    LogToDebugConsole($"  UID: {ts.UID.UID}");
    LogToDebugConsole($"  IsExplicitVR: {ts.IsExplicitVR}");
    LogToDebugConsole($"  IsEncapsulated: {ts.IsEncapsulated}");
    LogToDebugConsole($"  IsLossy: {ts.IsLossy}");
}

public static void LookupTransferSyntax()
{
    // By UID string
    var ts1 = DicomTransferSyntax.Parse("1.2.840.10008.1.2");
    LogToDebugConsole($"Parsed: {ts1.UID.Name}");

    // By predefined constant
    var ts2 = DicomTransferSyntax.ImplicitVRLittleEndian;
    var ts3 = DicomTransferSyntax.ExplicitVRLittleEndian;
    var ts4 = DicomTransferSyntax.JPEGProcess14SV1;  // Lossless
    var ts5 = DicomTransferSyntax.JPEG2000Lossless;
}

Transcoding Between Transfer Syntaxes

fo-dicom supports transcoding (changing transfer syntax):

public static void TranscodeExample(string inputPath, string outputPath)
{
    // Open original file
    var file = DicomFile.Open(inputPath);

    LogToDebugConsole($"Original: {file.FileMetaInfo.TransferSyntax.UID.Name}");

    // Transcode to JPEG Lossless
    var transcoded = file.Clone(DicomTransferSyntax.JPEGProcess14SV1);

    LogToDebugConsole($"Transcoded: {transcoded.FileMetaInfo.TransferSyntax.UID.Name}");

    // Save transcoded file
    transcoded.Save(outputPath);
}

public static void TranscodeWithParameters()
{
    // For lossy compression, you may specify quality parameters
    // This varies by codec and fo-dicom version

    // Example: JPEG quality (0-100)
    // var jpegParams = new DicomJpegParams { Quality = 90 };

    // Example: JPEG 2000 compression ratio
    // var j2kParams = new DicomJpeg2000Params { Rate = 20 };  // 20:1
}

Practical Considerations

Guidelines for choosing transfer syntax:

private static void DemonstratePracticalConsiderations()
{
    LogToDebugConsole("--- Practical Considerations ---");
    LogToDebugConsole("");

    LogToDebugConsole("Storage:");
    LogToDebugConsole("  - Use lossless for diagnostic images");
    LogToDebugConsole("  - JPEG 2000 Lossless for best ratios");
    LogToDebugConsole("  - Consider JPEG-LS for speed");
    LogToDebugConsole("");

    LogToDebugConsole("Network Transfer:");
    LogToDebugConsole("  - Negotiate supported syntaxes");
    LogToDebugConsole("  - Accept syntax requiring least transcoding");
    LogToDebugConsole("  - Explicit VR Little Endian widely supported");
    LogToDebugConsole("");

    LogToDebugConsole("Viewing/Display:");
    LogToDebugConsole("  - Web viewers may need JPEG for speed");
    LogToDebugConsole("  - Always decompress for measurements");
    LogToDebugConsole("  - Be aware of compression artifacts");
    LogToDebugConsole("");

    LogToDebugConsole("Regulatory/Legal:");
    LogToDebugConsole("  - FDA recommends lossless for mammography");
    LogToDebugConsole("  - Some jurisdictions prohibit lossy for legal");
    LogToDebugConsole("  - Document compression in DICOM attributes");
    LogToDebugConsole("  - Keep original as \"gold copy\" when compressing");
}

Best Practices

Use Explicit VR: Explicit VR Little Endian is preferred for network
Lossless for diagnostic: Always use lossless for original diagnostic images
Document lossy compression: Set Lossy Image Compression attributes
Test codec support: Verify your systems support required codecs
Avoid re-compression: Don't compress already lossy data
Keep originals: Maintain uncompressed "gold copy" when possible

Conclusion

Transfer Syntax is a fundamental DICOM concept that affects storage, transmission, and image quality. Understanding the trade-offs between different compression schemes helps you make informed decisions for your specific use cases.

For clinical applications, lossless compression is generally preferred to preserve diagnostic quality. However, lossy compression may be acceptable for certain viewing and communication scenarios, provided the limitations are understood and documented.

Please check out the next tutorial in this series where we cover DICOM character set handling.