Compare the intended change, amount behavior, browser compatibility, the 50 MiB input limit, the 30 million channel-sample limit, and WAV preservation before applying an effect online. The useful comparison is not simply which effect sounds best; it is whether the selected operation, amount, source, and export match the result you need.
Audio Effects Online performs decoding, processing, WAV encoding, and download creation in the current browser tab. Audio is not uploaded, no server render occurs, and no account storage is required. It applies one selected effect per run, so checking those details before processing helps prevent a mismatched result or an unnecessary second run.

Match the effect to the change you want
An effect name can suggest a larger or more realistic processor than the tool actually provides. Compare the result you want with the disclosed operation instead of assuming that “reverb” means a room simulation or that “normalization” means equal perceived loudness.
| Effect | Exact operation | What to compare | Important boundary |
|---|---|---|---|
| Echo | At 100% amount, each input sample is retained and a half-strength copy is added 200 milliseconds later. Lower amounts scale the delayed copy linearly. | Decide whether a clear, repeatable delayed copy fits the sound and whether the extra tail is acceptable. | The complete tail is allocated before processing, so the final echo is not cut off. |
| Lightweight reverb | Copies are added at 29.7, 37.1, and 41.1 milliseconds with weights of 0.50, 0.35, and 0.25 multiplied by the selected amount. | Compare it with a quick sound-design draft rather than a room, studio, plate, spring, or convolution processor. | It does not model room dimensions, frequency-dependent decay, diffusion, damping, pre-delay, or a professional reverberation tail. |
| Reverse | Reads the sample frames in the opposite order and blends the reversed result with the original according to amount. | Check whether reversing the entire frame sequence and controlling the blend matches your intended edit. | The amount determines how the reversed and original material are combined. |
| Fade in or fade out | Fade in scales from the selected dry proportion at the beginning to full level at the end; fade out performs the inverse. | Compare the transition direction and starting proportion with the shape your edit needs. | It is a full-range linear fade, not a separate fade editor with multiple curves or sections. |
| Normalization | Finds the largest absolute decoded sample and scales the signal toward a 0.95 sample peak. | Compare sample-peak consistency with the broader loudness matching you may actually require. | It does not target LUFS, perceived loudness, broadcast compliance, dynamics, equal loudness, or inter-sample true peak. |
The amount must be a whole number from 0% through 100%, but the same percentage does not represent the same change for every operation. Echo and reverb scale delayed components, reverse controls a blend, fades shape the beginning or end, and normalization scales the signal toward a sample-peak target. Compare the defined behavior rather than treating the percentage as a universal intensity scale.
Check source compatibility and processing limits
Source compatibility comes first because a recognized file name does not guarantee that the browser can decode it. Names such as MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC are accepted, but actual codec and profile support varies by browser and operating system. The W3C Web Audio API defines the decoded AudioBuffer and browser decoding contract used by the tool. If decoding fails, no result is created.
| Check | Required value | Why it matters |
|---|---|---|
| Encoded input | One file no larger than 50 MiB | The encoded-file ceiling is separate from the decoded-sample budget. |
| Browser decoding | The file must be decodable by the current browser | A supported extension alone does not guarantee a result. |
| Channel structure | 1–8 equal-length channels | Decoded channels must form a valid equal-length layout. |
| Sample rate | 8,000–192,000 Hz | Sources outside the supported decoded range cannot be processed. |
| Decoded input | No more than 30 million channel samples | This budget counts decoded samples across all channels. |
| Amount | An integer from 0 through 100 | Fractional amount values are outside the supported control. |
| Effect count | One selected transformation per run | A chain requires a completed result to become a later input. |
| Complete output | No more than 30 million channel samples, including any tail | An output above the limit is rejected rather than truncated. |
The 50 MiB encoded-file ceiling and the 30 million channel-sample decoded budget answer different questions. A relatively small compressed file may still decode into a large buffer. Echo and reverb can add tail frames, so an input that fits the input budget may fail the output budget. In that case, the tool preserves the complete calculated tail, does not truncate it, and creates no file.
Check level expectations before processing
Strong echo and reverb settings can clip when dry and delayed samples overlap. Output samples are constrained to the legal −1 through +1 floating range before WAV quantization, but that safeguard does not make clipping desirable. Compare the intended effect strength with the reported output peak and listen for distortion before replacing any source file.
Normalization needs a similarly narrow expectation. It raises or lowers the decoded signal toward a 0.95 sample peak; it does not measure or match perceived loudness. Two recordings with different dynamics can therefore receive different gains, and silent input remains silent. If consistent perceived loudness, dynamics, true-peak control, or compliance matters, do not treat this operation as a substitute for a dedicated loudness workflow.
Apply and inspect one effect in a controlled sequence
- Protect the source and choose the file. Keep an untouched copy of the original, then select one browser-decodable encoded audio file no larger than 50 MiB.
- Choose the operation and amount deliberately. Select echo, lightweight reverb, reverse, fade in, fade out, or normalization, then set a whole-number amount from 0% through 100%. Record the file, effect, and amount because changing any of them invalidates older work.
- Apply the effect locally. The complete echo or reverb tail is allocated before processing. If the resulting output would exceed 30 million channel samples, the tool creates no file rather than shortening the result.
- Inspect the reported values. Review channel count, sample rate, input and output frame counts, output peak, and exact WAV byte size. Compare the input and output frame counts when using echo or reverb because the tail can increase the output length.
- Download and retain both versions. Save the completed PCM16 WAV and keep the untouched original for comparison or a later revision. A downloaded result can be inspected in a local audio player without treating the transformed file as the only copy.
Know exactly what the WAV keeps
The download is a new interleaved, little-endian PCM16 RIFF/WAVE file. Microsoft’s WAVEFORMATEX documentation defines PCM block alignment as channels multiplied by bits per sample divided by eight; at 16 bits, that means two bytes per mono frame and four bytes per stereo frame. The reported exact byte size lets you verify the encoded result against the processed channel data.
The export preserves the processed channel samples and sample rate, but it does not preserve the source codec, bitrate, compression quality, tags, artwork, chapters, cue points, loop markers, or container metadata. Floating samples are quantized to signed 16-bit PCM. Treat the download as a rendered working copy rather than a metadata-preserving version of the source.
All file reading, decoding, sample processing, WAV encoding, and download creation stay in the current browser tab. There is no upload to Lizely, no account copy, and no hidden server-side or AI transformation. That makes the processing location and output boundaries concrete when comparing online options.
Combine effects one verified stage at a time
Because only one effect can be applied per run, build a chain by downloading a result, inspecting it, and then using that WAV as the input for a later effect. Compare each stage with the previous output and the untouched source. Repeated lossy decoding and PCM processing may reveal source artifacts, while repeated clipping or normalization can change the dynamics further.
For repeatable work, record the source name, effect, amount, and reported metrics together. This documented repeatable Audio Effects Online workflow helps preserve the settings needed to explain or reproduce a result without relying on memory alone.
Use a final go-or-no-go checklist
- The selected operation matches the exact change you want.
- The source is likely to decode and meets every input limit.
- The amount behaves as defined for that particular effect.
- The complete result, including any echo or reverb tail, fits the output budget.
- Your level expectations account for clipping and the limits of sample-peak normalization.
- You accept the PCM16 export and its metadata loss.
- The untouched original remains available for comparison or correction.
If you're weighing options, What Does the Download Preserve From My Original File? covers this in detail.
If you're weighing options, What Is the Best Way to Use Audio Effects Online? covers this in detail.