Case study · Website and product design
A Chrome extension that measures loudness in any browser tab, sold on a page as precise as the tool itself.
No explainer needed.
Built for audio engineers who already know what LUFS means. So the page skips the explainer and goes straight to a live meter with real numbers.
The brief, in short
The look
LiveLUFS is aimed at audio engineers who already know what LUFS and true peak mean, so the page doesn’t waste time explaining the category — it goes straight to a live-looking meter panel with real numbers (integrated, momentary, true peak, correlation) right in the hero.
Everything below reinforces the same technical confidence: a reference-target table for every major platform, a plain-language glossary for the handful of terms that do need explaining, and a closing note on local-only processing for anyone wondering where their audio goes.
The palette
A closer look
The live meter, on every screen.
Three choices that carry the whole page
A working-looking meter panel sits in the hero itself, numbers and a rolling trace included — a screenshot of the real thing beats another paragraph explaining what it does.
A built-in table mapping platforms — Spotify, Apple Music, broadcast — to their loudness targets turns a raw meter into a decision-support tool at a glance.
“Your audio never leaves your browser” gets its own short, unhedged section near the bottom — exactly the one sentence a skeptical engineer needs before installing an extension that reads tab audio.
The process behind the page, start to finish
LiveLUFS brought us on to give a Chrome extension a landing page as precise as the tool itself.
A handful of calls to understand which readings — integrated, momentary, true peak, correlation — actually mattered to engineers at a glance.
The live-looking meter panel and cyan-on-charcoal register came out of this stage — a developer tool that looks like one.
The meter, the targets and the glossary, one connected page instead of a feature list bolted onto a Chrome Web Store listing.
Low-fidelity layouts to test the pacing — meter, reference targets, privacy note — before the final visual language was applied.
A live-looking meter in the hero and a plain, unhedged privacy note — exactly what a skeptical engineer needs before installing it.
Pick your favorite agent — we'll open it with a question about what we do, who we're a good fit for, and how pricing works.
