
Reverse audio
Play an audio file (or a video's audio track) end to start, decoded to raw samples and re-encoded as WAV. WAV input decodes in Node, the CLI and MCP as well as the browser, the same PCM path audio-trim-merge's packet copy sits next to; AAC, MP3, Opus, FLAC and Vorbis need a browser.
Reverse audio flips a clip end to start by decoding its samples, reversing every channel, and writing the result back out as WAV. Sample rate and channel count stay exactly as they were; only the order changes. WAV input opens in Node, the CLI, or MCP; AAC, MP3, Opus and FLAC need a browser tab.
Questions
Does reversing change the sample rate or channel count?
No. The output keeps the exact sample rate and channel count of the source; only the order of the samples within each channel is reversed.
Does it work on a video file?
Yes, on the audio track. The picture is left alone here; only the decoded audio samples are reversed and written out as a standalone WAV file.
Why is the result always WAV, not the original format?
Because the audio is decoded to raw PCM samples before it can be reversed, and the tool re-encodes that PCM as WAV rather than back into the source codec.
Why does the command line accept some files but not others?
WAV carries raw samples that decode without WebCodecs, so it works in Node, the CLI and MCP. AAC, MP3, Opus and FLAC only decode through WebCodecs, an API only a browser tab provides.
What is the output named?
Your file name with -reversed.wav on the end, so voice.mp3 becomes voice-reversed.wav.