If you're trying to upload a video to Framer, you may have run into the 50 MB video size limit.

That means a video larger than 50 MB needs to be compressed before you can upload it directly.

But there's a bigger issue that Framer users often overlook:

Your video's file size isn't the same thing as your website's bandwidth usage.

A 10 MB video can potentially use hundreds of gigabytes of bandwidth if enough visitors watch it.

So if you're building a Framer website with multiple videos, the question isn't just:

"How do I get my video under 50 MB?"

It's also:

"How much bandwidth will this video consume when people visit my website?"

Let's break it down.

What is the Framer video size limit?

The direct upload limit for a Framer video is 50 MB per video.

So if your video is:

• 5 MB — you can upload it

• 20 MB — you can upload it

• 49 MB — you can upload it

• 50 MB — you can upload it

• 60 MB — you'll need to reduce the file size or host it elsewhere

However, 50 MB should not be treated as the ideal size for a website video.

Framer recommends keeping looping videos under 5 MB because browsers typically have limited media caching capacity. Larger looping videos can be downloaded again when they replay, increasing bandwidth usage.

So there are really two numbers to remember:

50 MB = upload limit

Under 5 MB = recommended target for looping videos

The real Framer video problem: bandwidth

This is where things get more interesting.

Framer defines bandwidth as the total amount of data your website delivers to visitors. Every time someone loads an asset such as a video, that data contributes to your bandwidth usage.

Let's say you have a 20 MB video on your website.

If 100 people download it:

20 MB × 100 = 2 GB

If 1,000 people download it:

20 MB × 1,000 = 20 GB

If 10,000 people download it:

20 MB × 10,000 = 200 GB

That's from one video.

Now imagine your Framer website has five or ten videos.

This is why simply getting every video below the 50 MB upload limit doesn't necessarily solve the problem.

A 5 MB video can still consume a lot of bandwidth

This is an important distinction.

Imagine you have a 5 MB autoplaying hero video.

5 MB sounds tiny.

But if 10,000 visitors load that video:

5 MB × 10,000 = 50 GB

And if you have multiple videos loading on the same page, the numbers can increase quickly.

Framer specifically identifies full-screen, autoplaying and unoptimized videos as some of the largest contributors to bandwidth usage.

So smaller videos help, but the number of visitors and how those videos are loaded matter too.

Autoplay videos can make the problem worse

Autoplay is one of the most common reasons Framer websites use a lot of video bandwidth.

Think about a typical modern landing page:

• Hero video

• Product demo

• Three scrolling video sections

• Portfolio previews

• Background animations

A visitor might not even intentionally watch these videos.

But if they're loaded automatically, your website can still deliver a significant amount of video data.

Framer recommends using posters and lazy loading where possible. Videos with posters can be loaded closer to when they're needed, while muted looping videos can pause when they're outside the viewport.

That can reduce unnecessary downloads.

Framer doesn't automatically compress your videos

This is another important part of the equation.

Framer optimizes how videos load, but it does not automatically compress the video file itself.

If you upload a 4K video, Framer says the uploaded video remains unaltered and can be served at its original resolution, even on smaller screens.

That means you should optimize your video before uploading it.

For example:

Original: 100 MB

Compressed: 12 MB

Or:

Original: 50 MB

Compressed: 6 MB

The exact result depends on the video's resolution, duration, bitrate, codec and content.

For most website videos, you don't need to preserve the same file that you'd use as your production master.

How to reduce a Framer video below 50 MB

If your video is over the limit, compression is the easiest solution.

You can reduce the file size by:

1. Lowering the resolution

You probably don't need a 4K video for a small background section.

1080p or even 720p may be sufficient depending on how the video is displayed.

2. Reducing the bitrate

Bitrate has a major impact on file size.

Reducing it can make a video dramatically smaller while retaining good visual quality.

3. Removing audio

If your video is a muted background animation, there's often no reason to include an audio track.

4. Shortening the video

A 10-second looping video will generally be much easier to deliver than a two-minute video.

5. Using an efficient codec

Framer recommends well-supported formats such as H.264 with an MP4 extension for broad browser compatibility.

Tools such as HandBrake and FFmpeg can be used to compress videos before uploading them.

What if you have lots of videos?

This is where compression alone may not be enough.

Imagine a portfolio website with:

20 videos × 8 MB each = 160 MB of video assets

You could technically upload those videos individually.

But every visitor doesn't necessarily need to download all 20 videos.

And if the videos are repeatedly requested by visitors, the total bandwidth consumption can become much larger than the storage size.

Framer's own bandwidth documentation recommends identifying bandwidth-heavy assets through the Framer dashboard and browser developer tools.

For a video-heavy website, this is often a better way to think about the problem:

Storage = how large your videos are

Bandwidth = how much video data your visitors actually receive

Those are two different things.

Host your videos outside Framer

If your videos are too large or you're building a website with lots of video, another option is to host them externally.

Framer supports externally hosted MP4 files through its Video component, and its documentation specifically explains using external video hosting to reduce the load on your Framer site.

Instead of:

Video → Framer → Visitor

you can use:

Video → External video host → Visitor

while Framer handles the website and video component.

This can be particularly useful when you have lots of background videos, portfolio clips or high-resolution media.

Nodstream: video hosting built for Framer

This is exactly the problem Nodstream is designed around.

Instead of uploading your videos directly to Framer, you can upload them to Nodstream, where they are compressed and hosted separately.

You then copy the video URL and add it to Framer's Video component.

So your workflow becomes:

Upload → Compress → Host → Copy URL → Add to Framer

Nodstream's Framer plugin is specifically designed for this workflow

The important part is that Framer handles the design and player while the video is served from Nodstream.

That makes the approach particularly useful for websites that rely heavily on video.

When should you use Framer's built-in video hosting?

You don't necessarily need external video hosting for every Framer website.

Framer's native video component can be perfectly suitable if you have a small number of properly optimized videos.

For example:

• One small hero video

• A short product demonstration

• A few lightweight background loops

In those cases, simply compressing your videos may be enough.

But external hosting becomes more interesting when you're dealing with:

• Lots of videos

• Large videos

• Autoplay backgrounds

• Portfolio websites

• Video-heavy landing pages

• High visitor traffic

• Videos that regularly push your bandwidth usage upward

Why Nodstream can make sense for video-heavy Framer sites

Nodstream is built specifically around the Framer video workflow rather than being a general-purpose video platform.

You upload the video, Nodstream compresses and hosts it, and you use the resulting URL inside Framer.

Its Framer plugin currently supports uploads of up to 240 MB per video, meaning you aren't constrained by the same 50 MB direct-upload ceiling when using Nodstream.

That can be useful if you're starting with a large source file and don't want to manually compress it before every upload.

And because the video is hosted separately, the goal isn't just to solve the 50 MB upload problem.

It's to solve the bigger video bandwidth problem.

Framer video size limit vs. bandwidth

Here's the simplest way to think about it:

The key point is that file size and bandwidth are not the same problem.

A 50 MB upload limit tells you how large an individual file can be.

Your bandwidth usage tells you how much data your website is actually delivering to visitors.

Final answer: What is the Framer video size limit?

The Framer video upload limit is 50 MB per video.

If your video is over 50 MB, compress it or host it externally.

If you're dealing with multiple videos or high traffic, external video hosting can solve a bigger problem than the upload limit.

And if you specifically want a Framer-focused option, Nodstream lets you upload, compress and host videos separately, then use the video URL directly inside Framer.