Convert images fast. Keep them private.
Drop supported image files, choose an output format, and convert locally in your browser. Originals stay unchanged on your device.
0 files
Processed locally in this browser session.
Certified output formats are filtered against the image engine running in your browser. Animated, multi-page, or layered inputs are currently exported as a single image; ICO inputs use the best available icon frame.
Drop, choose, convert, download.
The image converter is built for routine compatibility and specialist delivery tasks: HEIC photos that need JPG, PNG graphics that need WebP, modern AVIF images that need a fallback, JPEG 2000 or TGA assets from older workflows, HDR/EXR frames, or mixed batches that should be converted together.
For the current image workflow, supported image bytes are processed in the browser session. The original files remain on your device and are not overwritten by the converter.
- Batch multiple supported image formats in one workspace and drag additional files into an active batch.
- Use quality controls only where the selected output codec supports them.
- Cancel a running batch, retry only recoverable failures, and keep successful results.
- Download files one by one or package successful outputs into a ZIP.
Mainstream outputs first, specialist formats when you need them.
The packaged ImageMagick runtime is scanned in the browser. ConvertAnyFile intersects those writable codecs with a product whitelist that is exercised by the browser conversion matrix. HEIC/HEIF is supported as an input family when the decoder is available, but it is not offered as an output because this WASM build does not expose a HEIC writer.
| Group | Outputs | Use case |
|---|---|---|
| Mainstream | JPG, PNG, WebP, AVIF, TIFF, GIF, BMP, ICO | Photos, web delivery, transparency, scanning, icons, and broad compatibility. |
| Professional / archival | JXL, JP2, HDR, EXR | Advanced imaging, archival, VFX, rendering, and specialist pipelines. |
| Legacy / technical | PCX, TGA, QOI, PNM | Older graphics workflows, technical interchange, and explicitly requested formats. |
Conversion should be predictable, not silently magical.
The worker normalizes EXIF orientation into visible pixels before writing. Transparent sources are flattened to a deterministic white background only when the destination does not have a useful alpha channel. The product creates one output image per input file, so animation, page, layer, and icon-container semantics are not advertised as preserved.
The detector identifies multi-frame GIF/WebP, multi-page TIFF, and multi-size ICO containers when that information is available in the inspected bytes. ICO input uses the best PNG-backed frame when possible, with a legacy decoder fallback for older DIB/BMP icons.
Start with the format pair you need.
Each route opens the same conversion engine with a useful preset and pair-specific guidance. There is no duplicated converter backend.
Why the converter has limits.
Local processing uses the CPU and memory of the device running the browser. Compressed file size alone does not describe processing cost: a high-resolution image can expand to hundreds of megabytes after decoding. Sequential processing, dimension checks, estimated decoded-memory checks, and batch limits reduce the chance that a large job destabilizes the tab.
A known file extension is not enough. The workflow checks signatures and runtime codec availability so unsupported files do not silently enter a conversion queue that cannot process them.
Image conversion questions
Answers about certified outputs, input compatibility, batch limits, transparency, multi-frame behavior, quality, memory use, and what conversion can or cannot improve.
Which image formats can I add?
The image engine recognizes 57 filename extensions across common raster, specialist, legacy, and camera RAW families. A file still has to pass signature validation and runtime decoder checks before it is treated as supported.
Which image formats can I convert to?
The production output catalog contains 16 formats: JPG, PNG, WebP, AVIF, TIFF, GIF, BMP, ICO, JXL, JP2, HDR, EXR, PCX, TGA, QOI, and PNM. The browser only shows a format when the packaged ImageMagick runtime also reports that encoder as writable.
Why can I open HEIC but not choose HEIC as an output?
Input and output capability are separate. The current packaged WASM runtime can expose HEIC/HEIF decoding for compatible source files, but its runtime writer scan does not expose a HEIC encoder. ConvertAnyFile therefore keeps HEIC as an input family and does not advertise HEIC output in this release.
How many images can I convert in one batch?
The current safety policy allows up to 50 files, up to 75 MB per file, and up to 300 MB total input per batch. You can also drag or add more files after the initial batch as long as the limits are not exceeded.
Why do some outputs show a quality control?
Lossy outputs such as JPG, WebP, AVIF, JXL, and JP2 can use an encoder quality setting. Formats without a comparable quality control do not show the slider.
Does converting JPG to PNG restore lost detail?
No. Changing the container format cannot restore image detail already lost through earlier JPEG compression.
What happens to transparency when converting to an opaque format?
Outputs without a useful alpha channel use a deterministic white background instead of leaving transparent pixels undefined. JPG is the most common example.
What happens to animated, multi-page, layered, or multi-size files?
The current product creates one output image per input file. Animated GIF/WebP, multi-page TIFF, layered sources, and multi-size icon containers are therefore flattened to a single image representation. ICO inputs use the best available embedded icon frame when possible.
Can I convert HEIC photos to JPG?
Yes when the runtime can decode the specific HEIC file. HEIC to JPG is useful for broader compatibility with upload forms, older software, and general sharing.
Can a RAW camera file fail even if its extension is recognized?
Yes. RAW families vary by camera and decoder requirements. Recognition of the extension does not guarantee that the packaged browser runtime can decode every variant, so RAW remains a best-effort input path until more real-camera fixtures are certified.
Why can a small image file still use a lot of browser memory?
Compressed file size and decoded pixel memory are different. A very high-resolution image can expand to hundreds of megabytes after decoding even when the source file is only a few megabytes on disk. The image engine rejects extreme dimensions or estimated decoded memory before conversion.
Can I download all successful images together?
Yes. Successful batch results can be packaged into a ZIP while failed files remain isolated from the rest of the batch.
Does converting an image make it higher resolution?
No. Format conversion changes encoding or container representation. It does not add genuine source detail or automatically increase useful resolution.