14 Free Audio Loudness and LUFS Meter Tools for Fest Trailers and Demos - 2026

Your Steam trailer autoplays at full volume. Your fest demo menu music was mastered hot in headphones. A player alt-tabs, returns, and your VO line whispers while the explosion from the last cut still rings in their ears—or the opposite: everything clips and they mute the tab forever.

June 2026 store pages lean on autoplay video and short-session demos ahead of October Next Fest. Loudness is not vanity mastering—it is hour-one trust. This Listicles & Resource Roundups article curates fourteen free tools to measure LUFS, spot drift, and file loudness_receipt_v1.json before creative locks.

Not another metadata checklist—pair with trailer frame audit for picture; this list owns audio level discipline.

Time to read: ~35 minutes. Minimal stack tonight: Tools 1, 2, 6, 12 (~60 minutes).

Why this matters now (June 2026)

1. Autoplay trailers — First impression is sound + motion together; drifting LUFS feels “cheap.”
2. Short demo sessions — Menu music sets gain expectations for gameplay SFX.
3. VO + AI dialogue — Voice tool stacks need shared targets.
4. Refund language — “Too loud / can’t hear dialogue” shows in refund dashboards beside gameplay bugs.
5. May–September is fix month — October is typo-only for audio unless scope changes.

Direct answer: Target −16 to −14 LUFS integrated for trailer stereo (platform-dependent; document your choice), −23 LUFS for dialogue-forward VO stems when mixing like broadcast, and never ship a trailer 6 dB hotter than in-game menu without intent.

Who this is for

Beginner path (first hour)

1. Export trailer WAV from your editor.
2. Open Tool 1 (Youlean)—read integrated LUFS.
3. Open Tool 2 (Audacity)—normalize if needed; re-measure.
4. Log result in loudness_receipt_v1.json.
5. Play in-game menu at same system volume—does it feel matched?

Developer path (fest prep)

1. Define LOUDNESS_TARGETS.md (−16 trailer, −20 menu, −14 max SFX peak).
2. Tool 6 ffmpeg batch on CI render farm outputs.
3. Tool 4 Fairlight for final trailer pass.
4. Attach receipt to BUILD_RECEIPT.
5. Block fest marketing cap spend if trailer receipt fails.

LUFS targets (honest, not legal advice)

Platforms evolve—write chosen numbers into receipt notes.

loudness_receipt_v1.json

{
  "schema": "loudness_receipt_v1",
  "build_label": "trailer-nextfest-2026-06-rc1",
  "assets": [
    {
      "file": "store/trailer_main_v3.wav",
      "tool": "Youlean",
      "integrated_lufs": -15.8,
      "true_peak_dbtp": -1.2,
      "pass": true
    },
    {
      "file": "game/menu_loop_v2.ogg",
      "tool": "Audacity loudness",
      "integrated_lufs": -19.4,
      "pass": true
    }
  ],
  "promotion_allowed": true,
  "paired_trailer_audit": "release-evidence/03-store/trailer-frame-audit-v3.md"
}

Selection criteria

Each tool is free for the described workflow, produces a number you can log, and fits capture → measure → fix → re-measure.

Stereo vs mono traps (fest trailers)

Log mono_downmix_lufs in receipt optional row when targeting mobile-first discovery.

Compressor order (beginner)

1. High-pass rumble on VO (80–100 Hz)
2. Gentle compressor (2:1, slow attack)
3. Loudness normalization to target
4. True peak limiter at −1 dBTP

Skipping step 1 makes meters chase sub-bass that cheap speakers never reproduce—wasted headroom.

Evidence folder layout

release-evidence/03-store/audio/
  LOUDNESS_TARGETS.md
  loudness_receipt_v1.json
  youlean-screenshots/
  ffmpeg-logs/
  trailer_master_v3.wav

Pair with release-evidence taxonomy so partners find audio beside trailer hashes.

A/B listening protocol (beginner-friendly)

Subjective listening after meters prevents “correct numbers, wrong feel.”

The 14 tools

Tool 1 — Youlean Loudness Meter 2 (free plugin)

Industry-standard LUFS visualization as VST/AU. Drop on trailer master in any DAW or load WAV in standalone mode.

Beginner: Install once; drag WAV; screenshot integrated LUFS for evidence folder.
Dev: Use short-term vs integrated to catch explosive stingers.
Mistake: Measuring only peak meters—peaks lie.
Link: Youlean

