Yes, you can reverse audio in your browser using the Reverse Audio tool, which decodes a chosen file with the Web Audio API, reverses every sample in every channel locally in the current tab, and saves the result as a freshly encoded PCM16 WAV. Because file reading, decoding, sample reversal, WAV encoding, and preview creation all happen on your own device, nothing is uploaded to a remote server, and the original filename, bytes, and result stay on your machine. The tool accepts MP3, WAV, M4A, AAC, Ogg, and WebM files up to 50 MB, but actual codec support depends on the visitor's browser and operating system, so a familiar container can still fail to decode. Decoded audio must be five minutes or shorter, contain one to eight channels, use a sample rate from 8,000 to 192,000 Hz, and contain no more than 30 million channel samples in total. Reversal preserves the decoded duration, sample rate, and channel count, but it moves every audible event to the corresponding position measured backward from the end. The finished file is a new PCM16 WAV, not the original compressed stream played backward, and it is ready to open in any standard editor.
The Mechanics of In-Browser Audio Reversal
Reversing audio means playing a recording from its end back to its beginning so every audible event appears in the opposite order. In a browser-based workflow, this happens by reading the chosen file into an ArrayBuffer, decoding it with the Web Audio API into an AudioBuffer of floating-point samples, and reversing the order of the samples inside every channel independently. The tool performs this in the current tab rather than on a remote server, and it re-encodes the result as a fresh file rather than repackaging the source.
Because each accepted channel is reversed on its own and the channels are then interleaved back into the standard WAV frame order, a stereo input stays stereo, a mono input stays mono, and recordings with more channels follow the same rule. Reversal preserves the decoded duration, sample rate, and channel count when those values fit the stated limits. What changes is the position of every event: a snare hit at the three-second mark of the original becomes the snare hit that lands at duration minus three seconds in the result, while the final frame of the original becomes the first frame of the reversed file.
Reversing samples is a different operation from time-stretching, pitch-shifting, or reversing the compressed container. The tool only reorders decoded audible sample data. It does not normalize loudness, remove silence, change pitch on purpose, stretch time, or repair clipping, and the original metadata, tags, and artwork are not promised to be carried over into the new WAV.
File Types and Limits Before You Start
Before opening the file picker, it helps to know what the tool accepts and what it rejects, because the picker, the byte limit, and the decoder each apply their own checks. Acceptance and successful decoding are separate steps, so a file can pass the picker and still fail later when Web Audio tries to read the bytes.
The picker accepts common audio MIME types for MP3, WAV, M4A, AAC, Ogg, and WebM. The compressed source file must be no larger than 50 MB. Once decoded, the audio must be five minutes or shorter, contain one to eight channels, use a sample rate from 8,000 to 192,000 Hz, and contain no more than 30 million channel samples in total. The channel-sample budget is the number of frames multiplied by the number of channels, and it protects the tab from unexpectedly large decoded arrays even when a small compressed file would otherwise look harmless.
| Limit | Allowed value |
|---|---|
| Compressed file size | up to 50 MB |
| Decoded duration | up to 5 minutes |
| Channels | 1 to 8 |
| Sample rate | 8,000 to 192,000 Hz |
| Total channel samples | up to 30 million |
A file that exceeds any limit receives a specific message and is not partially processed. Changing files or retrying also clears the previous download first, so an old success cannot be mistaken for a new result after an error.
How to Reverse an Audio File in Your Browser
The full workflow takes three high-level steps. The picker, the reversal, and the download each have a clear role, and the steps below follow the verified operating steps directly.
- Choose a supported audio file up to 50 MB using the file picker, and optionally preview the original in the browser so you can compare it to the reversed result.
- Select Reverse audio and wait while every decoded channel sample is reversed locally in the current tab. Stereo files reverse each channel independently, multi-channel files do the same per channel, and the Web Audio context used for decoding is closed after the operation or when work is replaced.
- Preview the result, verify its duration and audio properties, then download the new file. The download is always a freshly encoded PCM16 WAV, even when the original was MP3, M4A, AAC, Ogg, WebM, or a compressed WAV.
Stale work is guarded against, so a previous asynchronous job cannot replace a newer result. The original file receives a temporary local object URL for the built-in preview, the finished WAV receives a separate temporary download URL, and selecting another file, running the operation again, or leaving the page releases obsolete URLs so they do not linger in the tab.
Checking the Output: Duration, Channels, and Sample Rate
The download is not the source container played backward; it is a fresh PCM16 WAV file written from the reversed decoded samples. Each browser-decoded floating-point sample is clipped to the range from -1 to 1, mapped to signed 16-bit PCM, and written little-endian, so negative full scale maps to -32768 and positive full scale maps to 32767. Reducing floating-point samples to 16-bit can change numerical precision, and the resulting WAV may be much larger than a compressed source.
Reversal preserves the decoded duration, sample rate, and channel count, and each accepted channel is written back into the WAV in the correct frame order. For a stereo source, the left channel is reversed independently, the right channel is reversed independently, and the two channels are interleaved again in the correct frame order so left-right alternation is correct throughout the file. Original metadata, album art, tags, chapters, loop markers, encoder settings, compressed bitrate, and container-specific fields are not copied, because the tool reverses decoded sample data rather than editing or preserving the source container.
For a reliable check, listen to the beginning and end of the result, confirm the duration, channel count, sample rate, and file size shown by the tool, and open the download in the editor or player where it will be used. Browser preview success does not guarantee that every older device supports the same WAV channel layout or high sample rate, so a quick open in the destination program confirms compatibility before the file is committed to a project.
When a Familiar File Format Will Not Decode
A file with a familiar extension can still fail, and the reason usually lives in codec support rather than the picker. The picker accepts common MP3, WAV, M4A, AAC, Ogg, and WebM audio MIME types, but actual codec support depends on the visitor's browser and operating system. A container can also contain a codec that a particular browser cannot decode, which is why the tool reports a decode error rather than claiming that every file with a familiar extension must work.
Web Audio's decodeAudioData returns a promise that resolves to an AudioBuffer when the bytes can be decoded and rejects when they cannot, so the tool stops before any sample is reversed and shows a clear decode error. Nothing is uploaded to diagnose the file, no remote fallback is substituted, and FFmpeg or a server-side converter is not installed to rescue the input. If the file cannot be read in the current browser, the practical options are to re-export the clip from the source program into a more widely supported codec, to switch to a different browser, or to use a desktop audio editor that can decode the file locally.
Codec limits can also interact with the other limits. A small compressed file may decode to a long, large sample array, which can push the total channel-sample count past 30 million even when the byte size stays under 50 MB. The total channel-sample budget protects the tab in this case and turns an otherwise silent crash into a clear, named error.
When an Audio Editor Is a Better Choice
A browser-based reversal is enough when the goal is to play a recording backward for sound design, a transition, a backwards lyric message, or a quick listen from the other direction. The local workflow is also a good fit for sample inspection, because reversing a short clip can reveal a click, breath, or transient that was buried at the end of the source recording.
A desktop audio editor is a better choice when more is needed. Fades, trimming, codec selection, metadata preservation, normalization, loudness targets, repair of clipping, time stretching, or pitch shifting all live outside what the in-browser tool is built to do. It reverses decoded audible sample data and re-encodes a new PCM16 WAV, so any pass that depends on tags, artwork, or a specific compressed codec should be done in a full editor after the reversed WAV is downloaded.
For mobile listeners, a smaller source file still works best because phones can run out of memory on large decodes. Keeping the clip inside the 50 MB, five-minute, and channel-sample limits keeps the reversal predictable on phones and laptops alike, and it leaves headroom in the tab for preview playback while the reversed samples are being prepared.