ForgeConvert Error Messages and Fixes

Match the message to the boundary that rejected the request. Do not rename files or retry deterministic errors.

Error reference

Message family Meaning Action
Selected file is another format Browser signature detection disagrees Switch source or choose another file
This conversion is not supported Invalid or unavailable direction Check current format matrix
Expected media type/extension Upload labels disagree with source Identify content; do not disguise it
Contents do not match Signature mismatch Inspect real format or replace file
Outside allowed range Zero bytes, over 8 MB, over 40 MP, or output over 64 MB Use a valid smaller derivative
Unsupported active content SVG violates static safety policy Sanitize in a trusted editor
Animated/multipage/sequence More than one frame/page Use a frame-aware workflow
Processing took too long 15-second boundary exceeded Try one smaller valid source
Too many requests Rate limit Wait before retrying
Could not safely convert Decoder/encoder rejected data Test integrity and variant support
Download expired Temporary staged output expired Convert again and download promptly

Limits that affect errors

ForgeConvert accepts up to 20 files per browser batch, 8 MB and 40 megapixels per file, one frame/page, 15 seconds of processing, and 64 MB of generated output. These limits measure different resources.

Safe troubleshooting

  1. Save the exact message.
  2. Identify the real source.
  3. Check supported formats and limits.
  4. Test one known-good control on the same route.
  5. Use stage diagnosis if the cause remains unclear.

A normal JPG to PNG test is useful only as a control; it does not fix unrelated corruption.

Failure-case examples

A 6 MB panoramic JPEG can pass the upload-byte check but fail the 40-megapixel boundary. A valid animated GIF can be rejected because the service is intentionally still-image only. A safe SVG logo can convert while a visually identical SVG with an external image reference is rejected. These are policy outcomes, not random failures.

Before contacting support

Reproduce with one file, save the exact message, record detected type, dimensions and route, and test a non-sensitive known-good control. Remove private metadata or use a synthetic sample before sharing evidence.

Related resources