How do I open a KTX2 file online?
Upload a .ktx2 or .ktx file to preview it in the browser, inspect RGBA channels, and export common image formats.
Free online KTX2 viewer and decoder. Open, inspect, and preview .ktx2 files (UASTC, ETC1S, Basis Universal, HDR) directly in your browser without upload. Convert KTX2 to PNG instantly.
Drag and drop a KTX2 file here
or
Supports both UASTC and ETC1S compressed KTX2 files
Effortlessly inspect KTX2 (Basis Universal) textures exported from Three.js, Babylon.js, PlayCanvas, or glTF/GLB 3D assets.
Instantly view decoded textures with interactive zoom and pan controls
View individual RGBA channels or combined RGB output
Export decoded textures as standard PNG images
View comprehensive metadata including format, dimensions, and compression type
Drag and drop or click to select a .ktx2 file from your computer
The browser decodes the base mip level using WebAssembly (supporting ETC1S, UASTC, and common formats)
Use channel filters and zoom controls to examine the texture in detail
Download the decoded base-level preview as a PNG file or choose other image formats
Drag and drop or select your .ktx2 file directly in this page. The WebAssembly decoder transcodes and displays your texture base mip level in your browser with interactive zoom, channel inspection, and PNG preview export—no software installation required.
The viewer accepts standalone .ktx2 or .ktx files; textures embedded inside glTF or GLB files must be extracted before uploading. For Three.js projects using the KTX2Loader runtime loading pipeline or assets configured with KHR_texture_basisu, you can upload and preview the standalone Basis Universal (ETC1S or UASTC) texture files directly.
No, all decoding happens locally in your browser. Your files never leave your device, ensuring complete privacy and security.
In modern PBR 3D pipelines, Roughness, Metalness, and Ambient Occlusion (AO) are often packed into R, G, and B channels. Channel isolation lets technical artists verify ORM map channels individually without desktop tools.
You can export the decoded texture as PNG, which represents the transcoded raster output of the base mip level. Note that lossy compression means the result will not be pixel-identical to the pre-compressed source image, and PNG export does not retain container mipmaps.
KTX2 commonly uses lossy compression, so minor visual differences can occur. ETC1S favors smaller file sizes and lower transmission bandwidth, while UASTC favors detail preservation. In practice, visual quality should be evaluated by comparing the transcoded output within your target rendering pipeline.
The current preview displays the base mipmap level. Support for viewing all mipmap levels is planned for a future update.
Any modern browser with WebAssembly support can run the decoder, including Chrome, Firefox, Safari, and Edge.
Upload a .ktx2 or .ktx file to preview it in the browser, inspect RGBA channels, and export common image formats.
Yes. The decode preview can export PNG directly, along with JPG, WebP, AVIF, TIFF, BMP, TGA, PPM, and PGM.
Exporting to PNG outputs the decoded SDR base mipmap raster pixels for viewing. Neither PNG export nor our KTX2 to DDS workflow preserves the original GPU payload or guarantees full original asset retention; converting KTX2 to DDS decodes the texture pixels first and then re-encodes them into the target DDS format.