Seismic Infrasound Viewer

Explore the typical infrasound frequency bands of geophysical and atmospheric events — earthquakes, volcanoes, meteors, thunder, avalanches and the ever-present ocean microbarom peak near 0.2 Hz — against an experimental live sub-20 Hz waterfall from your microphone.

This cannot detect earthquakes, eruptions or any distant event — and consumer mics cannot capture true infrasound. Built-in laptop and phone microphones roll off steeply below ~50–100 Hz and OS high-pass/AGC kills sub-20 Hz, so the live waterfall here is a device-limited demonstration, not a measurement — what you see below 20 Hz is usually noise floor or an artifact. There is no barometer in a browser, so atmospheric-pressure correlation is conceptual only. Real global infrasound monitoring uses arrays of calibrated microbarometers (the CTBTO network is building toward 60 such stations in the 0.02–4 Hz band). The reference chart is the real takeaway. Nothing is recorded or uploaded.

Seismic Infrasound Viewer Tool

Idle — the reference chart below works without a mic. Press Start for the experimental live sub-20 Hz waterfall.

The live view is an experimental, device-limited demonstration. The frequency axis covers 0–20 Hz (infrasound). Your hardware almost certainly cannot reproduce or capture true infrasound — treat any energy shown below 20 Hz as likely noise floor, not a real geophysical signal. Auto-gain, noise suppression and echo cancellation are requested off.

Waterfall spectrogram — horizontal axis = 0–20 Hz (left = 0 Hz), top row = newest. Brightness = relative dBFS (uncalibrated). Newest columns scroll down.

Instantaneous spectrum 0–20 Hz. Dashed cyan = reference event bands; amber dot = dominant low-frequency bin. Vertical axis = relative dBFS, not calibrated pressure.

Dominant <20 Hz bin
Reference band (overlap)
Sample rate
Frequency resolution

The classifier maps the dominant sub-20 Hz bin onto the reference band(s) that contain it — it is a band-overlap label, not a claim that the event itself is present. Many sources share the same band.

Reference: typical infrasound frequency bands of geophysical events

Published-typical bands — values are approximate and overlapping. Earthquakes, eruptions and meteors are detected by instrument networks, not by this page; this table is for understanding where each source's acoustic energy sits.

Approximate frequency bands and typical peaks of natural and atmospheric infrasound sources (see Sources note below the table).
SourceTypical bandNotes
Ocean microbaroms~0.1–0.5 Hz
peak ~0.2 Hz (~5 s period)
The persistent “voice of the sea” — standing ocean waves coupling to the atmosphere. Dominates global infrasound background noise.
Volcanic infrasound~0.01–20 Hz
most energy ~0.5–20 Hz
Broadband signals from explosions, jetting and tremor; can duct thousands of km. Used for remote eruption monitoring.
EarthquakesBroadband, strong <1 Hz to tens of HzGround motion (and air-coupled infrasound) spans well below 1 Hz up into the audible range; large quakes radiate strongest at very low frequencies.
Meteors / bolidessub-1 Hz signals
processed ~0.2–3 Hz
Large fireballs generate infrasound detected globally by the IMS; analysis band-passes roughly 0.1–4 Hz.
Thunder (infrasonic part)~0.1–10 Hz
most intense ~1–3 Hz
Separate from the audible crack (which peaks near ~200 Hz). The low-frequency rumble travels farther than the bang.
Avalanches / landslides~1–8 HzSub-audible pressure fluctuations from moving mass; monitoring arrays typically band-limit to ~0.1–8.5 Hz.
CTBTO IMS network0.02–4 Hz band60 planned stations, each an array of ≥4 microbarometers (flat 0.02–4 Hz, 1–3 km aperture). Detects nuclear tests, volcanoes and meteors.

