Skip to main content

​
Preview before you spend a render

The Framelane Playground is a browser-based editor that previews your composition locally with WebGPU. Lay out your elements, tune effects and motion, scrub the timeline, and export the exact POST /v1/renders body.

Open the Playground

Compose, preview, and export a render request — no API key required to experiment.

​
Why it maps cleanly to the API

Renders are declarative: the entire scene is one JSON payload (canvas + elements[] + transitions[]). The Playground is a visual editor over that same schema:
  • Same schema. What you build maps directly to a POST /v1/renders body — the preview is a fast layout and timing check, not a pixel oracle. For pixel truth, use POST /v1/preview, which runs the production render pipeline on a slice of your timeline.
  • Same fields. Every field in the editor corresponds to a field documented in Elements and catalogued by GET /v1/capabilities.

​
From preview to request

  1. Compose your scene in the editor — add video, image, text, and audio elements; apply effects, motion, and transitions.
  2. Preview it live in the browser. The WebGPU pipeline renders frames locally as you edit.
  3. Export the request. Copy the generated POST /v1/renders JSON.
  4. Validate it from code. POST /v1/preview with dry_run: true returns the full violation list for free, and contact_sheet renders the whole edit as one grid PNG — see Preview.
  5. Send it from your code, an agent, or the interactive API reference — the response is your rendered video.
Building requests with an AI agent? Pair the Playground with GET /v1/capabilities: the agent reads the capability catalog to assemble a request, validates it for free with POST /v1/preview (dry_run: true), and you eyeball the preview before committing a render.

​
Good to know

  • The Playground previews the composition itself. The backend additionally handles media ingest, AI tasks, and final encoding. For a pixel-accurate check from code, use POST /v1/preview.