TGA (Targa)

Targa — or more accurately: the TGA format — was for a long time the standard exchange format for VFX shots that required transparency. The reason lies in its elegance: RGB data plus a separate alpha channel, uncompressed or with RLE compression, small enough for network transfers, large enough for professional color depth. On set or in the edit, you notice this immediately — as soon as you need a compositing element that should lie over other material instead of just being a rectangular box, you pack it as a TGA.

Its practical strength lies in its reliability across platforms. Linux render farm, Windows compositing station, Mac editing suite — TGA loads everywhere. No surprises with gamma, no suddenly missing channels like with JPEGs. You save your VFX elements — particle passes, matte paintings, roto'd-out objects — as a sequence of TGAs, numbered from 0001 to 2400, and the compositing software reads them in its sleep. Particularly important: the alpha channel is truly lossless. This means your mattes remain razor-sharp, the edges of your explosions or chroma keyer cutouts retain their precision over multiple generations.

In the modern workflow hierarchy, TGA has long faced competition — EXR is now the standard for multi-channel work, and ProRes with Alpha is displacing TGA in offline editing. However, in larger VFX studios, especially with older pipelines or in houses with heterogeneous software setups, you still see TGA sequences as an exchange format between departments. Some render engines (especially Arnold, RenderMan in older versions) output TGA natively as their native output format — it's reliable, it's proven. For you, this means: if you're unsure which format the VFX supervisor will accept, don't hesitate — TGA is the safe bet. File sizes are moderate, compression is transparent (literally: RLE reduces size without discarding data), and in four decades of film production, no one has complained about a correctly created TGA package.