Watch how Editframe Elements turns HTML into video.

A motion study, then one film each for rendering, cloud rendering, playback and the editor.

Creative possibilities

Typography, texture, and motion made with web technology.

Motion study · 1:12

Editframe in motionA 72-second motion design film exploring typography, vectors, dimension, components, signal, and time.
A motion design film. Made with Editframe.
Use the timeline's arrow keys to seek. Press Home or End to jump to the beginning or end.
0:00 / 1:12

An editor inside your product

Editing panels, a timeline, your own styles, and an MP4 export in the browser.

Product film · 0:50

An editor inside your product
0:00 / 0:50
Film outline
  1. Editframe's editor panels in your app. Your app places Editframe's editor panels in its own layout.
  2. Edit the headline. Select the headline, move and resize it on the canvas, then retype it in your app's own inspector.
  3. Trim and scrub on the timeline. Trim the footage, then scrub. Canvas and timeline follow one composition clock.
  4. Restyle every panel. Your app's CSS variables restyle every Editframe panel at once.
  5. Export the MP4. Export the edited spot as an MP4 in the browser.

One HTML video, rendered three ways

One composition rendered in the browser, in a terminal and through the render API.

Product film · 0:45

One HTML video, rendered three ways
0:00 / 0:45
Film outline
  1. One HTML video, three renderers. The spot is one eight-second HTML composition. A render pulls its 240 frames off the timeline and encodes them into an MP4.
  2. Export in the browser. A click in your app calls renderToVideo(). An offscreen clone renders each frame while the preview keeps playing, and WebCodecs encodes the MP4 without a server.
  3. Render from a terminal. npx editframe render opens the composition in headless Chrome on your machine, renders its 240 frames and writes spot.mp4.
  4. Send HTML to the render API. POST /api/v1/renders with the composition's HTML returns a render ID. Editframe's GPU workers render it, and the MP4 downloads from the render's URL.
  5. The same moment from every path. Frame 142 from each MP4, side by side. Each renderer seeks the composition to 4.733 seconds, and the composition decides what is on screen.

A video for every row

One request per row, rendered in parallel slices on GPU workers.

Product film · 0:50

Rendering a video for every row in Editframe's cloud
0:00 / 0:50
Film outline
  1. One request per row. A table holds one row per name. A server loops over the rows and calls createRender once per row, sending that row's HTML to POST /api/v1/renders.
  2. Cut into 15-second slices. Editframe cuts each video's timeline into 15-second slices plus an init segment, so a 60-second video becomes five render jobs. Jobs from every video share one queue.
  3. Rendered on GPU workers. Each GPU worker renders eight slices at once, and more workers start as the queue grows. Timing in this scene is conceptual.
  4. Joined without re-encoding. The finished CMAF fragments are joined byte for byte into one MP4. Nothing is re-encoded.
  5. Your app hears back. Editframe posts render.completed to your webhook with the render ID, your metadata and a download URL. A progress stream reports each render while it runs.
  6. A video for every row. A personalized video for every row, and no render servers of your own.

Playing a 4K original from your bucket

Segments are made just ahead of the playhead, and replays come from cache.

Product film · 0:21

Playing a 4K original from your bucket
0:00 / 0:49
Film outline
  1. Your original file stays in your bucket. A 2.71 GB, 3840 × 2160 file keeps its storage URL. ef-video points at that URL, and the variants endpoint plans 2-second play segments and 30-second scrub windows without encoding anything.
  2. Segments are made just ahead of the playhead. Each segment reads one slice of the source, widened to the nearest keyframes, and becomes a 1080p segment as the playhead approaches, like track laid in front of a moving train.
  3. A far seek shows a coarse proxy first. Dragging the scrubber to 1:24 pulls a 30-second, 320-pixel scrub window, then the 2-second play segment for that position replaces it.
  4. A replay comes from cache. Segments that already exist are reused. Nothing is read from the bucket or encoded again.
  5. The video plays in your product. A title and synced captions play over the master, and playback requests carry a token your server signed.