Skip to content
uncompressed.io

The reel, at 8K

Where can I host an 8K showreel?
Somewhere that never re-encodes it.

A reel is not a broadcast. It is one file sent to one named person, and it has about ninety seconds to make its case. Host it where the bytes arrive as you exported them, and be straight about the part no host controls: 8K plays only when the viewer's hardware decodes it.

See plans and storage

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

Updated September 2026

The short answer

A reel has one hosting problem
and one it cannot.

A showreel is not published, it is sent. One file, one link, one named viewer: a producer, a commissioner, an agency producer with forty other reels open in tabs. That changes what hosting has to do, and it narrows the question to two things.

The first thing is whether the host alters the file. That one is solvable, and the solution is a host with no encode step. uncompressed.io stores the file you upload and hands the player those same bytes. There is no adaptive ladder, no rendition list and no lower version standing by, so nothing on our side imposes a resolution ceiling or a bitrate ceiling. An 8K HEVC or AV1 master is served exactly as you exported it. The one real limit in the upload path is 50 GB per file, and it is checked in the browser before the transfer begins rather than discovered an hour in.

The second thing is whether the viewer’s machine can decode 8K, and no host on earth solves that. 8K plays when the viewer’s hardware decodes it. Every sentence on this page carries that caveat, because a file streaming untouched from our side says nothing about what the machine at the other end can do with it.

0

transcodes

No ladder, no renditions, nothing between your export and the player

50 GB

per file

The only ceiling in the upload path. No resolution or bitrate ceiling exists

4K

where Vimeo's ladder ends

Its published renditions stop at 4K; above that a 5K to 8K transcode is conditional

0

seats for the viewer

External client viewers never need a paid seat, and storage is the only meter

The caveat that comes first

8K playback depends
on the viewer's silicon.

This is the part most 8K hosting pages bury. We are putting it above the product, because a reel that will not open is worse than a reel at a lower resolution.

Decoding 8K is work done by the recipient’s machine. A host can guarantee that the bytes leaving its storage are the bytes you uploaded. It cannot guarantee that a laptop, a phone or a five-year-old workstation has a decoder for the codec, the profile and the frame size you chose. Those are separate questions and they are answered by hardware.

The best published evidence of how narrow above-4K support is comes from Vimeo, not from us. Its article on watching above 4K lists Safari 11 and up and Edge 15 and up with supported hardware, macOS 10.13 High Sierra and Windows 10, and states that mobile devices on iOS and Android, including the Vimeo app and mobile browsers, do not support playback above 4K. Vimeo is not being restrictive there. It is describing the device population, and every host, ours included, faces the same population.

What we can promise, and what we cannot

We can promise that nothing re-encodes your master, that the file streamed is the file stored, and that no ceiling on our side sits below your export. We cannot promise that a particular reviewer’s machine decodes 8K, and we will not imply it. Send a fifteen-second test clip to the actual recipient before you send the reel. That test answers the question in a minute, and nothing else does.

What the usual homes do with an 8K reel

A reel becomes a rendition
of somebody else's decision.

Vimeo publishes its playback ladder: 240p, 360p, 540p, 720p, 1080p at 60fps, 2K and 4K. Its own wording is that the bitrates listed for each resolution are a maximum, and that a video could transcode at a lower bitrate depending on the complexity of the image. Above 4K, Vimeo states that videos are delivered using the HEVC codec, and that it will only generate a 5K to 8K transcode if the creator uploaded the video as an HDR video with greater than 5K resolution. Read that as the condition it is. An 8K SDR reel, which is what most 8K reels are, does not meet it. Two other Vimeo behaviours matter to a reel specifically: footage above 60 fps has its frame rate automatically reduced, and all uploads are converted to square pixels.

YouTube is direct about the mechanism. Its help centre states that YouTube always re-encodes videos to optimize their playback quality. It lists 4320p at 7680 by 4320 among its recommended 16:9 resolutions, and separately states that in 2022 it started removing support for playback at resolutions between 4K and 8K. Nothing on the pages fetched for this guide states what an 8K upload is delivered at today. For a reel there are three further published facts worth knowing: YouTube’s Terms grant it the right to monetize your content, its help centre says ads may appear on videos in channels not in the Partner Program, related videos cannot be disabled in the embedded player, and an unlisted video can be reshared by anyone who has the link.

