A silent audio file is useful when a screen needs a real duration but the final recording is not ready. It can exercise a player timeline, an upload field or an editing track. A short tone answers a different question: whether a playback path produces audible output. Use each fixture for the behavior it can actually demonstrate.
1. Start with five seconds of silence
Open the WAV generator, choose Silence, keep 44,100 Hz and Mono, and set the duration to 5 seconds. Generate the file, then use the player. Playback starts only after you press Play. The expected result is a moving time display with no sound. Download the WAV and keep that exact file as your baseline fixture.
Create a silent WAV or test tone →
2. Change one setting at a time
| Fixture | Check | What it does not prove |
|---|---|---|
| 1 second of silence | Short-file handling, end state and replay. | That the speakers are producing sound. |
| 30 or 120 seconds of silence | Duration formatting, seeking and longer uploads. | Speech recognition, music quality or compressed-codec support. |
| 5 seconds at 440 Hz | An audible playback path at a low device volume. | Calibrated loudness, frequency response or recording quality. |
| Stereo instead of mono | Whether a two-channel WAV is accepted. | Left/right channel routing: both channels contain the same samples. |
3. Know the exact size of this WAV
This tool writes uncompressed 16-bit PCM with a 44-byte WAV header. For its whole-second durations, the size in bytes is:
44 + seconds × sample_rate × channels × 2- 5 seconds, 44,100 Hz, mono: 441,044 bytes.
- 10 seconds, 48,000 Hz, stereo: 1,920,044 bytes.
- 120 seconds, 48,000 Hz, stereo: 23,040,044 bytes.
Silence and a tone have the same byte size when duration, rate and channels match. Other WAV files may contain extra metadata or a different encoding, so this formula is specific to these generated files. To test an exact upload-byte boundary without requiring audio, use the exact-size file generator.
4. Check the file after the upload
A successful selection is only the first step. Check the server response, then reload the record and play the stored file. Verify the displayed duration, pause/resume, seeking and the final state. If the application re-encodes audio, compare duration and channel count instead of expecting the downloaded bytes to be identical.
For a browser player, provide visible playback controls and let the listener start the sound. MDN documents the audio element and its controls. A preload setting is a browser hint, not a guarantee that only metadata is transferred.
5. Keep the right fixtures for the next test
Save the file together with its duration, rate, channels and expected result. The generator creates the WAV in your browser and does not need a microphone or a recording upload. Use separate synthetic speech, music or compressed files when those features are part of your product: a silent PCM WAV cannot stand in for every audio case.