# Studio Mode

> Understand the capabilities and restrictions of each Remotion Studio mode.

Understand the capabilities and restrictions of each Remotion Studio mode. Use when implementing or reviewing Studio actions, permissions, availability, or UI across interactive, detached, deployed, and browser-based Studios.

- Page: https://ss33.ai/skills/remotion-dev/studio-mode-96831388351
- Publisher: remotion-dev
- Category: [Creative & Media](https://ss33.ai/skills/category/creative-and-media-0j3x01) › [Video](https://ss33.ai/skills/category/creative-and-media-0j3x01/video-yerjjv)
- License: MIT
- Source: https://github.com/remotion-dev/remotion/blob/4ffefccd5b6838a78aad7fe83cadba00fe276c77/.agents/skills/studio-mode/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/remotion-dev/studio-mode-96831388351

# Studio Modes

Remotion Studio operates in four modes:

1. **Regular interactive Studio:** Started with `npx remotion studio`. A Studio server is attached and the Studio is fully interactive. It can render server-side, use "Open in" actions, execute codemods, install packages, and perform other server-backed actions.
2. **Regular Studio with the preview server detached:** `previewServerConnected` is `false`. The Studio is effectively read-only, although client-side rendering remains available.
3. **Read-only Studio:** A deployed Studio with no server attached. Hide or disable actions that require a server. GitHub is the only supported "Open in" action.
4. **Browser Studio:** Deployed at `remotion.dev/new` and backed by a virtual file system that is hidden from the user. It cannot use "Open in" actions, but it can install dependencies and execute codemods.

When adding or changing a Studio action, determine which modes support it and hide or disable it everywhere else.