Share video with a client
without them creating an account.

The reason this question gets asked at all is that the two platforms most people try first answer it badly. A private YouTube link makes the viewer sign in to a Google account, and not just any account: YouTube’s help page states that the viewer must be signed in to the account the video was shared with. Switch to unlisted and the sign-in disappears, but so does the gate, because YouTube states that unlisted videos and playlists can be seen and shared by anyone with the link. On Vimeo the viewer is fine, and you are the one who pays: its privacy article lists Unlisted, Password and Embed only as available with paid plans.

There is a third failure mode that looks like a win. Sending the file through a transfer service asks nothing of the client, but it does not let them watch either. WeTransfer supports in-browser preview for MP4 and MOV files up to 300 MB, and says the preview plays at a slightly lower resolution than the file you get when you download. A finished film is almost never under 300 MB, so the client downloads a large file blind, then plays it in whatever software is on the machine, then writes notes with no timecode you can act on.

Read the first two rows together and the picture is clear. Frame.io is genuinely good on the viewer question: a reviewer is free and has no login. The catch is disclosed in Frame.io’s own share article, where a first-time commenter on a public share is asked to enter a name and email address, and Secure sharing is exclusive to Enterprise customers. So the client does not sign up, but they do identify themselves before their first note, and the locked-down version of sharing is not on the self-serve plans.

Vimeo passes the viewer test and fails the price test for anyone who only needs to send one private cut a month. YouTube passes the price test and fails the viewer test in the private mode, then fails the privacy test in the unlisted mode by its own definition. The transfer and drive tools do not really compete for this job at all: they move a file to a machine, and the moment your client is downloading a 40 GB master to watch a rough cut, the round trip on notes has grown by a day.

The mechanism matters more than the marketing word around it. When a viewer submits the code, the server compares it against a keyed hash of the video id and the code, then sets a signed cookie. The watch page checks that cookie before it renders anything, so the film, its title and its download link are simply not in the page for someone who has not passed. The code never travels back to the browser, which means it cannot be read out of the page source by a viewer who was given the link but not the code.

One more consequence of the same design: a password film never renders inside an embed. If you want a gated cut visible on a page you control, that is what Embed only is for, and the two watch routes return 404 to everyone but you while it is set.

A shared code has an obvious weakness: everyone who has it is the same person as far as the gate is concerned. There is a second mode for that. If the access code you set contains an @ sign, the gate switches to an email allowlist. The viewer is asked for their email address instead of a code, and only the listed addresses pass. Nobody registers, nobody picks a password, nobody receives a confirmation link.

Describe it to yourself accurately, because that is what keeps it useful. It is the closest thing here to a per-person gate, and it is nothing more than that. A viewer types an address and the server checks it against your list. It is a way to stop a link from spreading to people you did not name. It is not proof of identity, and it is not an audit trail you could take to a legal argument.

What the client sees at the end of that is a player with no platform logo on it, on any plan including the free one. The only logo the player can show is your own, off by default. That is not cosmetic when the film is going in front of your client’s client: Vimeo states that on a Free or Basic plan you cannot remove watermarks from your videos, and YouTube’s player parameter for reduced branding is documented as deprecated with no effect.

Outside those three, the account requirement is a cost with no matching benefit to the person you are asking to pay it. Your client is trying to approve a cut between two meetings. Every step between the click and the picture is a step where the approval slips to tomorrow. See the plans for what each tier includes; the gates in this guide are on all of them, the free one included.