Workflow detail: Export trailer as 48 kHz 24-bit WAV before measurement. MP3 previews hide true peaks. Screenshot the meter with date and build_label in filename (youlean-trailer-v3-2026-06-02.png). Store under release-evidence/03-store/audio/youlean-screenshots/. When integrated reads −13.5 LUFS but short-term hits −10, add 200 ms fade on stinger SFX—numbers plus ears.

Tool 2 — Audacity (free DAW)

Built-in Loudness Normalization effect (LUFS-based) for quick fixes on VO and temp trailers.

Beginner: Effect → Loudness Normalization → set target −16 → export.
Dev: Batch macro on playtest-capture/ folders.
Pairs with: AI voice listicle loudness step.

Workflow detail: For dialogue batches, normalize each line to −23 LUFS individually, then mix music underneath at −18 or lower. Beginners: use Effect → Compressor lightly before loudness norm. Save Audacity projects beside WAV exports so trailer re-cuts get new receipt rows—not guesswork.

Tool 3 — ffmpeg loudnorm / ebur128 (free CLI)

Scriptable measurement and normalization in CI.

ffmpeg -i trailer.wav -af loudnorm=I=-16:TP=-1.5:LRA=11:print_format=summary -f null -

Dev: Fail build if printed Input Integrated outside band.
Beginner: Copy command from your receipt README—no need to master ffmpeg flags solo.

Link: ffmpeg loudnorm docs

Workflow detail: Wrap measurement in scripts/measure_lufs.sh that exits non-zero when integrated LUFS outside band—same spirit as validate-packet. Log stdout to ffmpeg-logs/trailer-v3.txt. Two-pass loudnorm (measure, then apply) beats one-pass when LRA swings wildly between quiet dialogue and loud stinger.

Tool 4 — DaVinci Resolve Fairlight (free license)

Fairlight loudness meter on timeline for trailer cuts; professional trim + fade.

Use when: You already cut trailers in Resolve.
Pro tip: Same project houses caption safe zones if you burn subs.

Workflow detail: Fairlight Effects Library → Loudness Meter on mix bus. Freeze timeline before export; note LUFS in delivery sheet for composer. When re-cutting trailer scope, re-open same Resolve project—do not rebuild audio chain from scratch without re-metering.

Tool 5 — OBS Studio + meter plugin (free)

Capture gameplay for trailer b-roll; monitor live input with VST meter on monitoring bus.

Beginner: Record 60s golden path; measure exported WAV in Tool 1.
Pairs with: 18 playtest tools OBS row.

Workflow detail: Record golden path audio as separate take for trailer honesty—do not fake gameplay with cinematic-only camera if store page implies in-engine capture. Measure OBS-exported WAV in Tool 1. Disable OBS “boost quiet audio” filters unless documented—they lie to meters.

Tool 6 — Loudness Penalty (free web analyzer)

Upload compressed trailer MP4/WAV—see how streaming platforms may reduce your loudness.

Use when: Final export before Steam upload.
Caution: Web upload = know your NDA policy; use offline tools for secret trailers.

Workflow detail: Run after local Tool 1 pass—compare predictions vs your chosen target. If platform penalty suggests heavy turn-down, consider bringing master down 1–2 dB before upload so autoplay does not feel whisper-quiet after normalization.

Tool 7 — TDR VOS SlickM (free meter)

Tokyo Dawn visual loudness meter—lightweight alternative when Youlean unavailable.

Dev: Good for second opinion on integrated LUFS.

Tool 8 — Orban Loudness Meter (free legacy)

Older but still useful broadcast-style meter for teams thinking in LKFS.

Use when: Composer delivers broadcast specs.

Tool 9 — VLC + ffmpeg extract (free combo)

Extract audio from trailer MP4 for measurement when only video export exists.

ffmpeg -i trailer.mp4 -vn -acodec pcm_s16le trailer_audio.wav

Then Tool 1 on trailer_audio.wav.

Tool 10 — REAPER (evaluation, generous)

Full DAW with JS: Loudness Meter scripts—indie staple for SFX pass.

Honest limit: Not unlimited commercial-free forever—read license; evaluation suffices for fest month.

Tool 11 — Godot Audio bus + export WAV (free engine)

Route music/SFX to buses; record Viewport or export stem WAV for external LUFS read.

Beginner: Solo dev on Godot—measure menu scene export nightly.
Pairs with: Defold audit for cross-engine habits.

Tool 12 — Unity Audio Mixer + recorded clip (free engine)

