Tone Generator
Play a sine, square, sawtooth or triangle tone at 20–20000 Hz and render the same oscillator graph to a 16-bit WAV in this tab.
What this page makes
One oscillator at a frequency, wave type and level you choose, played live and rendered offline through the same graph.
How to use it
Choose a wave type, set the frequency, the level in dBFS and the render length, then press Play. Press Stop to end it early. Download WAV renders the same settings through the offline graph and saves the result.
Worked example: sine at 440 Hz, −12 dBFS, 2 seconds becomes a 2.000 s mono WAV at 44.1 kHz whose peak sample is 0.251, the gain of −12 dBFS.
Method
Playback is one OscillatorNode through one GainNode to the audio destination; the WAV download runs the same oscillator and gain through an OfflineAudioContext and encodes the samples as 16-bit PCM. The graph is built only after your press, because a browser keeps audio suspended until a gesture.
What it refuses
A frequency below 20 Hz or above 20000 Hz is refused with the band named, and a level outside 0 to −60 dBFS or a render longer than 30 seconds is refused rather than clamped.
Where it runs
The tone is generated in this tab: there is no audio file, no network request and no stored setting, and nothing you type leaves your device. The browser requirement is stated on the page: Playback needs the Web Audio API (AudioContext); the WAV render needs OfflineAudioContext. A browser without either names the missing feature.
The rest of the family
The other audio and recurrence pages are listed under Calculators: tone and binaural generation, the virtual piano, pitch shifting, looping and reversal, the stated noise filter chain, mid/side cancellation, microphone recording and the closed-form recurrence solver.
One oscillator at a frequency, wave type and level you choose, played live and rendered offline through the same graph.
Playback is one OscillatorNode through one GainNode to the audio destination; the WAV download runs the same oscillator and gain through an OfflineAudioContext and encodes the samples as 16-bit PCM. The graph is built only after your press, because a browser keeps audio suspended until a gesture. The tone is generated in this tab: there is no audio file, no network request and no stored setting, and nothing you type leaves your device.
Worked example: sine at 440 Hz, −12 dBFS, 2 seconds becomes a 2.000 s mono WAV at 44.1 kHz whose peak sample is 0.251, the gain of −12 dBFS.
The WAV render is the same oscillator and gain as live playback, written to samples instead of to a device.
How to use the tone generator
Choose a wave type, set the frequency, the level in dBFS and the render length, then press Play. Press Stop to end it early. Download WAV renders the same settings through the offline graph and saves the result.
The tone is generated in this tab: there is no audio file, no network request and no stored setting, and nothing you type leaves your device.
- Domain: 20–20000 Hz, four wave types, one oscillator at a time, renders of 0.1–30 s.
What the page proves
One oscillator at a frequency, wave type and level you choose, played live and rendered offline through the same graph.
Playback is one OscillatorNode through one GainNode to the audio destination; the WAV download runs the same oscillator and gain through an OfflineAudioContext and encodes the samples as 16-bit PCM. The graph is built only after your press, because a browser keeps audio suspended until a gesture.
- Browser requirement: Playback needs the Web Audio API (AudioContext); the WAV render needs OfflineAudioContext. A browser without either names the missing feature.
- The page states its domain: 20–20000 Hz, four wave types, one oscillator at a time, renders of 0.1–30 s.
What it refuses, and what it leaves out
A frequency below 20 Hz or above 20000 Hz is refused with the band named, and a level outside 0 to −60 dBFS or a render longer than 30 seconds is refused rather than clamped.
- Not the right page for: audiometry, which needs a calibrated output chain
- Not the right page for: measuring a speaker's response
- Not the right page for: a hearing test you would act on medically
- Reported as a named state: no sound means the page has not been touched yet, because browsers block audio before a gesture
- Reported as a named state: 0 dBFS is refused rather than clipped, so the level must stay below it
- Reported as a named state: a frequency outside 20–20000 Hz is a refusal, not a clamp
What to Expect
Best for
- a reference tone for tuning by ear
- a left and right headphone check
- a short level test before a recording
Not ideal for
- audiometry, which needs a calibrated output chain
- measuring a speaker's response
- a hearing test you would act on medically
What this tool keeps
- the exact frequency, wave type, level and render length
What may need cleanup
- turn the system volume down before pressing Play
- keep the render short, because a sustained tone is fatiguing
Common errors
- no sound means the page has not been touched yet, because browsers block audio before a gesture
- 0 dBFS is refused rather than clipped, so the level must stay below it
- a frequency outside 20–20000 Hz is a refusal, not a clamp
Example use cases
- tune a guitar string against a reference
- check that both headphone channels work
- render a short reference tone as WAV
Sample input
sine at 440 Hz, −12 dBFS, 2 seconds
Sample output
a 2.000 s mono WAV at 44.1 kHz whose peak sample is 0.251, the gain of −12 dBFS
Who this is for
- musicians tuning by ear
- audio learners checking a level
- developers testing a playback chain
Frequently asked questions
Is my data sent anywhere?
The tone is generated in this tab: there is no audio file, no network request and no stored setting, and nothing you type leaves your device.
Which browser API does this page need?
Playback needs the Web Audio API (AudioContext); the WAV render needs OfflineAudioContext. A browser without either names the missing feature.
What can I download?
Download WAV writes the same oscillator and gain as 16-bit PCM at 44.1 kHz.
Is the tone loud?
The level is digital dBFS, not sound pressure. −12 dBFS is about a quarter of the largest sample a file can hold; what reaches your ears depends on the system volume and the headphones.
Why does nothing play when I press Play?
The click is the gesture that creates the AudioContext. If the browser still blocks it, the page shows the refusal; a muted tab or a muted system output produces the same silence and the page cannot see either.
Is the WAV the same as what I heard?
It is the same oscillator and gain, rendered at 44.1 kHz instead of the device's rate. It is the graph you configured, not a recording of your speakers.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.