White noise is a random signal with a nominally flat power spectral density across the frequencies your system can represent, meaning every frequency band carries roughly the same average power. Logic Pro producers search for it because a clean white-noise source helps with masking takes, calibrating monitor levels, testing plugin chains for noise floor, and seeding sound-design patches that need a neutral broadband stimulus. The White Noise Generator plays a bounded random signal directly in your browser, with an instant Stop and a 0–100 percent slider, so you have a controllable reference signal available even when your DAW session is closed. From there, you can audition the sound, route system audio into Logic Pro through a virtual device on macOS, or use the browser session as a quick audible reference while you build a native noise source inside Logic itself. This article walks through what the tool produces, how to operate it safely, and how to bring its output into a Logic Pro session.
What White Noise Actually Is
A white-noise signal has samples that are uncorrelated with each other in time, so its expected power spectral density is flat across the band you measure. The MathWorks Simulink documentation for band-limited white noise defines it that way, and National Instruments describes wide-band noise as flat in the frequency domain for the same reason. In practice, no real digital source is infinite-bandwidth; the audio system cuts off where your sample rate stops being able to represent a frequency, so the result is always a band-limited approximation rather than an ideal mathematical white noise.
The browser tool produces a band-limited digital approximation of white noise. It loops a two-second mono AudioBuffer of independent-looking samples uniformly distributed from -1 inclusive to 1 exclusive, then routes that buffer through a single GainNode. Uniform bounded white noise has a flat PSD just like Gaussian white noise; the two differ in amplitude distribution but match in spectral flatness because both keep samples uncorrelated. The recurrence that fills the buffer is xorshift32 as described by George Marsaglia, and each fresh Start requests a new 32-bit seed so consecutive sessions sound different.
For a Logic Pro user, the practical takeaway is that any broadband signal you route into a session can act as white noise for masking, calibration, or sound design, as long as the spectrum stays roughly flat and you control the gain deliberately. That is the standard a producer should hold any noise source to, browser-based or otherwise.
Use the White Noise Generator Tool
This is the practical workflow for operating the browser tool. It mirrors the verified operating steps and keeps loudness conservative by default.
- Set your device output low, then leave the tool at its conservative 15 percent starting volume or reduce it further. The slider controls only this page's linear GainNode; it is not a measurement of actual sound pressure at your ears.
- Select Start white noise. A fresh 32-bit seed is requested for the session, the two-second buffer is filled with new xorshift32 output mapped into the [-1, 1) range, and a single looping AudioBufferSourceNode is created through the GainNode. Playback uses the browser's native sample rate, accepted only from 8 kHz through 192 kHz.
- Adjust the 0–100 percent slider only as needed while playback is active. The slider range is inclusive on both ends, and 100 percent is not endorsed as a safe listening level. Start is guarded while playback is starting or active, so repeated clicks cannot layer overlapping players.
- Select Stop before leaving the page or whenever the sound feels uncomfortable. Stop disconnects the source, disconnects gain, and closes the AudioContext, so navigation never leaves a live audio graph behind. The same cleanup runs if startup fails or the component unmounts.
The fixed two-second duration caps allocation at 384,000 float samples, or about 1.5 MiB of sample storage at the maximum accepted rate. That explicit budget prevents an unusual AudioContext configuration from requesting an unbounded buffer, and the buffer simply loops until you press Stop. The W3C Web Audio API specification describes how AudioBufferSourceNode, GainNode, and AudioContext interact, which is the foundation the tool builds on.
Route the Browser Signal into Logic Pro
To capture the browser signal inside a Logic Pro project, you need a path from system audio into the DAW. On macOS, virtual audio devices such as BlackHole, Loopback, or the built-in aggregate device in Audio MIDI Setup can route browser playback into a Logic Pro audio track as an input. Create an aggregate device that combines your interface and the virtual device, set it as the input in Logic Pro, and arm a track to record from the virtual channel while the tool plays.
If you do not want to install a virtual device, macOS lets you capture the browser tab with QuickTime Player's screen-and-audio recording and drop the resulting file into a Logic Pro track as a region. On Windows, VoiceMeeter or any ASIO loopback driver achieves the same result: route the browser output back into a Logic Pro input channel and arm the track to record.
Within Logic Pro itself, you can also use the browser tool as an audible reference while you build a native noise source. Compare the character of the browser signal with the noise generator built into the Test Oscillator plugin or the noise output on instruments such as the ES2, and choose whether to route the browser signal in or to recreate the sound natively with more control. The same reference approach helps when you pair broadband noise with other Logic Pro tasks like pitch-based sound design; a related walkthrough on changing audio pitch in Logic Pro without Flex Pitch covers a complementary workflow.
For a quick browser-only audition that does not require Logic Pro at all, the standalone guide on how to generate white noise in your browser covers the same tool from a more general angle.
Loudness, Safety, and Listening Comfort
White noise is often used for extended listening, but loudness is the limiting factor. The browser tool starts at 15 percent tool gain as a conservative default, and you can lower it further before pressing Start. That 15 percent is not a safety guarantee; your operating system, browser, speakers, headphones, amplifier, and listening environment all contribute to actual sound pressure at your ears.
A low percentage on the slider is not a measurement or safety guarantee, and 100 percent is not endorsed as safe. Begin low, lower the output, or stop playback if the sound feels uncomfortable, and follow the guidance supplied with your audio equipment. The Stop button closes the AudioContext immediately, so you can end the signal at any moment without navigating away from the tab first. Starting playback creates one AudioContext, one looping AudioBufferSourceNode, and one GainNode, and Stop, startup failure, and unmount all close that graph cleanly.
If you intend to record the signal into Logic Pro for later listening, capture at a moderate gain and raise the level inside Logic Pro using the channel strip. That gives you more control over the final mix and protects against clipping during capture, because the captured region still carries the full 24-bit headroom Logic Pro offers even when the source level feels quiet at the speakers.
Browser Source vs. Logic-Native Noise
Both options are valid in different scenarios. The table below compares how each fits into a Logic Pro workflow.
| Scenario | Browser White Noise Generator | Logic Pro internal source |
|---|---|---|
| Audition the sound before opening a project | Yes, no DAW session required | Requires a project and a track |
| Capture into a Logic Pro session | Needs virtual audio routing or screen recording | Native, no routing required |
| Latency behavior | Subject to system audio path | Sample-accurate inside the DAW |
| Persistent signal across sessions | Stops when you close the tab or hit Stop | Stays in the project until you mute it |
| Customization (filtering, modulation, automation) | Only the gain slider | Full access to EQ, plugins, and automation |
| Microphone use | None, the tool does not access a microphone | None, generator is internal |
Use the browser tool for quick auditions, calibration references, and short captures; reach for a Logic-native noise source when you need automation, sample-accurate timing, or full plugin-chain processing inside a project. Both approaches give you a flat-PSD stimulus, and both stay under your direct control rather than depending on third-party recordings.
When the Browser Approach Is Enough
If your goal is to verify that a Logic Pro monitor chain is clean, to mask background noise during a vocal comp, or to test a plugin for self-noise, the browser tool covers the job without opening a project at all. Press Start, set your interface output to a comfortable level, and let the signal run for as long as the test requires. Press Stop when you are done, and the AudioContext closes so no signal survives the tab.
For longer captures or sound-design sessions where the noise needs to be filtered, modulated, or synced to a tempo, build the source inside Logic Pro instead. The browser signal is most useful as a reference and a quick capture, while native Logic Pro noise generators give you the routing depth a finished track usually demands. The two approaches complement each other, and the choice depends on how deep into the project you need the signal to travel.