AudioIntermediate

Reverb Zones

The same footstep sounds dry in a field and blooms into echoes in a cave — reverb tells the player what space they're standing in.

audioreverbspaceambience

Examples

Captured from this page's own interactive demo below.

Overview

Close your eyes in a cathedral and you still know you're in a cathedral. Reverb is how ears see architecture, and games get that channel almost for free: the same footstep, sword clink or voice line, sent through a room-shaped tail, instantly relocates the player from an open field to a stone corridor. It's world-building that costs no art budget.

The craft is in the transitions. Spaces overlap, so snap-switching the reverb at a doorway is as jarring as a texture pop — blend the wet mix over half a second as the player crosses the threshold. Unity ships this as AudioReverbZone with distance-based blending; a more controllable pattern is routing sounds through mixer groups and crossfading snapshots ('field', 'cave', 'boss arena') as zones trigger.

On mobile, budget matters: a real convolution reverb per sound is expensive, so run ONE shared reverb bus, send each sound to it at a per-zone level, and keep the dry path untouched. That's also the honest mix — sources keep their punch, the space only adds its tail. And leave UI sounds out of the bus entirely: menus don't live in the cave.

Interactive Demo

the same footstep: dry in the field, echoing in the cave · sound onfieldcave

Wet Mix60%

Decay700ms

Use Cases

Caves, temples and interiors vs. open fieldsFootsteps and combat sounds that follow the locationBoss arenas that sound bigger than normal roomsHorror spaces where the tail carries the dread

Best Practices

Do

✓Route everything through one shared reverb bus with per-zone send levels — cheap, consistent, and easy to mix.
✓Blend the wet mix over ~0.5 s at zone borders; rooms overlap, and ears notice hard cuts.
✓Keep the dry signal untouched — reverb adds a tail, it should never blur the transient that carries the impact.

Don't

✕Don't put UI and menu sounds through the room reverb — the pause menu doesn't live in the cave.
✕Don't run one convolution reverb per sound on mobile; one bus is the whole budget.
✕Don't max the decay for 'epic' feel everywhere — when every room is a cathedral, no room is.

Common Mistakes

⚠Reverb baked into the sample itself, so the footstep carries the cave with it into the field.
⚠The zone switches exactly at the door collider with no blend, popping the acoustics like a bad texture stream.
⚠Music routed through the zone reverb, turning the soundtrack to mud the moment the player steps inside.

Implementation

Paste this into your AI assistant (Cursor, Copilot, Claude) to add the effect to your project.

Prompt

Add the "Reverb Zones" game-feel effect to my project: The same footstep sounds dry in a field and blooms into echoes in a cave — reverb tells the player what space they're standing in.

How it works: Close your eyes in a cathedral and you still know you're in a cathedral. Reverb is how ears see architecture, and games get that channel almost for free: the same footstep, sword clink or voice line, sent through a room-shaped tail, instantly relocates the player from an open field to a stone corridor. It's world-building that costs no art budget.

Guidelines:
- Route everything through one shared reverb bus with per-zone send levels — cheap, consistent, and easy to mix.
- Blend the wet mix over ~0.5 s at zone borders; rooms overlap, and ears notice hard cuts.
- Keep the dry signal untouched — reverb adds a tail, it should never blur the transient that carries the impact.

Avoid:
- Don't put UI and menu sounds through the room reverb — the pause menu doesn't live in the cave.
- Don't run one convolution reverb per sound on mobile; one bus is the whole budget.
- Don't max the decay for 'epic' feel everywhere — when every room is a cathedral, no room is.

Implement the effect in whatever engine/stack the project already uses and follow its existing code style. Wire it up where it makes sense.