Does the 50 MiB limit apply to the finished WAV?

No. It applies only to the one encoded input file you select. The completed PCM16 WAV has its own 30-million-channel-sample output budget and can be larger than 50 MiB.

Why was my under-50-MiB file rejected?

Its decoded audio may exceed five minutes, eight channels, the 8,000–192,000 Hz sample-rate range, or the 30-million-channel-sample input budget. It may also use a codec profile that the current browser cannot decode.

Can I pitch-shift a file larger than 50 MiB?

Not directly. You must select a smaller source file. The tool does not compress an oversized input or render it in part.

Does changing pitch keep the original duration?

No. Playback-rate resampling changes pitch and duration together: raising pitch makes the audio shorter and faster, while lowering pitch makes it longer and slower.

Are the source and rendered files uploaded?

No. File reading, decoding, resampling, and PCM16 WAV encoding all run locally in the current browser tab.

What Does the 50 MiB Limit Mean in Audio Pitch Changer?

The 50 MiB limit means that Audio Pitch Changer accepts one selected audio file only when the file’s stored size is no greater than 50 MiB.

This is a limit on the single source file you select, not a duration limit, a multi-file quota, or a maximum size for the finished WAV. A compressed file can be smaller than 50 MiB yet fail later because its decoded audio exceeds another limit. Conversely, a file over 50 MiB cannot be processed by this tool even if it is short enough and would otherwise be suitable.

what does the 50 mib limit mean when using audio pitch changer — What Does the 50 MiB Limit Mean in Audio Pitch Changer?

What the 50 MiB limit covers

Think of the 50 MiB cap as the first gate. The browser checks the encoded file’s byte size before decoding or rendering it. “MiB” means mebibyte, a binary unit: one MiB contains 1,048,576 bytes. Because operating systems and file managers may label sizes as either MB or MiB, check the unit shown in the file properties rather than relying only on the rounded number.

The size belongs to the original file stored on your device. It is not the amount of uncompressed audio held in memory after decoding, and it does not restrict the generated output. For example, a small MP3 can expand into a much larger PCM WAV, while a source that is already close to 50 MiB has little room for an uncompressed export.

The selected file must also be browser-decodable. Audio Pitch Changer supports common MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC inputs, but actual decoding still depends on the current browser and the codec profile. A recognized extension does not guarantee that every unusual MP3, AAC, or container profile will work.

Limits checked after the file is decoded

Passing the 50 MiB check does not guarantee that the render can finish. Once the browser decodes the source, it checks the duration, channel count, sample rate, and sample budget. The completed pitch-shifted result is then checked against a separate output budget.

Check	Allowed value
Selected input file	One browser-decodable file, no larger than 50 MiB
Decoded duration	At most five minutes
Decoded channels	At most eight channels
Decoded sample rate	8,000 through 192,000 Hz
Decoded input budget	At most 30 million channel samples
Rendered output budget	At most 30 million channel samples
Output duration	No separate duration cap, but the complete output must fit the output budget
Pitch shift	Whole-number setting from −12 through +12 semitones

Channel samples count individual sample values across the audio channels, so duration, channel count, and sample rate can interact. A short file with many channels or a high sample rate can reach the 30-million-channel-sample input limit even when its encoded size is comfortably below 50 MiB.

Why the finished WAV can exceed 50 MiB

The 50 MiB rule applies only to the selected input. Audio Pitch Changer creates a new, uncompressed PCM16 RIFF/WAVE file, and the finished file has no 50 MiB ceiling. Its size depends on the resulting duration, sample rate, and number of channels. A downward pitch shift can also make the output substantially longer than the source.

The output is a fresh encoding rather than a modified copy of the input. It does not preserve the original compression method, compressed bitrate, tags, artwork, chapters, cue points, loop metadata, or other container metadata. PCM16 quantization can also differ from the decoded floating-point samples.

That distinction is important: the input-size limit protects the initial file-selection stage, while the output limit determines whether the complete resampled render fits within the tool’s processing budget. Neither limit silently shortens the result.

How pitch changes duration in this tool

Audio Pitch Changer uses playback-rate resampling rather than a time-stretching algorithm. Its equal-tempered playback ratio is 2^(n/12), where n is the number of semitones. In one worked example, choosing +12 semitones substitutes n = 12 into that formula and produces a 2× playback rate.

Shift	Playback rate	Effect
+12 semitones	2×	One octave higher, roughly half the original duration
0 semitones	1×	Original pitch and duration
−12 semitones	0.5×	One octave lower, roughly twice the original duration

MDN’s AudioBufferSourceNode playbackRate reference describes values above one as speeding up audio and values below one as slowing it down. The tool therefore changes pitch and duration together; it does not promise to preserve tempo, speech cadence, beat positions, or the exact original duration. The relationship is also explained in the guide Does Changing Pitch Keep the Original Speed and Duration?

If a production requires a different pitch while keeping the duration fixed, use a dedicated phase-vocoder or another time-stretching workflow. Lowering the pitch in this resampling method increases the number of output frames, which is why an input that passes the decoded-input budget can still fail the separate output budget.

Run the supported browser workflow

The Audio Pitch Changer performs the following workflow locally in the current browser tab:

Select one source file. Confirm in its file properties that it is no larger than 50 MiB and that its format and codec profile can be decoded by your browser.
Set a whole-number pitch shift. Choose a value from −12 through +12 semitones. Remember that a positive shift makes the audio faster and shorter, while a negative shift makes it slower and longer.
Create the complete local render. The browser decodes the source, calculates the full expected output, checks the output budget, and renders at the decoded sample rate. If the complete output is over budget or cannot be allocated, the tool reports an error and creates no download.
Review the stated duration change. Check the displayed duration against the direction and approximate magnitude of the selected shift before saving the result.
Download the PCM16 WAV. Save the newly encoded RIFF/WAVE file and play it in a trusted local player. The page does not provide a blob-backed audio preview.

File reading, decoding, offline resampling, and WAV encoding remain in the current tab. No source audio or rendered audio is uploaded to Lizely.

Resolve a rejected or over-budget file

If the selected file is larger than 50 MiB, create a smaller source with a trusted local editor or audio converter, then select that new file. The pitch changer does not compress oversized inputs or provide a way to bypass the 50 MiB check.

If the file is under 50 MiB but will not decode: try a more widely supported format or codec profile, such as a conventional MP3 or WAV file, and check that the current browser supports it.
If the decoded source fails a limit: shorten the source, reduce its channel count, or use a compatible sample rate before trying again.
If a downward shift is over the output budget: choose a shift closer to zero or a shorter source, because lower pitches require more output frames.
If rendering fails: do not expect a partial download. The tool reports an error and produces no file when the complete result cannot fit or cannot be allocated.

The safest workflow is to keep the original file untouched, verify its size before processing, and retain the downloaded WAV as a separate result. This browser-based method is suited to quick creative experiments, practice tracks, sound effects, and rough editing; browser resampling quality is implementation-defined, and strong upward shifts can reveal aliasing or source-codec artifacts.