Try ClipAsm

The playground below contains a complete three-scene project. In a few minutes you can check the source, make one edit, and render the result. Nothing is uploaded.

clipasm 1

config {
    video {
        width = 320
        height = 180
        fps = 24
        color = sdr_bt709
    }
    output = "generated/scenic-sequence.mp4"
}

clip {
    image("assets/morning.png", 1500ms, contain)
    image("assets/meadow.png", 1500ms, contain)
    image("assets/evening.png", 1500ms, contain)
} as pictures

$pictures

1. Validate the original

Select Validate, or press Ctrl+Enter. The source passes with 108 frames: three 1.5-second scenes at 24 frames per second.

2. Change one scene

Change the meadow duration from 1500ms to 1s.

3. Validate the change

Select Validate, or press Ctrl+Enter. The timeline is now four seconds, or 96 frames.

5. Check the video

When rendering finishes, play the preview. Confirm that the middle scene is shorter. Reset restores the original source and project files.

Project files

The images appear under Virtual project files. You can preview, rename, replace, or delete them. Everything stays in your browser.

Browser limits

The playground supports still-image and video-file sources together with the native operations reachable from them. It does not support imports, standalone Audio-file sources, or external programs.

It accepts one source file up to 256 KiB. Each asset can be up to 128 MiB, with a 256 MiB total limit. Browser rendering uses a single-threaded WebAssembly FFmpeg runtime with a bounded work budget. Use the installed CLI for larger projects.

Continue with Get ClipAsm running to create a local project and use the complete native feature set.

The browser downloads the renderer only when you select Render video. The renderer is separate GPL-licensed software. See the browser runtime notices.

Keyboard shortcuts

ClipAsm