Drop our node into n8n.
Get FFmpeg, instantly.
n8n Cloud doesn't ship FFmpeg — but our native, n8n-verified Renderio node does. Pop it onto your canvas, point it at any input, write the FFmpeg command you'd run locally, and we handle the workers, queues, storage, and webhooks.
Live in n8n in under three minutes.
Install the node
One package. One install button. Works on n8n Cloud and self-hosted. Paste @renderio/n8n-nodes-renderio in Community Nodes and install it once.
Paste your API key
Generate a key from your Renderio dashboard, paste it into the n8n credential, and reuse it across every workflow in your workspace.
Drop. Configure. Ship.
Drag the node onto the canvas, connect your inputs, type the FFmpeg command you would run locally, and send the rendered file to the next n8n node.
The package name is @renderio/n8n-nodes-renderio. Install it once, reuse the credential across every workflow in your n8n instance.
Integration guides for every n8n video workflow.
FFmpeg in n8n: the full guide
Why n8n Cloud cannot run FFmpeg
Convert video formats in n8n
Resize video for any platform
Extract audio from video in n8n
Batch video processing in n8n
Start with the plan that fits your workflow volume.
One FFmpeg execution is one command. Renderio includes workers, queues, storage, webhooks, and zero egress fees.
Frequently asked questions
Can I use FFmpeg on n8n Cloud?▾
Yes, through the Renderio n8n node. n8n Cloud does not ship FFmpeg and does not expose the Execute Command node, so the native Renderio node sends the job to Renderio and returns the processed file to your workflow.
Is Renderio an n8n-verified node?▾
Yes. Renderio is listed on n8n's integrations directory and installs as a native community node. You can add it from Settings → Community Nodes with @renderio/n8n-nodes-renderio.
Do I need Docker or a self-hosted n8n instance?▾
No. The node works on n8n Cloud and self-hosted n8n. You do not need to build a custom Docker image, install FFmpeg, size a server, or maintain workers.
What FFmpeg commands can I run?▾
Any FFmpeg command you would run locally. Use double-brace placeholders like {{in_video}} and {{out_video}} in the command, then map those keys to input and output files in the node.
How do output files come back to n8n?▾
The initial run action returns a command_id. After the command reaches SUCCESS, the Renderio get command response includes output_files keyed by output alias. For an output named out_gif, the URL is available at output_files.out_gif.storage_url. Webhook deliveries use the same command response under data.output_files.
Can I batch process videos in n8n?▾
Yes. Use n8n's loop or batch nodes to submit multiple URLs to Renderio. Each FFmpeg execution counts as one command, and your workflow can route each result to S3, Slack, a database, or another downstream node.
Does Renderio block the n8n workflow while FFmpeg runs?▾
No. Renderio handles workers, queues, storage, and webhooks outside your n8n instance. You can poll for status, wait for completion, or continue routing once the output URL is ready.
How much does it cost?▾
Plans start at $12/month for 500 commands. Growth is $29/month for 1,000 commands, and Business is $99/month for 20,000 commands. The Starter plan includes a 3-day free trial.
Drop the node. Run FFmpeg. Keep building.
Install the native Renderio node in n8n, paste your API key, and process video without Docker, shell access, worker queues, or storage plumbing. Your workflow stays in n8n; Renderio handles the video compute.