The work is executed in the page through browser workers, WebAssembly, Web Audio, or WebGPU as stated.
Music Visualizer
See what you hear. Turn frequency and amplitude data into exportable responsive visuals.
What does music visualizer do?
A music visualizer maps time-domain or frequency-domain audio data to moving graphics. SoundTools connects the selected local audio element to a Web Audio analyser and draws the result onto a recordable canvas.
A real local processor, not a decorative upload box
Web Audio + Canvas + MediaRecorder runs after you choose a source and explicitly start the operation. The audio samples remain in browser memory; SoundTools does not send the selected media to an application endpoint.
Choose bars, waveform, or radial motion, set signal and background colors, then record the track in real time as WebM or convert it locally to MP4. Results remain available for preview and download only in the current tab. Closing or refreshing the page releases those temporary objects.
How to use music visualizer
- 01
Choose the local source
Open a compatible file in the dedicated workbench at the top of this page. The browser validates and decodes it without an upload step.
- 02
Set the useful controls
Choose bars, waveform, or radial motion, set signal and background colors, then record the track in real time as WebM or convert it locally to MP4.
- 03
Process, check, and export
Run the local processor, inspect the status and preview, then save WebM · MP4 when the result is ready.
What this tool actually does
Clear limits are part of a useful tool. These values describe the processor currently running in this page.
Runtime and model assets may be downloaded, but the selected file is not attached to those requests.
The dedicated workbench exposes only formats it can actually produce in the current browser.
Useful reasons to open music visualizer
- Social visual
Create a clean moving graphic for an authorized music clip.
- Podcast teaser
Pair spoken audio with a responsive waveform.
- Listening display
Explore the energy and shape of a track directly in the page.
Questions about this tool
Answers based on the current browser processor—not promises about a future version.
01Is my audio uploaded for processing?
No. Audio samples stay in browser memory. The page may download a codec or model asset, but it does not send the selected file with that request.
02Why can the first run take longer?
This tool uses Web Audio + Canvas + MediaRecorder. A browser may need to download and initialize that runtime before the first operation; later runs can reuse cached assets.
03Can I preview the result before saving?
Yes. Audio-producing tools expose local result players, while analysis and transcription tools show their detected data before download.
04What happens when the browser is unsupported?
The workbench reports the missing capability instead of uploading the media or pretending that processing is still running.