TGA to JSON Converter: Free, Private, No Upload

What actually changes in this conversion

• JSON is an encoding of the image data, not a new compression scheme. The text is about a third larger than the binary file, so what you gain is portability rather than a smaller size.
• Transparency follows the image data being encoded. JSON itself is only a text wrapper.
• 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 JSON: what you get

JSON (JavaScript Object Notation) was specified by Douglas Crockford in 2001. Embedding images as base64 strings in JSON became common with REST APIs and AI model inputs (OpenAI vision, Anthropic Claude, Google Gemini).

Technical: { "image": "iVBORw0KGgo...", "name": "photo.png" }. The base64 string can be escaped differently per language. Some APIs require no prefix, others require data:image/png;base64, prefix.

Real-world size: A 1 MB image as JSON base64 is ~1.33 MB. Parsing 10 MB JSON is 100-500ms in most languages. This is why vision AI APIs often recommend URL uploads for large images.

Popular tools: OpenAI API, Anthropic API, Google Gemini API, Postman, any JSON parser.

Alternatives: Multipart upload, Object storage + URL, Signed URL, Base64 in headers (rare).

Browser and software compatibility

TGA: Supported by game engines and 3D tools, but not displayed by browsers. JSON: Readable by every language and API client.

JSON with an encoded image works with any parser. Large payloads parse slowly.

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 JSON

• JSON with an encoded image is useful for API fixtures, config files and mock data.
• The image travels together with the other fields as a single payload.

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.
• Large payloads are slow to parse and send. Store files in object storage and keep a URL in the JSON for anything over a few hundred KB.
• 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.