Reversing a sound recording means taking every audio sample in the file and replaying them in the opposite order, so the last sample in the original becomes the first sample in the result. The Reverse Audio tool does this inside the current browser tab by decoding the source file with the Web Audio API, reversing each channel's sample buffer independently, and then writing a brand-new 16-bit PCM WAV file. Stereo input remains stereo, mono stays mono, and the original sample rate and channel count are preserved within the tool's stated limits. The output is always a freshly encoded WAV, not the original MP3, M4A, AAC, Ogg, or WebM stream played backward, so file size, codec, and container metadata can differ from the source. Processing happens locally, the file is never uploaded to a server, and the original temporary preview URL is released when you pick another file or close the page.
What Reversing a Sound Recording Actually Does
When you reverse a sound, the tool reads each decoded audio sample and places it at the position measured backward from the end of the recording. A snare hit at 2.3 seconds in the source moves to a new position equal to the total duration minus 2.3 seconds in the result. The waveform shape of each sound stays the same; only its time position changes, so a cymbal crash still sounds like a cymbal crash, just played at a different moment. Reversing samples is not the same as reversing polarity, changing pitch, slowing the audio down, or stretching it. Nothing about the frequency content is altered; the playback direction is flipped at the sample level.
For multichannel files, each channel is reversed on its own. In a stereo file, the left channel is reversed independently of the right channel, and the two streams are interleaved back together in the correct WAV frame order. Reversing channel order instead of time is a common bug in less careful tools; the Reverse Audio implementation explicitly tests for it, along with odd and even frame counts and confirmation that the source arrays are not mutated.
What Reverse Audio Does and Where the Work Happens
Reverse Audio accepts an MP3, WAV, M4A, AAC, Ogg, or WebM file up to 50 MB and reverses every decoded channel sample locally. The browser picks the file, reads it as an ArrayBuffer, decodes it with Web Audio's decodeAudioData method, runs the same reverseChannels function exercised by the test suite, encodes the result with the same encodePcm16Wav function checked against golden WAV files, and finally creates a download URL for the new WAV. None of that touches a server. File bytes, decoded samples, filenames, and the result stay on the device, and the temporary object URLs used for previewing the original and downloading the reversed file are released when you select another file or leave the page. The Web Audio context used for decoding is also closed after the operation or when new work replaces it.
Because the output is freshly encoded, the original MP3, M4A, AAC, Ogg, WebM, or compressed WAV stream is never simply flipped and re-served. Each floating-point sample is clipped to the range from -1 to 1, mapped to signed 16-bit PCM, and written little-endian, with -32768 representing negative full scale and 32767 representing positive full scale. Reducing floating-point samples to 16-bit can change numerical precision, and the resulting WAV is almost always larger than the compressed input.
How to Reverse Sound Step by Step
- Open the Reverse Audio tool in your browser and click the file picker to choose an MP3, WAV, M4A, AAC, Ogg, or WebM file. The compressed file must be no larger than 50 MB.
- If you want to confirm the source before processing, use the built-in preview to listen to the original from start to end and note its duration, channel count, and sample rate.
- Select Reverse audio and wait. The browser decodes every channel, reverses each channel's samples without mutating the source arrays, and encodes the new PCM16 WAV. A decode error is reported if the browser cannot read the codec inside the chosen container, rather than claiming every file with a familiar extension must work.
- Preview the result inside the tool and read the displayed duration, channel count, and sample rate to confirm they match what you expected from the original.
- Download the WAV and open it in the editor or player where the reversed file will actually be used. Browser preview success does not guarantee that every older device supports the same WAV channel layout or high sample rate, so a final listen on the target software is worth doing.
Input and Output Limits at a Glance
Reverse Audio enforces every limit in the table below. A file that exceeds any one of them is rejected with a specific message and is never partially processed. Acceptance in the file picker and successful decoding are also separate checks: a familiar extension does not guarantee the browser can read the codec inside, and selecting another file or retrying clears the previous download first so an old success cannot be mistaken for a new result after an error.
| Limit | Accepted range |
|---|---|
| Compressed input size | Up to 50 MB |
| Decoded duration | 5 minutes or shorter |
| Channel count | 1 to 8 channels |
| Sample rate | 8,000 Hz to 192,000 Hz |
| Total channel samples | 30,000,000 or fewer (frames multiplied by channels) |
| Accepted containers | MP3, WAV, M4A, AAC, Ogg, WebM (codec depends on browser and OS) |
| Output format | PCM16 WAV, little-endian, signed |
The 30 million channel-sample budget is the safety net behind the file-size limit. A short compressed file can still expand into a very large decoded array, and the budget protects the browser tab from that surprise. If you hit it, trim the source first in Audio Cutter and then reverse the shorter clip with Reverse Audio.
What the Reversed File Does and Does Not Carry Over
Reversing samples preserves the decoded duration, sample rate, and channel count, but the result is a fresh audio file rather than a re-packed copy of the source container. The table below summarizes what stays and what is intentionally rebuilt.
| Property | Carried over to the reversed WAV |
|---|---|
| Decoded duration | Yes |
| Sample rate | Yes, within the 8,000 to 192,000 Hz range |
| Channel count | Yes, each channel reversed independently |
| Original codec and compressed bitrate | No, output is always PCM16 WAV |
| Album art, ID3 tags, chapters, loop markers | No, container metadata is not copied |
| Original encoder settings | No, the WAV is freshly encoded |
| Loudness, pitch, time stretch, de-clipping | No, reversing samples does none of these |
If you also need fades, trimming, codec choice, metadata preservation, or mastering controls, finish those in a full audio editor after downloading the reversed WAV.
Verifying the Reversed Result Before You Use It
For a reliable workflow, do not trust the preview alone. Keep the source file on disk, listen to the original preview from start to end, run the reverse, and then listen to the beginning and end of the result. The reversed clip should sound identical to the original, just played from the end toward the start. Check the duration, channel count, sample rate, and file size shown by the tool against what you expected, and open the download in the player or editor where it will actually be used. If the source contained a distinctive transient such as a snare hit, a vocal consonant, or a door slam, confirm that transient now sits at the opposite end of the timeline in the result. If it does not, the reversal did not run cleanly and you should re-run the tool on the original file.
Two extra checks are worth doing for stereo material. First, listen with headphones and make sure the left and right channels were not swapped; a swapped stereo image is a classic sign that channel order was reversed instead of time. Second, if the source has an odd number of frames, confirm that the center sample is present at the new midpoint rather than dropped. Both failure modes are explicitly covered by the tool's test suite, along with PCM clamping at the endpoints and RIFF, WAVE, fmt, and data field inspection, but a quick A/B between original and result is cheap insurance.
Practical Reasons to Reverse a Recording
Reversing sound is a common move in sound design, music production, and audio forensics, and the same tool serves several different jobs.
- Reverse speech experiments. Backmasking-style effects, palindromic phrases, and content moderation checks all start from the same reversed clip.
- Transition effects. Cinematic whooshes, drum fills, and risers are often a snare or reverb tail played backward and used as an impact at the end of a bar.
- Sample inspection. Listening to the end of a recording from a different angle is a fast way to spot hidden noise, clicks, or mic handling at the very last frame.
- Sound design scratch work. Reversing a piano chord, a vocal snippet, or a field recording can suggest a pad, a stab, or a texture that the forward version hides.
Because the reversed output is a fresh PCM16 WAV, it drops cleanly into any editor or sampler that reads WAV files, including projects that started from a different container. If you also need to shorten the clip, join several reversed takes, or shift the pitch of the result, chain the workflow with Audio Cutter, Audio Joiner, or Audio Pitch Changer rather than asking one tool to do everything at once.