Free · Fast · Privacy-first

Compress Video for Email

Most email services refuse attachments larger than 10 to 25MB, and corporate Exchange servers often draw the line even lower as a spam mitigation measure.

⚡

Compresses to email attachment limits

🔒

Works with all major email providers

✨

Supports MP4, MOV, AVI, and more

⚡

Free, no watermark, no sign-up

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this Video Compressor to your website

Drop the Video Compressor into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/video-tools/video-compressor?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Video Compressor by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/video-tools/video-compressor?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Video Compressor by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Email Video Attachment Limits: Why They Exist and How to Work Within Them

Email attachment size limits exist for a tangle of reasons that vary by provider, and understanding the landscape makes it easier to choose a target size that will reliably deliver. Gmail caps individual messages at 25MB across all attachments combined, after which it offers to convert the attachment into a Google Drive link instead. Outlook.com and the Microsoft 365 consumer tier cap at 20MB. Yahoo Mail allows 25MB. Corporate email servers, particularly those running Microsoft Exchange or open source mail transport agents like Postfix, are often configured by IT administrators to reject anything above 10MB as a combined spam mitigation and storage protection measure. The practical universal ceiling that will deliver to virtually any address on the planet is therefore 10MB, which is the number to target when you do not know what kind of server sits at the other end.

Compressing video for email is a balancing act between three competing priorities: hitting the file size ceiling, preserving enough visual quality that the video still conveys its intended message, and producing a format that the recipient's mail client can play inline without prompting them to download an unfamiliar codec. The universal compatibility winner remains H.264 video inside an MP4 container with AAC audio, because that combination plays natively in Outlook desktop, Apple Mail, Gmail's web client, and every major mobile email app from iOS Mail to Gmail for Android to Outlook Mobile. H.265 produces noticeably smaller files for the same visual quality but introduces a real risk that older corporate Windows machines or aging Android handsets will fail to play it back, which defeats the purpose of compressing in the first place.

For videos that simply cannot be compressed down to a deliverable size without becoming unwatchable, the professional fallback is to embed a single high quality still frame or a short looping GIF directly into the email body and link it to a hosted full version on YouTube, Vimeo, Google Drive, or Loom. The recipient sees something visually compelling at the moment they open the email, which raises the click through rate compared to a bare link, and the hosted video plays back at full quality through a browser rather than being squeezed through email attachment compression. This approach also gives you analytics: hosted video platforms report exactly who opened the link, how long they watched, and where they dropped off, which is often more valuable than confirming the attachment arrived.

It is also worth knowing how each side of the email chain handles attachments. Unlike messaging apps such as WhatsApp or iMessage, mainstream email clients do not re encode attachments after you hit send. The bytes you attach are the bytes that arrive in the recipient's mailbox, modulo MIME encoding overhead which adds roughly 33 percent to transmission size but does not affect the file as it lands. That means the work you do compressing the video locally is the work that determines what the recipient sees. The exception is mobile email apps on iOS, which sometimes offer to resize photo and video attachments at send time. Using a dedicated compressor first gives you predictable control over the final size and quality.

Google: Gmail attachment size limits Microsoft: Outlook attachment limits

How to use this tool

💡

Upload your video and set the target size to 20MB (for most email providers) or 10MB (for Gmail default). The tool adjusts compression automatically.

How It Works

Step-by-step guide to compress video for email:

1
Upload Your Video
Open FixTools in your browser and drag your video into the upload area, or click the button to pick a file from disk. The tool accepts MP4, MOV, AVI, MKV, and other common containers without needing a separate conversion step first. There is no maximum file size on the input, so you can drop in raw camera exports, screen recordings, or editor outputs that are hundreds of megabytes large.
2
Choose Your Email Size Target
Set the target output size based on who you are sending to. Use 20MB for Gmail, Yahoo Mail, and Outlook.com personal accounts; drop to 10MB for corporate or government addresses where Exchange filters tend to reject anything larger; or pick 5MB if you want guaranteed delivery across even the strictest filtering rules. The compressor will adjust bitrate, resolution, and codec automatically to hit the chosen number.
3
Download and Attach to Your Email
Click Compress, wait for the encode to finish, and download the result. Open your email client as you normally would, attach the compressed file, and send. The recipient gets a video that plays inline in their email client on desktop or mobile, with no cloud login, sharing prompt, or external service required to view it.

