Format reference

Choose the right format for the job.

ConvertAnyFile has four live browser-first converter categories—Images, Archives, structured Data, and Subtitles. Each category has its own validation, capability rules, safety limits, and supported outputs.

Start with the destination

Format choice is about the next workflow, not just the extension.

A photograph, transparent logo, phone original, archive package, CSV export, API payload, subtitle track, and HDR frame have different requirements. Choose an output based on what the next application accepts and what structure or fidelity must survive the conversion.

How support works

Each category has its own validation and output contract. The shared platform does not assume that a file is safe or meaningful just because its filename carries a known extension.

Subtitles

SRT, VTT/WebVTT, ASS, SSA, and SBV timed text.

The Subtitle Converter reads common timed-text formats and writes SRT, VTT, SBV, or plain TXT. ASS and SSA are input-only because their presentation model includes styling, positioning, karaoke, and effects that simpler outputs cannot preserve faithfully.

FormatRoleInputOutput
SRTWidely compatible numbered subtitle cuesYesYes
VTT / WebVTTWeb timed text and browser video captionsYesYes
ASSStyled Advanced SubStation Alpha subtitlesYesNo
SSAStyled SubStation Alpha subtitlesYesNo
SBVSimple timed caption formatYesYes
TXTReadable text extractionNoYes
Archives

ZIP, 7Z, RAR, TAR, TAR.GZ/TGZ, and GZIP.

The Archive category can read common archive/container families locally and repack supported regular files and folders. 7Z and supported RAR4/RAR5 are input-only through a lazy-loaded WebAssembly decoder. Certified public outputs are ZIP, TAR, and TAR.GZ.

FormatRoleInputOutput
ZIPWidely compatible multi-file archiveYesYes
7ZCompressed archive containerYesNo
RARRAR4/RAR5 archive inputYesNo
TARUnix-style archive containerYesYes
TAR.GZ / TGZGzip-compressed TARYesYes
GZIP / GZSingle-file compression streamYesNo
Structured data

CSV, TSV, JSON, JSONL, and NDJSON.

The Data category accepts five extensions and produces four output families. NDJSON is treated as JSON Lines input because both formats store one complete JSON value per non-empty line.

FormatRoleInputOutput
CSVComma-delimited tablesYesYes
TSVTab-delimited tablesYesYes
JSONStructured objects, arrays, and valuesYesYes
JSONLOne JSON value per lineYesYes
NDJSONJSON Lines alias/input extensionYesAs JSONL
Certified image outputs

16 image output formats in the production catalog.

Every image format below is filtered against the WASM runtime running in the browser. If a deployed build cannot write a codec, the converter hides that option rather than offering a conversion that cannot complete.

JPG

Photos & broad compatibility

A widely supported lossy image format that is especially practical for photographs and compact delivery copies.

Best for: Photographs, email, general sharing, upload forms, compatibility-focused delivery.

Trade-off: Repeated re-encoding can add artifacts, and transparent pixels cannot be represented as true alpha transparency.

PNG

Lossless graphics & transparency

A lossless format commonly used for screenshots, graphics, text-heavy images, and transparent assets.

Best for: Screenshots, logos, UI graphics, diagrams, overlays, and workflows that need lossless storage.

Trade-off: Full-resolution photographs can be much larger than efficient lossy formats without gaining new source detail.

WebP

Modern web delivery

A modern image format used widely on the web with support for lossy, lossless, and transparent workflows.

Best for: Website images, modern browser delivery, photos, and transparent web graphics.

Trade-off: Older or specialized software may still prefer JPG or PNG, and quality settings are encoder-specific.

AVIF

High-efficiency modern images

A modern format capable of strong compression efficiency for many photographic and graphic images.

Best for: Modern web delivery where small transfer size and current codec support are important.

Trade-off: Encoding and decoding behavior, tooling support, and quality controls should be tested with the real workflow.

TIFF

Scanning & professional imaging

A flexible image container common in scanning, print, archival, and professional imaging workflows.

Best for: Scanning, archival sources, print workflows, high-quality intermediates, and professional imaging.

Trade-off: Files can be large and may contain metadata or features that simple delivery formats cannot preserve.

GIF

Legacy animation & simple graphics

A long-standing palette-based image format known for simple animation and broad recognition.

Best for: Simple legacy animations and small palette-based graphics.

Trade-off: Limited color palette and inefficient photographic storage; the current single-image converter exports one frame.

BMP

Simple bitmap storage

A straightforward bitmap format that is easy to decode but often inefficient for everyday delivery.

Best for: Legacy Windows bitmap workflows and simple interchange with software that explicitly requests BMP.

Trade-off: File size can be dramatically larger than compressed alternatives such as JPG, PNG, or WebP.

ICO

Icons & favicons

A container used for Windows icons and website favicons, often carrying one or more icon-sized images.

