Media · WAV
A 2 MB WAV file, on demand.
Exactly 2,097,152 bytes of 16-bit stereo PCM audio at 44.1 kHz carrying a quiet 220.5 Hz tone, built on your machine the moment you press the button.
2,097,152 bytes, exactly.
Every byte above the 45 bytes structural minimum goes into audio samples — the whole file is real audio data, which is why this file still behaves like one a real user would send.
Unit convention
2 MB on this page means exactly 2,097,152 bytes, using the binary (MiB) convention some systems label "MB" for short. 1 MB in the strict decimal sense is 1,000,000 bytes; 1 MiB is 1,048,576 bytes — the readout above always shows the exact count either way.
Approximate size equivalents
Roughly 1,165 pages of typed text, 2 minutes of 128 kbps audio, 12 seconds of CD-quality audio. These figures compare file size only — the generated file does not contain this text, audio or image content.
Accepted by
PHP default upload_max_filesize, Discord free attachment, AWS API Gateway payload — all publish a limit at or above this size, based on commonly cited figures that can vary by plan and change over time.
Other WAV sizes
Default limits start biting here: PHP ships with a 2 MB cap, and many form builders stop at 5 MB.
2 MB in other media formats
Questions.
Is this 2 MB WAV file valid?
Yes. It is 16-bit stereo PCM audio at 44.1 kHz carrying a quiet 220.5 Hz tone. The extra bytes sit in audio samples — the whole file is real audio data, so it opens in media players, Audacity, ffmpeg and Python's wave module.
Does 2 MB mean 2,097,152 bytes?
On this page, yes — 2 MB uses the binary (MiB) convention, so the file is exactly 2,097,152 bytes. 1 MB in the strict decimal sense would be a different, smaller byte count. Upload validators may use either convention, so the exact byte count is always shown to remove any ambiguity.
What is a 2 MB file used for?
Default limits start biting here: PHP ships with a 2 MB cap, and many form builders stop at 5 MB. For WAV specifically, the usual job is testing audio upload limits and transcoding queues.
Where is the file downloaded from?
Nowhere. It is assembled in a Web Worker on your own device and handed to the browser as a Blob, so nothing is uploaded, fetched or stored.