# Run FFmpeg from your terminal

The Rendobar CLI runs the ffmpeg command you already type as a job on Rendobar. Local inputs upload, the output downloads to the path you named, and it runs on macOS, Linux and Windows.

Official, built by Rendobar · 3,002 downloads · v1.14.0 · MIT · macOS, Linux and Windows

Page: https://rendobar.com/integrations/cli/ · Read the docs: https://rendobar.com/docs/cli

macOS, Linux:

```
curl -fsSL https://rendobar.com/install.sh | sh
```

Windows:

```
irm https://rendobar.com/install.ps1 | iex
```


- Type: Command-line tool
- Built by: Rendobar
- Binary: `rb`, standalone, no Node needed
- Version: 1.14.0, MIT licence
- Runs on: macOS, Linux, Windows
- Pricing: Free
- Category: Code

## Overview

Put rb in front of the ffmpeg command you already run and it runs as a job on [Rendobar's FFmpeg API](https://rendobar.com/ffmpeg/). Local `-i` inputs upload first, and the output downloads to the file name you gave. `rb generate` and `rb edit` make and change images from a prompt. rb is one standalone binary for macOS, Linux and Windows with no Node dependency, and it updates itself with `rb update`. In CI it reads `RENDOBAR_API_KEY`, and `--json` prints the result for the next step. Every flag and exit code is in the [CLI docs](https://rendobar.com/docs/cli).

## Terminal

```bash
# Sign in through your browser
rb login

# clip.mp4 uploads, the job runs, out.mp4 downloads here
rb ffmpeg -i clip.mp4 -vf scale=1280:-2 -c:v libx264 -crf 23 out.mp4

# Generate an image and save it
rb generate --prompt "a red fox in a snowy forest" --output fox.webp
```

## Set up

1. **Install.** Run the script for your platform. It installs one standalone binary, and `rb update` keeps it current.

```bash
# macOS and Linux
curl -fsSL https://rendobar.com/install.sh | sh

# Windows, in PowerShell
irm https://rendobar.com/install.ps1 | iex
```

2. **Sign in.** `rb login` signs in through the browser, and `rb login --key` saves an API key on a headless machine.

```bash
rb login
```

3. **Run.** Put rb in front of your ffmpeg command, and the result downloads to the file name you gave. On a 5 second sample clip this command took 9 s and cost $0.0018.

```bash
rb ffmpeg -i clip.mp4 -vf scale=1280:-2 -c:v libx264 -crf 23 out.mp4
```

4. **Run it in CI.** In GitHub Actions, pin the version, put the binary on the path and pass an [API key](https://app.rendobar.com/api-keys?create=1&name=GitHub%20Actions) as a secret. `rb login` would wait for a browser, so CI uses the key.

```yaml
- name: Install rb
  run: |
    curl -fsSL https://rendobar.com/install.sh | sh
    echo "$HOME/.rendobar/bin" >> "$GITHUB_PATH"
  env:
    RENDOBAR_VERSION: v1.14.0
- name: Transcode
  run: rb ffmpeg -i ./input.mp4 -c:v libx264 -crf 23 out.mp4
  env:
    RENDOBAR_API_KEY: ${{ secrets.RENDOBAR_API_KEY }}
```


## Reference

### Install

- macOS and Linux: curl -fsSL https://rendobar.com/install.sh | sh
- Windows: irm https://rendobar.com/install.ps1 | iex
- Binary: rb (also rendobar), 1.14.0, github.com/rendobar/cli
- Update: rb update. Check: rb doctor

### Commands

- ffmpeg, ffprobe, generate, edit, storage, prompt
- login, logout, whoami, update, doctor, telemetry

### rb ffmpeg flags

- --output, --output-dir, --no-download, --url-only, --json, --quiet, --no-wait
- --timeout N: seconds, default 120, max 900
- --compute auto|cpu|gpu (gpu needs Pro)
- --deliver storage://<connection>/<path>, repeatable

### CI

- Auth: RENDOBAR_API_KEY
- Output: --json, --url-only
- Exit codes: 0 success, 1 job or delivery failed, 2 auth, arguments or credits, 130 cancelled

## Questions

### What does one rb ffmpeg job cost?

The CLI is free, and each command bills as one Rendobar job. Scaling a 5 second sample clip to 720p with `-c:v libx264 -crf 23` took 9 s and cost $0.0018.

### How do I use the rb CLI in CI?

Set `RENDOBAR_API_KEY` in the pipeline. It beats any saved login and writes nothing to disk. In GitHub Actions, add `$HOME/.rendobar/bin` to `GITHUB_PATH` after installing. Use `--json` or `--url-only` when a later step reads the output.

### Does the Rendobar CLI need Node.js?

No. rb is a standalone binary with no Node or npm dependency. It updates itself with `rb update`.

### Can the rb CLI make images too?

Yes. `rb generate --prompt` makes an image from text, and `rb edit --prompt --image` changes an image you pass by URL or local path. Both print the image URL, and `--output` also saves it.

### Can the CLI deliver outputs to my bucket?

Yes. Add `--deliver storage://<connection>/<path>` and the output goes to your connected S3, R2 or Supabase bucket. It works on `rb ffmpeg`, `rb generate` and `rb edit`.

## Resources

- [Docs](https://rendobar.com/docs/cli): Every command, flag and exit code, plus a GitHub Actions workflow.
- [GitHub](https://github.com/rendobar/cli): The source, the install scripts and the issue tracker. MIT licensed.
- [Releases](https://github.com/rendobar/cli/releases): Binaries for macOS, Linux and Windows, with a checksums file.

## More

- [FFmpeg recipes to run with rb](https://rendobar.com/ffmpeg/recipes/)
- [Deliver outputs to S3](https://rendobar.com/integrations/amazon-s3/)