Rendi
FFmpeg as an API
SubscriptionVisual editingAPI2,340 impressions#92 of its week
Rendi provides a REST API to run FFmpeg commands in the cloud, handling infrastructure, scaling, and storage.
- for
- Developers building media apps, automation workflows, and serverless functions that need video/audio processing.
- pricing
- freemium
Key features
- REST FFmpeg API — Send any standard FFmpeg command as a POST request and receive the processed media.
- Auto-scaling compute — High-CPU servers auto-scale with demand, supporting up to 32 vCPUs per command.
- Long runtimes — Supports command runtimes beyond typical serverless limits, up to 20+ minutes on standard plans and unlimited on higher tiers.
- Built-in storage — Outputs are stored with stable URLs, no egress/ingress fees.
- Chained commands — Batch multiple FFmpeg commands where later steps use previous outputs, reducing overhead.
- Webhook & polling — Notify your app via webhook or poll for results, fitting serverless workflows.
Use cases
- Generate video thumbnails and GIFs for social media
- Extract audio tracks or transcode formats for podcasts
- Add watermarks, overlays, and background music to videos
- Trim, crop, and merge clips for short-form content
- Automate media processing in Make, Zapier, n8n, or serverless functions
Rendi pricing
- Free$0/Month4 vCPUs · 50 GB processing/month · 1 min command runtime · 5 GB-month storage
- Pro$25/Month/month4 vCPUs · 250 GB processing/month · 10 min command runtime · Unlimited commands/minute
Rendi vs alternatives
 Rendi |  Live Video Calling SDK by Dyte |  Compress |  Hookdeck |  Grafbase | |
|---|---|---|---|---|---|
| Best for | Raw FFmpeg commands via API | Live video communication | Simple video size reduction | Event-driven architectures | GraphQL data APIs |
| Pricing | Freemium | Subscription | Free | Free | Free |
| DevHunt upvotes | 0 | 73 | 55 | 30 | 24 |
| Launched | Nov 2025 | Mar 2024 | Mar 2024 | Mar 2024 | Jan 2023 |
- Rendi vs Live Video Calling SDK by Dyte: Dyte’s SDK provides real-time video calling, not raw FFmpeg processing.
- Rendi vs Compress: Compress offers free video compression only, while Rendi runs full FFmpeg commands with storage and scaling.
- Rendi vs Hookdeck: Hookdeck is an event gateway, not a media processing service.
- Rendi vs Grafbase: Grafbase creates GraphQL APIs, whereas Rendi executes FFmpeg media pipelines.
Rendi FAQ
How do I run FFmpeg from AI coding assistants like Claude Code or Cursor?+
Install Rendi’s MCP server URL in the assistant’s config; the assistant can then call Rendi’s API directly using the documented schemas.
Can I use Rendi from serverless platforms such as Vercel or Cloudflare Workers?+
Yes—your function makes a short HTTP call to Rendi, which handles the heavy FFmpeg work and returns via webhook or polling.
What’s the advantage of Rendi over self-hosting FFmpeg?+
Rendi handles auto-scaling, security isolation, patching, and uptime, removing the need to manage servers or address codec CVEs.
How is processing billed?+
Processing equals the total size of input and output files; Pro plans start at $0.10 per GB processed.
Does Rendi support arbitrary FFmpeg commands?+
Yes—any command you can run locally, including complex filter graphs and dynamic expressions, is supported.
What FFmpeg workloads can’t be run on Rendi?+
Live streaming pushes, real-time `-re` inputs, and device capture commands require a persistent process and aren’t supported.
Summarized by DevHunt from rendi.dev · Sep 30, 2026. Details may change; check the official site.
.jpg?width=64)
