CueFrame CLI · For terminals and scripts

Video editing from the command line.

Work with footage, compositions, and renders from the terminal. Use commands yourself, or put them in a repeatable script with structured output your tools can read.

Install the CLIMake your first render ↓

Run CueFrame with Node.js 24 or newer

npx -y cueframe@0.8 --help

Sign in to your cloud account

npx -y cueframe@0.8 login

Your browser opens to finish signing in.

$20 free cloud creditsNo card required. Paid operations use credits; top up when you need more.

Get free creditsSee cloud rates

From one command to a repeatable job.

The terminal is useful when you want explicit steps you can inspect, rerun, and combine with the rest of your tooling.

Inspect the available tools

Discover capabilities with npx -y cueframe@0.8 describe --json and use command help to check arguments.

Keep your edit as a project

Work with the same composition format used by the API and desktop editor. Start from a template instead of reconstructing a finished video.

Connect it to your scripts

Use structured JSON output to pass results to other tools. Non-interactive cloud jobs can authenticate with an API key.

Your first render · CLI

Render Yosemite. Then change one word.

Make the PHENOMENAL version first. Replace the title with EXTRAORDINARY and render again.

Your first output, with the title behind the ranger.

Download the full original NPS video as yosemite-peregrines.mp4. The template selects 83.616–93.359 seconds and includes the prepared subject matte.

Get the original source video ↗

Cloud steps upload your source and use credits. Both renders and other paid processing are billed separately. See rates.

  1. Install and sign in

    Requires Node.js 24 or newer.

    npx -y cueframe@0.8 --help
    npx -y cueframe@0.8 login

  2. Run the first render

    Save the original source as yosemite-peregrines.mp4 in your current directory.

    npx -y cueframe@0.8 template run yosemite-peregrines --media source=./yosemite-peregrines.mp4 -o ./phenomenal.mp4

    The command uploads the source, creates the project, applies the template, and downloads the render. Keep the project ID it returns.

  3. Read the saved composition

    npx -y cueframe@0.8 composition get PROJECT_ID

    Replace PROJECT_ID with that ID. Keep the exact ETag from the comment for the save step. Save the returned composition JSON, without that comment, as extraordinary.json. In the clip named peregrines-phenomenal-title, change source.params.text to EXTRAORDINARY. Preserve every other field.

  4. Save and render the change

    Replace ETAG_FROM_GET with the exact saved ETag, including its double quotes, inside the command’s single quotes. If the save reports a stale ETag, read the latest composition and reapply only your title change before retrying.

    npx -y cueframe@0.8 composition validate --body @extraordinary.json
    npx -y cueframe@0.8 composition put PROJECT_ID --body @extraordinary.json --if-match 'ETAG_FROM_GET'
    npx -y cueframe@0.8 render PROJECT_ID --out ./extraordinary.mp4

Take it into your workflow.

Use API-key authentication for CI and headless scripts, or open the same project in the desktop editor. For agent conversations, connect through MCP. For application code, use the REST API or TypeScript SDK.

CLI commands and authentication ↗

CLI source and examples ↗ · npm package ↗ · Markdown quickstart

All developer resources →