How to use an online tone generator safely for an audio check
Start with your device volume low, choose a sine wave, keep the tone short, and test one question at a time. A browser tone generator can provide a repeatable digital frequency and channel reference. It cannot tell you the physical sound level at your ears, certify a speaker, or test your hearing.
Decide what you need the tone to answer
Open the WaveLocus tone generator only after naming one practical job. You might need to confirm that an output carries sound, reproduce a rattle near a known frequency, check whether a selected channel reaches the expected side, or provide a stable reference while changing one part of an audio path. A tone is less useful when the question is broad, such as whether a system “sounds good.”
A browser creates the digital signal and sends it into the current output path. The Web Audio specification describes an AudioContext whose destination is routed to a real-time output device. After that point, the operating system, interface, amplifier, processing, speakers or headphones, and physical volume control affect what reaches you. The browser does not know the final acoustic level.
Choose the settings by job
Start with a sine wave because it gives you one fundamental frequency without the strong harmonic pattern of square or sawtooth waves. Other waveforms are useful when their harmonic content is part of the experiment, but they are a poor default for isolating one frequency. MDN defines an OscillatorNode as a periodic waveform source and documents sine, square, sawtooth, triangle, and custom waveforms.
Understand frequency before changing it
Frequency is measured in hertz. A 440 Hz setting tells the browser's oscillator which digital frequency to create. It does not guarantee that a small speaker reproduces that tone cleanly or that a microphone will report exactly the same number after sound travels through a room.
Begin with a comfortable mid-frequency reference for a simple playback check. Very low tones can be difficult for small speakers to reproduce, while very high tones may be weak in the playback path or difficult for a listener to hear. Do not compensate by raising the volume. If a frequency seems absent, the result may involve the output device, processing, room, background noise, fit, or hearing. It does not establish a hearing threshold.
Set route, duration, and digital level
- Lower the hardware or system volume. Do this before pressing Play, especially with headphones or an unfamiliar output.
- Choose a short duration. One or three seconds is normally enough to confirm playback. A longer continuous tone adds exposure without automatically adding evidence.
- Leave the software level conservative. WaveLocus starts at -24 dBFS and prevents settings above -6 dBFS. These are digital full-scale values, not acoustic dB SPL.
- Select the route deliberately. Use both channels for a basic path check. Use left or right only when channel routing is the question.
- Press Stop if anything is uncomfortable. Do not continue through pain, pressure, ringing, severe distortion, heat, or an unusual equipment smell.
NIOSH explains that hearing risk depends on how loud a sound is, how long exposure lasts, and how often it repeats. Its noise and hearing-loss guidance recommends keeping personal-device volume low. WaveLocus cannot convert its dBFS control into the dBA or dB SPL reaching your ears because the downstream equipment and volume controls are unknown.
Run a controlled comparison
Write down the frequency, waveform, route, duration, software level, browser, selected output, connection, and physical volume position. Play the reference once and record what happened before changing anything. If you need a comparison, alter one safe variable and repeat the identical tone. For example, keep the same headphones and change only the output device, or keep the same computer and change only the endpoint.
A result that follows one path is useful evidence about that path. It is not automatic proof that one named component failed. Use guided diagnosis to preserve the observation and choose a discriminating next test. For a dedicated channel question, the structured left/right audio test is clearer than manually changing several tone settings.
Avoid common misuses
Do not sweep toward the edge of audibility while increasing volume. Do not use a tone to diagnose hearing, create a personal equalization curve from unaided listening, rate speaker frequency response, or force a woofer to reproduce very low frequencies loudly. Do not treat equal slider values on two devices as equal acoustic output. The dBFS versus dB SPL guide explains why those values describe different parts of the path.
If the problem spans a range rather than one known frequency, use the frequency sweep at low level and then confirm a narrow region with a short tone. If the task needs broadband energy, choose a suitable signal in the noise generator. The simplest signal that answers the question is usually the easiest to interpret.
Next step
Run one low-level reference and save the complete settings with your observation. If it fails, repeat it after one controlled path change in guided diagnosis. If another person or device needs the same reference, create a versioned local file with portable test packs.
Sources and method
This guide reflects the bounded WaveLocus tone controls and safety service. The Web Audio specification and MDN document browser signal generation, while NIOSH supports the low-volume and limited-exposure guidance. A browser tone is a controlled digital stimulus. It cannot measure physical SPL, acoustic frequency response, component condition, or hearing ability.