How to Compress a Video for Discord and Email (10 MB and 25 MB)

Every service sets its own ceiling, and most of them changed at least once in the last few years, so the number you remember may be out of date. Discord is the clearest example: in 2024 it lowered the free upload limit from 25 MB to 10 MB per file. Nitro Basic subscribers get 50 MB and full Nitro gets 500 MB. Server boosts also raise the cap for everyone in that server, to 50 MB at boost level 2 and 100 MB at level 3. If you post in a busy community server, check its boost level before you compress anything, because the limit that applies is whichever is higher.

Email works differently. Gmail lets you attach up to 25 MB per message, and anything bigger is turned into a Google Drive link automatically when you add it. Outlook.com stops at 20 MB of attachments and offers a OneDrive link above that. Many company mail servers sit lower still, often at 10 MB, and they bounce oversized mail without telling you which side rejected it. Chat apps have generous file limits but quietly re-encode videos sent as ordinary media, so the size limit is not the only thing that decides what the person on the other end actually sees.

The table below collects the numbers that matter as of 2024 and 2025. Treat them as a starting point and look at the service's own help page when a file sits right on the edge, since plans and regions differ. For the rest of this guide, the working targets are 10 MB for Discord and most work email, 25 MB for Gmail and 20 MB for Outlook. Pick the smallest limit among the people you are sending to, because a file that passes your mailbox can still be rejected by theirs.

A video file is mostly a stream of bits delivered at a steady average rate, the bitrate, measured in megabits per second (Mbps). Multiply that rate by the number of seconds and you have the file size in megabits; divide by 8 for megabytes. Resolution, codec and frame rate only matter because they change how many bits each second needs to look acceptable. This is why a 4K clip and a 480p clip can be exactly the same size: if both run at 2 Mbps for 30 seconds, both come out at about 7.5 MB, one of them just looks much worse than it would at its natural bitrate.

Work the formula backward and you get the budget for your limit. Ten megabytes is 80 megabits. Spread over a 60-second clip, that allows about 1.33 Mbps for everything, picture and sound together. A 25 MB Gmail target is 200 megabits, or about 3.3 Mbps over the same minute. Audio takes its share first: at 128 kbps, sound uses close to 1 MB per minute, which is a tenth of a Discord budget. The rest goes to the picture, and that leftover number is what decides whether the result looks sharp or smeared.

The same formula explains why phone footage is so heavy. Apple lists roughly 170 MB per minute for 4K at 30 fps in the High Efficiency format and about 60 MB per minute for 1080p at 30 fps, which works out to bitrates far above anything a 10 MB file can hold. Fitting a minute of 4K into 10 MB is a 17-fold cut. That is possible, but only by spending far fewer bits per frame, which in practice means fewer pixels per frame as well.

Trimming is the strongest lever because it shrinks the duration in the formula, and every second you remove hands its bits to the seconds you keep. Cut the countdown, the shaky first moments and the long goodbye at the end, and a 90-second clip often becomes a 40-second one with nothing worth seeing lost. Resolution comes next. 720p has 44% of the pixels of 1080p, so at the same bitrate each pixel gets more than twice the data. For anything watched on a phone or in a Discord chat window, 720p at a healthy bitrate looks cleaner than 1080p that is starved.

Bitrate or quality is the direct control. Encoders let you either set an average bitrate, which fixes the size, or a constant quality value, which fixes the look and lets the size float. In x264, the H.264 encoder used by HandBrake and FFmpeg, that quality value is called CRF; the default is 23, lower numbers mean better quality, and FFmpeg's documentation notes that raising it by 6 roughly halves the file. Constant quality is great for archiving, but it cannot promise you will land under 10 MB, so it is the wrong tool when a hard limit applies.

Frame rate and audio are the smaller levers. Dropping 60 fps footage to 30 fps saves a noticeable share, though not a full half, since neighboring frames compress well against each other. Talks, tutorials and screen recordings lose nothing visible at 30 fps or even 24 fps. For sound, 128 kbps AAC is comfortable for music, 96 kbps is plenty for voices, and 64 kbps still works for one person talking. On a short silent clip, such as a game highlight with music you do not need, removing the audio track gives the picture almost a full extra megabyte per minute.

