Convert Truevision TARGA (.tga) textures to PNG in your browser—up to 20 files, 100.00 MB each, with alpha preserved for 32-bit sources. Browse more on Free tools, shrink outputs with the PNG Compressor, or resize via the Image Resizer.
PNG options
Keeps 32-bit TGA transparency in RGBA PNG. Off composites onto white.
zlib 1–9
Higher levels spend more CPU on DEFLATE; default 6 balances speed and file size for textures and UI captures.
TGA decode and PNG encode run locally with pako zlib—files are not uploaded to SynthQuery. Supports uncompressed and RLE truecolor, indexed, and grayscale modes common in game pipelines.
TGA files
Drop TGA here or click to browse
Up to 20 files · max 100.00 MB each · 100% client-side
About this tool
Truevision TARGA—almost always seen on disk as a .tga file—survives wherever game engines, modding communities, and legacy 3D pipelines still ship raw pixels without wrapping them in DXT blocks or modern container formats. That persistence is a double-edged sword: TGAs are excellent at holding crisp RGB and optional alpha exactly as artists authored them, yet browsers, email clients, and many CMS media libraries still greet the extension with blank stares. SynthQuery’s TGA to PNG Converter is the lightweight bridge. You load up to twenty files at a hundred megabytes each, watch each row decode locally into a thumbnail preview, choose whether thirty-two-bit transparency should survive into RGBA PNG or flatten onto white for downstream tools that fear alpha, and dial PNG zlib effort from one through nine so you can favor speed on a huge texture batch or squeeze bytes for downloadable asset packs. Nothing leaves your machine for conversion—the decoder walks the TARGA header, optional color map, and image data (uncompressed or RLE) in JavaScript, then the same lossless PNG stack we use elsewhere packs filtered scanlines with DEFLATE. Whether you are normalizing Source engine dumps, Unreal exports, or archival renders from a DCC tool that still defaults to TGA for multipass compositing, this page keeps the workflow inside a tab you can open on a locked-down workstation. Scroll for step-by-step usage, pipeline-oriented use cases, and a FAQ that demystifies alpha bits, RLE packets, and when PNG is the right handoff versus keeping masters in EXR or PSD.
What this tool does
SynthQuery emphasizes inspectable, repeatable conversion instead of mystery “auto” buttons. TGA inputs pass through a purpose-built decoder that understands image types one through three and nine through eleven—indexed color with embedded palettes, uncompressed truecolor at sixteen, twenty-four, or thirty-two bits per pixel, grayscale eight- or sixteen-bit, plus the RLE variants that halve disk size for many studio textures. Row order follows the TARGA image descriptor: when the top-origin bit is clear, the decoder flips vertically so the PNG matches what artists saw in their viewers; when it is set, pixels map directly into a top-down RGBA raster. Alpha handling mirrors the BMP and TIFF converters: preserving alpha keeps partial transparency for foliage, glass, and decal stacks, while disabling it premultiplies against white and emits RGB PNG for slide decks or CMS fields that flatten everything. PNG output remains mathematically lossless for the samples you encode—zlib level adjusts encoder effort, never bit depth. Batch mode applies the same alpha policy and compression level across the queue, which keeps mod packs and documentation sets consistent. Byte readouts beside each filename show honest before-and-after archive sizes so you can explain to producers why PNG might grow relative to RLE TGA in pathological noise cases or shrink dramatically when DEFLATE finds long runs. ZIP export never touches SynthQuery disks; only your CPU, RAM, and storage participate. Keyboard-accessible drop zones, labeled switches, slider associations, and decorative preview thumbnails with empty alt text keep the interface aligned with WCAG-minded patterns used across other utilities. Unsupported combinations—exotic sixteen-bit alpha layouts you rarely see outside research archives, corrupted RLE packets, or dimensions beyond sixteen thousand pixels—surface as per-row errors you can retry after re-exporting from your DCC tool.
Technical details
TARGA stores an eighteen-byte header followed by an optional image ID field, optional color map, and image data. Truecolor types pack pixels as blue-green-red or blue-green-red-alpha depending on bit depth; indexed types store eight-bit indices into a BGR or BGRA map; RLE packets alternate raw runs with replicated pixels using the high bit of the control byte. PNG, standardized as ISO/IEC 15948, describes dimensions in IHDR, uses filter type zero per scanline in this encoder path, and wraps zlib-compressed image bytes in IDAT chunks. Both formats are lossless at the sample level you choose: TGA often stores pixels literally (or with run-length coding), while PNG applies reversible filtering plus DEFLATE. Transparency in thirty-two-bit TGA maps cleanly to PNG color type six (RGBA); twenty-four-bit sources become opaque RGB PNG unless you intentionally flatten. Neither format is inherently smaller—noisy albedo maps may compress modestly—yet PNG’s filters frequently win on gradients and UI-like regions. Metadata expectations differ: TGAs seldom carry EXIF the way JPEG or HEIC do; PNG can host ancillary text chunks, but this tool does not synthesize them from TGA headers—what you see is what the decoder reads as pixels. For regulated pipelines, log whether alpha was preserved and whether immutable originals remain in cold storage.
Use cases
Game modders unpacking texture folders from older titles often inherit thousands of TGAs; batching them here yields PNGs that Discord, GitHub, and wikis display inline without plugins. Technical artists building shader graphs can convert reference TGAs into PNG for quick browser-based reviews while keeping EXR masters for HDR work. Archivists digitizing nineties-era art packs normalize on PNG for consistent HTTP caching and predictable color types in public repositories. Marketing teams receiving TGA stills from cinematics pipelines can drop them into this tool before Figma import or email distribution, preserving alpha on logos that float over gradients. Educators teaching real-time graphics can contrast uncompressed versus RLE TGA sizes against PNG DEFLATE using the live byte counters on this page. Video editors who receive TGA sequences from 3D renders—but only need hero stills for thumbnails—can convert single frames without launching a compositor. Web publishers migrating legacy asset CDNs replace TGAs with PNG so responsive image components and CDN optimizers can apply familiar transformations. Indie studios preparing Steam store art sometimes receive contractor deliveries in TGA; this converter offers a policy-light checkpoint before optional WebP conversion. Whenever AI-generated or AI-edited imagery accompanies these textures, pair SynthQuery’s AI Content Detector and Humanizer on surrounding copy so compliance matches the visual polish you ship.
How SynthQuery compares
Game engines, image editors, and batch CLIs can all emit PNG from TGA when installed, licensed, and permitted by IT. SynthQuery targets the moment you already have files in Downloads, need consistent zlib control, and cannot install plugins on a loaner laptop. Hosted converters may upload confidential art; here the decode and encode stay in your browser tab. The table summarizes common trade-offs before you pick a workflow.
Aspect
SynthQuery
Typical alternatives
Install footprint
Runs in Chromium, Firefox, or Safari—no DCC license or plugin hunt before converting.
Photoshop, GIMP, and Blender can export PNG but require installs and updates.
Batch + ZIP
Queue up to twenty TGAs, compare sizes, download individually or as a JSZip archive.
Desktop batching needs scripting knowledge or commercial DAM tools.
Alpha policy
Explicit preserve-or-flatten toggle with documented RGBA versus RGB behavior.
Export dialogs vary; some tools silently premultiply or strip alpha.
Privacy posture
Pixels are not uploaded to SynthQuery for conversion—only the app shell loads over HTTPS.
Third-party upload services may retain files per their terms; read carefully.
RLE coverage
Implements standard RLE truecolor, indexed, and grayscale modes alongside uncompressed TGAs.
Some lightweight viewers only handle uncompressed type-2 files reliably.
How to use this tool effectively
Begin with the .tga or .tpic masters you truly intend to publish or hand to teammates—if a file is merely mislabeled, fix the extension before you queue it, because the preview step validates the binary header and will reject truncated or non-TARGA payloads with a clear toast instead of silently painting garbage. Open the dashed upload card or use Add TGA to browse; the tool filters on common extensions and MIME hints, enforces the per-file size ceiling, and caps the queue at twenty entries so laptops with finite RAM stay responsive while decoding multi-megabyte textures. Each row shows a spinner until the local decoder finishes building a PNG-based preview blob—this proves the file parsed before you spend time tweaking export options. In the left column, leave Preserve alpha channel enabled when your source uses thirty-two-bit pixels with meaningful cutouts, decals, or soft foliage cards; disable it when you know the destination composites on white and you want a smaller RGB PNG without an explicit alpha plane. Adjust the PNG compression slider between one and nine: low values finish quickly during iterative batches, while eight or nine ask zlib to hunt redundancy harder—often worthwhile on UI atlases with large flat fills. Press Convert to PNG to process pending or errored rows; if everything already succeeded, the same button re-encodes the full queue so you can compare compression presets without re-importing from disk. When conversions finish, download individual PNGs, trigger staggered multi-save downloads, or pack the lot into a ZIP generated with JSZip entirely in-browser. If you need JPEG afterward—for strict attachment limits—chain to the PNG to JPG tool once alpha is no longer required. If you need smaller PNGs still, open the PNG Compressor; if dimensions must match social templates, jump to the Image Resizer. Return to the Free tools hub whenever you want calculators, generators, and converters grouped in the same dark SynthQuery shell.
Limitations and best practices
Very wide or tall images can exhaust memory even under the file-size cap because decode expands to four bytes per pixel in RGBA paths—process giant lightmaps on a desktop workstation and close heavy tabs first. Sixteen-bit TGA pixels decode to eight-bit channels using five-bit scaling; if you need bit-perfect high dynamic range, keep EXR or floating-point masters and use this tool only for preview PNGs. Corrupted RLE packets or truncated color maps throw explicit errors—re-export from your source tool rather than expecting automatic repair. When PNG outputs grow relative to RLE TGA, the source may already be noisy photographic content where DEFLATE helps less; try a higher zlib level or accept that lossless PNG is not always the smallest container. Always retain originals when contracts require immutable archives. SynthQuery does not provide legal clearance for texture copyrights, trademarked logos, or AI disclosure—use adjacent policy tools when publishing commercially.
Full catalog spanning AI detection, readability, plagiarism, humanization, and advanced media utilities.
Frequently asked questions
TARGA—Truevision Advanced Raster Graphics Adapter—is a raster format popularized in the nineties and still common in game development because it stores uncompressed or RLE-compressed pixels with optional alpha in a simple layout. Files usually use the .tga extension (sometimes .tpic). Unlike JPEG, it does not throw away high frequencies, so it remains a faithful interchange format between 3D tools, though it is not as web-native as PNG or WebP.
When Preserve alpha channel is enabled, thirty-two-bit BGRA pixels decode into RGBA PNG with the same per-pixel alpha values. Semi-transparent foliage, glass, and decals stay cut out correctly for engines and design tools that read PNG alpha. If you disable the toggle, translucent texels composite onto white and the encoder emits an RGB PNG, which is smaller and safer for destinations that ignore alpha channels entirely.
Yes for the RGB or RGBA samples you encode. Neither TGA (in typical truecolor modes) nor PNG applies JPEG-style quantization. zlib compression in PNG is reversible: decoding returns identical pixels aside from the intentional flattening step when you turn alpha preservation off. Changing zlib level only affects how long the encoder searches for redundancy, not the final color values.
Yes. Types nine, ten, and eleven—run-length encoded indexed, truecolor, and grayscale—are supported alongside uncompressed types one, two, and three. If an RLE packet is truncated or declares more pixels than the header width and height allow, the tool stops with a readable error instead of writing a corrupted PNG.
Studios historically chose TGA because it is straightforward to parse, supports alpha without proprietary wrappers, and plays nicely with perforce-friendly text diffs when paired with external tooling. Many pipelines still default to TGA for quick iteration even if shipping builds transcode to BCn GPU textures. Converting to PNG helps when you need browser previews, documentation screenshots, or handoffs to teams outside the engine toolchain.
Queue up to twenty files, each up to one hundred megabytes. After previews validate each header, run conversion once or re-run after tweaking zlib or alpha settings. Download individual PNGs, timed multi-downloads, or a single ZIP—all generated locally.
No. Uncompressed TGA and PNG store the same raw samples, but PNG adds filtering and zlib; highly noisy albedo maps may compress only slightly. Conversely, flat UI textures and gradients often shrink dramatically. The on-page byte comparison shows your real ratio per file rather than marketing averages.
Type one and type nine indexed images read the embedded color map, expand each index to RGBA, and encode PNG as truecolor. Palette metadata from the TGA is not preserved as a PNG PLTE chunk in this build—output is always RGB or RGBA scanlines for maximum compatibility.
Decode and PNG encoding execute entirely in your browser with JavaScript and Web APIs you already trust for other SynthQuery converters. File bytes are not uploaded to our servers for processing. You still load the page over the network like any website, but image payloads remain on-device unless you choose to upload results elsewhere.
You can export JPEG directly from TGA using SynthQuery’s TGA to JPG tool when you already know you want lossy delivery with a quality slider and matte controls. If you prefer a lossless PNG master first—common when masks might change—use this converter, then open the PNG to JPG utility when downstream channels require JPEG-only attachments.