Make music visuals without uploading your audio
ImgTool runs in the browser like a private desktop web app, so your track stays on your device while you test styles, backgrounds, overlays and release-week export options. It is built for unreleased music workflows where you want to preview the look before sending audio anywhere else. Core 720p export is free, and one-time passes unlock clean HD/4K and release-week tools where supported.
Better for release prep
When the track is unreleased, the hassle is not just rendering the video. It is avoiding unnecessary uploads, signups, back-and-forth between multiple tools, and passing your unreleased work to a public service.
Keep the track local
ImgTool uses browser-side audio processing, so your audio never needs to leave your machine just to see a waveform, a video background, or a release-ready scene with your music. A paid 10-Day Release Pass may support higher-quality audio export where the source track and browser allow.
Built around release week
The paid workflow is not a subscription. It is a simple 10-Day Release Pass (software activation key) that fits how many artists work: a release burst, a batch of exports, then done.
Private release assets from one browser setup
-
1Build the scene once
Use the same editor for your style, theme, cover art, text, overlays, and supported image or video backgrounds.
-
2Keep the track local while you test
Preview the visualizer in-browser without sending the audio to a server, which is especially useful when the track is unreleased or not publicly shareable yet.
-
3Export the release assets you need
Use normal exports for longform promo videos, Spotify Canvas for a short vertical silent MP4, Release Pack when you need YouTube, vertical, and square outputs from one setup, Batch Tracks when you need the same look across multiple tracks, or Playlist Maker when you want finished exported videos joined into one ordered mix.
Release-week jobs musicians actually have
ImgTool is strongest when you already have a track, cover art, and visual direction, and you just need to turn that into clean browser-based assets without wasting time rebuilding the scene in three different products.
That is the main value behind the 10-Day Release Pass: not just fewer limits, but a faster route from private studio session to publishable release asset, with checkout using email only to deliver the key.
Who this private workflow helps most
Independent artists
Test visuals for an unreleased single, EP, or album without uploading the track while it is still in release prep.
Labels and promo teams
Build release-day assets locally, then export the versions you need once the campaign is ready to go live.
Anyone tired of upload-first tools
If you already know the scene you want, the fastest workflow is often staying in one browser app instead of moving the audio around between multiple services.
Private music visualizer FAQ
Does ImgTool upload my unreleased track?
No. ImgTool is built around local browser processing, so your audio stays on your device while you build the scene and export the release assets.
Do I need an account to use the private workflow?
No. The core visualizer opens without an account. If you buy the pass, checkout uses your email to deliver the key, but there is still no ImgTool account system or subscription.
What does the 10-Day Release Pass add?
It unlocks clean, watermark-free HD and ongoing 4K, removes the support watermark on paid exports, enables release-week tools like Spotify Canvas, X Exports, Release Pack, Batch Tracks, and Playlist Maker, and keeps you in the same private browser workflow.
Can I still use my own backgrounds and overlays?
Yes. The private workflow uses the same main editor, so your styles, cover art, text, overlays, image backgrounds, and supported video background setups still apply.
Why a private music visualizer matters
For ImgTool, "private" means the normal visualizer workflow runs inside your browser tab. When you choose an audio file, the Web Audio API decodes and analyses it locally so the visualizer can react to the waveform and frequency data. Your track is not sent to an ImgTool server for analysis, preview, or rendering. The same privacy-first idea applies to cover art, uploaded background clips, playlist videos, and promo stills: they are read by the browser and combined on your device.
That matters most before release day. An unreleased master, private demo, alternate mix, or label pitch can be commercially sensitive even if it is not secret in a high-security sense. Uploading it to a random render service creates another copy, another account, another retention policy, and another support team that might theoretically access it. Local processing keeps the working copy where it already is: on your computer, in your browser session.
Workflow comparison
| Step | Server-upload visualizer | ImgTool local processing |
|---|---|---|
| Audio analysis | Track is uploaded, stored temporarily or permanently, then analysed remotely. | Browser decodes the track locally and feeds spectrum data to the canvas. |
| Preview changes | Some tools need a cloud preview render before you can judge timing or style. | You can scrub, play, and adjust the scene directly in the page. |
| Export | Server renders the video and gives you a download link. | Supported browsers render from canvas/WebCodecs or the fallback real-time path on your device. |
| After the job | You rely on the provider's deletion, account, and retention behaviour. | The source media remains local unless you choose to publish the exported result elsewhere. |
What ImgTool does
ImgTool avoids making an extra hosted copy of your unreleased track. That means no upload queues, accounts, dashboards, forgotten share links, or retention policies sitting between you and release day. It is rendered and exported to your computer for you to manage.
ImgTool is still a browser tool on your own computer, so your normal device security still matters: trusted extensions, trusted collaborators, and where you choose to upload the finished video. ImgTool's idea is simple: build the visual locally, then publish only the export you mean to share.
Ready to build release visuals privately?
Start free in the visualizer, build the scene once, and keep your unreleased track local while you export the assets you actually need for release week.