Capture mixer output to WAV; measure in Youlean.

Dev: Document mixer snapshot in BUILD_RECEIPT notes.

Tool 13 — FMOD Studio meter (free indie license tier)

If using FMOD, master bus peak + loudness meters before bank build.

Use when: Adaptive music fest demo—levels shift with stems.

Tool 14 — Spreadsheet loudness log (free ops)

Not a meter—a discipline tool. Columns: asset, tool, LUFS, dBTp, build_label, pass.

Template row weekly beside Wednesday metadata diff—audio is metadata for ears.

Tool 8–14 — expanded workflow notes

Tool 8 (Orban): Useful when contractors deliver EBU R128 paperwork—translate their PDF into your LOUDNESS_TARGETS.md so indie leads speak one language.

Tool 9 (VLC + ffmpeg): Mandatory when marketing only has trailer_final.mp4 from agency—extract audio before you reject trailer for “no WAV.”

Tool 10 (REAPER): Indie teams already in REAPER for SFX: master chain with Tool 7 + 1 double-check; render stems (music, sfx, vo) for receipt rows per stem.

Tool 11 (Godot): AudioServer bus layout documented in export README. Capture 30s menu loop WAV each promotion week.

Tool 12 (Unity): [AudioMixer].FindMatchingGroups snapshot screenshot in evidence; offline bounce of menu bus.

Tool 13 (FMOD): Master bus meter before Build banks; adaptive music must not spike 8 dB on combat entry—log max short-term in receipt.

Tool 14 (Spreadsheet): Column delta_trailer_vs_menu_db = numeric difference between integrated LUFS rows; flag if > 3 dB without design doc.

Construct / NW.js / HTML5 note

Browser-first teams: measure desktop NW.js export menu audio, not only editor WebAudio preview. Pair Construct NW.js freeze with loudness row in Friday ops review.

Worked example (composite duo)

Lesson: Trailer was “finished art” but audio blocked fest spend until receipt existed.

CI pseudocode (Tool 3 + 14)

#!/bin/bash
LOG=$(ffmpeg -i "$1" -af loudnorm=print_format=summary -f null - 2>&1)
LUFS=$(echo "$LOG" | awk '/Input Integrated/ {print $NF}')
# compare to band in LOUDNESS_TARGETS.md

Attach log to GitHub Action artifact—partners see numbers, not vibes.

Promotion gate integration

[ ] loudness_receipt_v1.json promotion_allowed == true
[ ] trailer integrated LUFS within LOUDNESS_TARGETS.md
[ ] menu loop within band
[ ] true peak <= -1.0 dBTP on trailer
[ ] Wednesday metadata diff notes trailer hash + audio receipt

Partner and diligence crosswalk

Q3 diligence may ask about “professional audio.” Receipt + targets answer without claiming Grammy mastering.

Incident response when players complain about audio

Operating review hook

Four-Friday operating reviews Block 4: trailer LUFS trend over four weeks.

Minimal stacks

Common mistakes (seven)

1. Only peak limiting — Integrated LUFS still wrong.
2. Trailer hot, demo quiet — Feels like false advertising.
3. Different targets per VO actor — Normalize per line batch.
4. Measuring MP3 only — Measure lossless WAV; compress last.
5. Ignoring true peak — Clips on Bluetooth speakers.
6. No receipt — Cannot answer “what was loud on ship day?”
7. Fixing in October only — May–August is loudness month.

Pro tips (six)

1. Reference track at known LUFS—not copyrighted trailer; use licensed tone.
2. Same headphones for A/B trailer vs menu.
3. Document target in LOUDNESS_TARGETS.md once.
4. Re-measure after any trailer re-cut.
5. Pair with pixel font pass—players read and hear together.
6. Attach receipt to partner ZIP 03_store/.

Wednesday ritual extension (optional)

Add audio row to Wednesday metadata diff:

• Trailer hash unchanged?
• If hash changed, loudness_receipt pass attached?

Five minutes prevents “we only re-exported video.”

Non-repetition note (editorial)

Consumed Blog-Planner High #1 after Defold tutorial. No dedicated LUFS fest listicle existed; AI voice tools mentions loudness but not fourteen meter workflows.

Key takeaways

