What is DDS? DirectDraw Surface Texture Format Explained

How DDS Works

A DirectDraw Surface file is a container designed to hold texture data in a form the graphics processor can consume directly. Rather than storing a plain grid of pixels, a .dds file usually stores texture data that has already been compressed with one of the block compression schemes. These schemes divide the image into small fixed-size blocks, most commonly four pixels by four pixels, and encode each block using a compact representation of its colors. Because the block size is fixed, the compression is fixed-rate: the file size is predictable and does not depend on image content.

The original block compression families are widely known as DXT1, DXT3, and DXT5, which correspond to the later Direct3D names BC1, BC2, and BC3. Newer additions in the BCn family include BC4 and BC5 for one and two channel data such as height or normal maps, along with BC6H for high dynamic range color and BC7 for higher quality general color. The defining advantage of these formats is that the GPU can decode a block on the fly in hardware while sampling the texture, so the compressed data can stay compressed in video memory.

DDS files also commonly store a full mipmap chain. A mipmap chain is a sequence of progressively smaller versions of the same texture, each half the width and half the height of the previous level. When a surface is far from the camera or viewed at a shallow angle, the renderer samples a smaller mip level, which improves both image quality and memory bandwidth. Storing these levels in the file avoids generating them at load time.

Beyond flat textures, the format supports cube maps, which bundle six faces into a single texture used for environment reflections and sky boxes, as well as volume textures and texture arrays. The file header records the pixel format, dimensions, mip count, and surface type, so a renderer can upload the data to the GPU with little additional processing. This close alignment with how graphics hardware stores textures is the main reason DDS remains common in game and real time engine pipelines.

History and Standardization

The DDS format originates from Microsoft and is closely tied to the DirectDraw and later Direct3D components of the DirectX family. It was introduced as part of the DirectX software development kit to give developers a straightforward way to ship textures that mapped cleanly onto the surface types the graphics API already used. The name itself reflects that lineage.

The underlying block compression approach that DDS files carry was developed in the late 1990s as a texture compression technique and was subsequently integrated into Direct3D under the BCn naming. Over successive DirectX releases, Microsoft extended the format header to describe the newer block formats and additional surface types, which is why some tools distinguish between the legacy header and an extended header variant.

Rather than being governed by an independent standards body, DDS is defined by Microsoft documentation and by the behavior of the DirectX runtime and its tools. It became a de facto standard within game development because it matched the hardware and the dominant graphics API on Windows, and support was later added by many third party engines, image editors, and asset pipelines across multiple platforms.

DDS Compared to PNG and Modern Texture Containers

Compared with PNG, DDS is a fundamentally different tool. PNG is a lossless, general purpose image format that is excellent for authoring and distribution, but its data must be decoded to plain pixels and then re-encoded into a GPU friendly format before it can be used efficiently as a texture. DDS skips that step by storing the GPU ready block compressed data directly, at the cost of being lossy and less convenient to edit by hand.

Against newer texture containers such as KTX and the Basis Universal system, DDS shows its age in flexibility. KTX is designed to be cross platform and to carry textures for multiple graphics APIs, and Basis style formats add transcodable compression that can target different GPU block formats from a single asset. These modern options are often better suited to engines that must ship to a wide range of devices.

The honest trade off is that DDS remains simple, well understood, and extremely well supported inside the Windows and Direct3D world, which keeps it in heavy use for existing game pipelines. For new cross platform projects, a container like KTX or a Basis based workflow may offer more portability, while PNG stays the better choice for lossless source art that will be processed later.