Webflow is an embed-only platform for real video

How to embed high bitrate video in Webflow.
The upload ceiling is 30 MB, so the file has to live somewhere else.

Webflow has exactly one video upload path, the Background video component, and it accepts files under 30 MB. The video element does not accept uploads at all. That settles the question this page was searched for: you cannot host a high bitrate file inside Webflow, so the real decision is which embed to paste and what it delivers.

See the plans

Video hosting for filmmakers · 5 GB free · Paid plans from USD 9/month

Updated September 2026

Start from what Webflow documents

Webflow does not host video;
it is an embed wrapper.

This is not an opinion about Webflow. It is what Webflow’s own help center says, in two sentences, and both of them close the door on hosting a serious file inside the platform.

30 MB

The only video upload ceiling

The Background video component, in webm, mp4, mov or ogg. It is the single documented video file-size limit anywhere in Webflow.

Video formats the Assets panel takes

Images, documents, audio and animation files only. Video is not a supported asset type.

2.4 s

Of a 100 Mbps master fits in 30 MB

Thirty megabytes is 240 megabits. At 100 megabits a second that is 2.4 seconds of film.

50,000

Character cap on a Code Embed

The iframe you paste is under 400 characters, so the cap is never the problem. The plan gate is.

On the video element, Webflow writes: “Currently, we don’t support uploading video files to the Asset panel and using them in the video element.” The element is a wrapper around someone else’s player, and the help article lists the sources it accepts: YouTube, Vimeo, DailyMotion, Kickstarter, TED, Wistia, Ustream, Livestream, Twitch, Tudou, Hulu, SproutVideo and Vidzflow.

On the Background video component, Webflow writes that it “accepts video files smaller than 30MB with the following formats: webm, mp4, mov, ogg.” That component is the whole of Webflow’s native video hosting. The Assets panel, where every other file on your site lives, takes images to 4 MB, documents and audio to 10 MB and ZIP files to 25 MB, and it does not list video at all.

So there is no version of this question where the answer is “upload the master to Webflow”. A high bitrate file gets onto a Webflow page one way: it lives on a host that will serve it at its own data rate, and an iframe points at it.

The arithmetic nobody does before trying

What 30 MB actually buys:
the answer is seconds, not minutes.

Thirty megabytes is 240 megabits. Divide that by the data rate of your export and you get the length of film that fits. The result is why the background component is a decoration slot and not a hosting product.

Length that fits in 30 MB

What an export at that rate usually is

3 Mbps

80 seconds

A heavily compressed 1080p web loop

8 Mbps

30 seconds

An ordinary 1080p delivery file

12 Mbps

20 seconds

A good 1080p export with motion in it

24 Mbps

10 seconds

A light 4K export

50 Mbps

4.8 seconds

A normal 4K delivery master

100 Mbps

2.4 seconds

A high bitrate 4K master

150 Mbps

1.6 seconds

What a reel page should be serving

The only sourced number in this table is Webflow's 30 MB ceiling for the Background video component. The rest is arithmetic: 30 MB read as 30,000,000 bytes is 240 megabits, and the length that fits is 240 divided by the data rate in megabits per second. Audio is inside that rate. Webflow publishes no output resolution or bitrate for its background-video transcode, and does not document whether the 30 MB is measured before or after that transcode, so treat these lengths as the ceiling on what you can hand it, not on what it gives back.

Read the bottom of that table

A serious export cannot be a Webflow background video at any length worth watching. The component is sized for a soft looping texture behind a headline, which is what Webflow built it for. The moment the video is the content rather than the wallpaper, the file leaves the platform, and the only question left is where it goes and what the visitor is served.

Three ways to get video onto the page

Two of them are Webflow’s;
one of them keeps your bitrate.

Webflow Background video

Webflow Video element

Where thefile lives

Your library, streamedfrom there

Uploaded to Webflowand transcoded

On the third-party hostyou link to

File sizeceiling

5 TB per file, checkedin the browser; the reallimit is your plan storage

Under 30 MB

No upload, so none

Formatsaccepted

Anything you can upload;H.264, HEVC and AV1are what browsers play

webm, mp4, mov, ogg

A link to asupported host

Re-encode

None. The stored bytesare the served bytes

Transcoded to mp4 and webm;no output specs published

Whatever thathost does

Delivereddata rate

Your export's own rate;a 100 Mbps masterplays at 100 Mbps

Undocumented

Set by that host,not by you

Webflow planrequired

A paid Site plan, or a Core,Growth, Agency orFreelancer Workspace

No documentedplan gate

Counts againstWebflowbandwidth

