Skip to main content
Cloud rendering lets you export videos without needing Chromium or ffmpeg installed locally. Your project is bundled, uploaded, and rendered on hosted infrastructure using Remotion Lambda.

​
Usage

oanim render --cloud
Cloud rendering requires authentication. Run oanim login first, or set ANIMATE_API_KEY.

​
How it works

1
Bundle
2
Remotion bundles your project locally (remotion bundle), creating a static site with your compositions.
3
Upload
4
The bundle tarball is uploaded to the platform via /api/v1/render/upload.
5
Render
6
The platform renders your composition on AWS Lambda using Remotion’s distributed rendering. Your animate.json settings (resolution, codec, fps, props) are applied.
7
Stream progress
8
The CLI polls for progress updates every 2 seconds and displays a percentage.
9
Download
10
The rendered MP4 is downloaded to your output path via a presigned S3 URL.

​
Options

All standard oanim render flags work with --cloud: 
oanim render --cloud --out out/video.mp4
oanim render --cloud --fps 60 --res 3840x2160
oanim render --cloud --codec h265
See oanim render for the full flag reference.

​
Output

On success: 
✔ Cloud render complete

Output:     /path/to/out/MyComp.mp4
Size:       2.4 MB
Resolution: 1920x1080
FPS:        30
Codec:      h264

​
When to use cloud rendering

ScenarioRecommendation
Local developmentUse local oanim render for fast iteration
CI/CD pipelinesUse --cloud to avoid installing Chromium in CI
Machines without ffmpegUse --cloud
Long/complex compositionsUse --cloud for better hardware
Quick previewsUse local render

​
Pricing

Cloud rendering is billed based on render duration and resolution. Check your current balance with oanim usage and purchase credits with oanim billing buy. See Credits & Billing for details.