Converting TGA to BMP produces uncompressed Windows bitmap data. Useful for feeding TGA textures into legacy Windows software or tools that only read BMP.
Drag & drop image files here, or browse
Drop your TGA files here
Lossless pixel preservation. File size grows if the TGA was RLE compressed; stays similar if it was already uncompressed. Alpha support in BMP is inconsistent across tools.
BMP works on every Windows version and most cross-platform viewers.
TGA (Targa) was developed in 1984 for Truevision graphics cards. It persists in game development, 3D rendering, and film VFX pipelines because it supports high bit-depths, an alpha channel, and optional run-length compression. Many DCC tools (Maya, Blender, ZBrush) use TGA for textures.
BMP is the uncompressed Windows bitmap format from 1990. Files are huge because almost nothing is compressed, but the format is trivial to decode and supported by virtually every Windows utility, embedded system, and legacy tool. Useful as an interchange format when other options fail.
In 32-bit BMP, technically yes; but many tools ignore BMP alpha. For reliable transparency use PNG.
Typically similar or slightly larger. Both are uncompressed or lightly compressed; BMP adds some padding and header overhead.
TGA (Targa) was developed in 1984 for Truevision graphics cards. It persists in game development, 3D rendering, and film VFX pipelines because it supports high bit-depths, an alpha channel, and optional run-length compression. Many DCC tools (Maya, Blender, ZBrush) use TGA for textures.
BMP is the uncompressed Windows bitmap format from 1990. Files are huge because almost nothing is compressed, but the format is trivial to decode and supported by virtually every Windows utility, embedded system, and legacy tool. Useful as an interchange format when other options fail.
Yes. The converter runs entirely in your browser using WebAssembly. Your images are never uploaded, never sent to a server, and never leave your device.
There's no hard limit, but because everything runs in your browser you're bounded by available memory. Very large images (over a few hundred megapixels) can hit browser memory limits. Process in smaller batches if you run into issues.