No. Webflow's CDNnever serves the video

Yes. Every byte itsCDN delivers is metered

No. The hostserves the video

Branding onthe player

None at any tier,including free

Your own file onyour own page

Set by that host

Domain thevideo isserved from

uncompressed.io.No custom domain

Your Webflow domain

The host's domain,inside the iframe

Slowconnection

Buffers. There is norendition ladder todrop down to

Small file, sorarely an issue

Set by that host

What it isactually for

A reel, a portfolio page,a case study, a client link

A short decorative loopbehind a headline

A film already publishedsomewhere else

Webflow figures from the help-center articles listed in the sources, all fetched 7 September 2026. Webflow prices come from the May 2026 pricing-change article, not from the pricing page, which could not be retrieved. Our 5 TB per-file figure is a check in the browser, not a server guarantee; on the free plan the practical ceiling is the 5 GB of storage the plan includes.

The one row that surprises people is bandwidth. Webflow meters what its own network delivers for your site: HTML, CSS, JavaScript and assets, counted from bots and humans alike and at any status code. A 30 MB background video is squarely inside that meter. The Premium plan includes 50 GB, which is about 1,600 full plays of a single 30 MB file before anything else on the site is counted. Webflow’s overage rule is that the first month over is a notification with no charge, and a second consecutive month over upgrades the site automatically to a higher plan with an additional fee.

A video inside an iframe is not served by Webflow’s network, so it does not land in that meter. On our side there is no meter to land in either: the Terms state that storage is the only thing measured and there are no bandwidth caps, and the pricing page states unlimited views, uploads and viewers on every plan, the free one included.

The actual procedure

Upload, copy,
paste, publish.

Export a file a browser can decode

H.264, HEVC and AV1 play in a video element. ProRes, DNxHR and camera RAW do not: those are hosted here for client download at full fidelity, not streamed. If the film is finishing in RAW, export to HEVC or ProRes first and upload the export. There is no re-encode on our side, so what you hand over is exactly what a visitor receives.

Upload it and open the Embed panel

Drop the file into your library and open the video. The Embed panel carries eleven player switches, including the custom logo, the title, the views counter, the share button, autoplay, muted and loop, plus three colour swatches. They save instantly and travel with the embed. Vaulted, private and password-protected videos cannot be embedded at all.

Copy the iframe it generates

The snippet is plain HTML with no parameters and no script. It is under 400 characters, comfortably inside Webflow's 50,000 character cap for a Code Embed element.

Add a Code Embed element in Webflow and paste

Webflow gates that element to any active Site plan or to a Core, Growth, Agency or Freelancer Workspace, so a site still on the free Starter plan has to move up first. The May 2026 pricing article lists Basic at 15 dollars a month billed yearly, or 25 dollars a month billed monthly. Paste the iframe as it is: no html, body or head tags, which Webflow rejects inside the element anyway.

Publish, then watch it on a phone

Publish the site and open the page on a phone over mobile data, not office Wi-Fi. That is the test that tells you whether the data rate you chose is right for the audience the page actually gets.

What you paste into the Code Embed element

<iframe
  src="https://uncompressed.io/embed/VIDEO_ID"
  title="Your video title"
  width="1280" height="720"
  frameborder="0" loading="lazy"
  allow="autoplay; fullscreen; picture-in-picture; clipboard-write"
  allowfullscreen
  style="border:0;max-width:100%;aspect-ratio:16/9;height:auto;"></iframe>

Six switches you can set in the URL

Tune one embed
without touching the panel.

The generated snippet carries no parameters. Six of the player settings can be overridden per embed by appending them to the iframe source, which is how the same film behaves one way on a hero section and another way on a case-study page.

autoplay=1

Starts playback on load, and forces muted, because every browser requires that of an autoplaying video.

muted=1

Starts the film with the sound off. The viewer can turn it back on from the control bar.

loop=1

Runs the film back to the start when it ends. The setting a hero section usually wants.

title=1

Shows the film's title as a pill over the frame. Off by default, so the picture arrives bare.

accent=RRGGBB

Six hex digits, no hash. Paints the progress bar fill in your colour.

bg=transparent

Drops the frame around the video so the player floats on your own page background. A hex value paints it instead.

A hero embed on a Webflow page usually ends up as https://uncompressed.io/embed/VIDEO_ID?autoplay=1&loop=1&bg=transparent with the rest left at the panel defaults. Any parameter that is not one of those six is ignored, so there is no hidden switch to hunt for.

