ConvertBlink
EN

TGA to PNG Converter: Open Targa Files Anywhere

Convert Truevision TGA (Targa) files to PNG right in your browser. Lossless, keeps the alpha channel, handles RLE and uncompressed, nothing uploaded.

Browser Native
Privacy First
Free Tool

Convert Now

Drag & drop your file here

or

How It Works

Truevision shipped the Targa format in 1984 for early true-color capture boards, and it never left game and VFX pipelines. Crack open almost any Unity, Unreal, or Source project and you will find diffuse maps, normal maps, and UI sprites saved as .tga, because it stores a clean alpha channel and never runs the pixels through a lossy codec. The catch is that almost nothing outside a production tool will show you the file. Browsers don't decode TGA, macOS Preview and the Windows Photos app give up on it, and plenty of image libraries skip it entirely. This converter bridges that gap without sending your asset anywhere. Decoding runs through @lunapaint/tga-codec, a pure-JavaScript reader. It parses the 18-byte TGA header to identify the image type, then reads the pixel data the right way: uncompressed scanlines or run-length-encoded (RLE) packets, 16/24/32-bit color, grayscale, and color-mapped (indexed/palette) variants. Bottom-left vs top-left origin is resolved by the codec, so rows come out the right way up, and everything is normalized to 8-bit RGBA. Those RGBA pixels go into an ImageData buffer, get painted onto an OffscreenCanvas, and come back out as a PNG. TGA and PNG are both lossless, so the round trip is pixel-exact: same colors, same transparency, no generation loss. One real-world Targa quirk is handled on purpose. Some 32-bit files ship with a zeroed alpha channel that would make the whole image read as invisible, so ambiguous-alpha detection is enabled to treat those as fully opaque instead of fully transparent. The whole thing runs in your browser tab. The file is read into memory, decoded, and offered back as a PNG download with nothing leaving the machine, which is the point when the asset is an unreleased game texture under NDA.

Related Conversion Tools

Discover more powerful converters that might be useful for your workflow

AVIF to PNG Converter: Decode AV1 Images in Browser

Decode AVIF (AV1) images to lossless PNG in your browser, with transparency kept pixel for pixel. No uploads, no server, fully private and free.

.avif
Try Now

Base64 to PNG: Decode Data URIs in Your Browser

Paste a Base64 string or data: URI and decode it to a PNG locally. Keeps alpha transparency, no uploads, no server. Pure client-side decode.

.txt
Try Now

Compress WebP: Re-Encode an Existing WebP Smaller

Re-compress an existing WebP to a smaller WebP entirely in your browser. Lossy re-encode at quality 82, never inflates, no uploads, fully private.

.webp
Try Now

Image Optimizer: Shrink JPG, PNG, WebP, Same Format

Compress JPG, PNG, or WebP without changing format. PNG stays truly lossless via oxipng; JPEG and WebP re-encode smaller. Runs in your browser, no uploads.

.jpg.jpeg +2
Try Now

QOI to PNG Converter: Decode Quite OK Images Free

Decode QOI (Quite OK Image) files to PNG right in your browser. Lossless, no uploads, opens .qoi assets in editors and browsers that can't read QOI.

.qoi
Try Now

PNG to QOI Converter: Lossless Quite OK Image Encode

Encode PNG to QOI (Quite OK Image) in your browser. Lossless, single-pass, no uploads. Built for game engines, asset bakers and decoder testing.

.png
Try Now

Convert toPNG

avif → pngbase64 → pngbmp → pnggif → pngheic → png
View All Converters

Key Features

  • No file uploads required - works offline
  • 100% privacy focused - client-side processing
  • Browser powered - no software installation
  • Fast processing - WebAssembly technology
  • Free forever - no premium accounts

Supported File Formats

.tga

Output Format: PNG

Technical Specifications

