ConvertAnyFile now has two production categories. Image output support is capability-derived from the packaged ImageMagick runtime, while structured Data uses a deterministic browser text engine for CSV, TSV, JSON, JSONL, and NDJSON workflows.
A photograph, transparent logo, phone original, CSV export, API payload, line-oriented dataset, 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.
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.
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.
| Format | Role | Input | Output |
|---|---|---|---|
| CSV | Comma-delimited tables | Yes | Yes |
| TSV | Tab-delimited tables | Yes | Yes |
| JSON | Structured objects, arrays, and values | Yes | Yes |
| JSONL | One JSON value per line | Yes | Yes |
| NDJSON | JSON Lines alias/input extension | Yes | As JSONL |
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
No single column decides the winner. The right image output depends on the content and destination.
| Format | Compression | Transparency | Compatibility note |
|---|---|---|---|
| JPG | Lossy | No alpha transparency | Extremely broad across browsers, operating systems, editors, and consumer applications. |
| PNG | Lossless | Yes | Extremely broad across browsers, design tools, office software, and image editors. |
| WebP | Lossy or lossless | Yes | Strong in current browsers and increasingly common in content and image pipelines. |
| AVIF | Lossy or lossless depending on encoder | Yes | Good in modern browsers, but legacy applications and older workflows may still require a fallback. |
| TIFF | Can use multiple compression modes | Capabilities depend on the TIFF content | Strong in professional imaging software; less convenient for ordinary web or messaging delivery. |
| GIF | Lossless palette compression | Limited transparency | Very broad, especially for playback of simple animations. |
| BMP | Often uncompressed or lightly compressed | Not a dependable transparency workflow | Widely recognized, but rarely the best choice for web or general-purpose delivery. |
| ICO | Container-specific | Commonly supported | Strong for icon-specific use cases rather than ordinary image delivery. |
| JXL | Lossy or lossless | Yes | Best treated as an advanced output for tools that explicitly advertise JPEG XL support. |
| JP2 | Lossy or lossless | Can support alpha/channel data depending on workflow | Strong only in software and workflows that explicitly support JPEG 2000. |
| HDR | HDR-oriented RGBE encoding | Not a general alpha workflow | Specialist 3D, VFX, and imaging software. |
| EXR | Multiple lossless and lossy professional modes | Supports alpha and multiple channels | Excellent in professional VFX and 3D software; limited in consumer applications. |
| PCX | Run-length encoded raster data | No dependable modern alpha workflow | Specialist and legacy rather than mainstream. |
| TGA | Uncompressed or run-length encoded | Can carry alpha | Good in graphics software; weak for ordinary web delivery. |
| QOI | Lossless | Yes | Niche; use only when the destination explicitly supports QOI. |
| PNM | Typically uncompressed/simple raster storage | No general alpha model | Strong in technical tooling; uncommon in consumer applications. |
Compatible HEIC/HEIF photos can be decoded and converted to supported outputs, but the current packaged WASM build does not report a HEIC writer, so HEIC is intentionally not listed as a certified output.
Image conversion creates one output image per source and documents flattening behavior for multi-frame or layered inputs. Data conversion preserves explicit JSON types where possible, keeps delimited cells as text, and uses documented rules for headers, nested object paths, arrays, line endings, and BOM output.
Both live categories use the shared browser-first batch system, but their engines, validation, limits, and output controls remain category-specific.