Compress a video to 64 MB
Drop a video and FitSize shrinks it to fit under 64 MB, in your browser. Nothing is uploaded to a server.
Instant client-side compression · Up to 2 GB per file · Zero server upload
- Target size
- 64 MB
- Platforms with this limit
- 1
- Table assumes
- 30 fps, 16:9, stereo audio
You are preparing a video for mobile distribution over global messaging networks where wireless carriers and chat protocols enforce conservative transport ceilings. On cellular connections and roaming mobile profiles, messaging applications aggressively reject or truncate transfers that cross operational data limits. Squeezing your clip under sixty-four megabytes guarantees instantaneous delivery without prompting recipients with metered bandwidth warnings, while keeping high-definition resolution intact for casual viewing. When sharing family clips, field recordings, or conference highlights across international chat groups, hitting this threshold ensures every participant receives the media directly in their active chat thread rather than as an external storage link.
How long a video fits in 64 MB
The longest clip that keeps each resolution at each quality, worked out with the same arithmetic FitSize uses to plan an encode. Times use h, m and s for hours, minutes and seconds, and are rounded down, so a clip at the listed length fits.
| Resolution | High | Balanced | Smallest |
|---|---|---|---|
| 1080p | 1m 05s | 1m 37s | 2m 32s |
| 720p | 2m 23s | 3m 31s | 5m 26s |
| 480p | 5m 07s | 7m 22s | 10m 59s |
| 360p | 8m 32s | 11m 58s | 19m 42s |
Assumes 30 fps, a 16:9 picture and stereo AAC audio at 128 kbps. A different frame rate, a taller picture or a bigger audio track changes the times.
Worked examples
- A 30-second clip: 1080p at Balanced quality (that resolution holds up to 1 min 37 s).
- A 2-minute clip: 720p at Balanced quality (that resolution holds up to 3 min 31 s).
- A 10-minute clip: 360p at Balanced quality (that resolution holds up to 11 min 58 s).
What quality to expect
A 2-minute 720p clip at this size gets about 0.145 bits per pixel per frame. That is above our High preset (0.12), so the clip should look close to the original at that resolution. This is an estimate from bitrate arithmetic, not a measurement: real quality depends on the footage, and fast motion or fine detail needs more.
Who needs 64 MB
These verified limits are at or just above 64 MB. Where a limit is for email, the file has to be smaller than the number, so the third column is what to aim for.
| Platform | Its limit | Aim for |
|---|---|---|
| WhatsApp: Video, slower connection | 64 MB | 64 MB |
| Fastmail: Whole email (a little above this size) | under 70 MB | 50.9 MB |
What each of these limits covers
- WhatsApp: Video, slower connection. Default video size limit for users on a slower connection, with 480p resolution. Use this one as the target when the sender's connection is unknown: it is the smaller of the two. Source: faq.whatsapp.com
- Fastmail: Whole email. Any attachment can be sent or received as long as the resulting email is under 70 MB in total. Fastmail says that with email encoding an attachment should usually be no larger than 50 MB. Blocks some risky file types, such as double extensions. Source: fastmail.help
Tips at 64 MB
- Aim for the lower limit whenever you are not sure which platform policy applies to your recipient, because a file under this threshold satisfies both standard and legacy messaging constraints simultaneously across modern iPhone and Android installations.
- Mobile messaging clients parse container timestamps strictly: encoding with progressive MP4 faststart places metadata index headers at the front of the file so video playback streams instantly without waiting for the full transmission to download over flaky wireless signals.
- Cellular radio networks frequently drop slow file transfers midway across weak coverage zones; keeping video bitrate strictly regulated under this boundary prevents transport resets while avoiding document-mode workarounds that clutter recipient storage drives.