A target-size encoder does the arithmetic above for you. It reads the clip's duration, subtracts the audio share, keeps a small margin for the container overhead, and sets the video bitrate to whatever is left. With two-pass encoding, the first pass scans the whole clip to find out where the motion is; the second pass then spends more bits on busy scenes and fewer on static ones while keeping the average on target. The compress video tool works this way: leave Compress by on Target size, type the limit, and Two-pass encoding is already on.

The container and codec matter as much as the size. H.264 video with AAC audio inside an MP4 file plays inline in Discord, previews in Gmail and Outlook, and opens on every phone, laptop and smart TV made in the last decade. H.265 (HEVC), AV1 and VP9 squeeze more quality into the same megabytes, but a friend on an older Windows laptop or a browser without the right decoder may only see a download link or a black frame. iPhones record HEVC in MOV by default under the High Efficiency setting, which is why converting MOV to MP4 and compressing often happen in the same step.

Two habits keep target-size encodes reliable. First, aim slightly under the limit, at 9.5 MB rather than exactly 10 MB, because operating systems count megabytes differently and a file showing 10.0 MB in one place can be rejected in another. Second, always start from the original recording. Every lossy re-encode throws away detail, and compressing a file that a chat app already compressed stacks the damage. If the first result is too soft, go back to the source and change the resolution, instead of running the small file through the compressor again.

The quickest route for a one-off clip is a browser tool, because the target-size math, two-pass encoding and H.264 MP4 output are already set up. UltKit takes files up to 95 MB each and up to 20 at a time, with nothing to install and no sign-up, and deletes uploads 30 minutes after processing. The compress video to 10 MB page opens with Target size at 10 MB and Maximum resolution at 720p; for Gmail, type 24 MB into the same field. If the recording is longer than you need, cut it first with trim video so the budget goes to the part that matters.

HandBrake is the desktop route: free, open source, and available for Windows, macOS and Linux from handbrake.fr. It no longer has a target-size field, so you calculate the bitrate yourself and type it in. Phones are the third route. They cannot set a target size, but recording at a lower resolution and trimming in the gallery app before sharing go a long way, and both happen before any compression at all. The columns below give the steps for each.

At 10 MB per minute you have roughly 1.2 Mbps for the picture after 128 kbps audio. With H.264 at 720p and 30 fps, that is enough for talking heads, product demos, pets, and most everyday phone clips: on a phone screen the result looks close to the original, and on a laptop you will notice softer fine detail such as hair, grass and distant text. Screen recordings with large flat areas look especially good at this rate, because static backgrounds cost almost nothing to encode.

Fast motion is where the budget runs out. Game footage, sports, handheld walking shots, confetti and water all change most of the frame every second, and at 1.2 Mbps they break into blocks during the busiest moments. For that kind of material, drop to 480p, lower the frame rate to 30 fps if the source was 60, or cut the clip to the 20 or 30 seconds that matter. A 30-second gameplay highlight at 10 MB gets about 2.5 Mbps, which is plenty for 720p and often fine for calm 1080p.

Longer videos follow the same curve downward. Two minutes in 10 MB leaves about 0.6 Mbps, which needs 480p to stay readable. Five minutes leaves around 0.2 Mbps, enough only for 360p speech where the picture barely matters. At that point the honest answer is that 10 MB is the wrong container for the video. Moving the target up to 25 MB for Gmail, or 50 MB for a Nitro Basic friend, changes the outcome far more than any encoder setting will.

Compression is the right move when the clip is short, when it should play inline in a chat, or when the receiver will never open a cloud link. It is the wrong move when the file is long, when detail matters, or when the recipient needs the original for editing. A wedding video, a property walkthrough, a recorded lecture or footage you are handing to an editor should travel at full quality. In those cases, Google Drive, OneDrive, iCloud Drive or Dropbox links cost you nothing in quality and avoid all of the trade-offs above.

Several services already make that switch for you. Gmail turns an attachment over 25 MB into a Drive link, Outlook.com offers OneDrive above 20 MB, and Apple Mail's Mail Drop sends files up to 5 GB through iCloud and keeps them available for 30 days. On Discord, a shared cloud link shows a preview card instead of a player, so viewers click through to watch. A practical split: compress anything under about two minutes that should play right in the chat, and link everything longer or more important.