TGA to SVG Converter: Free, Private, No Upload

What actually changes in this conversion

• Converting TGA to SVG in a browser normally embeds the pixels inside an SVG file. The image will not scale like a true vector drawing.
• Transparency is preserved, including soft edges.
• EXIF, GPS and camera data are stripped on every conversion. That is good for privacy, but you lose capture dates.

About TGA: history and technical details

Created by Truevision in 1984 for the TARGA and VISTA graphics cards. It became a standard for video editing (Windows and Mac) and later game texture pipelines. Still widely used in Unity, Unreal and 3D tools.

Technical: 18-byte header with image type, colour map, width, height, bit depth. Types 1, 2, 3, 9, 10, 11 for uncompressed and RLE variants. Supports 8-bit indexed, 15/16-bit high colour, 24-bit truecolour, 32-bit with alpha. Bottom-left origin by default.

Real-world size: A 1024x1024 32-bit TGA is 4 MB uncompressed, 1-3 MB with RLE. A 2048x2048 texture is 16 MB uncompressed. Game engines prefer DDS or KTX2 for shipping but TGA for authoring.

Popular tools: Unity, Unreal Engine, Blender, GIMP, Adobe Photoshop, ImageMagick, NVIDIA Texture Tools.

Alternatives: DDS (better for games), KTX2 (modern GPU texture), PNG (universal), WebP (web).

About SVG: what you get

SVG 1.0 was released by the W3C in September 2001. SVG 2 became a Candidate Recommendation in 2016 and is partially supported in modern browsers. Used on every major website for icons and logos.

Technical: XML-based. Root element is <svg> with viewBox defining coordinate space. Paths use <path d="..."> with move/line/curve commands. Supports gradients, filters, masks, clipping, and animation via SMIL or CSS. Can embed fonts and images.

Real-world size: A typical logo as SVG is 2-15 KB; the same logo as PNG at 500px is 20-80 KB. Icons saved as SVG are usually 80-95% smaller than PNG and sharp at any size.

Popular tools: Inkscape, Adobe Illustrator, Figma, Sketch, Affinity Designer, SVGOMG, SVGO, VS Code (with extensions).

Alternatives: PNG (fixed size, universal), WebP (lossless or lossy, alpha supported), PDF (for print), ICO (favicon only).

Browser and software compatibility

TGA: Supported by game engines and 3D tools, but not displayed by browsers. SVG: Renders in every browser and most design tools, but many upload forms and social platforms refuse it.

SVG renders in every browser, but many upload forms and social platforms refuse it.

Why people move away from TGA

• Browsers and most messaging apps cannot display TGA, so sharing it is awkward.
• TGA files are large because compression is minimal.

Why people choose SVG

• SVG scales to any size without blur, which suits logos, icons and illustrations.
• It is plain text, so it can be styled, searched and often gzipped very small.

Common mistakes with TGA

• Uploading TGA to a website — browsers will not display it
• Forgetting alpha channel in TGA exports — some tools drop it
• Assuming RLE TGA is fast — it is slower to decode than uncompressed

Best practices for keeping quality

• A TGA from a game pipeline may use a bottom-left origin or channel-packed data. Compare against the original before relying on it.
• Converting a bitmap to SVG in a browser normally means embedding the pixels inside an SVG wrapper. That helps compatibility but does not make the image scale cleanly. True vectorising needs a tracing tool such as Inkscape Trace Bitmap or Illustrator Image Trace, and works best on simple logos.
• Resize before converting if the image will be shown small. A 4000 pixel photo displayed at 800 pixels wastes bytes in any format.
• Check the result at 100 percent zoom, especially around text, edges and gradients, before you replace any originals.
• Keep your original files. Conversions to a lossy format cannot be undone.
• When you convert a set of images, use the same quality setting for the whole batch. The converter handles up to 20 files at once.