The video timeline runs on the same engine as the stills, which means an effect looks identical in a frame of video and in a still export. It is built for music videos, looping visuals and short-form work rather than for long-form narrative editing.
Multiple tracks with trim, split and speed change, beat detection with beat-synced auto-editing, motion-tracking overlays, transitions and per-clip three-band EQ.
Effects apply per frame, so riso, halftone, dither and glitch run across the whole clip. Because they are deterministic rather than random, the grain and the damage stay stable between frames instead of strobing.
A single image can be turned into a seamless looping animation and exported as MP4, GIF, WebM, animated SVG or Lottie. That covers the looping visual most platforms now want alongside a static cover.
Rendering happens in the browser and produces frame-perfect MP4 up to 4K. There is no upload, no queue and no server-side render farm, so what the preview shows is what lands in the file.
Most glitch, grain and texture tools in video software are driven by a random seed that changes every frame. Played back, that reads as strobing rather than as texture, and it is why so much filtered video looks noisy rather than filmic.
Bitgrain's effects are functions of their settings, not of a random source, so grain sits still, a halftone screen holds its position and a glitch stays where you put it until you move it. If you want movement, you animate the parameter rather than relying on noise.
Beat detection analyses the audio track and marks the beats on the timeline, which cuts can then snap to. Auto-editing takes that a step further and cuts a sequence to the detected tempo, which is a reasonable first pass for a music video that you then adjust by hand.
Each clip carries a three-band EQ, so a rough mix can be balanced without leaving the timeline.
Up to 4K MP4, rendered in the browser. The free tier exports at web resolution with a watermark; Pro unlocks the full resolution range.
No. Rendering happens in your browser, so there is no upload, no queue and no server-side render farm.
Yes. A still can be turned into a seamless loop and exported as MP4, GIF, WebM, animated SVG or Lottie.