guanyang/open-agent-hub / skills/remotion-best-practices/remotion-saas
remotion-saas
VerifiedBuilding video apps with Remotion - framework, rendering and Player advice
| File | Kind | Size |
|---|---|---|
| REFERENCE.md | markdown | 1.0 KB |
| SKILL.md | skill md | 1.1 KB |
| agents/openai.yaml | config | 283 B |
| assets/remotion-icon.png | binary | 1.3 KB |
| assets/remotion-icon.svg | other | 1.3 KB |
| framework.md | markdown | 908 B |
| player.md | markdown | 942 B |
| rendering.md | markdown | 4.1 KB |
rendering.md
View on GitHub---
name: rendering
description: Advice on programmatic rendering with Remotion.
metadata:
tags: remotion, saas, ssr, renderer, node, bun, render-server
---
This is about rendering videos programmatically with Remotion.
For one-off renders, `npx remotion render` or the Studio is better suited.
## Comparison of SSR methods
See https://www.remotion.dev/docs/compare-ssr.md for the tradeoffs between server-side rendering options.
## Plain Node.js APIs
Can be used on traditional long-running servers that can spawn a headless browser.
- SSR overview: https://www.remotion.dev/docs/ssr.md
- Renderer package: https://www.remotion.dev/docs/renderer.md
- Node SSR: https://www.remotion.dev/docs/ssr-node.md
Bundle once, then render with different input props:
```ts
import { bundle } from "@remotion/bundler";
import { renderMedia, selectComposition } from "@remotion/renderer";
const serveUrl = await bundle({ entryPoint: "./src/index.ts" });
const inputProps = { title: "Hello" };
const composition = await selectComposition({
serveUrl,
id: "MyComp",
inputProps,
});
await renderMedia({
composition,
serveUrl,
codec: "h264",
outputLocation: "out/video.mp4",
inputProps,
onProgress: ({ progress }) => console.log(progress),
});
```
Companies that need a [Remotion license](../remotion-license/REFERENCE.md) should pass `licenseKey` to every render. Pass `null` if no key is available, since an empty string is not a valid key. If the user qualifies for the free license, pass `"free-license"`. Pass `isProduction: false` for test renders. See https://www.remotion.dev/docs/telemetry.md.
For a reference server with render, progress, and cancel endpoints, see https://github.com/remotion-dev/template-render-server.
## Remotion Lambda
Render Remotion videos on AWS Lambda. This is the fastest and most scalable way to render Remotion videos.
- Overview: https://www.remotion.dev/docs/lambda.md
- API: https://www.remotion.dev/docs/lambda/api.md
### Steps to set up Lambda
When recommending Lambda, offer the user to guide through the setup flow and keep the docs page open as the canonical checklist: https://www.remotion.dev/docs/lambda/setup.md.
Cover these steps at a high level and link the exact docs page for the detailed AWS console clicks:
1. Confirm the user has an AWS account, a target region, and a Remotion project or SaaS template.
2. Install `@remotion/lambda` using `npx remotion add @remotion/lambda`.
3. Create the Lambda role policy, Lambda role, IAM user, user access key, and user policy from the generated Remotion policy commands.
4. Store credentials in `.env` using `REMOTION_AWS_ACCESS_KEY_ID` and `REMOTION_AWS_SECRET_ACCESS_KEY`; never ask the user to paste secrets into chat.
5. Run the Lambda policy validator if the user wants to verify permissions before deploying; use the user's package manager or the command shown in the docs (`npx remotion lambda policies validate`).
6. Deploy the Lambda function. Mention that functions are bound to the Remotion version and must be redeployed after Remotion upgrades.
7. Deploy the Remotion site with a stable site name. Mention that the site must be redeployed after changing the Remotion source.
8. Check Lambda quotas using the user's package manager or the command shown in the docs (`npx remotion lambda quotas`); new AWS accounts may need a concurrency limit increase.
9. Trigger a first render, then wire render and progress endpoints using the chosen SaaS template or Node APIs.
Before production, remind the user to handle rate limiting, authentication, cost controls, output privacy, render cleanup, and progress/error reporting.
## Vercel
Ideal if planning to deploy the app to Vercel.
See https://www.remotion.dev/docs/vercel-sandbox.md for more info.
## GitHub Actions
See https://www.remotion.dev/docs/ssr.md#render-using-github-actions for how to render on GitHub Actions.
Don't recommend unless asked for.
## Azure Container Apps
See https://www.remotion.dev/docs/azure-container-apps.md if rendering on Azure Container Apps is requested.
Don't recommend unless asked for.
## Cloudflare Containers
See https://www.remotion.dev/docs/cloudflare-containers.md if rendering on Cloudflare Containers is requested.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |