Audioframe ← Back to site

About Audioframe

Audioframe turns a piece of audio into a video you can post. It runs entirely inside your browser — your music is never uploaded, and there is no account to create.

Sounak Das
Built by Sounak Das
Independent developer · sounakdas.in

Why it exists

If you make music, you eventually hit the same wall: the platforms that could carry your work reward video, and you have an audio file. The usual answers are a $20-a-month subscription service, or an afternoon in After Effects learning to rig an audio-reactive template.

Neither felt proportionate to what is, at heart, a small problem — draw a spectrum, make it move with the music, export it. Browsers have had everything needed to do that for years: the Web Audio API for frequency analysis, Canvas for drawing, and MediaRecorder plus WebAssembly for encoding. Audioframe is what happens when you use them instead of a render farm.

Why it runs in your browser

Every hosted visualizer works the same way: you upload your unreleased track to a stranger's server, wait in a queue, and download the result. That's a lot of trust to ask for a thirty-second clip.

Audioframe never sends your media anywhere. Analysis, rendering and encoding all happen on your own machine, which has three consequences worth stating plainly:

The honest trade-off: exporting uses your CPU, so a long 4K render takes real time on a slower machine — and very old browsers can't do it at all.

What it does

Where it's going

Audioframe is in beta and actively developed. The near-term list is trimming a track to the section you actually want, a waveform timeline, and faster-than-real-time export. If you have a request or hit a bug, get in touch — the roadmap is genuinely shaped by what people ask for.

Contact

Questions, bugs or feature requests: sounakdas.in or LinkedIn.

Open the editor →