Texture compression formats for platform-specific overrides

While Unity supports many common image formats as source files for importing your TexturesAn image used when rendering a GameObject, Sprite, or UI element. Textures are often applied to the surface of a mesh to give it visual detail. More info
See in Glossary (such as JPG, PNG, PSD and TGA), these formats are not used during realtime renderingThe process of drawing graphics to the screen (or to a render texture). By default, the main camera in Unity renders its view to the screen. More info
See in Glossary by 3D graphics hardware such as a graphics card or mobile device. 3D graphics hardware requires Textures to be compressed in specialized formats which are optimised for fast Texture sampling. The various different platforms and devices available each have their own different proprietary formats.

By default, the Unity Editor automatically converts Textures to the most appropriate format to match the build target you have selected. Only the converted Textures are included in your build; your source AssetAny media or data that can be used in your game or Project. An asset may come from a file created outside of Unity, such as a 3D model, an audio file or an image. You can also create some asset types in Unity, such as an Animator Controller, an Audio Mixer or a Render Texture. More info
See in Glossary files are left in their original format, in your project’s Assets folder. However, on most platforms there are a number of different supported Texture compression formats to choose from. Unity has certain default formats set up for each platform, but in some situations you may want to override the default and pick a different compression format for some of your Textures (for example, if you are using a Texture as a mask, with only one channel, you might choose to use the BC4 format to save space while preserving quality).

To apply custom settings for each platform, use the Texture Importer to set default options, then use the Platform-specific overrides panel to override those defaults for specific platforms.

The following table shows the default formats used for each platform.

All supported Texture compression formats

The following table shows the Texture compression format options available on each platform, and the resulting compressed file size (based on a 256px-square image). Choosing a Texture compression format is a balance between file size and quality; the higher the quality, the greater the file size. In the description below, see the final file size of a in-game Texture of 256 by 256 pixelsThe smallest unit in a computer image. Pixel size depends on your screen resolution. Pixel lighting is calculated at every screen pixel. More info
See in Glossary.

When you use a Texture compression format that is not supported on the target platform, the Textures are decompressed to RGBA 32 and stored in memory alongside the compressed Textures. When this happens, time is lost decompressing Textures, and memory is lost because you are storing them twice. In addition, all platforms have different hardware, and are optimised to work most efficiently with specific compression formats; choosing non-compatible formats can impact your game’s performance. The table below shows supported platforms for each compression format.

Notes on the table below:

• RGB is a color model in which red, green and blue are added together in various ways to reproduce a broad array of colors.

• RGBA is a version of RGB with an alpha channel, which supports blending and opacity alteration.

• Crunch compression is a lossy compression format (meaning that parts of the data are lost during compression) on top of DXT or ETC Texture compression. Textures are decompressed to DXT or ETC on the CPU, and then uploaded to the GPU at run time. Crunch compression helps the Texture use the lowest possible amount of space on disk and for downloads. Crunch Textures can take a long time to compress, but decompression at run time is very fast.

You can import Textures from DDS files, but only DXT, BC compressed formats, or uncompressed pixel formats are supported.

Notes on Android

Unless you’re targeting specific hardware (such as Tegra), ETC2 compression is the most efficient option for Android, offering the best balance of quality and file size (with associated memory size requirements). If you need an alpha channel, you could store it externally and still benefit from a lower Texture file size.

You can use ETC1 for Textures that have an alpha channel, but only if the build is for Android and the Textures are placed on an atlas (by specifying the packing tag). To enable this, tick the Compress using ETC1 checkbox for the Texture. Unity splits the resulting atlas into two Textures, each without an alpha channel, and then combines them in the final parts of the render pipeline.

To store an alpha channel in a Texture, use RGBA16 bit compression, which is supported by all hardware vendors.

• 2017–11–20 Page amended

• Linear rendering on WebGL added in 2017.2 NewIn20172

• Crunch compression format updated in 2017.3 NewIn20173

• Tizen and Samsung TV support discontinued in 2017.3 NewIn20173