Embed video on a client website without the Vimeo logo.
Two different plan gates, and one iframe that has neither.

The first gate is Vimeo’s mark coming off. The player parameter is named vimeo_logo, it governs “Whether the Vimeo logo appears”, it defaults to true, and turning it off “requires a Starter plan or higher account”. The same requirement covers controls, which “Hides or reveals all player elements, such as the playbar and sharing buttons”. On Free and Basic the embed can only change “Player size”, “Embed privacy” and “Playback settings such as Autoplay, Mute, and Loop”, so the logo stays where it is.

The second gate is your mark going on. Uploading and displaying a custom logo requires a “Standard, Advanced, Pro, Business, Premium, or Enterprise plan”. Starter is not on that list. Vimeo adds two details worth carrying into a client conversation: “The logo will only appear on videos embedded on another website”, and it displays “in the lower right corner of the player”. Player branding is listed as a Standard-plan feature, which is consistent with the same line.

So the honest summary is that the cheapest paid Vimeo plan buys you a blank player, and the plan above it buys you a branded one. A page that tells you otherwise has read one help article and not the other.

Two things about that src are worth saying out loud before a client asks. It carries no query string, so whatever you set in the dashboard is what plays, and adding a parameter is something you do yourself by editing the URL. And the domain is ours. There is no custom domain on this product, so uncompressed.io is what appears in the page source, in the network tab and in a browser extension’s list of third-party frames. If the client’s brand or security review requires every asset to come from their own hostname, that requirement rules us out, and it is better to know that at the quote than at the launch.

What the visitor sees inside the frame is your film and your controls. There is no advertising code, no recommendation query, no up-next list, no end screen and no feed of anyone else’s work, because the player contains nothing that could produce them. The site chrome that wraps the rest of uncompressed.io is excluded from the embed route entirely, so no wordmark reaches the frame.

The common case is a hero band: a silent film that starts by itself, repeats, and sits directly on the client’s background colour with no black box behind it. That is three parameters and a transparent frame.

Four of the eleven overlap with the URL list: autoplay, muted, loop and title. The other seven have no URL equivalent at all. The logo, views, share button, play button, volume, AirPlay and fullscreen switches live in the panel and nowhere else, so if a page needs those off, turn them off on the film before you hand the iframe over. A parameter will not do it.

The colour side needs the same precision, and this is where our own older copy overstated things. The Embed panel shows three colour pickers, but only two of them change what a visitor sees. The accent colour paints the progress bar fill. The background colour paints the frame around the picture. The primary colour is stored and is not read by the player: the control bar is a fixed dark, and the default centre play button is a fixed gradient rather than your accent. Your logo is the element that carries the brand inside the frame, as the transparent PNG you uploaded, at the size you uploaded it, and it ships off by default so you have to switch it on.

The player streams the file you uploaded. There is no transcode at upload, no transcode at playback and no rendition ladder, so a high-bitrate export plays at its own bitrate rather than a platform’s idea of it. The direct consequence is that there is no smaller version for the player to fall back to. On a thin connection the browser buffers and waits. It cannot quietly drop to a mushier copy, because a mushier copy was never made.

That trade is easy on a client review link and much harder on a public homepage. Vimeo “re-encoded into several formats” is precisely the thing that keeps a phone on a weak signal playing, and their published 4K ceiling of “22Mbps” is low for a reason. Vimeo also notes that the listed figure is “a maximum”, so the delivered bitrate can be lower still depending on the complexity of the image. If the embed sits above the fold on a page that takes traffic from everywhere, weigh a guaranteed-to-play mushy version against a beautiful one that sometimes stalls, and pick deliberately.

Two ways to make the trade smaller. Export the hero at a sane bitrate rather than handing a marketing page a 150 Mbps master: the no-re-encode promise means what you upload is what every visitor pulls, which cuts both ways. And keep the heavy version for the pages where the audience is known, a client review or a director’s reel, where the connection is a desk and not a train.

If the requirement behind your search was privacy rather than branding, the neighbouring guide covers it: how to embed a film while the watch page returns 404. If it was a whole page of work rather than one video, start with video portfolio hosting. And if you are doing this for clients under your own studio name, the white-label embed guide covers the agency side.