demo · v151

Use Case Picker

Six real-world WebAudio scenarios. Pick the one closest to what you're building and see the recommended renderSizeHint, the code snippet, and the latency / CPU / glitch trade-offs to expect.

Decision aid. The recommendations are derived from the Web Audio WG explainer and the Chromium origin-trial wrap-up. Real apps should benchmark on representative hardware (see the Latency Benchmark and Glitch Stress Test).

pick a scenario

Game / VR

Tight reaction loop, hundreds of simultaneous voices, can't tolerate audible latency.

low latency · high CPU

Voice chat

Bi-directional voice with echo cancellation. Latency matters more than throughput.

interactive

DAW / music app

Heavy DSP chains, plug-ins, look-ahead processing. Throughput beats latency.

CPU intensive

Audio player

Plain playback of pre-rendered audio. Tolerant of latency, sensitive to power.

battery-aware

Podcast recorder

Long-running capture, EQ + compressor, render-to-file. Hardware alignment helps stability.

long session

OfflineAudioContext render

Bouncing a mix to a buffer for download. No real-time constraint at all.

render-to-buffer

recommendation

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