The machine in front of you does the render.
Files stay in the browser session
The core audio, image and video files used to build a visualizer are processed locally instead of being uploaded to a cloud render queue.
The preview uses the real track
Audio analysis drives the selected waveform, spectrum, scope or other visual style directly on the device while you preview and configure it.
The export is local too
A supported Chromium desktop browser encodes the finished video on the computer. Faster hardware usually completes the same export sooner.
Local rendering removes the source-file upload, not every network request
An honest privacy answer distinguishes the creative files from the account, payment and optional online services around them.
What stays on the device
The song, cover artwork and optional video background used for the core visualizer are read by the browser. The preview is generated there, and the finished video is encoded there.
That is different from a cloud renderer, where the source media must first be transferred to a remote server before a render can start.
What still uses online services
BeatVisualiser is still a web application. Loading the site, signing in, purchasing exports, support, analytics choices and other account functions use normal online services.
Optional features may have separate processing requirements. For example, automatic lyric transcription is not the same operation as the core local visualizer render. Check the current privacy explanation before using an optional feature with sensitive material.
The trade-off for local rendering
The browser and computer must support the APIs and performance needed to encode video. This avoids an upload and queue, but it makes device compatibility relevant.
- Use a supported desktop Chromium browser.
- Keep the tab open during export.
- Expect render time to vary with the computer and project length.
- Use YouTube Mode on a supported setup for long-form export.
Local browser render or remote render queue?
Neither architecture wins every situation. The difference is where the source file and rendering work go.
| Feature | Local browser | Cloud rendering |
|---|---|---|
| Source media | Stays in browser session | Uploaded to a server |
| Render hardware | Your computer | Provider infrastructure |
| Queue | None | Possible |
| Device dependence | Higher | Lower |
| Best for | Desktop privacy and immediacy | Weak devices or phone workflows |
Can I make a music visualizer without uploading the song?+
Does my cover artwork stay local too?+
Does local rendering mean the website works offline?+
Are all optional features local?+
What is the downside of rendering locally?+
Keep the unreleased file close.
Make the video on your machine.
Open the browser editor, add the track and judge the complete workflow before deciding how you want to export.
Create locally in your browser