Noise diary · Free

Noise Logger

Leave a phone or laptop listening overnight and wake up to a timestamped log of every loud event, a chart of the night, and a noise diary to export as CSV or PNG. Levels are relative decibels from your microphone, with an optional calibration offset, and you can add a note and a rating to each event.

Runs in your browser · No audio is recorded, stored, or uploaded
Report a problem

Noise logger workspace

Logger

Listen and log

Nothing is requested until you press Start listening.

Off. Nothing has been requested yet.

Browsers hide microphone names until you allow access. The list fills in after you start.

Screen

While logging, the page asks the browser to keep the screen awake.

Shows a black screen while logging continues, for a phone by the bed.

Settings

Levels and events

Changes apply to the whole session: events are worked out again from the stored levels.

Weighting

Counts low and very high frequencies less, as the ear does. The usual choice for noise complaints.

An event starts when it gets
Margin above background

The background is the L90 of the last 10 minutes of quiet. Events can start once 30 quiet seconds have set it.

Shortest event
Join events closer than

Leave empty for relative levels. With an offset, levels become an estimate on a reference meter's scale, labelled as calibrated by you and approximate.

Start listening to match a reference reading.

Level now
–dBA rel.

Start listening to see the level.

Average (Leq)
–
Maximum
–
Background (L90)
–
Events
0
Logged
–
Not measuring
–

Relative to the microphone's full scale (dBFS). Uncalibrated: not dB SPL.

Chart

Level over time

The line is each second's average and the band reaches its loudest 100 ms. Events are red; time not measured is hatched.

Start listening and the level is drawn here, one point per second.

  • Level (1 s)
  • Loudest 100 ms
  • Background (L90)
  • Event threshold
  • Event
  • Not measuring
Events

Loud events

Newest first. Write what you heard and rate how disturbing it was; both are saved with the session.

Events appear here as they happen, with their times and levels.

Gaps

Not measuring

Time when no sound was measured, with the reason the page observed. Nothing is filled in.

Any time the logger cannot hear is listed here with its reason.

Export

Save the noise diary

Files are made on this device and go straight to your downloads.

Exports are ready once something has been logged.

Honest limits

What the numbers mean, and what they cannot prove.

A browser hears the room through a microphone it cannot identify, so this logger is careful about what it claims. These are the limits worth knowing before you rely on a log.

Relative decibels, not dB SPL

Every level starts as dBFS, relative to the digital full scale of your input. The same room reads differently on another phone, at another input volume, or with the device moved. Compare readings within a session, and do not hold them against legal limits.

Why a browser cannot know the true level

Turning sound pressure into a number needs the microphone's sensitivity, the preamplifier's gain, and the system's input level. Browsers expose none of them, and many add voice processing, which this page asks them to switch off.

Calibration is an estimate

An offset from a reference meter puts readings on that meter's scale for one device, position, and input volume. It does not correct the microphone's frequency response, so the result stays approximate and is always labelled as calibrated by you.

Microphones miss bass and can clip

Built-in microphones fall away below about 100 Hz and can overload on very loud sounds. Seconds where the input reached full scale are marked, because their peaks read low.

Measuring needs the device awake

A phone that locks, a tab the system pauses, or a lost microphone stops measurement. Those spans are recorded as not measuring with the reason the page saw, and never filled in.

Officers use certified meters

Environmental health officers measure with calibrated Class 1 or Class 2 sound level meters to IEC 61672. This log is a diary that supports a complaint and helps you decide when to call them; it does not replace their measurement.

Measured on this device, recorded nowhere

No audio is recorded, stored, or uploaded. The page keeps only levels, your settings, and your notes, in this browser's storage, until you discard the session or start a new one. Exports go straight to your downloads.

How it works

A level every second, an event whenever it gets loud, and a gap whenever it cannot hear.

The page opens your microphone with the browser's voice processing switched off and passes the sound to an audio worklet, a small script on the browser's audio thread. For every 100 milliseconds it adds up the sound energy twice, once flat and once through an A-weighting filter, then throws the samples away. Each second's level is the energy average of its ten blocks and its maximum is the loudest block. An event starts when that maximum rises a set margin above the background or past a fixed level. Times come from your device's clock, and any stretch without sound arriving is recorded as not measuring instead of being filled in.

  1. 01

    Set up the device

    Put the phone or laptop where you hear the noise, away from your own fans, fridge, and chargers, with nothing covering the microphone. Plug it in and keep this tab open and on screen.

  2. 02

    Start listening

    Press Start listening and allow the microphone. The first 30 quiet seconds teach the logger your background level; after that, anything 10 dB louder is logged as an event. Dim the screen keeps the display awake but dark.

  3. 03

    Leave it running

    The level is stored every second for up to 24 hours. If the device sleeps, the tab is paused, or the microphone is lost, that time is marked as not measuring, and the session is saved in this browser every 30 seconds.

  4. 04

    Review, annotate, export

    In the morning, read the chart and the event list, write what you heard and rate how disturbing each event was, then download the minute log and the event list as CSV and the noise diary as a PNG.

Built for a noise diary

The record a complaint asks for, with its limits written on it.

Events with times and levels

Each event has a start, an end, a duration, its peak and average level, and how far it rose above the background. Loud moments a few seconds apart merge into one event, and you set the margin, the minimum duration, and the merge window.

