TGA to AVIF: Complete Conversion Guide for Game Art & Web

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

Connect on LinkedIn →

What Is the TGA Format?

TGA — short for Targa Graphics Adapter — is a raster image format developed by Truevision Inc. in 1984. Originally created for use with Truevision's video boards, TGA became one of the dominant formats in game development, 3D animation, and visual effects pipelines throughout the 1990s and 2000s. Despite its age, TGA remains in active use today across many game engines, 3D rendering tools, and texture authoring workflows.

What makes TGA particularly useful in game development is its simplicity and flexibility. It supports 8-bit grayscale, 16-bit, 24-bit RGB, and 32-bit RGBA (with full alpha channel) pixel data. It can store data as uncompressed raw bytes or using a simple RLE (run-length encoding) compression scheme. This makes TGA files trivial to parse and write, which explains their longevity in pipelines that prioritize reliability and speed over file size.

Common use cases for TGA files include: diffuse textures, normal maps, specular maps, and alpha masks exported from game engines like Unreal Engine and Unity; render output from 3D applications like Blender, Maya, 3ds Max, and Cinema 4D; and intermediate files in compositing pipelines using software like Adobe After Effects or Nuke.

What Is the AVIF Format?

AVIF (AV1 Image File Format) is a modern, royalty-free image format derived from the AV1 video codec. Developed by the Alliance for Open Media (AOMedia) and first published in 2019, AVIF is designed to replace older lossy formats like JPEG for web images. By 2026, AVIF is supported natively in Chrome, Edge, Firefox, and Safari 16+, covering the vast majority of web users.

AVIF's compression advantage over JPEG is substantial — typical savings range from 40% to 70% at equivalent visual quality. AVIF also supports a range of features that JPEG does not: full alpha channel transparency, HDR and wide color gamut, lossless compression modes, and animation. For game art and rendered imagery being published to the web, AVIF is one of the most efficient delivery formats available.

When Should You Convert TGA to AVIF?

TGA files are optimized for offline workflows: fast I/O, lossless data, and broad toolchain compatibility. They are not optimized for web delivery. AVIF occupies the opposite position: excellent compression, wide browser support, and no offline toolchain requirement. The conversion from TGA to AVIF makes sense in several scenarios:

• Web portfolios and galleries. Game artists and 3D artists frequently maintain web portfolios showcasing texture work, concept art, or render sequences. Publishing these directly from TGA would result in very large page loads. Converting to AVIF reduces asset size dramatically while preserving visual quality.
• Game mod distributions. Some game mods include modified TGA texture files. When distributing screenshots, preview images, or comparison galleries on mod hosting sites, converting TGA previews to AVIF reduces download burden for visitors.
• Documentation and wiki assets. Game development documentation, wikis, and tutorials often reference texture assets. AVIF-encoded versions of TGA textures are far more suitable for embedding in web pages than the raw TGA files.
• Build pipeline outputs. Automated build systems that produce TGA render sequences can convert outputs to AVIF as a post-processing step for web review tools, preview dashboards, or client-facing galleries.

TGA vs AVIF: Format Comparison

Alpha Channel: What to Know

Many TGA files used in game development are 32-bit RGBA — the fourth channel carries alpha transparency data used for things like opacity masks, cutout geometry, and decal blending. When converting TGA to AVIF, preserving this alpha channel is often essential.

AVIF natively supports alpha transparency in both lossy and lossless modes. When you convert a 32-bit TGA to AVIF using the browser-based tool on this site, the alpha channel is fully preserved through the canvas rendering pipeline and encoded into the AVIF output. The result is an AVIF file that retains the transparency information from the original TGA, ready for use in web contexts where alpha compositing is needed.

If you are converting 24-bit TGA files (no alpha channel), the AVIF output will also have no alpha channel. The converter handles both 24-bit and 32-bit TGA inputs transparently.

AVIF Compression and Quality

