oxframe vs Revideo

Pick oxframe when you want templated videos rendered natively, with no browser and no telemetry, and an agent that checks its own frames. Pick Revideo when you want the Motion Canvas model in TypeScript with a React player and render endpoints out of the box.

At a glance

One scene in both

The scene from the Revideo migration guide: a welcome card with a name passed in at render time. Two seconds at 1080p.

// src/scenes/card.tsx
import {Txt, makeScene2D} from '@revideo/2d';
import {createRef, useScene, waitFor} from '@revideo/core';

export default makeScene2D('card', function* (view) {
  const name = useScene().variables.get('name', 'Ada');
  const title = createRef<Txt>();
  view.add(<Txt ref={title} text={`Welcome, ${name()}`} fontSize={96} fill={'white'} opacity={0} />);
  yield* title().opacity(1, 0.5);
  yield* waitFor(1.5);
});

// render.ts
import {renderVideo} from '@revideo/renderer';

await renderVideo({
  projectFile: './src/project.ts',
  variables: {name: 'Grace'},
  settings: {outFile: 'welcome.mp4'},
});

use oxframe::prelude::*;

#[oxframe::scene]
pub async fn card(view: View) {
    // Revideo's variables: here the environment (or a file you read).
    let name = std::env::var("NAME").unwrap_or_else(|_| "Ada".into());
    let title = view.add(Txt::new().text(format!("Welcome, {name}")).display().opacity(0.0));
    title.opacity().to(1.0, 0.5).await;
    wait_for(1.5).await;
}

pub fn project() -> Project {
    Project::new("welcome").scene(card())
}

Render time

Each time is the whole render command, start to file. oxframe's scene is already compiled; after a one-line edit, cargo build adds about 0.6 s. On a scene this short the GPU spends more time starting than drawing, so the CPU renderer wins. The script is bench/vs/measure.sh: run it to time both on your machine.

Templated video without a browser

What Revideo adds, in oxframe

When to pick Revideo

• You want TypeScript and the Motion Canvas model with headless rendering.
• You embed a player in a React app and render from Node.

When to pick oxframe

• Renders should not need a browser and should be byte-identical.
• You want no telemetry, with nothing to turn off.
• An agent writes or fills the templates and should check the frames.
• You want regular releases and a changelog.

Moving from Revideo

The Revideo migration guide maps scenes, variables and renderVideo to oxframe and ports the welcome card above.

FAQ

Is Revideo still developed?

Its README describes it as the engine behind Midrender. It has no GitHub releases; npm has 0.11.0. Check its repository for the current state.

Does Revideo send telemetry?

Its README says it anonymously counts how many videos are rendered, via PostHog, and that DISABLE_TELEMETRY=true disables it. oxframe has no telemetry.

Can oxframe render a video per row of data?

Yes. A scene is a Rust function, so it takes any data you pass it; render one video per row from a loop or a script.

Is there a player for web pages?

Revideo has a React player. oxframe has the playground and the editor; a player to embed in your own page is not available yet.

How hard is it to move from Revideo?

Revideo scenes are Motion Canvas scenes, which map almost line by line: generators become async functions and yield* becomes .await. The migration guide shows one.

Sources

Checked on October 22, 2026. Found something out of date? Open an issue on oxframe-web.

• Revideo on GitHub
• @revideo/core on npm
• oxframe license and what leaves your machine
• oxframe-sdk on GitHub

Other comparisons

• oxframe vs Remotion
• oxframe vs HyperFrames
• oxframe vs fframes
• oxframe vs Manim
• oxframe vs Motion Canvas
• oxframe vs cloud video APIs
• Remotion alternatives

Get started with oxframe