What KTX2 means in Microsoft Flight Simulator, when add-on creators should use it, and why converting DDS files rarely improves performance.
KTX2 (Khronos Texture 2.0) is a texture container designed for efficient GPU delivery and able to carry mipmaps plus compressed image data. In Microsoft Flight Simulator, it is an add-on-development format rather than a visual-upgrade switch. Use it only through the supported SDK pipeline for the simulator version you target; do not convert working textures just for performance.
What does a KTX2 texture actually contain?
KTX2 is a container, not a compression method by itself. A .ktx2 file can hold GPU block-compressed data, a transcodable Basis Universal payload, mip levels and information describing how the texture should be interpreted.
That distinction matters because two KTX2 files can have very different quality, storage and runtime characteristics. The encoder settings, source resolution, mipmaps and treatment of colour, normal and material maps matter more than the filename extension.
For someone installing a finished add-on, KTX2 requires no separate plug-in or manual conversion. Install the complete package supplied by its creator; for aircraft, our MSFS aircraft installation checks explain the correct Community-folder structure and common nesting mistake.
Should add-on creators use KTX2?
Use KTX2 when the SDK, exporter and package builder for your target Microsoft Flight Simulator version explicitly support it and you can test the resulting package. It is most relevant to the MSFS 2024 content pipeline; MSFS 2020 add-ons normally use its established DDS-centred workflow.
| Situation | Recommended choice | Reason |
|---|---|---|
| Installing a finished add-on | Keep the supplied files unchanged | The package's materials and file references were built for that format. |
| Creating an MSFS 2024-only add-on | Use KTX2 where the target SDK supports the texture type | It can provide efficient packaging and platform-appropriate texture delivery. |
| Supporting MSFS 2020 and 2024 | Keep lossless masters and produce separate builds | A KTX2 file accepted by the 2024 pipeline should not be assumed to work in a 2020 package. |
| Editing an existing repaint or texture | Follow the add-on's existing build workflow | Converting an already compressed DDS or JPEG can add artefacts without delivering a useful saving. |
Do not place loose KTX2 files in the Community folder or rename .dds to .ktx2. Changing the extension does not convert the contents, and changing the format without rebuilding material references can leave an aircraft untextured or prevent part of the package from loading correctly.
Does KTX2 improve FPS, VRAM use or texture quality?
KTX2 does not automatically increase frame rate, reduce VRAM use or sharpen textures. It may reduce package or download size, but memory consumption after loading depends on the final GPU format, texture dimensions, mip levels and number of textures in use.
Image quality likewise comes from the source and encoding choices. Excessive compression can produce colour blocks, damaged alpha edges, noisy normal maps or poor material reflections. Missing or badly generated mipmaps can make textures shimmer nearby or become soft too early.
If the whole simulator looks blurred rather than one KTX2-based add-on, check render scaling, texture resolution, anisotropic filtering, VRAM pressure and level-of-detail settings. Our blurry MSFS scenery troubleshooting guide covers those wider causes.
Why do converted KTX2 textures fail, and how do you fix them?
Most KTX2 failures come from an unsupported target, incorrect material treatment or an incomplete package rebuild rather than from the container itself.
- Wrong simulator target: a package built for the MSFS 2024 texture pipeline is not automatically backwards-compatible with MSFS 2020.
- Colour-space mistakes: base-colour textures and linear data maps must not be encoded identically. Treating a normal map or channel-packed PBR mask as ordinary sRGB colour can corrupt shading.
- Double compression: converting a low-quality JPEG or previously compressed DDS compounds existing artefacts. Return to the original lossless artwork.
- Broken references: the model or material may still point to the former DDS filename after conversion.
- Missing mipmaps or alpha: these faults may appear only at a distance, around transparent edges or under particular lighting.
Safe KTX2 conversion workflow
- Choose the target first. Build against the SDK and exporter intended for MSFS 2020 or MSFS 2024 rather than using a generic converter and hoping the output loads.
- Preserve master artwork. Keep an uncompressed or lossless source for every texture so you can change encoding without repeatedly recompressing it.
- Identify the map type. Configure base colour, normal, emissive, alpha and packed material maps according to their data rather than applying one preset to all files.
- Generate the full mip chain. Let the supported build pipeline create and validate mipmaps unless the SDK workflow specifically expects prepared levels.
- Perform a clean package build. Check the build log for rejected formats, unresolved references and material errors; copying only the new texture file is not enough.
- Test the add-on in isolation. Check close and distant views, different lighting and VRAM-heavy locations. When several Community packages are involved, isolating packages with MSFS Addons Linker can expose a conflict or stale duplicate.
If an existing add-on works and its textures look correct, leave its format alone. Adopt KTX2 for a new MSFS 2024 build when the supported toolchain calls for it or testing shows a useful packaging benefit; retain a separate, version-appropriate build when MSFS 2020 compatibility is required.