The main risk with the Audio Pitch Changer is that it changes pitch, speed, and duration together, so a higher-pitched result may be faster and shorter rather than a clean, tempo-preserving edit.
That behavior comes from playback-rate resampling rather than time stretching. Changing the playback rate changes the perceived pitch and consumes the decoded material in less or more time. The tool does not preserve tempo, speech cadence, beat positions, or the exact original duration.
Other possible problems include aliasing, audible source artifacts, loss of the original encoding and metadata, a rejected input, or an output that exceeds the render budget. A key safeguard is that the tool produces either a complete render or an error. It does not quietly cut off the ending or offer a truncated download. There is also no in-page audio preview, so you must download the WAV and check it in a trusted local player. Try the Audio Pitch Changer to do this in your browser.
The timing change may defeat the intended edit
The control accepts whole-number shifts from -12 through +12 semitones. Its playback-rate ratio follows twelve-tone equal temperament: playback rate = 2^(n/12), where n is the signed semitone shift. The MDN playbackRate reference explains that values above one speed up audio, values below one slow it down, and a non-unit rate causes resampling. The W3C Web Audio playback algorithm expresses detuning in cents, matching the related equal-tempered semitone relationship.
| Shift | Playback rate | Expected effect |
|---|---|---|
| +12 semitones | 2× | One octave higher, roughly half the original duration |
| +1 to +11 semitones | Above 1× | Higher pitch, faster delivery, shorter duration |
| 0 semitones | 1× | Original pitch and duration retained |
| -1 to -11 semitones | Below 1× | Lower pitch, slower delivery, longer duration |
| -12 semitones | 0.5× | One octave lower, roughly twice the original duration |
These timing changes can be useful for a deliberately sped-up or slowed effect, but they are undesirable when the goal is to move a vocal or instrument to another key while keeping the musical timing intact. If fixed duration is essential, use a dedicated phase-vocoder or another time-stretching workflow rather than expecting playback-rate resampling to hold the tempo. For a separate example of that distinction, see how to change audio pitch in Audacity without affecting tempo.
Resampling can expose unwanted sound
Browser resampling quality is implementation-defined, so the result is not guaranteed to have pristine mastering quality. A strong upward shift can reveal aliasing or codec artifacts that were less obvious in the original recording.
- Aliasing: The faster resampling process can make unwanted high-frequency content more noticeable.
- Source artifacts: Compression noise or distortion already present in the input may become easier to hear after resampling.
- Clipping: Floating-point samples outside the legal -1 through +1 interval are clipped before the PCM16 conversion, so problematic peaks cannot remain as unclipped overs.
A zero-semitone setting does not deliberately alter timing, but it still creates a newly rendered and encoded file. Any clipping, quantization, or browser-rendering differences still apply. Listen to the complete downloaded result instead of assuming that an unchanged pitch setting guarantees an identical file.
The export is a new audio file
The download is newly encoded as uncompressed, interleaved, little-endian PCM16 in a RIFF/WAVE container. It is a derivative suitable for experiments and editing, not a bit-for-bit replacement for the source.
| Source feature | What the downloaded result contains |
|---|---|
| Codec and compression | New PCM16 encoding; the original codec, compression quality, and bitrate are not preserved |
| Tags and artwork | No transferred tags or artwork |
| Timeline and container information | Chapters, cue points, loop metadata, and other container metadata are not preserved |
| Sample values | Floating-point samples are clipped when necessary and quantized to PCM16, so the sample representation can differ |
Keep the original file if you need its codec, metadata, artwork, or an untouched master. The shifted WAV is better treated as a new working asset. It can be useful for quick creative experiments, practice tracks, sound effects, and rough editing, but the tool does not present its processing as a transparent mastering stage.
Limits decide whether a render can finish
The input must be one browser-decodable encoded file no larger than 50 MiB. Common MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC inputs are supported, although the current browser still determines whether a particular codec profile can decode. A recognized extension alone does not guarantee successful decoding.
- Decoded duration may be at most five minutes.
- Decoded audio may contain at most eight channels.
- The decoded sample rate must be between 8,000 and 192,000 Hz.
- Input decoding is limited to 30 million channel samples.
Passing those input checks does not guarantee that the shifted output will fit. The output has a separate 30 million channel-sample limit. Lowering pitch makes the audio longer and requires more output frames, so an input that passes the decoded limit can still exceed the output budget.
Empty files, unsupported types, invalid decoded dimensions, and failed decodes are rejected. If the complete output would exceed the output budget or the browser cannot allocate it, the tool reports an error and creates no download. It does not silently truncate the tail, impose a hidden duration cap, or substitute an incomplete file.
Run a controlled pitch-shift workflow
- Choose one eligible file. Confirm that it is no larger than 50 MiB and can be decoded by your current browser. Do not assume every file with a common extension will open successfully.
- Set a whole-number shift from -12 through +12 semitones. Treat the setting as both a pitch and timing decision: positive values raise pitch and shorten the result, while negative values lower pitch and lengthen it.
- Create the complete local render. Wait for the current render to finish. If the requested shift is over budget or the browser cannot allocate the full result, an error is shown and no WAV is offered.
- Review the stated duration change. Confirm that the new timing suits the intended use. Changing the input or semitone setting invalidates the previous result, and an older background job cannot replace the newer result.
- Download the PCM16 WAV and inspect it locally. Play the file in a trusted local player because the tool does not create an in-page audio preview. Keep the source file separately if you need its original encoding or metadata.
File reading, decoding, offline resampling, and WAV encoding all happen locally in the current browser tab. No source audio or rendered audio is uploaded to Lizely.
Recognize when this approach is unsuitable
Choose a different production method when the shift must preserve duration, tempo, beat alignment, or speech cadence. A dedicated phase-vocoder or other time-stretching workflow is designed for that task; this tool explicitly does not promise those properties. Likewise, if metadata, chapters, cue points, or the original master file must survive intact, retain the source and treat the WAV as a separate derivative.
For creative sound design, rehearsal, and rough editing, the predictable speed-and-duration relationship can be an advantage rather than a problem. The important distinction is whether that change is intentional. A fast, short result is not a failed pitch shift when that is the effect you requested.
Review the result before relying on it
Use the downloaded WAV for the final review because there is no page preview. Check the following before moving the file into a larger project:
- Compare the rendered duration with the duration change stated by the tool.
- Listen through the entire file for harsh high frequencies, aliasing, codec noise, distortion, or flattened peaks.
- Confirm that the new speed and cadence still work for the intended task.
- Check whether any tags, chapters, cue points, or artwork you expected are absent from the new WAV.
- Keep the untouched source available for comparison and for projects that need the original timing or format.
Related reading: What Should I Review After I Use an Audio Speed Changer?.