Native VisualizerWave demonstration with Keep the whole project text and orange bars on a dark blue background

How to Save, Reopen and Move a Music Visualizer Project

To save a music visualizer project in VisualizerWave, choose File → Save project file and keep the downloaded .visualizerwave file. Use File → Open project file to select that editable backup later. To continue on another computer, copy the project file there and open it in VisualizerWave.

Keep the project file as well as your finished video. An MP4 or WebM contains the rendered result; it does not retain editable text layers, visualizer settings or imported MIDI parts. Browser-local recovery is a third, separate way to resume work, and should not be your only backup.

Choose the file that matches what you want to keep

What you keepWhat it is for
.visualizerwave projectReopening the editable design with its available embedded source files and settings
MP4 or WebM videoWatching, publishing or editing the finished picture and soundtrack
Browser-local draftResuming the recent workspace in that browser when its stored draft is available

A project file is not a video upload. It can contain your source audio and artwork, so treat it as part of the release's working material. Conversely, renaming an MP4 to .visualizerwave cannot recreate the original design layers.

Save an editable backup from the File menu

  1. Check the current project. Confirm the intended audio, artwork and text. If the editor reports unavailable media, reselect those files before treating the backup as complete.
  2. Choose File → Save project file. VisualizerWave packages the current project locally and starts a download.
  3. Locate the downloaded .visualizerwave file. Keep the extension and give the file a useful version name, such as single-title-landscape-v03.visualizerwave.
  4. Keep a copy outside browser storage. Store it with the original recording, artwork and finished exports. Save another version after important changes.

The Saved locally status describes the browser draft. It does not mean you have downloaded a portable project file. Check the actual downloaded file when you want a backup you can copy or move.

Project saving is separate from Export video. You do not have to render the entire song to keep an editable design. For creating the composition first, follow the complete music visualizer tutorial.

What is inside a VisualizerWave project file?

The portable file stores project settings and packages available imported media. It does more than remember the original filename or a temporary browser address.

We created a real 1,177,824-byte project file, about 1.18 MB, using VisualizerWave's native packager. A local read-and-save check restored the following five file payloads with identical hashes:

Embedded file in our checkVerified result
Source WAV recordingOriginal bytes, filename and audio metadata retained
Artwork imageImage bytes retained
Logo imageLogo bytes retained
Hidden video layer's clipVideo bytes retained even though the layer was hidden
MIDI fileOriginal bytes retained; four notes parsed and its 0.125-second source offset kept

The reader also retained the title, layer settings and 1280 × 720, 30 fps project configuration. After saving the opened data into another project file, its five media payloads still matched. The complete archive's size can change with its header and metadata; matching the embedded files is a different check from requiring every archive byte to be identical.

This was an offline native packager/reader check, not an interactive file-picker import or a transfer between two physical computers. It verifies the saved payloads and project data, not playback compatibility for every embedded file. A deliberately truncated archive was rejected rather than treated as a complete project.

An available file can be included even when its layer is hidden. Remove an unwanted layer or source deliberately before saving a copy meant to exclude it. Hiding it only changes visibility.

Reopen the project and check its media

Before opening another project, save your current work if you need to keep it. Opening a project replaces the working scene; the File menu is not a library of automatically retained versions.

Choose File → Open project file, select the .visualizerwave file and allow the project and media to load. Check:

  • The title, artwork, colors and video shape.
  • The intended recording and a representative passage during playback.
  • Any video background's trim and loop behavior.
  • Imported MIDI parts and timing, if the design uses them.

The source recording is still needed for a soundtrack. MIDI contains note events rather than instrument audio; the MIDI synchronization guide explains how to check the matching performance.

If the editor reports that a project opened but its audio could not be decoded, do not interpret that as a successful soundtrack check. Keep the original project and source files while investigating the recording and browser compatibility.

Move a project to another computer

Save a fresh .visualizerwave file, copy that file through your chosen storage or transfer method, and open it in VisualizerWave on the destination computer. Local browser recovery does not perform that transfer for you.

Keep the original copy until the destination project has been checked. Verify its media, text, framing and timing, then save a short video test on that machine. A file containing the media does not establish that the destination browser can decode it or finish the same export.

The project retains font choices and design settings, while the application supplies its fonts and rendering code. It is not a frozen copy of the entire app. Check the appearance again when reopening on another system or after application changes.

For a later release, preserve the previous project version before replacing the song or artwork. General design reuse belongs to the release creation workflow; this guide focuses on keeping and reopening the actual files.

What local browser recovery can restore

VisualizerWave also saves a draft locally as you work. In a separate check using the actual editor, we changed a text layer to “Local recovery check · 2026-11-03”, waited for Saved locally, reloaded the page and reopened the editor. It displayed Local draft recovered, and the text matched.

That was a text-only browser recovery check on an isolated local origin. It did not import the portable archive or establish recovery after a crash, deleted site data or missing media.

Browser storage belongs to the site and browser environment on that device. A different computer, browser or profile should not be expected to contain the same local draft. Clearing site data can remove it; private browsing storage is generally removed when that private session ends. Keep a downloaded project for work you need to retain independently.

If the stored draft is gone and no project backup exists, VisualizerWave cannot reconstruct all editable settings from the finished MP4. The video and original source files may help rebuild the design, but they are not the missing project file.

When the design returns but media is unavailable

The newer editor can report Design recovered · media unavailable while retaining the layout and settings. Read the named missing files, choose Open Media, and reselect the matching sources. Recheck timing and appearance after replacing them.

A project backup made in that state includes available files only. Saving the surviving layout is useful, but it does not restore bytes that the browser no longer has.

If Local recovery needs attention or Draft protected · autosave paused appears, keep any current work you can save and read the error before using Retry recovery. The retry confirmation asks you to save current changes first. Avoid clearing site data or starting fresh while the local draft is your only remaining copy.

A separate native demonstration scene using VisualizerWave's built-in preview spectrum. It contains no audio track and is not a recording of an archive being imported. The portable-file inspection and text-only recovery checks described above are separate evidence.

Once a project reopens correctly, make a short saved video and inspect it before the full render. The export settings guide covers that output check. VisualizerWave is $19 once, with unlimited exports; see access and pricing.


Built for artists, not render credits

Ready to make the next one yours?

Pay $19 once. Create unlimited private, locally rendered music videos.

4.5/5 · 17 reviews
200+ happy users
Get Lifetime Access — $19