Reverb can be added to an audio file on a Windows PC entirely inside a browser tab using Audio Effects Online, which decodes one local file, mixes three disclosed early reflections, and exports the result as a PCM16 WAV without uploading audio to a server. The same browser session that loads the page also runs the decoding, the sample-level math, the signed sixteen-bit quantization, and the download, so no DAW, VST plugin, or command-line tool needs to be installed. Reverb on this page is a bounded lightweight reflection design rather than a room or hall emulation: copies of the input are added at 29.7, 37.1, and 41.1 milliseconds with weights of 0.50, 0.35, and 0.25 multiplied by a whole-number amount between zero and one hundred percent. Windows users benefit from this design because every modern browser on Windows 10 or Windows 11 already ships with the Web Audio decoding pipeline the tool uses, which means the only practical requirements are a browser, a file under fifty mebibytes, and a single click to apply the chosen effect.
How a Browser Tab Replaces a Windows DAW Plugin
A Windows machine usually means opening a DAW to add reverb: install Reaper or Audacity, download a reverb plugin, configure an audio driver, scan for VSTs, and only then drag a clip into a track. Audio Effects Online takes a different path because every step after the file picker runs in JavaScript inside the existing browser tab. Edge, Chrome, and Firefox on Windows already include the W3C Web Audio API used for decoding, so the audio path is the same one a web game or a music-learning site would use. There is no installer, no driver handshake, no plugin scan, and no reboot. The browser's sandbox does the rest of the work: the decoded AudioBuffer, the effect math, the PCM16 quantization, and the temporary object URL that triggers the download all live in the current tab and disappear when the tab is closed. For a Windows user who wants to hear a quick reverb idea on a podcast clip or a guitar take, that is the shortest path between the file on disk and a wet WAV.
How to Add Reverb to Audio Online on Windows
- Open Audio Effects Online in Edge, Chrome, or Firefox on Windows 10 or Windows 11.
- Click the file picker and choose one browser-decodable audio file no larger than fifty mebibytes.
- Select Reverb from the effect list. Leave Echo, Reverse, Fade In, Fade Out, and Normalization off, since the tool applies only one effect per run.
- Type a whole-number amount between zero and one hundred percent. Lower values blend less of the three reflections with the dry signal; one hundred percent applies the full 0.50, 0.35, and 0.25 tap weights.
- Click the apply button and wait for the page to report channel count, sample rate, input and output frame counts, output peak, and the exact WAV byte size.
- Click the download link to save the PCM16 WAV to your Windows Downloads folder. The original file on disk is not modified.
- If you want a stronger effect, feed the downloaded WAV back into the tool with a new amount. Each run produces one effect, so a chain is built one step at a time.
Inside the Three-Tap Reverb Design
Reverb on this page is a disclosed lightweight early-reflection design rather than a room, hall, plate, spring, or convolution reverb. Each input sample is kept at full strength, and three delayed copies are added at fixed offsets:
| Tap | Delay | Weight at 100% | Scaled weight at 50% |
|---|---|---|---|
| 1 | 29.7 ms | 0.50 | 0.25 |
| 2 | 37.1 ms | 0.35 | 0.175 |
| 3 | 41.1 ms | 0.25 | 0.125 |
At one hundred percent amount the dry signal is unchanged and three delayed copies sit on top of it; lower amounts scale the three weights linearly. The complete delay tail is allocated before processing starts, so the last reflection is not cut off mid-decay. What the design does not claim to emulate is equally important: there is no frequency-dependent decay, no stereo diffusion, no damping, no pre-delay sweep, no impulse-response convolution, and no simulation of a real acoustic space. The three taps are Lizely product choices chosen for fast, predictable, sample-accurate results on a single file, not measurements of any particular room. If you want a more detailed look at why those numbers were chosen, the guide Reverb Delay Times Explained: 29.7, 37.1, and 41.1 ms walks through the same offsets and weights in plain terms.
Windows Browsers, Web Audio, and Supported Codecs
Every step the tool performs depends on the browser's own decoder. The W3C Web Audio specification defines the AudioBuffer contract the tool reads from and writes to, and the same spec is implemented in the Chromium engine that powers Edge, in Chrome itself, and in Firefox on Windows. The page accepts filenames ending in MP3, WAV, M4A, AAC, Ogg, WebM, or FLAC, but the actual codec support comes from the browser and operating system, not from the page. A file name that looks like FLAC is not a guarantee that the encoded contents will decode; if decoding fails, the page reports no result and writes nothing to disk. Channels must be one through eight with equal length, sample rate must fall between eight thousand and one hundred ninety-two thousand hertz, and the decoded total must stay under thirty million channel samples for both the input and the post-effect output.
Because reverb adds a tail, a file that fits the input budget can still fail the output budget, in which case the page refuses to truncate and refuses to write the result. Windows users who hit that wall usually see it on long source recordings with strong reverb settings, since each second of extra tail adds to the channel-sample total. The contract is honest about that boundary: budgets are not stretched to fit the file, and the original audio stays untouched on disk.
Inspecting the Output Before You Download
The page exposes several values after processing so the result can be checked on Windows without opening another tool:
| Reported value | What it tells you |
|---|---|
| Channel count | One through eight, equal length, as decoded by Web Audio |
| Sample rate | Eight thousand through one hundred ninety-two thousand hertz |
| Input frames | Sample-frame count of the decoded original |
| Output frames | Sample-frame count after the reverb tail is appended |
| Output peak | Largest absolute sample after clipping to the -1 through +1 range |
| WAV byte size | Exact file size of the PCM16 WAV that will download |
These numbers let a Windows user sanity-check a result in the browser tab. If the output peak sits at 1.0 after a strong reverb setting, the dry and delayed samples overlapped enough to clip and the floating range held the line. Microsoft documents the underlying WAV block alignment as channels multiplied by bits per sample divided by eight, per the Microsoft WAVEFORMATEX structure; at sixteen bits this produces two bytes per mono frame and four bytes per stereo frame, which matches the WAV byte size the page reports.
When One Effect Is Not Enough: Building a Chain
The page applies exactly one effect per run, which is a deliberate contract rather than an oversight. Stacking six independent transformations inside a single pass would make the math harder to verify and easier to hide behind a black box, so the tool keeps each run deterministic and reproducible. To build a longer chain on Windows, download the WAV from run one, open it with the file picker for run two, choose the next effect, and apply. A common sequence is reverb first to add space, then fade out to land the last reflection cleanly, then normalization to bring the loudest sample to a 0.95 peak.
Because each WAV is encoded as signed sixteen-bit PCM, every lossy decode and re-encode cycle can expose source artifacts, and every normalization cycle will shift dynamics. The contract recommends keeping an untouched original so any chain step can be redone from the same starting point. Job identity, AudioContext cleanup, and object URL revocation prevent stale results from replacing newer ones, which matters when a Windows user switches between several browser tabs and several open jobs. The file picker, the effect math, the WAV encoder, and the download trigger all stay in the current tab; nothing is uploaded, nothing is stored in an account, and there is no server render waiting in the background.