Sources: ocean microbarom peak ~0.2 Hz / ~5 s period — Microbarom (Wikipedia) and De Carlo et al. 2021 (Geophys. Res. Lett.). Volcanic ~0.01–20 Hz — USGS, “Infrasound for volcano monitoring.” Thunder audible peak ~200 Hz — Few 1967 (J. Geophys. Res.); infrasonic maxima ~1–3 Hz — Farges & Blanc 2010 (J. Geophys. Res. Space Physics). Avalanche ~1–8 Hz — infrasonic snow-avalanche monitoring literature. Meteor processing band ~0.2–3 Hz — bolide infrasound studies (IMS / CTBTO). CTBTO IMS 0.02–4 Hz, 60 stations — CTBTO.org, “Infrasound monitoring.”

How to Use This Viewer

  1. Read the reference chart first. It is the most reliable part of this tool and needs no microphone. Each row shows the approximate frequency band where a geophysical or atmospheric event radiates infrasound energy, with cited published values.
  2. (Optional) Start the live view. Press Start live view and grant microphone access. The waterfall and spectrum cover 0–20 Hz. The tool reads the real AudioContext sample rate and shows the resulting frequency resolution.
  3. Understand what you are seeing. On almost all consumer hardware, the sub-20 Hz region will show only noise floor — the low-frequency rolloff and OS high-pass remove genuine infrasound before it ever reaches the FFT. The dominant-bin readout and “band-overlap” label are for exploration, not detection.
  4. Use Freeze to inspect. Pause the scrolling waterfall to study a moment without the display moving. Press Resume to continue.
  5. Stop when finished. Pressing Stop releases the microphone immediately. Closing the tab also stops all capture — nothing is recorded or uploaded.

Understanding Your Results

The reference bands are the takeaway

Infrasound — sound below the ~20 Hz threshold of human hearing — is generated by some of the largest processes on Earth. Because the atmosphere absorbs very little energy at these frequencies, infrasound from eruptions, large meteors and explosions can travel thousands of kilometres. The reference chart shows roughly where each source's energy concentrates: the persistent ocean microbarom peak near 0.2 Hz (a ~5-second period), broadband volcanic and earthquake energy reaching well below 1 Hz, meteor signals processed in roughly the 0.2–3 Hz band, the infrasonic part of thunder peaking around 1–3 Hz, and avalanche/landslide energy near 1–8 Hz.

Why the live view almost certainly shows nothing real

The browser AudioContext samples at typically 44,100 or 48,000 Hz, so the Nyquist limit (the highest capturable frequency) is around 22,050 or 24,000 Hz — that part is fine for infrasound. The problem is the low end: built-in MEMS microphones in laptops and phones roll off steeply below roughly 50–100 Hz, and the operating system or browser typically applies a high-pass filter and automatic gain control that remove sub-20 Hz content entirely. So any energy you see in the 0–20 Hz waterfall is almost always noise floor or a digital artifact, not real infrasound. There is also no barometer in a browser, so the “atmospheric pressure correlation” that real infrasound work relies on is conceptual only here.

The classifier is a band label, not a detection

When the live view runs, the tool finds the strongest bin below 20 Hz and reports which reference band it lands in. This is a band-overlap label, not a claim that an earthquake, eruption or meteor is occurring — several sources share the same frequency range, and on consumer hardware the “dominant” bin is usually just where your device's noise floor happens to peak. Genuine detection requires calibrated microbarometers deployed in arrays, the approach used by research observatories and the CTBTO International Monitoring System (0.02–4 Hz, 60 stations).

How It Works

The live view streams audio from your microphone and runs a Fast Fourier Transform (FFT) on each short window. To get usable resolution in the infrasound band, the tool requests the largest FFT the Web Audio API allows (32,768 samples). At a 48 kHz sample rate that gives about 1.46 Hz per bin (48000 ÷ 32768) — the actual figure is read at runtime and shown under Frequency resolution. Only the bins below 20 Hz are mapped onto the 0–20 Hz display; bin 0 (the DC offset) is ignored so a constant bias in the signal is not mistaken for a 0 Hz tone.

