Remotion Interactivity

{children} ); }; const lowerThirdSchema = { children: {type: 'text-content', default: '', description: 'Text'}, accentColor: { type: 'color', default: '#0b84f3', description: 'Accent color', }, } as const satisfies InteractivitySchema; export const LowerThird = Interactive.withSchema({ Component: LowerThirdInner, componentName: '', schema: lowerThirdSchema, wrapInSequence: true, }); ``` Forwarding the injected `style` inside the component is required; keep editable styles inline at the component's call site. ### Choose schema fields Each key in the schema is a prop that Studio can read and edit at the call site. Props that are not in the schema still work, but are not editable in Studio. Keys may use dot notation, such as `style.color`. | Type | Use for | Keyframable | | ---------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------- | | `text-content` | Text, such as a title | No | | `number` | Numbers, with optional `min`, `max`, `step`, `integer` | Yes | | `boolean` | On/off switches | Yes (hold) | | `color` | CSS color strings | Yes | | `enum` | A choice between `variants`, each with its own nested schema | Opt-in (hold) | | `array` | Lists of numbers, colors, enums and more | No | | `asset` | Media sources, with optional `assetType` | No | | `font-family` | CSS font family | No | | `font-weight` | Font weight | Yes | | `translate`, `scale`, `rotation-css`, `rotation-degrees`, `transform-origin` | Transforms | Yes | | `uv-coordinate` | A normalized `[x, y]` point on the element | Yes | | `svg-path` | SVG path data | Yes | | `remotion-captions` | `Caption[]` data | No | | `hidden` | A value kept out of the controls | — | Every field needs a `default` and should have a `description`, which Studio shows as the label. Set `keyframable: false` to show a static control. Expose content and per-instance appearance, such as the text and an accent color. Do not add fields for `style.translate`, `style.scale`, `style.rotate`, `style.transformOrigin` and `style.opacity`: `wrapInSequence: true` already adds them. To make CSS properties of the root editable per instance, spread the built-in schema fragments: ```tsx const cardSchema = { ...Interactive.textSchema, // style.color, style.fontSize, style.fontWeight, ... ...Interactive.backgroundSchema, // style.backgroundColor ...Interactive.borderRadiusSchema, // style.borderRadius, ... } as const satisfies InteractivitySchema; ``` Also available: `Interactive.borderSchema`, and `Interactive.captionsSchema` for components that accept captions. See [`InteractivitySchema`](https://www.remotion.dev/docs/interactivity-schema) for all options. ### Register reusable components as connected compositions Register substantial scenes and reusable components with their own layers or animation as standalone compositions. Studio calls these **connected compositions**: they can be opened in their own timeline while sharing the same component implementation with the parent video. Define required styles and load fonts inside the component so it works without its parent. See parent independence. Register the same exported component reference that the parent renders. For the example above, use `component={LowerThird}`, not `LowerThirdInner` or an inline wrapper. With `wrapInSequence: true`, no extra `` is needed for the connection. ```tsx title="Root.tsx" import {Composition} from 'remotion'; import {LowerThird} from './LowerThird'; export const RemotionRoot = () => ( ); ``` Choose a unique ID, representative inline defaults, and dimensions, fps, and duration suitable for previewing the component. Registration defaults do not automatically copy props from a parent instance. See connected compositions for registration and extraction details. ### Put timing directly on the component Avoid a separate `` around one component that already accepts timing props. Built-in interactive components and custom components made with `wrapInSequence: true` can receive `name`, `from`, `durationInFrames`, `trimBefore`, `playbackRate`, and `premountFor` directly. ```tsx Jane Doe, Product Designer ``` When removing a redundant sequence, move its timing and name to the child. Preserve any existing child timing; do not overwrite or double-apply offsets. A `useCurrentFrame()` call inside the component reads its local frame, while a style expression at the call site still uses the caller's frame. Preserve that distinction when moving animation styles. Keep a `` when it provides shared timing for multiple siblings, overrides dimensions for `useVideoConfig()`, or wraps a component that does not handle timing. Keep `` for consecutive layout and `` for transitions; direct `from` props do not replace those behaviors. ## Give every independently editable item its own JSX node The Studio edits the JSX source node that created an item. If multiple runtime items come from the same JSX node, they share one source-editing target. For every composition registration, clip, scene, layer or sequence that should be editable on its own, write a separate JSX node and keep its editable props on that node. This applies to ``, ``, built-in media components, ``, ``, `` and custom components. For example, author an editable timeline like this: ```tsx title="Separate source nodes" ``` A `.map()` or another programmatic loop would create multiple runtime items from one JSX source node. That is appropriate for repeated output that is intentionally controlled as one template, such as visualization bars or particles. It is not appropriate when the instances need independent IDs or names, props, metadata, timing, ordering, deletion or duplication in the Studio. ## Make an HTML element interactive using `Interactive` Every HTML and SVG element (except ``, it already is interactive) such as `