Vimeo
YouTube
uncompressed.io
What happensto the master
Transcoded into the publishedladder. Over 60 fps is reduced,pixels converted to square.
Always re-encoded, inYouTube's own words, tooptimize playback quality.
Stored as uploaded,served as uploaded.No encode step exists.
Renditionsabove 4K
A 5K to 8K transcode onlywhen the upload is HDRabove 5K, delivered in HEVC.
4320p is a recommendedupload resolution. Playbackbetween 4K and 8K beganbeing removed in 2022.
None. There is one versionof your film and it isthe file you uploaded.
Above 4Kon phones
Not supported on iOS orAndroid, including theVimeo app and mobilebrowsers.
Not published on thepages fetched forthis guide.
Decided by the viewer'shardware. 8K plays whenthat hardware decodes it.
Your logoin the player
Requires Standard, Advanced,Pro, Business, Premiumor Enterprise.
The branding parameter isdeprecated and hasno effect.
No platform logo on anyplan. The only logo isthe one you upload.
Ads onyour reel
The Free plan page statesno ads before, after oron your video.
The Terms grant a rightto monetize. Ads may appearon channels not in thePartner Program.
None. No ads, no suggestedvideos, no end screen,on any plan.
Viewer getsthe original
Letting viewers downloadrequires a paid plan.
Not published on thepages fetched forthis guide.
A per-film switch hands overthe exact stored object,byte for byte, on every plan.
Per-fileceiling
Advises keeping files under200 GB. No uploadslonger than 24 hours.
256 GB or 12 hours,whichever is less.
50 GB per file, checked inthe browser before thetransfer starts.
The meteron views
A monthly bandwidththreshold of 2 TB, withnotifications and possiblesuspension if unresolved.
Not published on thepages fetched forthis guide.
Storage only. No bandwidthcaps and no per-view charge.

Vimeo and YouTube cells quote their own help centres, developer documentation and terms, fetched 7 September 2026. Where a cell says not published, it means no official page fetched for this guide states it, not that the opposite is true.

The 50 GB ceiling, in minutes

A file ceiling
is not the constraint on a reel.

We publish one hard number, so it deserves arithmetic rather than reassurance. The runtime 50 GB buys depends entirely on the data rate you finished at, and that rate is a choice you make in your export dialog. We impose no bitrate ceiling and recommend no 8K rate.

Video bit rate
Runtime inside 50 GB
Vimeo's 8K uploadrecommendation, low end
50 Mbps
about 2 h 13 min
Vimeo's 8K uploadrecommendation, high end
80 Mbps
about 1 h 23 min
A heavier 8K exportyou might choose
120 Mbps
about 55 min
A very heavy 8K exportyou might choose
200 Mbps
about 33 min

Runtime computed from the stated bit rate, counting 50 GB as 50 billion bytes and ignoring the audio track. The 50 and 80 Mbps rows are Vimeo's published 8K upload recommendation, quoted as an upload recommendation. The 120 and 200 Mbps rows are arithmetic at rates a colourist might pick; they are export choices, not limits imposed here and not figures from any vendor.

A showreel runs one to three minutes. At every rate in that table, a reel fits many times over, which is the practical point: for this use case the 50 GB ceiling is irrelevant. It becomes real on long-form 8K work, and the category view of that trade lives on our 8K video hosting guide, which covers what each platform does with a long 8K master rather than with a reel.

The honest part

For most reels,
8K is the wrong file to send.

This argues against the premise of the page, and it is still true. The person who decides whether you get the job is usually watching on a laptop, and a well-made 4K master will look better to them than an 8K file their machine struggles to decode.

The complaint is usually bitrate, not pixels

Macroblocking in smoke, banding in a sky, mush where the grain used to be: those are starved-bitrate artifacts, and more pixels do not fix them. A 4K master served untouched does, and it plays on far more machines. Resolution is the expensive answer to a bitrate problem.

8K is often an acquisition format

Plenty of 8K exists so the edit can punch in, reframe and stabilise. If the finished reel is a 4K or 2K deliverable, deliver that. Nobody needs to stream your headroom, and the reviewer cannot see it anyway.

Your reviewer may be on a phone

Notes come back from a producer on a train more often than from a suite. Vimeo excludes iOS and Android from above-4K playback entirely, which is a fact about phones rather than about Vimeo. If that is your audience, an 8K master is the wrong deliverable.

Camera RAW is not a delivery format

R3D, BRAW, ARRIRAW, N-RAW, X-OCN and ProRes RAW never stream in a browser, here or anywhere. The compatible macOS app is the only route for RAW and ProRes playback. For a reel sent by link, finish to HEVC or AV1 and upload that.

When 8K is genuinely right, it is right for a specific reason: the reel is going to a colourist, a post supervisor or a client with a large display and a machine chosen for the job, and the whole point of the send is that they see the resolution and the grade you actually finished. In that case the thing you need from a host is that it changes nothing, and that it does not decide on your behalf which rendition the viewer receives.

How to send it

Export, test,
then one link.

1

Finish to a browser-decodable codec

Export the reel to HEVC or AV1 in MP4 or MOV at the rate the work deserves. There is no codec allowlist in our code and no bitrate ceiling; what plays in a browser is decided by the browser. Camera RAW is a storage and archive question, not a streaming one.

2

Test on the recipient's machine, not yours

Upload a fifteen-second slice first and send that link. If it plays clean on their setup, the reel will. If it stalls, you have learned it before the reel went out, and you can send a 4K master instead. 8K plays when the viewer's hardware decodes it, and this step is how you find out which case you are in.

3

Send one clean link, and decide on the download

