DDS to AVIF: Complete Conversion Guide for Game Textures

By Bill Crawford  ·  March 2026  ·  9 min read  ·  Last updated March 5, 2026

Connect on LinkedIn →

What Is the DDS Format?

DDS — DirectDraw Surface — is Microsoft's standard compressed texture format, introduced with DirectX 6 in 1998. It remains the dominant format for GPU-ready texture data in games and real-time 3D applications more than two decades later. Nearly every PC game released since 2000, and many console titles, stores texture assets as DDS files internally.

What makes DDS special is that its compression formats — collectively called BCn (Block Compression) — are designed to be decompressed directly by the GPU hardware, with zero CPU overhead. The GPU reads a DXT5 texture from VRAM just as fast as an uncompressed one. This is why games can have hundreds of megabytes of texture data on screen simultaneously without slowing down rendering.

The downside is that DDS files are essentially useless outside the specific context they were made for. Web browsers cannot display them. Most image editors require plugins. Sharing a DDS file with a non-developer is effectively sharing an unreadable file. Converting to a modern format like AVIF bridges that gap.

DDS Compression Formats Explained

DDS is not a single format — it is a container that holds one of several different GPU compression schemes. Understanding which scheme your file uses is important because it determines color fidelity, alpha channel behavior, and the right conversion approach.

DXT1/BC1 is the smallest format — 4 bits per pixel, exactly 8:1 compression compared to uncompressed RGBA. It works well for any opaque texture where the 2-color-per-block interpolation is not visible. Skyboxes, terrain, and solid walls are common DXT1 candidates.

DXT5/BC3 is the workhorse format. It stores color in BC1 blocks and alpha in a separate BC4-style block with two endpoint values and 8 interpolated steps. This gives smooth alpha gradients — essential for foliage, hair, glass, particles, and any texture with soft edges. Most game character diffuse textures with transparency use DXT5.

BC5 is specifically designed for normal maps. It stores only the Red and Green channels (the X and Y components of the surface normal), relying on the shader to reconstruct the Z component mathematically. When you open a BC5 normal map file, it appears as a blue-tinted image with the blue channel reconstructed from RG by the decoder.

BC7 is the modern high-quality option, introduced with DirectX 11. It uses a complex multi-mode scheme with partition data to achieve visibly better quality than DXT5 at the same bit rate — or much smaller files at equivalent quality. Most modern AAA games targeting PC use BC7 for their highest-quality texture assets.

What Is AVIF?

AVIF (AV1 Image File Format) is a modern image format derived from the AV1 video codec, developed by the Alliance for Open Media. It was finalized in 2019 and has since achieved broad browser and OS support. As of 2026, AVIF is supported by Chrome, Edge, Firefox, Safari 16.4+, Windows 11 Photos, and macOS Preview.

AVIF's key strength is compression efficiency. At equivalent visual quality, AVIF typically produces files 50% smaller than JPG and 30–40% smaller than WebP. It also supports full alpha channel transparency, wide color gamut, and HDR — capabilities JPG lacks entirely. For converting game textures that need to be shared or published on the web, AVIF is one of the best output choices available today.

When Should You Convert DDS to AVIF?

The most common scenarios for DDS-to-AVIF conversion are:

• Sharing texture assets. Game modders sharing their work, 3D artists posting portfolio pieces, or developers including texture previews in documentation all need a format that non-technical viewers can open. AVIF works in every modern browser.
• Web-based texture viewers. If you are building a web tool to preview game assets, AVIF is the most efficient format to serve texture previews. A 2 MB DXT5 texture may compress to under 200 KB as AVIF with minimal visible difference.
• Archiving extracted textures. When extracting textures from game packages for archival or reference, AVIF provides a good balance of file size and visual fidelity — much better than PNG for large diffuse textures.
• Cross-platform asset pipelines. Design teams that review assets across different operating systems and tools benefit from a universally readable format rather than DDS, which requires plugins on every machine.
• Social sharing and forums. Game modding communities and texture artist forums cannot embed DDS files directly. AVIF is accepted by all major platforms.

DDS vs AVIF: Format Comparison

Choosing the Right Quality Setting

The AVIF quality slider controls the AV1 encoder's quantization parameter. Higher quality means more bits used to preserve detail, larger output files, and less visible difference from the source. Here are practical guidelines:

• Quality 90–100: Near-lossless. Recommended for archival, reference, or any texture where accuracy matters. Files will be larger but the visual difference from the decoded DDS source is negligible.
• Quality 80–89: Excellent quality for most uses. Diffuse textures, UI assets, and normal maps at this range look effectively identical to the source at normal viewing distances. A good default for portfolio or documentation use.
• Quality 70–79: Good for web thumbnails, preview images, or any context where file size is more important than pixel-perfect fidelity. Slight softening is visible on close inspection but not at standard display sizes.
• Quality 50–69: Aggressive compression. Appropriate only for tiny thumbnails or situations where bandwidth is severely constrained.

The default quality of 85 is a reasonable balance for general-purpose conversion of game textures. DXT5 and BC7 source files are already lossy, so adding moderate AVIF compression is unlikely to produce objectionable artifacts unless the texture contains fine high-frequency detail.

Alpha Channel Handling

One of the most important considerations when converting game textures is alpha channel preservation. Different DDS formats handle alpha differently, and the output treatment matters for how the AVIF will look.

DXT1 (BC1) files may have either no alpha or 1-bit (punch-through) alpha. 1-bit alpha means each pixel is either fully opaque or fully transparent — there are no semitransparent values. The converter preserves this, so the output AVIF will also have binary transparency.

DXT5 (BC3) and BC7 files store full 8-bit alpha gradients. Foliage textures with soft leaf edges, character hair with smooth opacity transitions, and particle textures all rely on smooth alpha. The converter passes this directly to the AVIF encoder, which supports full 8-bit alpha. The result is a file that can be used anywhere PNG would work, with better compression.

BC5 normal map files have no alpha channel — they use two 8-bit channels (R and G) for X and Y normal components. The converter reconstructs the Z (blue) channel for display purposes, so the AVIF output shows a human-readable blue-tinted normal map rather than the raw RG data. This is the expected behavior for visual review, though the reconstructed Z is not mathematically exact for every normal direction.

Best Practices for DDS to AVIF Conversion

• Use Chrome or Edge. Both browsers support AVIF encoding via the Canvas API's toBlob method. Firefox 93+ also supports it. Safari's encoding support via canvas.toBlob is limited — use Chrome for reliable AVIF output.
• Convert the mip level 0 only. DDS files may contain multiple mip levels at decreasing sizes. This tool decodes the base (largest) mip level — mip 0. This gives the highest-resolution output.
• Batch similar textures together. The tool processes files sequentially two at a time. Grouping similar textures by quality need (e.g., all normal maps at q90, all diffuse at q85) makes workflow cleaner than converting mixed sets.
• Use ZIP for large batches. Downloading 50+ individual AVIF files is impractical. Enable the ZIP option before converting large batches.
• Keep originals. Converting DDS to AVIF is lossy. Always keep the original DDS files if you may need them for actual game engine use. AVIF is for sharing and viewing, not for re-importing into a game engine.

Related Tools