Before the deal is signed
Send a rough cut to a distributor.
What to send, who gets a link, and what security actually buys you.
A sales agent, an acquisitions executive or a commissioner is about to watch a film that is not finished. The cut is being judged and a leak at this stage costs you a sale, not just your dignity. Here are the decisions in the order you have to make them.
Video hosting for filmmakers · 5 GB free · Paid plans from USD 9/month
Updated September 2026
Decision one
Send a cut
that tells the viewer what it is.
A distributor watching an unfinished film judges what is in front of them. If nobody told them the score is temporary, they judge the temporary score. This is the cheapest thing on the page and the one people skip.
Build one slate card, eight to ten seconds, black, before frame one. It carries the title, the date of the cut, the running time, and two short lists: what is locked and what is temporary. Then put the same two lists in the email, because the executive watching on a phone between meetings will skip the card.
Be specific about temporary. The words “temp music” are not enough on their own. Say which cues are temp and whether a composer is engaged. Say whether the visual effects are grey-box, previz or final, and how many shots are outstanding. Say whether the picture is graded, one-lit or straight from the camera. Say whether the sound is a stereo work mix and whether dialogue levels are final. A viewer told that the mix is temporary hears a temporary mix. A viewer told nothing hears a bad one.
If the film is under an embargo, put the date on the card as well as in the email. Most early press damage is not malice. It is somebody assuming the embargo had passed.
What goes on the slate card
- Title, director, running time of this cut.
- Cut name and date, for example “Assembly 4, 9 September 2026”.
- Locked: what will not change.
- Temporary: music, visual effects, colour, mix, titles, each named individually.
- Outstanding: number of visual effects shots, missing scenes, pickups still to shoot.
- The embargo date, if there is one.
- The recipient’s name, if you are burning one in per viewer.
Decision two
High enough to be judged fairly.
Low enough that it arrives.
Two failure modes sit either side of this decision. A file so heavy it never finishes uploading, or stutters on the viewer’s machine. And a file so squeezed that a week of grading reads as mush.
Export, do not upload the master
A ProRes master is hosted here for download, not for streaming, and camera RAW review requires our compatible macOS app. Browser playback is H.264, HEVC and AV1. Export a viewing file in one of those and upload that; the master stays where it belongs.
The bitrate you export is the bitrate they watch
The player streams the exact bytes you uploaded, with no transcode anywhere, so there is no delivery ladder quietly re-encoding your grade down to something safe. The uploader recommends 80 to 100 Mbps for maximum compatibility, and takes up to 5 TB per file, subject to your available storage.
8K carries a caveat
8K plays when the viewer's hardware decodes it, and you cannot see their laptop from here. A sales agent whose machine stutters blames the film, not the file. Send UHD unless you actually know the machine on the other end.
The last quality decision is really a framing decision. Most cuts that read as flat were watched on laptop speakers with a work mix. You cannot fix the speakers. You can write one line in the email saying the mix is a stereo work mix and dialogue levels are not final, which is the difference between a note about your sound design and a note about your scenes.
Decision three
One recipient.
One link. Every time.
This is the whole discipline of screener distribution. It is boring, it is administration, and it is the part that makes every control further down this page worth anything at all.
The reason is arithmetic. Eleven people on one link and a copy in the wrong place gives you eleven suspects and no way to narrow them. Eleven people on eleven links gives you one. A watermark, a forensic mark and a view log all resolve to a session, and a session is only useful if that session belonged to exactly one named person when you issued it.
Be honest with yourself about the cost, because this is where people quietly give up. A round of fifteen sales agents is fifteen links, fifteen NDAs matched to fifteen names, fifteen expiry dates, and fifteen rows in a document recording what was sent and when. Budget an afternoon for the first round and about an hour for each round after it. No product removes that hour. What a product can do is make each of the fifteen links carry its own identity so the hour pays out later.
It is also why the default sharing model of most video platforms does not fit this job. Vimeo’s help center describes an Unlisted video as one that “can be accessed and shared by anyone who has the video’s unique URL”. That is the vendor describing a transferable link, accurately. A transferable link is a fine way to show a finished film and a poor way to run a controlled round on an unreleased one.
Make the list before you make the links
Name, company, role, and whether they have signed. A person with no signature does not get a link yet. This list is also your delivery record, so start it properly.
Issue one link per name, not per company
The assistant who opens it on behalf of a partner is a second name and a second link. So is the head of acquisitions who wants to show a colleague. Ask who else will watch, and add them before the link goes out.
Set the expiry to the meeting
The link should stop working shortly after the call it exists for. A live link nobody is watching is exposure with no upside, and reissuing one takes seconds.
Write down what you sent
Cut version, date sent, expiry, recipient. When something goes wrong, this document is most of the investigation, and it is the one part that survives you changing platforms.
Decision four
What each control
actually buys you.
Ranked honestly, from the one that changes how a person behaves down to the one that only helps after the damage is done. None of them is a substitute for sending fewer copies.
Ranked by what changes a person's behaviour, not by what sounds strongest in a feature list. On uncompressed.io the session watermark, the forensic per-person mark, capture blocking, AES-256 at rest, short-lived links and the tamper-evident view log are the Vault's native macOS review path.
The screen recording question deserves a plain answer, because it is the one people are sold hardest on. You cannot prevent a viewer recording their own screen in a browser. The specification usually invoked here is Encrypted Media Extensions, and the W3C’s own text says it plainly: “This specification does not define a content protection or Digital Rights Management system. Rather, it defines a common API that may be used to discover, select and interact with such systems as well as with simpler content encryption systems.” It is a way to talk to a protection system, not a protection system.
The rest of the browser surface says the same thing. MDN’s Screen Capture API page documents how a page asks the user to share a screen and the consent model around that, and documents no mechanism for a page to keep its own content out of a capture. The one output-protection lever a web application gets is a query asking whether keys would be usable at a given minimum HDCP version, and MDN describes that as a check about the connection between the machine and a display, run against a hypothetical key. It is a question, not a block.
So the honest position is this. Capture blocking on uncompressed.io belongs to the Vault’s native macOS path, where the operating system exposes that control to an application. It is not a property of a link you paste into an email, ours or anyone else’s. And a phone on a tripod in front of a monitor defeats all of it, everywhere, permanently. Plan for attribution and for consequences, not for prevention.
The comparison most people know
Why an unlisted link
is not a screener programme.
There is nothing wrong with Vimeo, and it is where most unreleased cuts are actually sent. Two lines in Vimeo’s own documentation explain why that is a different thing from running a controlled round.

