What to Do When a Video Is Too Big to Send or Upload

What the size error looks like

The message varies by destination, but the cause is the same: the file is bigger than the receiving service will accept in one piece.

• Email. The attachment is refused, or the mail app offers to send a cloud storage link instead. Attachment limits are commonly in the tens of megabytes, which a minute or two of phone video can exceed.
• Chat and messaging apps. The app refuses the file or quietly recompresses it, so the recipient gets a softer, smaller copy.
• Course platforms and intranets. An upload form reports that the file exceeds the maximum size an administrator has set.
• Video sites. Large uploads are usually allowed, but slow connections make them stall, and some sites cap length or size per account level.

Limits change over time and differ between plans, so check the current documentation for the service you use rather than relying on a number you remember.

Why video files get so large

File size is almost entirely the video bitrate, the number of bits used per second of picture, multiplied by the duration. A file averaging 40 megabits per second uses 2,400 megabits per minute, which is 300 megabytes. Four things drive the bitrate:

Resolution

4K has four times the pixels of 1080p, and encoders spend more bits to describe them

Frame rate

60 frames per second gives the encoder twice as many pictures to describe as 30

Codec

Newer codecs such as HEVC usually reach similar quality at a lower bitrate than H.264, at some cost in compatibility

Encoder settings

Phones and cameras record at generous bitrates so footage survives editing; that headroom is what makes originals so big

Audio is a minor share. A stereo AAC track at 128 kb/s adds under a megabyte per minute, so cutting audio quality barely changes the total. The video codec explainer covers how codecs and settings trade size for quality.

Find out what you are dealing with

1. Look up the exact limit at the destination, and whether it applies to size, duration or both.
2. Check the file's size, duration, resolution, frame rate, codec and bitrate in a media inspector such as MediaInfo, or with ffprobe -hide_banner clip.mov in a terminal.
3. Divide the limit by the duration to get the average bitrate you can afford. A 500 MB limit for a 10-minute video allows about 6.7 megabits per second, including audio.
4. Ask whether the recipient needs the whole video. A clip or a link may serve them better than a smaller copy of everything.
5. Decide which option below gets under the limit with the least loss.

Four ways to make it fit, from lossless to lossy

Share a link. Uploading to cloud storage or an unlisted video page and sending the link sidesteps attachment limits and keeps full quality. It is often the right answer for email.

Trim or split without re-encoding. If only part of the video matters, cut it out with a stream copy, which copies compressed data and loses nothing. Cuts snap to the nearest keyframe, so leave a second or two of margin. This keeps 15 minutes starting at the 2-minute mark:

ffmpeg -ss 00:02:00 -i webinar.mp4 -t 00:15:00 -c copy webinar-part.mp4

Splitting a long recording into parts that each fit a limit works the same way; splitting a video file covers choosing cut points.

Remux to a different container. Moving streams from MOV to MP4, for example, fixes compatibility errors but leaves the size almost unchanged, because the compressed picture is identical:

ffmpeg -i clip.mov -c copy clip.mp4

Re-encode. This is the only option that makes the picture itself smaller. Lowering resolution and letting the encoder target a quality level usually beats choosing a bitrate by hand:

ffmpeg -i clip.mov -vf scale=-2:1080 -c:v libx264 -crf 23 -preset slow -c:a aac -b:a 128k clip-1080p.mp4

With x264, a higher CRF value means a smaller file and lower quality; values in the low twenties are a common starting point. Graphical converters such as HandBrake offer the same controls with presets.

A worked example: a training clip and a 500 MB limit

Before uploading, play the compressed copy full screen and pause on fine detail such as text in slides. Screen text and fast motion are where compression shows first.

Mistakes that cost quality for nothing

• Re-encoding a file that was already compressed for sharing. Each lossy generation discards more detail.
• Compressing the original instead of a copy. Once overwritten, the headroom is gone for good.
• Using one low bitrate for everything. Screen recordings with small text need more bits than a talking head at the same resolution.
• Changing the frame rate to save space, which can make motion stutter and create sync trouble.
• Squeezing audio hard to save a few megabytes. Speech becomes harder to understand and to transcribe, and the saving is tiny.
• Sending a full video when the recipient needed a transcript or a two-minute clip.

How mydubly handles large source files

mydubly never uploads your video file. The browser decodes the audio locally, splits it into chunks of about 30 seconds and compresses each one to Opus at about 32 kb/s, roughly 120 KB per 30 seconds, and only those chunks are sent over HTTPS. A multi-gigabyte recording therefore uploads only a few megabytes of speech; reducing upload size for video translation explains each stage. The practical limit is length, a maximum of 2 hours per file, rather than size.

The output is a different story. The translated MP4 keeps the original picture without re-encoding, because the browser only swaps the audio track, so it is about the same size as the source. If the source was too big to email, the translated video will be too, and you would compress it afterwards with the methods above. The translated audio is a small M4A file you can send on its own. On low-memory devices such as some phones, a very large file produces the translated audio rather than a merged video; why browsers hit that ceiling is covered in processing large video files in the browser.

When another workflow fits better

• Use a link or the platform's own uploader for anything recipients will stream rather than download.
• Recordings over 2 hours need splitting before translation, as described in translating long videos.
• For courses, upload the full-quality video once and add translated subtitles as separate SRT or VTT files, which are tiny, instead of re-uploading a second large video; the online course translation page covers that setup.
• If confidentiality is the reason you are reluctant to upload a big file, private video translation explains what stays on your device.

Next step: translate first, compress last

Keep your full-quality source, run it through the video translator, and compress only the copy you need to send. That way the translated video is made from the best picture you have, and any re-encoding happens once, at the end.