File size exceeds platform limit - causes and fixes
Compare the exact file size with the limit shown by the current destination's composer. The error message usually names the limit; if not, check the platform's upload help page. Compressing a copy in a local editor is the standard fix; the in-browser tools here accept inputs only up to 100 MB.
Check these first
- Read the exact composer error; note the stated size limit.
- Compare the file size (in bytes, not rounded MB) against the limit.
- Check whether the limit applies to your account tier (Premium / Business / Ads) - they often differ.
Likely causes
- File size exceeds the destination's published cap
Each destination has its own limit; account tier can change it.
- Source used an inefficient codec or container
Editing codecs and uncompressed audio inflate size.
- Source contains an unintended extra audio track
Some editors add a separate audio track that doubles the bitrate.
Fix it
- Re-encode with a destination-appropriate preset
Use the registry's recommended preset for this platform + surface; pick a quality profile designed to fit within the cap.
Re-encode with a destination-appropriate preset - Trim to the destination's length limit
If trimming reduces duration enough, you can sometimes drop one quality preset.
Trim to the destination's length limit
Check your file
Extension and MIME type are labels, not proof of the container. Dimensions and duration come from this browser's media reader. This does not detect codecs, bitrate, corruption or platform upload compatibility. Files and measurements are not sent anywhere.
Prepare a copy in Koldflux, review its output and check the current destination requirements before publishing.
Automate this in Koldflux