The waterfall spectrogram stacks successive spectra as rows, newest on top, scrolling downward; brightness encodes relative level. The instantaneous spectrum below it draws the current frame with dashed cyan markers at the centre of each reference band so you can see where, say, the microbarom peak or the avalanche band would fall. The number of waterfall columns is bounded to the canvas width so the display can never grow without limit.

The microphone source is connected to an AnalyserNode only — never to the audio output — so there is no feedback path and nothing is played back. We request the raw signal with automatic gain control, noise suppression and echo cancellation off, because those features reshape the spectrum; even so, a browser or OS may apply low-frequency filtering it does not expose, which is the main reason genuine infrasound rarely survives to the FFT. All buffers are fixed-length, the analysis loop pauses when the tab is hidden, and the microphone and audio context are released the instant you press Stop or close the tab. Audio is analysed live and discarded — never recorded or transmitted.

Frequently Asked Questions

Can this tool detect earthquakes, eruptions or distant events?
No. This page cannot detect earthquakes, volcanic eruptions, meteors or any distant event. Those are detected by networks of calibrated microbarometers and seismometers arranged in arrays, such as the CTBTO International Monitoring System. The live view here only shows what your own microphone captures in real time, and consumer microphones cannot meaningfully capture infrasound at all. The reference chart of typical frequency bands is the genuinely useful part of this tool.
Why does the live view below 20 Hz look like noise?
Because it usually is. Built-in MEMS microphones roll off steeply below roughly 50–100 Hz, and the operating system or browser typically applies a high-pass filter and automatic gain control that remove sub-20 Hz content before it reaches the FFT. Any energy shown in the 0–20 Hz waterfall is therefore almost always noise floor or a digital artifact, not real infrasound. Genuine infrasound measurement needs a microbarometer or an accelerometer with extended low-frequency response.
What is the ocean microbarom at 0.2 Hz?
Microbaroms are persistent, nearly sinusoidal atmospheric infrasound waves generated when ocean surface waves travelling in nearly opposite directions interact. They have a wave period near 5 seconds, which is about 0.2 Hz, and a band of roughly 0.1–0.5 Hz. They dominate the global infrasound background noise and are sometimes called the "voice of the sea." This is far below what any consumer microphone can capture, so this tool lists it for reference only.
What frequency band does the CTBTO infrasound network use?
The CTBTO International Monitoring System operates infrasound stations sensitive across the 0.02–4 Hz band. When complete, 60 stations are distributed worldwide, each built as an array of at least four microbarometers with a flat response from 0.02 to 4 Hz spread over an aperture of roughly 1–3 km. The arrays act as acoustic antennas to detect and locate nuclear tests, large volcanic eruptions and meteor entries from thousands of kilometres away.
Can my browser measure atmospheric pressure to find infrasound?
No. A web browser has no access to a barometer, so there is no way to measure the slow pressure fluctuations that real infrasound monitoring records with microbarometers. Any reference to atmospheric-pressure correlation in infrasound science is conceptual here and cannot be performed in this tool. The live view relies only on the microphone, which is the wrong instrument for true infrasound.
How is the dominant frequency and reference band chosen?
When the live view runs, the tool finds the strongest bin below 20 Hz (ignoring the 0 Hz DC bin) and reports its frequency, then labels whichever reference band that frequency falls within. This is a band-overlap label for exploration, not a detection — several sources share the same band, and on consumer hardware the "dominant" bin is typically just where the device noise floor peaks. It is not a calibrated measurement and not a claim that any event is occurring.
Is my audio recorded or uploaded?
No. The microphone signal is analysed in real time entirely in your browser to draw the spectrum and waterfall, then discarded — nothing is recorded, saved, or transmitted. The microphone source is connected only to an analyser node, never to the speakers, and the microphone is released the moment you press Stop or close the tab.