Process the audio locally in your browser rather than uploading it. Audio Effects Online can apply one effect in the current tab, so an upload failure or privacy concern does not have to stop the job. Local processing, however, does not guarantee that the web page will open on a restricted or offline connection; if access is blocked, use an installed editor until the page is reachable.
When you cannot use audio effects online, check four layers in order: access to the interface, browser decoding, an input limit, or the output budget. Each layer has a different fix, so changing effects before diagnosing the failed step can waste time.

Identify which part of the online workflow failed
The first distinction is whether the page is unusable or the selected audio is unusable. The table below separates common symptoms without treating them as interchangeable.
| Symptom | Likely blocker | Best next check |
|---|---|---|
| The page or controls do not open | Page access, browser policy, or site availability | Use an installed editor or return when the page becomes accessible. |
| The file is selected but decoding fails | The browser or operating system cannot decode its codec or profile | Re-encode it locally as a PCM WAV and retry. A failed decode creates no result. |
| The input exceeds a limit | The encoded file is over 50 MiB or the decoded data exceeds the channel-sample budget | Shorten the source or use a smaller decoded file before trying again. |
| Processing ends without an export | An echo or reverb tail pushes the complete output over 30 million channel samples | Shorten the source or select an effect that does not add a tail. |
A failed decode creates no result. Likewise, if echo or reverb pushes the complete output beyond 30 million channel samples, the tool rejects the output rather than truncating the tail and creates no file.
Choose a local workflow when uploads get in the way
Use Audio Effects Online when the page opens but a hosted upload flow or server-side rendering is the problem. The tool reads, decodes, processes, encodes, and creates the download in the current browser tab. Audio is not uploaded to Lizely or stored in an account; there is no server render or hidden AI transformation. The W3C Web Audio API 1.1 defines the decoded AudioBuffer frame model and browser decoding contract used for local handling.
This distinction matters: local processing removes the audio upload from the workflow, but it cannot remove a network or browser restriction that prevents the page from loading. If a recognized file still fails to decode, re-encode it with a trusted local editor to an uncompressed PCM WAV and retry. That is a troubleshooting step, not a guarantee that every browser accepts every WAV.
Apply one effect and keep a recoverable copy
Use the following recovery workflow to get a downloadable result without changing the original context:
- Protect the source. Keep an untouched copy of the original recording. The tool creates a separate result, but the downloaded WAV does not retain every property of the source file.
- Choose one input. Select a browser-decodable file no larger than 50 MiB. MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC filenames are accepted, but actual codec and profile support varies by browser and operating system. A recognized extension does not guarantee successful decoding, and a decoding failure produces no result.
- Select one transformation. Choose echo, lightweight reverb, reverse, fade in, fade out, or normalization. The tool applies one selected effect per run rather than an automatic multi-effect chain.
- Set the amount. Enter a whole-number value from 0% through 100%. This control blends or scales the selected operation according to the effect you chose.
- Apply the effect locally. Start the local operation and wait for validation. Echo and reverb reserve their complete tails before processing, so an input that passes the initial checks can still exceed the final output budget.
- Inspect the result report. Check the channel count, sample rate, input and output frame counts, output peak, and exact WAV byte size before downloading.
- Download the new PCM16 WAV. Keep the original file, then inspect the result. To build a chain, download one result and use that WAV as the input for a later run, while remembering that repeated clipping or normalization can change dynamics and existing lossy-source artifacts may become easier to notice.
Account for the limits before processing
The 50 MiB cap applies to one encoded input file, not to the eventual uncompressed output. Understanding how the 50 MiB limit applies to this workflow can prevent a late rejection. Shortening the source can also reduce the decoded data.
After decoding, valid inputs use 1–8 equal-length channels and a sample rate from 8,000 to 192,000 Hz. The decoded input and complete effect output may each contain no more than 30 million channel samples. These limits interact, so a file that passes the encoded-size check may still be too large after decoding.
Echo and reverb allocate their full delayed tails before processing, so an input within budget can still fail the output budget. For a source near the ceiling, shorten it or use reverse, fade in, fade out, or normalization; those operations do not allocate an additional echo or reverb tail.
Match the effect to the result you need
| Effect | What it does | Important boundary |
|---|---|---|
| Echo | At 100%, retains each input sample and adds a half-strength copy 200 milliseconds later. Lower amounts scale the delayed copy linearly. | The complete delayed tail is allocated, so the last echo is not cut off. |
| Lightweight reverb | Adds reflections at 29.7, 37.1, and 41.1 milliseconds with disclosed weights of 0.50, 0.35, and 0.25 multiplied by the amount. | It is an early-reflection design, not a room or professional processor simulation. |
| Reverse | Reads the sample frames in the opposite order and blends them with the original according to the amount. | The result is a blended reverse rather than an automatic replacement of the source. |
| Fade in | Scales from the selected dry proportion at the beginning to full level at the end. | The amount determines how much of the fade is applied. |
| Fade out | Performs the inverse of fade in, moving toward the selected dry proportion at the end. | The amount determines how much of the fade is applied. |
| Normalization | Finds the largest absolute decoded sample and scales toward a 0.95 sample peak. | Silent input remains silent; normalization does not measure perceived loudness. |
Strong settings can clip when dry and delayed samples overlap. Audio Effects Online therefore constrains finite output samples to the legal -1 through +1 range before WAV quantization.
The lightweight reverb does not model room dimensions, frequency-dependent decay, stereo diffusion, damping, pre-delay, convolution, or a professional reverberation tail. Normalization does not target LUFS, perceived volume, broadcast compliance, dynamics, true peak between samples, or equal loudness across different recordings.
Verify the export before replacing anything
The download is a new interleaved little-endian PCM16 RIFF/WAVE file. The Microsoft WAVEFORMATEX documentation describes the underlying WAV structure. The processed samples and sample rate are carried into the export, but the original codec, bitrate, compression quality, tags, artwork, chapters, cue points, loop markers, and container metadata are not preserved.
Use the displayed frame counts and peak to confirm that the operation behaved as expected. An echo or reverb output can have more frames because its tail extends beyond the input. Preserve and inspect the WAV before using it as the next input in a chain, and keep the original recording as the recovery point.
Use an installed editor when the page itself is blocked
If the page cannot open because of a connection, site restriction, or browser policy, no online interface can complete the task in that session. Use an installed DAW or audio editor already available to you: re-encode an unsupported codec, trim an over-limit source, apply the required effect, and export a WAV. If the browser tool opens but refuses one particular file, local conversion is the practical fallback.
This boundary is important: Audio Effects Online solves upload and privacy concerns and many decoding problems once the page is accessible, but it does not turn a blocked web page into an offline desktop application.
If you're weighing options, Before You Use Audio Effects Online: A Pre-Use Checklist covers this in detail.