Long audio project export fails: what to do

You finish editing a long recording, start the export, and it stops, stalls, or produces a file that will not play. The cause may be limited memory, low storage, a problem in one section of the project, or an export that is too demanding for the browser.

Use the Audio Editor to test a short piece first. That helps show whether the issue affects the whole project or only the full-length export, without risking your original audio files.

Test the export without risking your edit

1. Open the Audio Editor and load the project or audio files. If the project is already open, leave that tab open while you troubleshoot.
2. Play the beginning and a section near the end. Note whether playback stops, skips, or sounds wrong in the same place each time.
3. Make a short export test, about 20 to 30 seconds. If the editor lets you export a selected range, choose a section with several tracks or edits. Otherwise, create a temporary shorter edit and keep the original files unchanged.
4. Export the short test as WAV or MP3. Then try the full project again and note whether the export finishes, where it stops, and whether a playable file appears in your downloads.

Keep the original source files until you have listened to the complete exported file. A file that appears in your downloads may still be incomplete if the export stopped early.

What the result means

The short export works, but the full one fails

The browser can process the project, but the full export may need more memory, time, or free storage than is available. A long timeline with several tracks, edits, speed changes, or fades can take more work to render than a short test.

Try the fixes below, especially freeing storage and exporting the project in shorter sections. If the short test was made from a simple part, also test a short section from the part of the timeline where the full export stopped.

The export fails at the same point each time

A repeated failure at one section can point to a problem with a source file or a particular edit. Play that section on its own. If it also stops or sounds damaged, reload the original source file if you have it, then test that section again.

Even a short export fails

The issue is less likely to be the length alone. Check that the browser has not lost access to the page, that the download location has free space, and that the project plays in the editor. Try a different output format as a test.

The export finishes, but the file is silent or will not play

The file may be incomplete, or the player you used may not support the format. Check its file size and try opening it with another player. Export the same short section in WAV and MP3 to see if one format produces a usable file.

How to fix a failed long export

1. Keep the editor open and the device awake. Do not close or reload the tab while an export is running. Keep the computer plugged in if possible, and temporarily prevent it from sleeping until the export finishes.
2. Close other demanding apps and tabs. Video calls, games, and many open browser tabs can compete for memory. On Windows 11, press Ctrl + Shift + Esc to open Task Manager and close apps you do not need. On macOS, open Applications › Utilities › Activity Monitor and quit apps you recognize and are not using.
3. Check free storage. On Windows 11, open Settings › System › Storage. On macOS, open System Settings › General › Storage. Make room on the drive used for downloads, and check that the destination is not an almost-full external drive.
4. Export the project in shorter sections. Keep a copy of the original edit and split the work into manageable parts using the editor's cut and track tools. Export each part, then listen to the joins. This can avoid a single export that exceeds the browser or device's available resources.
5. Try the other output format. WAV preserves uncompressed audio but creates larger files. MP3 usually creates a much smaller file, though it reduces audio quality. Test both on a short section first, then use the format that works for your project and intended use.
6. Restart the browser and retry once. Save or preserve your source files, close the browser, reopen it, and load the project again. Avoid running several export attempts at the same time.
7. Check whether a source file is causing the failure. If playback or export repeatedly fails at one section, make a temporary edit without that section and test again. If that works, replace or reimport the affected source file rather than rebuilding the whole project.

Estimate how much space the export needs

WAV files can be much larger than MP3 files. As a rough example, stereo PCM audio at 44.1 kHz and 16-bit is about 10 MB per minute, or roughly 600 MB per hour. Higher sample rates, more channels, or higher bit depth increase the size. A stereo MP3 at 192 kbps is about 1.4 MB per minute, or around 86 MB per hour.

These figures estimate the finished file, not all the memory the browser may need while processing the project. Leave additional free space, especially when exporting WAV, and avoid deleting your source files to make room until you have checked the finished export.

The Audio Editor runs in your browser, and the audio files you open and export stay on your device.