AVIF is a lossy format by default, similar to JPEG. The quality level determines the trade-off between file size and visual fidelity. Unlike JPEG, which uses a 0–100 quality scale, AVIF quality is typically controlled through a quantizer parameter — but when using the browser's canvas.toBlob('image/avif', quality) API, quality is expressed as a 0.0–1.0 value.

The TGA to AVIF converter on this site uses a quality setting of 0.85, which produces excellent visual results for game textures and artwork. At this quality level, the output is visually indistinguishable from the original TGA for most content, while achieving file size reductions of 60–90% compared to the raw TGA.

For scenarios where pixel-perfect accuracy is required — such as archiving master texture assets — lossless PNG is a more appropriate target format. AVIF is best suited for delivery and display contexts where visual quality matters more than bit-for-bit accuracy.

Browser AVIF Support in 2026

As of early 2026, AVIF display support covers the vast majority of browsers in active use:

• Chrome 85+: Full AVIF support for display and canvas encoding
• Edge 85+: Full AVIF support (Chromium-based)
• Firefox 93+: AVIF display support; canvas encoding support varies
• Safari 16+: AVIF display support; canvas encoding support varies by version

For the browser-based TGA to AVIF conversion tool, AVIF encoding via canvas.toBlob works reliably in Chrome and Edge. If your browser cannot encode AVIF, the tool will display a warning and fall back to PNG output so you are never left without a usable output file.

Understanding TGA File Structure

TGA files have a relatively simple binary structure that makes them easy to parse in JavaScript. The file begins with an 18-byte header containing fields for image type, dimensions, bit depth, and an orientation flag. Following the header is an optional image ID field (variable length), an optional color map (for indexed color images), and then the raw pixel data.

The most common TGA variants in game development are:

• Type 2 — Uncompressed RGB/RGBA: The most common type. Raw pixel data stored in BGR or BGRA byte order (blue first, not red). A 1024×1024 32-bit type-2 TGA is approximately 4 MB uncompressed.
• Type 10 — RLE-compressed RGB/RGBA: Pixel data compressed using run-length encoding. Often used for textures with large uniform areas. Compression ratio varies widely — flat-color textures compress well; highly detailed textures may see little benefit.
• Type 3 / Type 11 — Grayscale (uncompressed/RLE): Single-channel images used for normal map components, heightmaps, and masks.

The TGA orientation flag determines whether pixel rows are stored bottom-up (the historical default) or top-down. Many tools produce bottom-up TGA files, which require vertical flipping during decode. The converter handles both orientations automatically.

Software That Produces TGA Files

TGA output is supported by virtually every major image editing, 3D, and game development tool:

• Unreal Engine: Exports many built-in textures and allows texture export to TGA from the Content Browser
• Blender: Supports TGA as both input and output in its image editor and compositor
• Autodesk Maya and 3ds Max: Long-standing TGA render output support
• Adobe Photoshop: Full TGA read/write support including 32-bit alpha layers
• Substance Painter / Designer: Exports texture maps in TGA format
• GIMP: Native TGA read/write support
• Paint.NET: Reads TGA with the appropriate plugin

When Not to Convert TGA to AVIF

While AVIF is excellent for web delivery, there are scenarios where keeping the TGA original — or choosing a different format — is more appropriate:

• Game engine input textures: Game engines like Unreal Engine and Unity have their own internal texture compression formats (DXT, ASTC, BC7, etc.). They typically accept PNG or TGA as source input and handle compression internally. Do not use AVIF as game engine texture input — convert to PNG or keep TGA.
• Archival and master storage: For long-term archival of master texture assets, lossless formats (TGA, PNG, TIFF) are preferable to avoid any generation loss from re-encoding.
• Environments without AVIF support: Some older CMS platforms, e-mail clients, and legacy browsers do not support AVIF. In those contexts, PNG or WebP may be more appropriate.

Frequently Asked Questions