Real-world examples

Common situations where this approach makes a real difference:

Sending a proposal video to a client

A two minute company overview or product pitch video that exports out of your editor at 85MB needs to land in a prospect's inbox as part of a formal proposal email. Compressing it to 20MB at 720p preserves a professional polish, plays inline in their mail client, and keeps the entire pitch contained in one email rather than fragmenting your message across a separate cloud sharing link they may forget to click on.

Sharing a short training video

An internal training clip showing staff how to operate a new piece of software or follow a safety procedure runs ninety seconds and weighs 150MB straight out of the screen recorder. Compressing it to 15MB lets you email the whole company at once, satisfies even strict corporate Exchange attachment limits, and ensures every team member receives the same training material without anyone being blocked by mailbox quotas.

Submitting evidence to an insurance claim

A claim adjuster requests video evidence of property damage by email, and your phone recording weighs in at 200MB. Compressing it to 10MB makes the file safely deliverable through both your outbound mail server and the insurer's incoming filters, keeps a clean paper trail of the submission, and avoids the friction of setting up a cloud share that the adjuster may not have the time or permissions to access.

Sending a personalised message to a remote relative

A short personal video message such as a birthday greeting, a tour of a new home, or a baby's first steps needs to reach a relative who only ever checks email and has no interest in learning new apps. Compressing the 120MB phone capture to 18MB lets you email it directly, the recipient sees it the moment they open the message, and nothing about the workflow requires them to install anything new.

When to use this guide

Use when a client, colleague, or family member needs a video as an email attachment but your file exceeds the attachment limit.

Pro tips

Get better results with these expert suggestions:

Compress to 10MB for universal deliverability

Corporate email servers and aggressive spam filters often reject attachments over 10MB. Compressing to 10MB ensures your video reaches every inbox, including strict corporate accounts with Exchange filtering.

720p at 1.5 Mbps gives about 11MB per minute

As a rule of thumb: 720p H.264 at 1.5 Mbps produces roughly 11MB per minute of video. A 1-minute video at this setting will be about 11MB. Adjust resolution and bitrate proportionally for your target file size and video length.

H.264 MP4 is the safest email format

H.265 is more efficient but not universally supported in email clients. H.264 MP4 plays in Outlook, Apple Mail, Gmail browser, and all mobile email apps without any codec installation. Always use H.264 for email attachments.

Test deliverability by sending to your own address first

Before sending the compressed video to a client or important contact, send it to yourself first. This confirms the attachment size is accepted, the video plays correctly in your email client, and the audio and video are in sync after compression.

Different email providers have different limits

Gmail: 25MB. Outlook: 20MB. Yahoo Mail: 25MB. Corporate email servers often limit to 10MB. When in doubt, compress to 10MB to ensure delivery across all providers and corporate firewalls.

Consider a sharing link for videos over 3 minutes

A 3-minute video at watchable quality (720p, 2 Mbps) is about 45MB, far above email limits. For longer videos, compress to a preview (30 seconds) and share the full video via a Google Drive or Dropbox link.

Add the video as a thumbnail with a link

A professional alternative to attaching video: compress a still frame as a JPEG, embed it in the email, and link it to the full video in cloud storage. This keeps email deliverability high and allows recipients to watch in a browser.

FAQ

Frequently asked questions

The maximum varies by provider and how the recipient's server is configured. Gmail allows total attachments up to 25MB per message, Outlook.com 20MB, Yahoo Mail 25MB. Microsoft 365 business plans can be configured up to 150MB per attachment but most organisations cap inbound mail at 25 to 50MB to manage mailbox storage. Government and corporate Exchange servers commonly limit to 10MB and sometimes lower. When the recipient is unknown, target 10MB for universal deliverability. When you know you are sending Gmail to Gmail, you can safely use up to 25MB of total attachments per message.