Nothing of ours is drawn over the picture. There is no logo, no wordmark and no watermark on the player at any tier, the free plan included, and no ads, no recommended videos and no end screen, because the embed renders the film and one control bar and nothing else. The creator’s own logo can sit on the frame instead, as the transparent file you uploaded, once the logo switch is turned on.

Where this is the wrong answer

Two limits worth knowing,
and one is ours.

No rendition ladder, so a slow line buffers

There is one file and no smaller version of it, which is the whole point on a reel page and a real cost on a busy marketing page. A visitor on a weak connection waits rather than watching a soft version. If the video is decoration that every visitor loads, a small heavily compressed file inside Webflow's own 30 MB background component is the better engineering decision, and this page will not pretend otherwise.

No custom domain

The iframe resolves to uncompressed.io, and creator pages live at yourname.uncompressed.io. There is no way to serve the video from a domain you own. If that is a requirement of the brief, this is the row where we lose, and a platform that sells a custom domain is the honest choice.

8K and very high data rates depend on the viewer

The file is served untouched, so playback depends on the hardware decoder in front of it. An 8K master plays where the viewer's machine can decode 8K, and stutters where it cannot. Nothing on our side changes that, because nothing on our side changes the file.

Where it pays off

A portfolio, a reel, a case study, a client link: pages where a handful of people arrive on purpose and image quality is the entire argument. A 150 Mbps grade reaches them as a 150 Mbps grade instead of as a platform's delivery ceiling, and the player around it carries nobody's brand but yours.

The short version

Webflow builds pages beautifully and does not host video. Keep the 30 MB component for the looping texture behind your headline, where a small file is genuinely the right call. Put the work that has to look like the grade behind a Code Embed element, on a paid Site plan, pointing at a host that serves your export at the rate you exported it.

Questions

Frequently asked

Can I upload a high bitrate video file to Webflow?

No. The only component that accepts a video upload is Background video, and Webflow documents the ceiling as files smaller than 30 MB in webm, mp4, mov or ogg. The video element is an embed wrapper, and Webflow states plainly that uploading video files to the Asset panel and using them in the video element is not supported. Video is not a supported Assets panel type either: that panel takes images, documents, audio and animation files.

Which Webflow plan do I need to paste an embed?

A paid one. Webflow gates the Code Embed element to any active Site plan, or to a Core, Growth, Agency or Freelancer Workspace. A site on the free Starter plan cannot use it, so the embed route starts at the Basic Site plan, which the May 2026 pricing article lists at 15 dollars a month billed yearly or 25 dollars a month billed monthly. The element itself caps custom code at 50,000 characters, and the iframe you paste is under 400.

Does an embedded video count against my Webflow bandwidth?

Webflow meters the bytes its own CDN delivers for your site: HTML, CSS, JavaScript and assets, from bots and humans alike, at any status code. A video streamed from a third-party embed is not one of those bytes, because Webflow's CDN never serves it. The page around the iframe still counts. Our side does not meter bandwidth at all: the Terms state that storage is the only meter, and the pricing page states unlimited views on every plan including the free one.

What bitrate can I actually deliver through the embed?

The one you exported. The player streams the stored bytes with no transcode and no rendition ladder, so a 100 Mbps master plays at 100 Mbps rather than at a platform's delivery ceiling. What plays is what the viewer's browser can decode: H.264, HEVC and AV1 stream. ProRes, DNxHR and camera RAW are hosted for download rather than streamed. 8K and very high data rates depend on the viewer's hardware decoder.

Will the player carry someone else's logo?

No. There is no uncompressed.io logo, wordmark or watermark on the player or on the embed, on any tier including the free one, and there are no ads, no recommended videos and no end screens. The honest limit on the other side: there is no custom domain, so the iframe resolves to uncompressed.io. If the video has to be served from a domain you own, this is the row where we lose.

Should I use this for the hero background on a busy marketing page?

Often not. There is no rendition ladder here, so a viewer on a slow line buffers instead of dropping to a lower quality. For a decorative loop behind a headline, seen by every visitor including the ones on a train, a small heavily compressed file inside Webflow's own 30 MB background component is the better engineering choice. Use the embed where image quality is the point: the reel, the portfolio page, the case study, the client link.

What does Webflow do to a background video after I upload it?

It transcodes it. The help article says the file is transcoded to mp4 and webm for maximum browser support, and asks that videos be optimized for the web. Webflow publishes no output resolution and no output bitrate for that transcode anywhere we could fetch, so there is no documented answer to what comes out the other side.

Put the master on the page, not a proxy of it

The player streams the file you uploaded, at the data rate you exported it at, with no platform logo on it. Start on the free plan with 5 GB, then pick a plan when the library outgrows it.