ForgeConvert Supported Image Formats
Last reviewed:
This reference reflects the current production capability registry—not theoretical codec support. A format appears as an input or output only after its installed engine and ForgeConvert safety tests permit that direction.
Quick capability table
| Format | Input | Output | Important current behavior |
|---|---|---|---|
| JPG/JPEG | Yes | Yes | Lossy output at quality 82 with 4:2:0 chroma subsampling; no alpha |
| PNG | Yes | Yes | Lossless output preserves decoded pixels and alpha |
| WebP | Yes | Yes | Lossy output at quality 82; alpha supported |
| GIF | Yes | Yes | Static output, up to 256 colors; animated input rejected |
| TIFF | Yes | Yes | Lossless LZW output; multipage input rejected |
| AVIF | Yes | Yes | Lossy output at quality 60; sequences rejected |
| SVG | Yes | No | Restricted static SVG is sanitized and rasterized |
| HEIC/HEIF | Yes | No | Primary still image only; multi-image sequences rejected |
| BMP | Yes | Yes | Restricted true-color variants; 24-bit output removes alpha |
| ICO | Yes | Yes | Largest valid input frame selected; one PNG-backed output frame |
| TGA | Yes | Yes | 24/32-bit true-color input; uncompressed 32-bit output |
How directional support works
“Supported” is not a single yes-or-no property. ForgeConvert distinguishes decoding from encoding. SVG and HEIC can be decoded under current restrictions but cannot be selected as outputs. The other enabled formats in the table can be used in both directions, except that source and destination cannot be identical.
Use the exact converter page for the direction you need. Representative routes include JPG to PNG, PNG to WebP, SVG to PNG, and HEIC to JPG. A format page describing a standard does not imply that every possible codec feature is accepted by ForgeConvert.
Current operating limits
| Limit | Current value | Why it matters |
|---|---|---|
| Files per batch | 20 | Keeps one browser operation manageable |
| Compressed upload per file | 8 MB | Rejects oversized uploads before processing |
| Decoded dimensions | 40 megapixels | Controls decompression and memory risk |
| Output size | 64 MB | Stops unexpectedly large generated files |
| Frames/pages | 1 | Prevents silent animation or page loss |
| Processing time | 15 seconds | Stops conversions that exceed the bounded request window |
A file can be below 8 MB yet exceed 40 megapixels after decoding. Conversely, a valid 8 MB input can produce a much larger lossless output and hit the output limit. Compressed bytes and decoded workload measure different risks.
Format-specific restrictions
Animation and multiple pages
ForgeConvert does not create animated output. Animated GIF, animated WebP, AVIF sequences, multipage TIFF, and multi-image HEIC are rejected rather than reduced silently to one frame. ICO is the deliberate exception to ordinary single-frame selection: up to 32 embedded frames are inspected and the largest valid frame up to 256 × 256 is selected.
SVG
SVG is accepted only as a restricted, static input. Documents containing scripts, external references, embedded media, animation, event handlers, entities, or other disallowed active content are rejected. Successful SVG input is rasterized to the selected output format at bounded dimensions.
BMP and TGA
BMP input is limited to uncompressed Windows true-color variants with compatible DIB headers. BMP output is uncompressed 24-bit RGB and cannot preserve alpha. TGA input is limited to uncompressed or RLE 24/32-bit true-color data; color-mapped and grayscale variants are not accepted.
HEIC
HEIC/HEIF is decoded through a bounded worker process. The primary still image is used, orientation is applied to pixels, and sequences are rejected. ForgeConvert does not encode HEIC output.
Output and metadata policy
ForgeConvert changes encoding but does not resize, crop, or edit the image as part of normal conversion. Source metadata is not carried into normal output. For HEIC, orientation is applied during decoding before other metadata is removed. This can help prevent an incorrectly rotated result, but the converted file is not a metadata-preserving archival copy.
Keep originals when EXIF, IPTC, XMP, capture details, color workflow data, or provenance matters. The converter creates a practical derivative; it does not replace a master.
Formats not currently enabled
PSD, camera RAW, JPEG XL, and JPEG 2000 are present in the capability model but do not generate public converter routes. The current runtime lacks the vetted decoders or encoders required by ForgeConvert’s policy. “Coming soon” is not a promise of a date and should not be interpreted as partial support.
Before converting
- Confirm the actual source type with the format-identification workflow.
- Check that the required source and output directions are both listed.
- Preserve animated, layered, multipage, or metadata-rich originals.
- Ensure compressed size and pixel dimensions are within limits.
- Choose an output for the receiving application—not merely the smallest extension.
- Inspect the downloaded result for dimensions, transparency, color, and file size.
Frequently asked questions
Can ForgeConvert convert animated images?
No. ForgeConvert currently processes one still frame and rejects animated, multi-image, and multipage inputs rather than silently discarding frames.
Can ForgeConvert create SVG or HEIC files?
No. SVG and HEIC are currently accepted as restricted input formats only. They are not available as output formats.
What are ForgeConvert’s upload limits?
A batch can contain up to 20 files. Each file can be up to 8 MB and 40 megapixels; processing and output limits also apply.