input Format TGA / Truevision Targa (.tga, .tpic; uncompressed & RLE, 16/24/32-bit, grayscale, color-mapped)
output Format PNG (Portable Network Graphics, 8-bit RGBA)
compression Type Lossless to lossless (RLE/raw TGA decoded, DEFLATE-compressed PNG)
quality Retention Pixel-exact, identical color and alpha, no generation loss
color Space Support RGB and RGBA with full 8-bit alpha; grayscale and palette images expanded to RGBA
max Resolution Limited only by your device's memory
processing Time Instant, runs in your browser

Key Benefits

  • Opens TGA files that browsers and default OS image viewers refuse to display
  • Lossless conversion, so the PNG is pixel-identical to the source Targa
  • Preserves the full 8-bit alpha channel that TGA is valued for
  • Decodes RLE-compressed, uncompressed, grayscale, and color-mapped TGA automatically
  • Fixes the zeroed-alpha case that makes some TGA files look fully transparent elsewhere
  • Runs entirely in your browser with no uploads, accounts, watermarks, or file caps
  • Works on any modern browser and OS without installing software

Common Use Cases

  • Previewing Unity, Unreal, or Source engine texture assets shipped as .tga
  • Bringing 3D model textures from 3ds Max, Maya, or Blender into web and design tools
  • Sending a Targa render to a reviewer who can't open TGA on their machine
  • Prepping TGA artwork for the web, where PNG or WebP is expected
  • Inspecting a TGA alpha mask in an ordinary image viewer
  • Migrating legacy TGA archives into a format every tool still reads
  • Recovering a TGA that looks blank or transparent in other software

Pro Tips

  • Keep PNG as the target when your TGA has transparency; it carries the alpha through exactly
  • If a TGA looked transparent or blank elsewhere, try it here, since ambiguous alpha is auto-corrected
  • You don't need to know whether your file is RLE or uncompressed; both are detected from the header
  • For opaque photos where file size beats fidelity, convert TGA to JPG instead for smaller files
  • Keep the original .tga if your game or render pipeline expects that exact format
  • Large textures (4K and up) use more memory; close other heavy tabs if a huge file stalls

Frequently Asked Questions

TGA predates the web and stayed niche outside graphics production, so it never picked up native support in browsers or in the default image viewers on Windows and macOS. A file that opens fine in Photoshop or a game engine shows nothing in Chrome, Preview, or Windows Photos. Converting to PNG gives you the exact same pixels in a format every viewer, editor, and browser reads.
No. TGA and PNG are both lossless raster formats, so this is a pixel-for-pixel rewrite, not a recompression. Every color value and the full alpha channel carry over exactly. There is no quality slider and no generation loss, unlike exporting to JPG, which would throw detail away.
Yes, and that is usually the whole reason to pick PNG as the target. The decoder pulls the 8-bit alpha out of 32-bit TGA files and writes it straight into the PNG, so transparent and semi-transparent pixels look identical. PNG supports full alpha natively, so nothing gets flattened or approximated.
Yes. The header is read first, then the right decode path is taken automatically: uncompressed or run-length-encoded data, 16/24/32-bit true color, grayscale, and color-mapped (palette) images all work. You don't need to know or set which variant your file is.
This is a known Targa edge case: some files write 32-bit pixels but leave the alpha bytes at zero, which strict decoders read as fully invisible. Ambiguous-alpha detection is turned on, so those files are treated as opaque and render correctly instead of disappearing.
No. The conversion runs entirely in your browser. The TGA is read into local memory, decoded, and re-encoded to PNG on your own device. Nothing is sent to a server, logged, or stored, which makes it safe for proprietary or pre-release game and film assets.
Use PNG if the image has transparency or you want a lossless copy, which covers most TGA textures, sprites, and masks. Choose JPG only for opaque photographic content where a smaller file matters more than perfect fidelity, since JPG drops the alpha channel and recompresses lossily.
There is no fixed cap beyond what your device can hold in memory, since the file is decoded in the browser rather than uploaded. Very large textures, roughly 4K and up, use noticeably more RAM during the canvas step, so close other heavy tabs if a huge file stalls.