Reverse Audio does not keep the original MP3 or M4A encoding in the output. The tool always writes a newly encoded 16-bit PCM WAV file, regardless of whether the input was MP3, WAV, M4A, AAC, Ogg, or WebM. This is a deliberate part of how the tool works: it decodes the source file into raw audio samples using the browser's Web Audio API, reverses each channel's sample order, and then re-encodes the result as a fresh WAV with signed 16-bit little-endian PCM samples. Because the data passes through a decoder and a new WAV encoder, the original codec, compressed bitrate, container format, ID3 or iTunes tags, album art, chapters, encoder settings, and any container-specific fields are dropped along the way. The output WAV is also several times larger per second than the compressed input because uncompressed PCM stores one 16-bit sample per channel per frame. Anyone who needs the reversed audio back in MP3 or M4A has to transcode the new WAV separately using an audio editor or a separate converter.
What Format Does Reverse Audio Actually Export?
Reverse Audio always writes a single output type: a 16-bit PCM WAV file. This applies whether the source file is MP3, WAV, M4A, AAC, Ogg, or WebM. The WAV that downloads is a freshly written file produced by the same encoder that the tool's golden tests inspect, not a copy of the source container with its bytes mirrored.
Inside that WAV, every sample is a signed 16-bit integer. The browser decodes the source into floating-point samples (typically between -1 and 1), Reverse Audio clips any out-of-range value to the -1 to 1 range, maps each value to a signed 16-bit integer where negative full scale becomes -32768 and positive full scale becomes 32767, and writes the bytes in little-endian order. The header includes the RIFF marker, the WAVE identifier, a fmt chunk with the PCM format tag, and a data chunk whose length reflects the actual number of samples written.
The sample rate and channel count of the WAV match the decoded source, within the tool's limits. A 44.1 kHz stereo MP3 input produces a 44.1 kHz stereo WAV output. A 48 kHz mono M4A input produces a 48 kHz mono WAV output. If the source's decoded sample rate falls outside 8,000 to 192,000 Hz, or the channel count falls outside 1 to 8, the file is rejected before any reversal happens and no WAV is produced.
Why the Original Codec Cannot Stay in the Output
Reverse Audio reverses decoded samples, not container bytes. To reverse a compressed stream you have to decode it first, and once you have raw PCM in memory, the original compressed representation is no longer available to be rewritten. The tool uses the browser's Web Audio API, documented at the MDN BaseAudioContext.decodeAudioData reference, to produce an AudioBuffer of floating-point channel data. From that point on, the only thing left to do is rearrange the samples and write them to a new file.
That two-step process — decode, then encode — is the structural reason the output cannot be the same MP3 or M4A file played backward. A reversed MP3 is not a meaningful file format because MP3 is a perceptual codec that depends on frame ordering, Huffman coding, and the encoder's psychoacoustic model. There is no standard "MP3 with the audio reversed" you could write directly. The same is true of AAC inside an M4A container. Reverse Audio could in principle call FFmpeg on a server and re-encode the reversed PCM into MP3 or M4A, but it does not. It does not install FFmpeg, does not call a conversion server, and does not silently substitute a remote workflow. It produces WAV because WAV is the simplest faithful container for raw reversed PCM.
For background on how the reversal itself works at the sample level, the guide What Is Reverse Audio and How Does Sample Reversal Work? walks through the per-channel sample flip.
How to Reverse an MP3 or M4A File Locally
- Open Reverse Audio in your browser and choose a supported audio file. The file picker accepts MP3, WAV, M4A, AAC, Ogg, and WebM files up to 50 MB. Use the file picker to choose a supported audio file, and use the optional original-preview control to confirm the file plays correctly before reversing.
- Select Reverse audio. The browser decodes the file with Web Audio and reverses every decoded channel sample locally in the current tab. Decoded audio is rejected (not truncated) if it exceeds five minutes, contains more than eight channels, contains more than 30 million total channel samples, or uses a sample rate outside 8,000 to 192,000 Hz.
- Wait for the reversal to complete. Long files take longer because the browser has to decode the entire stream before reversing. No samples are skipped or capped inside an accepted file; every channel is reversed end-to-end.
- Preview the result in the built-in player. Listen to both ends of the reversed clip. The original end should now be at the start, and any attack transients that were forward should now fade in instead of cutting in.
- Confirm the duration, channel count, sample rate, and file size shown next to the preview. These values describe the WAV you are about to download.
- Click the download button to save the new PCM16 WAV to your device. The download is a freshly encoded file with its own temporary local URL, separate from the temporary URL used for the original preview.
What the WAV Keeps and What the WAV Drops
Below is a side-by-side view of which properties survive into the reversed WAV and which ones are dropped during the decode-and-re-encode cycle.
| Property | In the source MP3 or M4A | In the reversed WAV output |
|---|---|---|
| Audio sample order | Forward in time | Reversed in time |
| Sample rate | Original rate, if 8 kHz–192 kHz | Same as decoded source |
| Channel count | 1–8 channels | Same as decoded source |
| Duration | Source length, if ≤5 minutes | Same length, in reversed order |
| Bit depth | 16-bit or 24-bit floats internally | Forced to 16-bit signed PCM |
| Codec (MP3, AAC, Opus, Vorbis, etc.) | Compressed | None — uncompressed PCM |
| Container (MP3, M4A, OGG, WebM) | Source container | WAV only |
| Bitrate | Source bitrate | Uncompressed; file grows |
| ID3 / iTunes / Vorbis tags | Present | Not copied |
| Album art, chapters, loop markers | Present | Not copied |
| Encoder settings, encoder delay | Present | Not copied |
A few rows deserve extra explanation. The bit depth row matters because some source files contain 24-bit samples inside their compressed stream; Reverse Audio still writes 16-bit PCM, so the rounding can shift very quiet values. The bitrate row matters because compressed input has a fixed number of bits per second of audio, but PCM WAV has no bitrate in the same sense — the WAV simply stores one 16-bit sample per channel per frame. As a result, the WAV is several times larger per second than a compressed source of the same material, and a long reversed clip can easily be much bigger on disk than the MP3 or M4A you started with.
Limits That Decide Whether the Reversal Completes
A few hard limits decide whether Reverse Audio produces a WAV or reports an error, and they are checked both at the file-picker stage and after decoding. The compressed input file must be no larger than 50 MB on disk. The 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. The channel-sample budget is the number of frames multiplied by the number of channels, and it exists so a small compressed source cannot expand into a multi-gigabyte decoded array inside your tab.
If the file picker accepts a container but the browser's Web Audio decoder cannot read the codec inside it, the tool reports a specific decode error rather than producing an empty WAV. Codec support varies by browser and operating system, so a familiar extension such as .m4a or .ogg is not a guarantee that the file will decode. Input acceptance and successful decoding are separate checks inside the tool, and the message you see is specific to which check failed.
When a file is rejected, the previous successful download is cleared first, so an old WAV cannot be mistaken for a new result after a fresh error. Job and mounted-state guards also prevent stale asynchronous work from writing a late result over a newer one. These guards are part of why the same encoder and reversal functions can be reused across production and isolated tests without producing mismatched output.
Verifying the WAV Before You Use It
The browser preview confirms the WAV decodes and plays inside the same browser tab, but it does not guarantee that every downstream device accepts the same channel layout or sample rate. Open the downloaded WAV in the editor or player where you plan to use it. Confirm the duration, channel count, sample rate, and file size match what the tool displayed. If the destination expects a compressed MP3 or M4A file, you will need to transcode the new WAV separately — Reverse Audio does not output compressed formats and does not promise to.
For a reliable workflow, keep the original MP3 or M4A source, listen to the original preview, run the reversal, listen to the start and end of the new WAV, and only then move the WAV into the project that needs reversed audio. The guide Are Audio Files Uploaded When You Use Reverse Audio? is a useful companion if you want to confirm the file never leaves the tab. If you also need fades, trimming, codec selection, metadata, or mastering controls, use an audio editor on the WAV after the reversal. Reverse Audio focuses on one task — reversing decoded samples and producing a faithful WAV — and leaves those adjacent steps to dedicated tools.