Guide · VibeGen Studio

Make generative art in a browser tab

Sixty-three engines. Nothing to install, nothing to render on a server, no image model in the loop. You pick an engine, move its parameters until it is yours, play it to your music if you like, and take it out as a picture or a video.

Open the studio →

The loop, in four moves

Pick an engine

The left rail groups all of them into five shelves. Flow is particles, vortices and flowfields. Pattern is noise, voronoi and geometry. Organic is growth and reaction simulations. Effects processes an image you bring. Lab is experimental, and it is badged that way on purpose. Clicking one switches instantly; nothing is lost.

Move the parameters

Every engine exposes its own controls on the right. There is no wrong value: the worst outcome is an ugly frame, and the fastest way to learn an engine is to take one slider to each end and watch what breaks.

Change the seed

The seed is the whole difference between one artwork and a family of them. Same parameters and a different seed gives you the same idea drawn again from scratch. This is how you get a coherent series instead of one lucky frame.

Take it out

Four doors, and they are not the same door. Below.

The four ways out, and when each is right

Export PNG

The frame on screen, at full resolution. Instant. This is the one you want for a cover, a print or a post.

Record

R captures what you play in real time, with the song's sound, as an MP4 at 1080x1080, 1080x1920 or 1920x1080 (WebM on browsers that cannot write MP4). Scene changes land in the same clip. Because it is real time, what you see is what you get, including any stutter. Right for a quick social clip.

Export the song

Drop a song, then Record's menu renders the whole track frame by frame with its sound inside, at the shape and size you pick, up to 4K. The picture reacts exactly as it does live, your automation lanes included (a lane that changes scene plays live only), and the same song gives the same video every time. You can stop halfway and keep what is done.

Bake video

Re-renders at the resolution you choose, stepping the engine with a fixed time slice so the result is deterministic and smooth regardless of your machine. Slower, and the only correct choice for anything you are going to publish as video.

Record and Bake are not two names for the same feature. Record is a screen capture of a live thing and inherits your computer's bad moments. Bake ignores real time entirely and computes every frame properly, which is why the same bake on a slow laptop and a fast desktop produces the identical file.

Stills and motion are the same artwork

The still engines are not a separate family with separate code. A still is the motion at its first instant, so turning animation off gives you exactly the frame the video starts from. Compose it moving, stop it where you like it, export.

That is also why a still and its video always match: there is one engine, not a picture version and a video version that drift apart.

Coming back to the same piece

Every piece is an engine plus a seed, so the address bar is enough to store it:

studio.vibedna.ai/studio?engine=still-flow&seed=11

Open that link on any machine and you get the same artwork. Bookmark it, send it, put it in a document. Nothing is stored on our side and nothing expires.

My Work

Point the studio at a folder on your own disk and it shows what you made, as a thumbnail grid. The files are yours, in your folder, and the studio only reads them.

Batches

A named list of pieces you can click through, useful when you are curating a set rather than exploring.

What each tier opens

Free

Every engine, the music, MIDI and live play. Ten images and five videos of up to thirty seconds a month (recordings or song exports), each carrying a small badge. Enough to decide whether the tool is for you, on real work rather than a demo.

Pro

No badge, no monthly count, and video and song exports up to five minutes.

Ultra

Video of any length, whole songs included, control from your AI through the MCP, and new engines as they land.

Nothing you have already exported is ever taken away. If a subscription lapses, the studio returns to the free limits and every file you made stays yours.

Playing it live, to music

The bar under the canvas is where the sound comes from: drop a song anywhere on the studio, use your mic or audio interface, or take the sound of another browser tab. Every scene hears the kick, the accented kick that comes after a rest, and the tempo. Seven controls shape how it answers: React, Chaos, Trails, Heat, Bright, Decay and Gain. Demo plays a built-in beat when there is no audio at all.

Scenes

1 to 0 jump to the first ten scenes, the arrows step through them, Tab opens a grid of all of them with thumbnails.

Looks

N rolls new dials for the scene, L a new look, X a new scene and palette, P the next palette, B goes back. K stores looks in ten slots; Shift with a number recalls one, gliding over the morph time you set.

MIDI

Right-click any slider and pick MIDI learn, then turn a knob or hit a pad. Knobs set a position; pads step through choices. Mappings stay in your browser.

Automation

Z opens lanes over the loaded song: draw a curve for any control, the scene or the palette, snapped to the song's beat grid. The scene follows it while the song plays, and the lanes save with the song.

Output window

O opens a clean window for a projector or a second screen, at the window's size or a fixed one up to 4K. It follows every move, the mouse included, and the main window can draw lighter while it is open.

Your own picture

Drop a photo or a video, or press C for your camera, and the image scenes transform it. A photo also lends its colors to the palette. A cutout PNG becomes a logo on the effects layer, and a 3D model file turns in its own scene.

G hides the panels, A cycles the frame shape (square, full, 16:9, 9:16), F goes fullscreen, and ? shows every key.

The music visualizer

A separate room in the same studio: load a track and the engine moves with it. Each engine in the roster loads a hand-tuned preset first, so it starts looking finished rather than black, and the beat then modulates only how it moves. It never touches brightness or glow, because a visualizer that pulses its own exposure looks like a bug rather than a performance.

The engineering behind this studio, including the traps and the reasons, lives in the journal Build a Generative Art Studio, on the journals page.