• Fourteen free tools from Youlean to spreadsheet discipline.
• Target documented LUFS per asset class—trailer vs menu vs VO.
• loudness_receipt_v1.json pairs with BUILD_RECEIPT and trailer audits.
• ffmpeg enables CI gates; Audacity helps beginners.
• Autoplay trailers need integrated LUFS, not peak-only checks.
• May–September fixes beat October emergency mastering.
• Cross-link gameplay capture with playtest and smoke rituals.
• True peak and integrated LUFS both belong in receipt rows.
• Spreadsheet Tool 14 makes audio audits searchable by build_label.
• Agency MP4 deliveries still need Tool 9 extract before sign-off.

Glossary (beginner)

True peak vs integrated (developer)

Players experience both. A trailer at −16 LUFS integrated can still clip if true peak hits +2 dBTP on laptop speakers. Gate receipt on both numbers. ffmpeg loudnorm TP=-1.5 is a sane fest default.

Music vs SFX bus discipline

Document bus gains in LOUDNESS_TARGETS.md so contractors do not “fix” trailer without touching game.

Tool 7 — TDR VOS SlickM (expanded)

Tokyo Dawn free meter plugin—alternative UI to Youlean. Beginner: If Youlean install fails on older OS, try SlickM. Dev: Run both on contested masters; if readings diverge > 0.5 LUFS, investigate stereo correlation or DC offset.

Tool 11–13 — engine capture recipes

Godot 4.x: Add AudioStreamPlayer bus Music → record via external loopback or export .ogg stems from project. Unity: Use OnAudioFilterRead only in dev builds—strip before ship; prefer offline bounce. FMOD: Solo master + export WAV after File → Build.

Ambient libraries cross-link

Layering ambient libraries under dialogue requires 6–12 dB headroom—re-measure after adding beds, not only at VO import.

Snippet-friendly answers (extra)

What LUFS for Steam Next Fest 2026?
Document −16 to −14 integrated for many indie trailers; verify with Tool 1 and log in receipt—platforms do not publish one eternal number for all games.

Free loudness meter for beginners?
Youlean + Audacity cover 90% of first-trailer passes.

How to match trailer and demo loudness?
Measure both WAVs; keep integrated within 2–3 dB unless creative intent says otherwise.

Should I normalize gameplay SFX to trailer loudness?
No—trailers are cinematic; gameplay should be slightly quieter than trailer peaks with dialogue still intelligible. Document the gap in Tool 14.

What if my demo has no dialogue?
Use −16 LUFS integrated as default; raise music beds only after Tool 6 confirms you are not clipping on mobile speakers.

Month-one adoption ladder

Week-by-week detail for producers

Week 1 is policy, not mastering: write LOUDNESS_TARGETS.md with trailer band, demo band, and true-peak ceiling. Run Tool 1 on the current trailer WAV even if you plan to re-export—baseline numbers prevent arguments in Discord.

Week 2 locks trailer v1: Tools 2 and 6 on the same file; store trailer_lufs.txt and a screenshot of the meter in evidence/loudness/trailer_v1/. Do not swap music beds after sign-off without bumping trailer_version in the receipt.

Week 3 adds menu and one combat clip rows to Tool 14. Fest demos often fail here: menu music mastered hot while VO in the first scene was normalized cold. Measure both; log delta in the spreadsheet.

Week 4 optional automation: a five-line ffmpeg script in CI that fails builds when integrated LUFS drifts more than 2 dB from signed targets—pair with Wednesday demo smoke so audio regressions block promotion like binary smoke.

FAQ

Is −14 LUFS always correct for Steam?
No—pick a band, log it, stay consistent across trailer and menu.

Do I need all fourteen tools?
No—stacks above pick three to five.

What about in-game dynamic range?
Measure menu + one combat clip; document in receipt.

Replace mastering engineer?
No—list reduces surprises; finals may still need pros.

How does this relate to voice AI tools?
Normalize AI VO into same targets before mix.

Conclusion

Players forgive indie visuals before they forgive audio lies—too loud, too quiet, or incoherent between trailer and demo.

Measure tonight. Log the receipt. Ship October with ears open.

Fest prep is a stack of small proofs: BUILD_RECEIPT for binaries, metadata diff for store copy, demo smoke for launch—and loudness receipts for what players hear in the first fifteen seconds. Missing any one layer ships a product that is true on paper and wrong in the room.

When your composer asks “how loud?”, send LOUDNESS_TARGETS.md, not a shrug. When marketing asks “can we ship the new trailer?”, send loudness_receipt_v1.json with pass rows. That is how micro-studios look professional without a mastering suite on retainer.

Next reads: Trailer frame scope audit, Fest marketing cap, BUILD_RECEIPT pipeline.