Best for: Favicons, Windows icons, and software that explicitly requires ICO.

Trade-off: Not intended as a general-purpose photo format; single-image conversions use the best available icon frame.

JXL

Modern high-efficiency imaging

JPEG XL is designed for efficient still-image compression with modern fidelity features and flexible lossless or lossy workflows.

Best for: Modern archival or specialist pipelines that explicitly support JPEG XL.

Trade-off: Application and browser support is not as universal as JPG, PNG, or WebP.

JP2

JPEG 2000 interchange

JPEG 2000 is used in archival, imaging, document, and specialist workflows that need its wavelet-based compression model.

Best for: Archival, imaging, geospatial, medical, and legacy professional pipelines that require JPEG 2000.

Trade-off: Consumer and web compatibility is much lower than JPG or PNG.

HDR

Radiance high-dynamic-range images

Radiance RGBE stores high-dynamic-range image data for lighting, rendering, and environment-map workflows.

Best for: 3D rendering, lighting, environment maps, and HDR technical pipelines.

Trade-off: Not intended for ordinary sharing, websites, or office applications.

EXR

Professional HDR & VFX imaging

OpenEXR is a professional high-dynamic-range format used heavily in VFX, compositing, rendering, and production pipelines.

Best for: VFX, CGI, compositing, rendering, and high-dynamic-range production interchange.

Trade-off: Advanced channel/layer semantics may not map to simpler single-image outputs.

PCX

Legacy bitmap interchange

An older raster format associated with classic PC graphics and paint applications.

Best for: Legacy software, preservation, or interchange where PCX is explicitly required.

Trade-off: Rare in modern consumer workflows and usually larger or less convenient than current formats.

TGA

Legacy graphics & texture workflows

Truevision TGA remains useful in some graphics, game-development, and texture pipelines.

Best for: Legacy graphics tools, game assets, textures, and pipelines that explicitly request TGA.

Trade-off: File sizes can be large and web/browser use is uncommon.

QOI

Simple lossless image interchange

Quite OK Image is a compact, simple lossless raster format designed for fast encoding and decoding.

Best for: Developer tools, experiments, and applications that explicitly support QOI.

Trade-off: Small ecosystem compared with PNG, WebP, or JPG.

PNM

Portable bitmap family

The Netpbm family is intentionally simple and useful for command-line, scientific, and interchange workflows.

Best for: Unix tools, scientific workflows, testing, and simple raster interchange.

Trade-off: Large files and very limited consumer-facing usefulness.

Image comparison

Compression, transparency, and compatibility.

No single column decides the winner. The right image output depends on the content and destination.

FormatCompressionTransparencyCompatibility note
JPGLossyNo alpha transparencyExtremely broad across browsers, operating systems, editors, and consumer applications.
PNGLosslessYesExtremely broad across browsers, design tools, office software, and image editors.
WebPLossy or losslessYesStrong in current browsers and increasingly common in content and image pipelines.
AVIFLossy or lossless depending on encoderYesGood in modern browsers, but legacy applications and older workflows may still require a fallback.
TIFFCan use multiple compression modesCapabilities depend on the TIFF contentStrong in professional imaging software; less convenient for ordinary web or messaging delivery.
GIFLossless palette compressionLimited transparencyVery broad, especially for playback of simple animations.
BMPOften uncompressed or lightly compressedNot a dependable transparency workflowWidely recognized, but rarely the best choice for web or general-purpose delivery.
ICOContainer-specificCommonly supportedStrong for icon-specific use cases rather than ordinary image delivery.
JXLLossy or losslessYesBest treated as an advanced output for tools that explicitly advertise JPEG XL support.
JP2Lossy or losslessCan support alpha/channel data depending on workflowStrong only in software and workflows that explicitly support JPEG 2000.
HDRHDR-oriented RGBE encodingNot a general alpha workflowSpecialist 3D, VFX, and imaging software.
EXRMultiple lossless and lossy professional modesSupports alpha and multiple channelsExcellent in professional VFX and 3D software; limited in consumer applications.
PCXRun-length encoded raster dataNo dependable modern alpha workflowSpecialist and legacy rather than mainstream.
TGAUncompressed or run-length encodedCan carry alphaGood in graphics software; weak for ordinary web delivery.
QOILosslessYesNiche; use only when the destination explicitly supports QOI.
PNMTypically uncompressed/simple raster storageNo general alpha modelStrong in technical tooling; uncommon in consumer applications.
Different fidelity contracts

Pixels, records, archive trees, and timed text need different rules.

Image conversion creates one output image per source and documents flattening behavior for multi-frame or layered inputs. Data conversion uses explicit table/JSON rules. Archive conversion preserves safe regular file trees where representable. Subtitle conversion focuses on cue timing and readable text while making richer presentation loss explicit.

Local first

All four live converter categories use the shared browser-first batch system, while their engines, validation, limits, and output controls remain category-specific.