On the media item
Analyse an existing WordPress media file or a fresh upload without leaving the post you are writing.
Loudness check — runs in your browser
Is this episode loud enough to publish?
Drop the file in. It is measured right here in this tab against the target your platform expects — no upload, no account, an answer in seconds.
- Nothing leaves your browser
- No account, no queue
- EBU R128 / ITU-R BS.1770-4
Check against
Drop an episode here to measure it.
The file is read inside this browser tab. Nothing is uploaded, nothing is stored — you can watch the network tab while it runs.
WAV · MP3 · FLAC
No account. No upload. No queue.
The product
The same check, where episodes are actually published.
The check above answers one file at a time. AudioLinter runs it inside WordPress — on the media item, on the upload you just made, with a repair that writes the corrected file back.
Repair, not just report
One click renders a corrected file at -16 LUFS with true peak under -1 dBTP, then measures it again to show the result.
A deletion date you can point at
Uploads are processed on EU servers and deleted within 48 hours — the answer to the question your legal or works council will ask.
Reference
What each platform expects
Loudness targets are set by the platform, not by us. These are the numbers the check above measures against.
| Platform | Integrated loudness | True-peak ceiling |
|---|---|---|
| Apple Podcasts | -16 LUFS | -1 dBTP |
| Spotify | -14 LUFS | -1 dBTP |
| YouTube | -14 LUFS | -1 dBTP |
| EBU R128 (broadcast) | -23 LUFS | -1 dBTP |
Publish quieter than the target and normalisation raises your noise floor with the voice. Publish louder and it is turned back down anyway.
Who it is for
Teams that publish audio from WordPress
People with publishing responsibility and no audio-engineering background — the ones who have to sign off that an episode can go out.
Editorial teams
Keep quality consistent across contributors without asking every editor to think like an audio engineer.
Stations and campus radio
Catch loudness misses, clipping risk and dead air before a post goes live or gets distributed downstream.
Podcast operations
A QC layer inside the CMS, with the publishing decision left explicit and reviewable.
Straight answers
What we claim, and what we can show for it
This is a small, young product. Instead of borrowed credibility, here is what is verifiable.
- Measured, not estimated
- The plugin measures with ffmpeg's EBU R128 meter. The browser check implements the same standard and is tested against that meter to within 0.3 LU.
- Processing in the EU, deleted in 48 hours
- Files sent to the plugin are processed on EU servers and removed within 48 hours. The browser check sends nothing at all.
- A free tier that is actually usable
- The free key needs no card. The paid plan buys volume and repair, not the right to see your own numbers.
Next
Check a file first. Decide afterwards.
The check costs nothing and asks for nothing. If it finds something, the fix is a guide away — or a plugin away.