Troubleshooting
Why Waveform Export Fails on Some Phones (and What to Do)
Why does waveform export fail on your phone?Because the encoding happens on the phone itself — there is no server doing the work. Two causes cover almost all of it: the browser has no WebCodecs encoder (iOS below Safari 17, in-app browsers, out-of-date Android browsers), or the device runs out of memory partway through a long export.
The settings that help, in order: trim to the section you need, drop to 720p, drop to 30 fps, lower the bitrate. Avoid the PNG sequence on mobile — it is by far the heaviest output.
Let us be straight about this: Music Waveform, the browser-based audio visualizer, runs entirely on your device. There is no server doing the heavy lifting, which is exactly why your audio never gets uploaded — and it is also why, on a phone, your phone's own limits become the export's limits. Here is what actually goes wrong, and what to do about it.
First: can your browser encode video at all?
Video export uses a browser feature called WebCodecs. The preview works nearly everywhere, but the export needs that encoder. In practice:
- Android → Chrome, Edge, Opera or another up-to-date Chromium browser.
- iPhone / iPad → Safari 17 or newer.
If the waveform animates beautifully but the export never produces a file, an out-of-date browser is the first thing to rule out. Updating it is usually the whole fix. In-app browsers — the ones that open inside a social or messaging app when you tap a link — are a common culprit here; open the page in the real browser instead.
Second: memory
An export renders and encodes every single frame. A four-minute track at 60 frames per second is over fourteen thousand frames, each drawn at your chosen resolution. A desktop shrugs at that. A phone has far less memory to work with and will be killed by the operating system long before a laptop would even slow down.
This is the usual cause of an export that runs for a while and then dies, or a tab that reloads itself mid-way. It is not a bug you can report away and it is not a paywall — there is no paid tier that moves the work to a server, because moving the work to a server is the one thing this tool exists not to do.
The settings that actually help
In rough order of how much difference they make:
- Trim. Set a start and end time and export only the part you need. Halving the length halves the work, exactly. For a social clip you rarely want the whole track anyway.
- Drop the resolution. Going from 1080p to 720p is well under half the pixels per frame. On a phone screen the difference is hard to see.
- Lower the frame rate. 30 fps instead of 60 is half the frames. A waveform reads perfectly well at 30.
- Lower the bitrate. The tool accepts 1 to 30 Mbps; the default is comfortable, but a lower number means less to hold and write.
- Avoid the PNG sequence on mobile. It is the heaviest output by a wide margin — full-size uncompressed frames, all of them. If you need a transparent export on a phone, keep the clip short.
When to just use a computer
If you are exporting a full-length track at 1080p60, or you need a transparent PNG sequence of anything longer than a few seconds, use a desktop or laptop. It is not a limitation worth fighting: the same page, the same settings, the same result, in a fraction of the time. Phones are excellent for a thirty-second clip and genuinely bad at a six-minute one.
Make your waveform video
Free, no signup, right in your browser. Load a track and export an MP4.
About this article: it was written with the help of AI (Claude) and published by Music Waveform. We review our posts for accuracy against how the tool actually works, but if you spot something off, email damienyvert.dev@gmail.com.