Vimeo rows quote Vimeo's Help Center, fetched 9 September 2026 and cited below. Vault rows describe the uncompressed.io Vault, a native macOS review path whose access is included on every plan, including the free Starter. What the paid plans change is storage and included team seats: Studio, the top plan, is $250 a month or $2,500 a year with 2 TB hot plus 2 TB cold and five seats, and extra seats are $25 a month, or $300 a year, on any paid plan.
Read those two facts together and the conclusion is not dramatic, just clear. The link travels, by Vimeo’s own description. And the analytics that would tell you who watched are documented for logged-in team members, which the outside sales agent you sent it to is not. So on a plain unlisted link handed to a distributor you have a copy that can be passed on and a record that cannot name who passed it. For a finished film that is fine. For an unreleased one with a deal in play, those are the exact two things you needed.
The part that actually protects the film
The paperwork
is the enforcement layer.
Every technical control above is a deterrent or a forensic aid. The thing that lets you do something about a leak is a signed document with a person’s name on it.
An NDA that names the recipient
The person, not only the company. It should name the film, the cut, the permitted purpose such as evaluation for acquisition, who inside their organisation may watch, the embargo, and the consequence of breach. A blanket company NDA signed three years ago by somebody who has since left is not a control.
A delivery record
Who received what, on what date, at what cut version, expiring when. It is dull to keep and it is the document that turns a leak into a short list of names. Keep it somewhere that outlives the platform you sent from.
An embargo date in writing
In the email, on the slate card, in the NDA, the same date in all three. Ambiguity about when a film may be discussed is the most common cause of early exposure, and it is entirely avoidable.
One question is worth asking every time, in writing, before a link goes out: who inside your organisation will watch this. Get those names into the delivery record and issue them their own links. It takes a minute and it removes the conversation that otherwise begins with “we only shared it internally”.
When it happens anyway
The log and the mark tell you who.
The contract tells you what to do about it.
Calmly, and in this order. The instinct to send angry emails to the whole round is the one thing guaranteed to make the next round smaller.
Get hold of the copy
Nothing else on this list works without it. A forensic mark is recovered from a file, never from a rumour or a description of one.
Read the view log
Who opened it, when, and how often. This narrows the list before you accuse anybody, and sometimes it closes the question on its own.
Run the copy against the mark
The per-person forensic mark is what turns a list into a name. If the copy is itself a screen recording, do not assume the mark survived; fall back on the log and the delivery record.
Pull the NDA and revoke the links
Your remedy lives in the contract that name signed, not in the platform. Revoke every live link the same day, then reissue only where the round genuinely has to continue.
What none of this does
Honest framing
Most films
do not need any of this.
A short film going to a festival with no commercial embargo needs none of the above. Send a link, be pleasant, get the screening. The worst case is a stranger watching your short a few weeks early, which is not a business problem. Spending your energy on watermarks there is spending it in the wrong place.
The friction is also real and it costs you viewings. Asking a busy sales agent to install a native macOS application to watch a rough cut will lose you some of them, and the ones you lose will not tell you why. That is a genuine trade, not a detail, and you should make it deliberately rather than because a feature list impressed you. As of 9 September 2026, Sundance’s own Submit page states no screener security requirement at all, so do not invent an industry rule to justify the friction. Ask the person you are sending to what their terms are.
Who genuinely needs the full programme: an unreleased feature with a sale in play, a project under a studio or streamer embargo, a film where a competitor knowing the content changes a negotiation, a round going out to more than a handful of parties at once, and anything where a leak reduces the price rather than merely embarrassing you. In those cases the hour of administration per round is cheap and the burn-in is normal.
The middle path is usually right. Run the ordinary recipients on a plain private link with one link per person, a short expiry and the paperwork done, and reserve the Vault native path for the two or three parties where the exposure is real, or for anyone who has already been careless with something of yours. If you want the full menu of controls with what defeats each one, that is in secure screener sharing.
Questions
Frequently asked
Should I send a rough cut at all, or wait for picture lock?
That is a strategy question, not a technical one, and the honest answer is that most agents and acquisitions executives would rather see an unfinished film early than a finished one late. What matters is that the cut arrives framed. A slate card and three lines in the email stating the cut date, what is locked and what is temporary costs you ten minutes and changes the note you get back. Sending an unframed rough cut is what actually damages you, not sending a rough cut.
Will a distributor still watch a film with a visible watermark on it?
Yes. A viewer identity burned into the corner of an unreleased screener is an ordinary sight in acquisitions and nobody treats it as an insult. What loses you viewings is friction, not a burn-in: an extra install, a password that does not arrive, a link that expired before the meeting. Keep the mark and remove the friction.
Can I stop a distributor from screen recording my cut?
Not in a browser. The W3C's Encrypted Media Extensions specification states that it does not define a content protection or Digital Rights Management system, and MDN's Screen Capture API page documents how a page captures a screen, with no mechanism for a page to opt its own content out of capture. On our side, capture blocking belongs to the native macOS Vault path, where the operating system gives an application that control. It is not a property of a link you paste into an email. And a phone pointed at a monitor defeats every control on every platform.
Is an unlisted Vimeo link good enough for an unreleased feature?
It depends on what a leak costs you. Two things in Vimeo's own documentation are worth knowing before you decide. Vimeo describes an Unlisted video as one that can be accessed and shared by anyone who has the video's unique URL, so the link is transferable by design. And Vimeo's viewer-level analytics are documented for showcases, report a team member's email address, and only appear for logged-in team members, not for signed-out viewers, on an Advanced or Premium plan or Enterprise with the Events feature. An outside sales agent opening a link is a signed-out viewer, so those analytics will not name them.
Do festivals or distributors require secure screeners?
Do not assume a rule exists. As of 9 September 2026, Sundance's own Submit page states no screener security requirement at all: it routes applicants through a third-party submission platform and gives a programming contact. Individual distributors set their own terms in the deal memo or the NDA, so the correct move is to ask the person you are sending to rather than guess at an industry standard.
What quality should the screener be?
Export a viewing file in H.264 or HEVC and upload that. Our player streams the exact bytes you upload with no transcode anywhere, so the bitrate you export is the bitrate they watch; the uploader recommends 80 to 100 Mbps for maximum compatibility, with a ceiling of 5 TB per file subject to your available storage. Send UHD unless you know the viewer's machine: 8K plays when the viewer's hardware decodes it. Do not upload a ProRes or camera RAW master expecting it to stream, because browsers decode H.264, HEVC and AV1 and not those.
It leaked. What do I do first?
Get hold of the copy, because nothing else works without it. Then read the view log to narrow the list of who had access and when. Then run the recovered copy against the forensic per-person mark to turn that list into a name. Then pull the NDA that name signed from your delivery record, because the contract, not the platform, is what gives you a remedy. Then revoke every live link. If the copy is itself a screen recording, do not assume the mark survived it; in that case the log and the delivery record are your primary evidence.
For the cuts where a leak costs a sale
The Vault is a native macOS review path, and access to it is included on every plan: capture blocked, a session watermark carrying the viewer's identity, a forensic per-person mark, AES-256 at rest, short-lived links and a tamper-evident view log. Studio, the top plan, is $250 a month or $2,500 a year with 2 TB hot plus 2 TB cold and five seats. Extra seats are $25 a month, or $300 a year, on any paid plan.
Sources
- 1.About video privacy settings, Vimeo Help Center (Vimeo's own wording for Unlisted; fetched 9 September 2026)
- 2.How to access viewer-level analytics in showcases, Vimeo Help Center (logged-in team members only, not signed-out viewers; Advanced, Premium or Enterprise with Events; fetched 9 September 2026)
- 3.Encrypted Media Extensions, W3C (the specification does not define a content protection or DRM system; fetched 9 September 2026)
- 4.Screen Capture API, MDN Web Docs (documents capture and its consent model; no opt-out for page content; fetched 9 September 2026)
- 5.MediaKeys.getStatusForPolicy(), MDN Web Docs (the only documented output-protection lever is a minimum HDCP version check; fetched 9 September 2026)
- 6.Submit to the Sundance Film Festival (no screener security requirement stated on the page; fetched 9 September 2026)
- 7.uncompressed.io: the Vault, and the storage and seats each plan includes (Vault access included on every plan; Studio $250 a month or $2,500 a year, 2 TB hot plus 2 TB cold, five seats; extra seats $25 a month or $300 a year with no storage attached; product page, verified 9 September 2026)
- 8.uncompressed.io: security switches, documented (session watermark, per-person forensic mark, capture blocking on the native macOS path, AES-256 at rest, short-lived links, tamper-evident view log; FairPlay listed as roadmap; product page, verified 9 September 2026)
- 9.uncompressed.io pricing (video views carry no additional charge; the uploader's own recommendation of 80 to 100 Mbps for maximum compatibility and its 5 TB per-file ceiling, subject to available storage, read in app/dashboard/Uploader.tsx on 9 September 2026)