Each film gets an address like uncompressed.io/you/the-reel, with your logo and accent colour in the player and no platform branding of any kind. Downloads are a per-film switch: turn it on and the viewer receives the exact stored object, byte for byte; leave it off and no download link is ever generated.

4

Recut without breaking the link

Replace the file on the same film and the address, the embed and the share card all keep working. A producer's bookmark from March opens tonight's cut. That matters more for a reel than for anything else you host, because the link is on your resume and on festival forms.

A note on 10-bit 4:2:2

Our side is safe by construction: we never re-encode, so a 10-bit 4:2:2 master is stored and served exactly as it was exported. The browser side is not documented. No vendor publishes whether a video element decodes 10-bit 4:2:2 HEVC, in either direction, and the one primary specification available covers 4:2:0 only. We will not tell you it plays and we will not tell you it fails. Test it with the actual recipient, which is the only answer worth having.

What it costs to keep a reel online

Priced by what you store,
not by who watches it.

An 8K reel is a large file that a small number of important people watch, which is exactly the shape a bandwidth meter punishes. Here, storage is the only meter. The Terms state that the exact file you upload is the file your viewers receive, that there are no bandwidth caps, and that streaming is unlimited on every plan within that plan’s storage allowance. The pricing page adds that external client viewers do not require a paid team seat. A reel that thirty producers open costs the same as one nobody opens.

The ladder is short. Starter is free with 5 GB of hot storage and one film at a time, which is enough to host a single 8K reel and test the whole chain. Lite is $9 a month or $90 a year for 100 GB. Pro is $25 or $250 for 500 GB. Max is $75 or $750 for 1.5 TB hot plus 1 TB cold. Studio is $250 or $2,500 for 2 TB hot plus 2 TB cold. Beyond a plan, storage blocks are $40 per TB of hot storage a month and $20 per TB of cold. If you are building a page of films rather than sending a single reel, the layout and branding side of that is covered in video portfolio hosting for filmmakers.

Questions

Frequently asked

Where can I host an 8K showreel without it being re-encoded?

On a host with no encode step. uncompressed.io stores the file you upload and hands the player those same bytes, so there is no ladder, no rendition list and no resolution or bitrate ceiling on our side. The only limit in the upload path is 50 GB per file, checked in the browser before the transfer starts. Whether the 8K then plays is decided by the viewer's hardware, which is true of every host.

Will a producer actually be able to play my 8K reel?

Only if their machine decodes it, and many do not. Vimeo's own above-4K article is the clearest published evidence: it lists Safari 11 and up and Edge 15 and up with supported hardware, macOS 10.13 and Windows 10, and states that mobile devices on iOS and Android, including the Vimeo app and mobile browsers, do not support playback above 4K. That is a statement about the device population rather than about Vimeo. Send a short test clip before you send the reel.

Does Vimeo play an 8K reel at 8K?

Not for an ordinary SDR upload. Vimeo's published playback ladder runs 240p, 360p, 540p, 720p, 1080p60, 2K and 4K. Above that, Vimeo states that videos beyond 4K are delivered in HEVC and that it will only generate a 5K to 8K transcode if the creator uploaded the video as HDR with greater than 5K resolution. Most 8K reels are SDR, so most 8K reels do not meet that condition.

Does YouTube play 8K?

YouTube lists 4320p at 7680 by 4320 among its recommended 16:9 upload resolutions, and separately states that in 2022 it started removing support for playback at resolutions between 4K and 8K. It also states plainly that YouTube always re-encodes videos to optimize their playback quality. Nothing on the pages fetched for this guide states what an 8K upload is delivered at today, so a reel sent through YouTube is a reel whose delivered image is undocumented.

How long can an 8K reel be if the ceiling is 50 GB per file?

Longer than any reel. At 50 Mbps, the low end of Vimeo's published 8K upload recommendation, 50 GB holds about 2 hours 13 minutes. At 200 Mbps it still holds about 33 minutes. A showreel runs one to three minutes, so the file ceiling is not the binding constraint here. It binds on long-form 8K work, not on a reel.

Should my reel be 8K at all?

Usually not. The person watching is typically on a laptop, and a well-made 4K master will look better to them than an 8K file their machine struggles to decode. Most complaints that send people looking for 8K hosting are bitrate complaints, not pixel-count complaints: macroblocking in the smoke, banding in a sky, mush in the grain. A 4K master served untouched fixes those and plays on far more machines.

Can I upload the camera original, like R3D or BRAW, at 8K?

Not as something that streams. Camera RAW never streams in a browser, here or anywhere, and the honest workflow is to finish to HEVC or ProRes and upload that. The compatible macOS app is the only route for RAW and ProRes playback. For a reel going out by link, export a browser-decodable file.

Send the reel you actually exported

No transcode, no rendition ladder, no resolution or bitrate ceiling on our side. Up to 50 GB per file, storage as the only meter, and a link that keeps working when you recut.

Where Can I Host an 8K Showreel? | uncompressed.io