Preview before you spend a render
The Framelane Playground is a browser-based editor that runs the renderer in your browser via WebGPU. It compiles from the same Rust/wgpu codebase that powersPOST /v1/renders on the backend — so the preview you see is what the API produces. Lay out
your elements, tune effects and motion, scrub the timeline, and only submit a real render
once it looks right.
Open the Playground
Compose, preview, and export a render request — no API key required to experiment.
Why it matches the API exactly
Renders are declarative: the entire scene is one JSON payload (canvas +elements[] +
transitions[]). The Playground is a visual editor over that same schema:
- Same renderer. The in-browser WebGPU preview and the GPU backend share one rendering core, so positioning, effects, motion, and transitions look identical in preview and in the final artifact — no “looked different once rendered” surprises.
- Same schema. What you build maps directly to a
POST /v1/rendersbody. Every field in the editor corresponds to a field documented in Elements and validated byGET /v1/capabilities.
From preview to request
- Compose your scene in the editor — add video, image, text, and audio elements; apply effects, motion, and transitions.
- Preview it live in the browser. The WebGPU pipeline renders frames locally as you edit.
- Export the request. Copy the generated
POST /v1/rendersJSON. - Send it from your code, an agent, or the interactive API reference — the response is your rendered video.
Good to know
- The Playground previews the composition itself. The backend additionally handles media ingest, AI tasks, and final hardware encoding.
- AI media operations (background removal, gaze redirect, super-resolution) run as standalone
tasks first; reference their output URLs as element
source_urls in the scene you preview.

