--- name: remotion-best-practices description: Router for all Remotion skills version: 4.0.535 title: remotion-best-practices canonical_url: https://skilld.dev/gh/remotion-dev/skills/remotion-best-practices last_updated: 2026-10-13T21:25:48.000Z --- > Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt) > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > 140 supporting files sit beside this SKILL.md. When the Skill refers to one, fetch https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/PATH with PATH replaced. > > If the user asked to install this Skill, run `npx skilld install remotion-dev/skills/remotion-best-practices`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/remotion-best-practices`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/remotion-dev/skills/remotion-best-practices) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/remotion-best-practices`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/remotion-best-practices --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/remotion-best-practices --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. ## Preserve user changes Users may make edits in the code outside of the conversation. If you detect a surprising change made in the meanwhile, don't overwrite it, assume it was intentional or ask for confirmation. ## Creating a video If the user asks to make, create, or build a new video or composition, load [Create a new Remotion video](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-create/REFERENCE.md), whether or not a Remotion project already exists. ## New project setup If no Remotion project currently exists, load [Create a new Remotion project](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-create/REFERENCE.md) ## React Markup Best Practices If you are writing Remotion React Markup, load [Remotion Markup Best Practices](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-markup/REFERENCE.md) ## Maps For static maps, animated routes and markers, geographic explainers, Mapbox, MapLibre, MapTiler, GeoJSON, or 3D geographic flyovers, load [Remotion Maps](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-maps/REFERENCE.md). ## Multimedia For achieving multimedia tasks in the browser, such as trimming, cropping videos, or getting metadata from them, load [Remotion Multimedia](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-multimedia/REFERENCE.md) ## Improving Interactivity By structuring the Remotion markup well, we can allow users to interactively change things in the Studio and write back to code. If relevant: [Interactivity Best Practices](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-interactivity/REFERENCE.md) ## Open the preview If the user asks to "make" a video, "create" a video, etc. Don't render the video by default unless they are very explicit. They want to instead see an interactive preview. As soon as the project can run, start Studio and open the preview in the browser before building or editing the composition. Keep it open while you work so the user can watch progress and steer. ### If you are using Cursor Run Studio without `--no-open` so it opens the browser automatically: ```bash npx remotion studio ``` ### If you are using another agent client with an in-app browser You can use the command above to let Studio open the browser, or run: ```bash npx remotion studio --no-open ``` This will start a long-running process and print the server URL for the preview. If the server is already started, it will print the URL. If you use `--no-open`, open the exact printed URL in the in-app browser and verify that Studio loads. Once a composition exists, verify that its video preview loads. If you cannot open it there, run Studio without `--no-open`. You can visit a specific composition by navigating to `/[composition-id]`, for example `http://localhost:3000/MapAnimation`. :::note The Studio supports WebMCP tools. ::: ### If you do not have an in-app browser This will open the Studio in the browser or refocus it if it is already open. ```bash npx remotion studio ``` ### More options To launch a project in Remotion Studio, open its exact local URL, or configure Studio CLI flags, load [Remotion Studio](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-studio/REFERENCE.md). ## Render the video Only render if the user is very explicit in asking for it. E.g. "Render the video", "Export", "Give me the MP4". The preview also has a more intuitive rendering interface, so consider using it instead of the command line for rendering. ``` npx remotion render ``` For more options, see [Rendering](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-render/REFERENCE.md). For advanced rendering beyond simple `npx remotion render`, see: [Rendering Best Practices](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-render/REFERENCE.md) ## Captions When working with Captions, load [Remotion Captions](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-captions/REFERENCE.md). ## Creating a SaaS, automation or application Use the [Remotion SaaS skill](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-saas/REFERENCE.md) for knowledge about Remotion-powered SaaS apps, such as ``, rendering on Lambda, Vercel, Cloudflare, via Express.js, client-side rendering, or for finding the right SaaS template. ## Looking up Remotion APIs and documentation To find and read current Remotion documentation, load [Remotion Docs](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-docs/REFERENCE.md). ## Upgrading To upgrade Remotion, related packages, compatible Mediabunny packages, and installed Remotion Agent Skills, load [Remotion Upgrade](https://skilld.dev/api/skills-raw/remotion-dev/skills/remotion-best-practices/remotion-upgrade/REFERENCE.md).