Studio Protocol security
An Element contains executable React source code and may declare npm dependencies. Studio requires confirmation before applying an Element delivered through drag-and-drop or an installation request. It also requires confirmation before adding an external Element Library to a project.
Allowed origins
Any HTTPS website can request an Element installation or request to add an Element Library. HTTP is supported only for local development pages on localhost or 127.0.0.1.
Studio reflects only the requesting allowed origin in CORS. It does not use wildcard CORS or cross-origin credentials.
Confirmation boundary
Elements delivered using setStudioDragData() or installInStudio() require confirmation in Studio. A successful installInStudio() result only means the request reached Studio and is awaiting confirmation.
Before confirming, Studio shows the requesting source, destination choice, source code, packages that will be installed, and whether an existing Element source file will be replaced. Drag-and-drop data has no reliable website provenance and is labeled as unverified. Installed source code runs with the project's file and network access. Package lifecycle scripts are disabled when Studio installs dependencies.
Declining the confirmation does not write source files or install packages.
An Element Library request made with addElementLibraryToStudio() shows the requesting origin, exact Element Library URL, and requested display name. The Element Library is not loaded before confirmation. Confirming persists a Config.addElementLibrary() call in remotion.config.ts; it does not install Element source code or dependencies. Individual Element installations still require confirmation.
Declining or closing the Element Library confirmation does not change the config.
Target information
Discovery exposes limited metadata needed to present the destination: project name, composition ID when applicable, Studio version, focus time, and a short-lived target token. It does not expose project source code, config contents, or filesystem paths.
Target tokens are opaque, single-use, short-lived, and bound to the requesting origin, selected Studio tab, and operation. Changing the selected composition invalidates an Element installation token.