A-weighted, like noise rules

Noise guidance usually quotes A-weighted levels (dBA), which count low rumble less, the way the ear does. Switch to unweighted to see bass and hum at full weight. Both are stored every second, so you can switch after the night.

Honest gaps

A sleeping device, a paused tab, a muted or unplugged microphone, and a stop all show as labelled not-measuring spans in the chart, the lists, and the CSV. Nothing is interpolated across them.

Relative dB, or your own calibration

Levels are relative to the microphone's full scale. If you have a sound level meter or a meter app, read it beside the logger once and the offset turns every reading into an estimate on that meter's scale, labelled as calibrated by you.

Notes and ratings

Write what you heard (music, voices, a door, a dog) and rate each event from 1 to 5, as council noise diaries ask. Notes are saved with the session and appear in the CSV, the diary image, and the summary.

Files you can hand over

A per-minute CSV with local time and UTC offset, an event CSV with your notes, a PNG diary with the chart, the session details, and the event table, and a plain-text summary to paste into an email.

Noise logging questions

Decibels, calibration, overnight setup, and what a log can show.

Is this a sound level meter? Why are the readings negative?+

No. Readings are decibels relative to the microphone's digital full scale (dBFS): 0 is the loudest the input can carry, so real sounds read below zero, often around -60 in a quiet bedroom on a phone. A sound level meter reports dB SPL, the sound pressure in the room, and converting needs the microphone's sensitivity, the device's gain, and the system's input volume, none of which a browser can read. Within one session on one device the relative numbers still compare fairly: a 10 dB rise is a 10 dB rise.

How does the calibration offset work, and how accurate is it?+

While the logger runs, hold a sound level meter or a meter app beside the microphone, type its reading into Reference reading, and press Match now. The page sets the offset that makes its last 10 seconds match, and from then on every level is shown as an estimate on that meter's scale, labelled as calibrated by you. It is only as good as the reference, and it holds for one device, one position, and one input volume. Phone microphones are not flat across frequency, so a calibration made on one kind of sound can be several decibels off on another, especially bass. You can also type a known offset directly.

What do dBA, Leq, L90, and peak mean here?+

dBA means A-weighted: low and very high frequencies count less, roughly as the ear hears at moderate levels. Leq is the energy average over a period, so a short loud bang raises it far more than an ordinary average would. L90 is the level exceeded 90% of the time, the usual measure of background. Peak here is the loudest 100 milliseconds, close to a sound level meter's Fast maximum, and different from the instantaneous sample peak.

How should I set up a phone or laptop for an overnight log?+

Plug it in. Put it in the room where the noise bothers you, at about head height, away from walls you do not share and from your own fans, fridge, and chargers, with the microphone uncovered. Close other apps that use the microphone and turn on Do Not Disturb. Keep this tab open and in front: the page asks the browser to keep the screen awake, and Dim the screen turns it dark while it stays on. If the wake lock is not supported, set the display to never sleep for the night, and do not close a laptop's lid.

What stops a session, and what happens then?+

Locking the phone, switching to another app or tab on a phone, closing a laptop lid, a phone call, the system muting the microphone, or unplugging it. Desktop browsers usually keep measuring in a background tab; phones usually do not. Whatever the cause, time without sound arriving is recorded as a not-measuring span with the most likely reason. If the microphone is lost, logging stops and can be resumed, and the time in between is marked. A session covers at most 24 hours from its start.

Will this log count as evidence for a noise complaint?+

It can support a complaint, but it is not a certified measurement. Councils and landlords usually ask for a diary of dates, times, durations, what the noise was, and how it affected you, which is what this produces. Where a statutory nuisance or a noise limit has to be proven, environmental health officers take their own measurements with calibrated Class 1 or Class 2 sound level meters. Present these numbers as relative readings from a phone or laptop, and let the times, durations, and your notes carry the weight.

How are events detected?+

Every second, the loudest 100 milliseconds is compared with a threshold. By default that is 10 dB above the background, the L90 of the last 600 quiet seconds, learned over the first 30 quiet seconds; a fixed level is the other option. Loud seconds up to 10 seconds apart join into one event. You can change the margin, the level, the minimum duration, and the merge window at any time, and the whole session's events are worked out again. If the background itself changes for good, such as heating or rain starting, switch to a fixed level.

Does anything get recorded or uploaded?+

No audio is recorded, stored, or uploaded. The audio worklet folds each 100 milliseconds of sound into a few numbers and discards the samples. The per-second levels, your settings, and your notes are saved in this browser's local storage (about 0.8 MB for a full 24 hours) so that a reload does not lose the night, and nothing is sent to a server. Discard the saved session or start a new one to delete them. Files exist only when you export them.

Why does bass or hum read quieter in the log than it sounds?+

Phone and laptop microphones fall away steeply below about 100 Hz, and A-weighting counts low frequencies less on purpose: at 63 Hz it takes off 26 dB. A thumping bass line or a pump's hum can be very disturbing while reading only a few decibels above the background. Switch to unweighted for a fairer view of low-frequency noise, check which frequencies are present with the Online Spectrum Analyzer, and say in your notes that the noise is low-pitched.

More focused tools, ready when you are.

Explore the growing collection for calculations, documents, writing, and everyday work.

Browse all tools