About
What this is, and the decisions behind how it works.
Making a visualizer for a track should not require learning After Effects, and it should not require uploading unreleased music to somebody else's server. That is the whole idea.
Everything runs locally
The audio analysis, the rendering and the export all happen in your browser. There is no upload, no queue and no processing time beyond what your own machine takes. It is faster for you, it is cheaper to run, and it means unreleased material never leaves your device.
The trade off is honest: some things a server could do are not possible this way. A plain video export encodes in your browser with WebCodecs where that exists, and falls back to recording in real time where it does not. The architecture leaves room for a server renderer later, but nothing here pretends to have one now.
No accounts
There is nothing to sign up for. Open the editor and start. Presets are saved in your browser and labelled as local, because that is what they are. Calling them a library and implying they follow you between devices would be a lie.
Features that actually do what they say
Transparent export produces genuine transparency. It is a real alpha channel video, WebM or ProRes, encoded in your browser with FFmpeg, because the normal recording paths cannot keep an alpha channel and a transparent button that quietly outputs a black background is worse than not having the feature. The transparent visualizer page explains the reasoning in full.
The same applies elsewhere. If your browser cannot record video, the option is not offered and the dialog says why. Nothing in the interface is a placeholder waiting to be built.
Controls that mean something
Every visualizer declares its own controls, so bar spacing appears for bars and inner radius appears for rings, rather than everything sharing one generic panel of sliders that mostly do nothing. Advanced settings sit in their own section instead of being spread through the interface to look sophisticated.
Where it is going
The visualizer system is built so new styles are a self contained addition rather than a change to the editor. Server side rendering for faster and higher quality video is the obvious next step, along with project files you can save and reopen. Neither is here yet, and this page will not claim otherwise until it is.