To check the result after using an audio pitch changer, render the full file with your chosen semitone shift, download the new PCM16 WAV, and verify three things: that the pitch moved by the expected musical interval, that the duration changed in the correct direction, and that the output plays cleanly in a trusted local media player. Audio Pitch Changer on Lizely follows exactly that workflow - you upload one file, choose a whole-number shift between -12 and +12 semitones, and the browser produces one complete PCM16 WAV file you can save and inspect. Because the tool uses playback-rate resampling, the pitch and the duration change together, so confirming one confirms the other. A positive semitone value shortens the audio and raises the pitch; a negative value lengthens the audio and lowers the pitch. The page intentionally does not offer an in-browser preview, so the downloadable file is the only artifact you can listen to and verify. That makes the download step itself part of the verification, not an optional convenience.
What "the Result" Actually Means Here
When an audio pitch changer finishes, the result is a single new audio file, not a live effect or a streaming preview. For Audio Pitch Changer, that file is always an uncompressed, little-endian, 16-bit PCM WAV wrapped in a standard RIFF/WAVE container. Nothing from the original file is preserved beyond the decoded audio itself: the source codec, bitrate, ID3 tags, artwork, chapters, cue points, and loop metadata are all discarded. Floating-point samples are clipped to the legal -1 through +1 range before conversion, and the final PCM16 quantization can differ slightly from the decoded source. Treat the downloaded WAV as a freshly rendered take rather than an edited copy of your original.
This distinction matters for checking the result, because the most reliable way to verify a shift is to load the new WAV into a media player or audio editor and listen to it next to the source. If the file plays and the duration direction matches what you asked for, the math behind the shift has worked correctly. For more on the speed-versus-pitch relationship that defines this kind of result, the guide on whether pitch changes keep the original speed and duration walks through the same tradeoff in detail.
Pick a File and a Semitone Shift
Before the tool can render anything, you need two inputs: one audio file the browser can decode and one whole-number semitone value. Audio Pitch Changer accepts the common browser-decodable formats - MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC - but actual codec support still depends on the browser you are using, so a familiar extension does not guarantee that every unusual profile will decode. The file itself has to be 50 MiB or smaller, and once decoded the audio cannot exceed five minutes, eight channels, a sample rate from 8,000 to 192,000 Hz, or 30 million channel samples on the input side. Those caps exist so the full render can complete inside the browser without truncation.
The semitone control runs from -12 to +12 in whole steps. A value of -12 lowers the file by exactly one octave, +12 raises it by exactly one octave, and 0 returns the original pitch. Every other whole-number value shifts the pitch by a fixed musical interval under twelve-tone equal temperament, the same system described in McGill University's reference material on MIDI and frequency conversion. Pick the shift that matches what you want to verify; the result cannot be a fraction of a semitone, so choose the nearest whole number.
Generate the Result and Download the WAV
The verification path is short, but each step is deliberate. Audio Pitch Changer renders the complete file before exposing a download, so partial or streaming previews are not part of the workflow. The downloadable file is the artifact you verify.
- Open Audio Pitch Changer in your browser and choose one audio file no larger than 50 MiB in a browser-supported codec.
- Set a whole-number semitone shift from -12 through +12. Remember that positive values also shorten the audio and negative values lengthen it.
- Trigger the local render and wait for the page to show the new stated duration. If the requested shift would push the output past the 30-million-channel-sample budget, the tool reports an error and creates no file.
- Download the PCM16 WAV that the page offers once the render finishes.
- Open the downloaded file in a trusted local player or audio editor and compare it against the original. Confirm the pitch moved in the direction you asked for and the duration moved in the matching direction.
Because processing happens inside the current tab and the file is offered as a single complete download, the WAV is what you actually verify. There is no separate "preview vs. final" comparison built into the page; the download is the source of truth.
Understand Why Duration Changes With Pitch
The fastest way to confirm a pitch change is correct is to check the new duration. Audio Pitch Changer uses playback-rate resampling, which is the same mechanism MDN documents for AudioBufferSourceNode.playbackRate: a rate of 1.0 plays at original speed, values above 1.0 speed the audio up and resample it to a higher pitch, and values below 1.0 slow it down and resample it to a lower pitch. The exact ratio follows the equal-tempered formula rate = 2^(n/12), where n is the chosen semitone shift. A shift of +12 doubles the rate, a shift of -12 halves it, and 0 keeps it at 1.0.
| Semitone shift | Musical effect | Playback rate | Duration vs. original |
|---|---|---|---|
| -12 | One octave down | 0.5× | About 2.0× longer |
| -7 | Perfect fifth down | 2^(-7/12) ≈ 0.667× | About 1.5× longer |
| 0 | Original pitch | 1.0× | Same length |
| +7 | Perfect fifth up | 2^(7/12) ≈ 1.498× | About 0.667× as long |
| +12 | One octave up | 2.0× | About 0.5× as long |
Worked example for the +7 row: with n = 7, the playback rate is 2^(7/12) = 2^0.5833..., which is about 1.4983. A 60-second input therefore becomes roughly 60 / 1.4983, which is about 40.05 seconds of output. The W3C Web Audio specification defines the cents relationship the same way in the AudioBufferSourceNode playback algorithm, where detuning in cents multiplies the rate by 2^(cents/1200); with n semitones that simplifies to the formula above.
Because the relationship is fixed, an unexpected duration direction means the pitch went the wrong way too. The two are linked: if the new file is shorter than the source, the pitch is higher than the source; if it is longer, the pitch is lower. The tool never claims to preserve tempo, speech cadence, beat positions, or exact original duration, so a duration change is expected, not a bug.
Recognize the Limits and Error Messages
Some inputs look valid but still cannot produce a downloadable result. Audio Pitch Changer validates every limit before allocating the offline render and rejects inputs that would force an incomplete output. The checks are explicit: an encoded file above 50 MiB, decoded audio longer than five minutes, more than eight channels, a sample rate outside 8,000 to 192,000 Hz, or more than 30 million channel samples on the input side all cause a rejection. The pitch-shifted output has its own 30-million-channel-sample cap, and because lowering pitch makes the file longer, an input that passes the decoded limit can still fail the output limit. When that happens the message states that the requested shift is over budget and nothing is truncated - no half-finished WAV is offered as a "result." Empty files, unsupported types, invalid decoded dimensions, and failed decodes are rejected the same way. Every change to the file or semitone value invalidates the previous render, so the download button always corresponds to the settings currently shown on the page.
When You Need a Different Workflow to Verify
Playback-rate resampling is the right approach when you want pitch and duration to move together the way a tape playing faster or slower would. It is the wrong approach when you want pitch to change but the length to stay the same, which is a different problem that time-stretching tools are built for. If a production needs pitch change at fixed duration - for example, repitching a vocal while keeping the backing track the same length - a phase vocoder or another time-stretching workflow is the correct tool, and the result from Audio Pitch Changer will not satisfy that need. For listeners and editors checking whether a simple, joined pitch-and-speed change happened as expected, the local render plus a trusted media player is the right verification step. The math behind the shift is fixed, the file format is fixed, and the result either matches the table above or it does not. If it does not, the page tells you that the shift was over budget rather than handing you a silently broken file.
For a deeper look, see Verify Correct Use of an Audio Speed Changer.