Video Embeds

Video embeds mean a video lives in one place and plays everywhere you allow it. Instead of exporting a file and uploading it to every website, CMS page, and intranet separately, you drop one small snippet into the page - and when the video is replaced or the embed is revoked, every page reflects it without anyone touching the site.

What it does

Any video in the library can be turned into an embeddable player. It streams adaptively, so each viewer automatically gets a quality suited to their connection, and it supports the things people expect from a modern player: fullscreen, picture-in-picture, and autoplay where browsers allow it.

You can tune how it behaves with simple options: autoplay (muted, as browsers require), looping, whether the controls show, a start point inside the clip - handy for pointing at one moment in a longer video - and size presets, including a responsive one that scales to fit its container.

The distinctive part is domain restriction. Each embed can carry a list of websites where it is allowed to play. Someone can still copy the snippet onto another site - but there, the browser simply refuses to show it. You can set the list per embed, set a default for your whole workspace, or leave it open for genuinely public content. The choice is yours, and it is enforced by the viewer's own browser.

How it works

You generate an embed straight from the asset page - or programmatically through the REST API and TypeScript SDK if embedding is part of an automated publishing flow.

Behind each embed sits its own dedicated share link. It renews itself automatically, so an embed on a long-lived page never quietly dies. And because that share exists only for the embed, revoking it kills the video on every page at once - without touching the asset itself or any other way it is shared.

Good to know

• Video only - embeds are for video assets; other file types have their own sharing options.
• Permissions apply as usual - viewing embed details and creating or revoking them are covered by the same share permissions as the rest of the product.
• Embed shares stay out of the way - they are kept separate from your regular share links, so they never clutter that list or get revoked by accident.
• You can force a fresh embed - rotating an embed invalidates the old snippet everywhere and issues a new one.

The technical details for developers are in the API documentation. Want to generate a snippet against a real library first? Try the demo.