Destination stuck at 0% / processing failed - causes and fixes
Stuck or failed processing is usually triggered by a non-standard container/codec combination, an extremely high resolution, or a destination-side issue. Re-export with a documented preset; if the second upload behaves the same, the problem is likely destination-side and not your file.
Check these first
- Re-export from the original with a documented preset and try again.
- Check whether the upload has actually started (some destinations show 0% until first frame is decoded).
- Check the destination's status page; outages cause processing delays.
Likely causes
- Container / codec combination not decodable
Editing codecs or unusual containers can pass upload but fail processing.
- Extremely high resolution beyond the destination's max
Some destinations cap processing resolution below the upload limit.
- Destination-side outage
An outage shows as stuck processing; check the destination's status page.
Fix it
- Re-export with a documented preset
MP4/H.264/AAC inside the destination's resolution and bitrate limits.
Re-export with a documented preset - Wait and retry
Some destinations retry processing; a manual retry after 10–15 minutes often clears stuck processing.
Prepare a copy in Koldflux, review its output and check the current destination requirements before publishing.
Automate this in Koldflux