Use H.264 video inside an MP4 container with AAC audio for the broadest possible compatibility across email clients and operating systems. MP4 H.264 plays natively in Outlook on Windows, Apple Mail on macOS and iOS, Gmail's web client in any browser, and every mainstream mobile email app, without requiring any additional codec installation. Avoid Windows specific formats like WMV that fail on Mac and mobile, avoid MKV which is essentially a desktop container with patchy mobile support, and avoid H.265 unless you have specifically verified the recipient's setup can play it. When in doubt the answer is always H.264 MP4.

When a video genuinely cannot be compressed to deliverable size without becoming unwatchable, upload it to a hosted service such as Google Drive, Dropbox, OneDrive, YouTube (set to unlisted if it is not for public consumption), Vimeo, or Loom, and paste the share link into the email body. This approach has effectively no size ceiling, lets the recipient stream the video at full quality through their browser, and often provides view analytics so you know whether the link was opened. For polish, embed a still frame as the email's inline image and hyperlink it to the hosted video so recipients see a visual rather than a bare URL.

For videos under about two minutes in length, compressing down to a 10 to 20MB email attachment produces quality that is genuinely fine for almost any business context: 720p resolution at 1.5 to 2 megabits per second looks crisp on a laptop screen and entirely clean on a phone. For longer videos or content where quality is critical, such as showreels, finished marketing assets, or anything intended to represent your brand, the compression required to fit inside email limits starts to introduce visible artefacts. In those cases use a hosted link rather than degrading the file to the point where it undermines the message it is supposed to deliver.

Yes, every modern smartphone email app supports video attachments up to the provider's underlying size limit. On iOS, the Mail app and Photos share sheet both offer to reduce the size of large videos at the moment you attach them, with options ranging from small to actual size. On Android, Google Photos provides a compress and share workflow that handles common email size ceilings automatically. These built in options are convenient but lack fine control over the final size, so for predictable results, especially when sending to a specific corporate inbox with a known limit, use a dedicated compressor on a laptop or in a mobile browser.

There are three common causes when a compressed video bounces or refuses to attach. First, the file may still be above the recipient's server limit even though it fits under your provider's outbound limit, which often happens with corporate Exchange servers. Second, your own outbound mail server may have a stricter attachment ceiling than the email client interface suggests, particularly on company managed Outlook setups. Third, some highly secured mail servers block all video attachments outright as a policy regardless of size. If direct attachment fails for any of these reasons, switch to a cloud sharing link as the reliable fallback.

Mainstream desktop and web email clients do not re encode attached video files. The bytes you attach are the bytes the recipient downloads, with only MIME encoding overhead added in transmission and then stripped at the other end. Gmail does not re encode. Outlook does not re encode. Apple Mail does not re encode. The one exception is mobile email apps on iOS, which sometimes prompt to resize large photo and video attachments at the moment of sending, but only if you accept the prompt. Using a desktop compressor first means you control the final file completely without trusting any automatic prompt.

Email itself has no native attachment password mechanism, but there are two practical workarounds. The simplest is to compress the video first and then wrap it in a password protected ZIP or 7z archive using built in tools on Windows, macOS, or Linux, and share the password through a separate channel such as a phone call or text message. The more robust option is to upload the compressed video to a service like Google Drive, OneDrive, or Tresorit and use the platform's built in access controls to restrict viewing to specific email addresses or require a one time password.

Compression time depends on the original file length, resolution, and how powerful the device running the compressor is. For a typical case, a two minute 1080p MP4 compressed down to a 20MB email target takes roughly thirty to ninety seconds in a modern laptop browser using FixTools, and a similar time on a fast desktop. Longer source files and higher source resolutions extend the encode time proportionally. Hardware accelerated encoders in native desktop apps are faster than browser based WebAssembly encoders but require installing software, which for most email use cases is not worth the speed gain.

No. FixTools processes the compression in your browser, which means the original file and the compressed output exist only inside your current session. Nothing is uploaded to a server, stored in a database, or scanned by a third party. When you close the tab the files are gone from the tool entirely. This matters when emailing video evidence in a legal matter, internal corporate communications, personal family footage, or anything else where you would prefer the file never sit on someone else's infrastructure even briefly.