Game Audio Glossary: 30 Terms Every Sound Designer Should Know

A sound designer and a programmer can listen to the same effect and describe different problems. One might say the transient is too soft; the other might say the event feels late. A producer may ask for more punch, while an audio programmer asks whether the sound should be spatialized or limited to a certain number of simultaneous instances. These descriptions are not interchangeable, and knowing the terms makes revisions faster.

This glossary is designed as a working reference, not a dictionary of isolated definitions. Each entry explains what the term means and where it becomes useful during game audio production. The examples focus on practical decisions: why a pickup feels weak, why repeated footsteps become tiring, why an explosion disappears on phone speakers, or why a sound continues after its gameplay event has ended.

You do not need to memorize all 30 terms at once. Start with the words that describe the problem you are solving, then return to the glossary when you edit, export, or implement the sound.

When you are shaping a sound

1. Transient

The brief, often sharp beginning of a sound, such as the initial crack of a gunshot or the click at the front of a menu sound. A strong transient helps an event read clearly; too much can make an effect harsh or cause clipping. If a hit feels dull, check the attack and transient before simply raising the entire file's volume.

2. Envelope

The way a sound's level changes over time. An envelope is commonly described through attack, decay, sustain, and release. A button click usually needs a fast onset and little tail, while a magical charge may rise gradually and hold before releasing. Envelope shape often changes the perceived character more than adding another layer.

3. Attack

The time it takes a sound to reach its initial level. A short attack makes a cue feel immediate; a slower attack can suggest a swell, charge, or distant source. For gameplay feedback, an unnecessarily slow attack may make a sound seem disconnected from the action that triggered it.

4. Decay

The drop in level after the initial attack. A short decay can make a sound compact and percussive. A longer decay leaves more audible body or tail. When a coin pickup feels too soft, a little more sustained tonal body may help; when a UI sound lingers over the next interaction, shorten the decay.

5. Sustain

The level a sound holds after its initial attack and decay while it is being sustained. Not every one-shot has an obvious sustain stage, but the concept is useful for held energy sounds, charging effects, engines, and loops. A steady sustain can make a sound feel continuous rather than like a single impact.

6. Release

The fade or falloff after a sound is released or its sustained stage ends. A release that is too short can create an abrupt cutoff; one that is too long can leave unwanted audio after a character stops an action. In a game, the release should fit both the sound's identity and the event's duration.

7. Pitch

How high or low a sound is perceived. Pitch movement can communicate direction, speed, size, or transformation. A quick upward sweep may help a reward feel bright, while a descending sweep can make a laser or falling object feel as though it is dropping. Pitch is a design choice, not a universal emotion code: context and timbre change how it reads.

8. Waveform

A representation of how a signal changes over time; in synthesis, the term often refers to a basic periodic shape such as sine, square, sawtooth, or triangle. A sine wave is relatively pure, while square and sawtooth waves usually sound richer in harmonics. For a retro effect, waveform choice is a useful starting point, but pitch, timing, and envelope matter too. See how 8-bit sound effects are designed for a focused treatment.

9. Timbre

The quality that makes two sounds seem different even when they share a similar pitch and loudness. A flute and a muted synth can play the same note but have different timbres. In game audio, timbre helps distinguish a friendly pickup from an error cue, or a wooden impact from a metallic one.

10. Harmonics

Frequency components related to a sound's fundamental frequency. Their relative strength contributes to timbre. Adding or emphasizing upper harmonics can make an effect brighter or more audible on small speakers; reducing them can make it softer or darker. More harmonics do not automatically mean a better sound—too many can make a mix crowded.

When you are recording, editing, or combining layers

11. Noise

A signal with energy spread across a range of frequencies rather than one clear pitched tone. White noise has roughly equal power per unit of frequency across its defined range; other noise types have different spectral balances. Noise is useful for air movement, bursts, friction, impacts, and explosions. Shape it with filtering and a short envelope so it behaves like an event instead of a constant hiss.

12. Filter

A process that changes which frequency regions are emphasized or reduced. A low-pass filter reduces higher frequencies above its cutoff region; a high-pass filter reduces lower frequencies below its cutoff region. Filtering can make a source feel muffled, distant, thin, or brighter. For example, filtering the high end of a heavy impact may help it feel less brittle, while retaining some midrange keeps it recognizable on small speakers.

13. EQ (Equalization)

Adjusting frequency balance, usually with controls that boost or cut selected regions. EQ is often used to remove rumble, tame a piercing resonance, or make space between overlapping sounds. If a weapon effect masks dialogue or a critical alert, try identifying the competing frequency region before turning everything down indiscriminately.

14. Layering

Combining two or more sound elements to create one composite effect. An explosion might use a sharp crack, a low thump, a noisy burst, and a brief debris tail. Each layer should contribute something identifiable. If all layers begin at the same instant and occupy the same frequency range, the result may become muddy rather than bigger.

15. Foley

Performance-based recording of everyday physical sounds, often synchronized to an action. Examples include cloth movement, gear handling, footsteps, or objects being placed on a surface. Foley is useful when a game needs tactile detail that a purely synthetic sound does not provide. The field guide to recording real-world sounds covers practical ways to capture source material.

16. Reverb

The dense collection of reflections that follows a sound in an enclosed or reflective space. Reverb can suggest a room, tunnel, hall, or cavern, but too much can blur fast gameplay cues. A short UI click usually needs little spatial tail; a distant impact in a large stone chamber may need more. Reverb is not the same as a distinct echo.

17. Delay

An effect that repeats a signal after a time interval, sometimes with feedback so repeats continue and fade. Delay can create a clear echo, rhythmic texture, or sci-fi trail. Keep the repeats intentional: a long delay on a frequently triggered effect can pile up and interfere with later events.

18. Dry / Wet

“Dry” refers to the original signal without an effect; “wet” refers to the processed signal. A dry impact sounds close and direct, while a wetter version may feel more distant or spacious. Many effects let you blend the two. Retaining some dry signal often preserves clarity even when the wet effect creates atmosphere.

19. Clipping

Distortion that occurs when a signal exceeds the available level range. Hard digital clipping can create harsh, unintended artifacts. Deliberate distortion is a creative effect, but accidental clipping during recording, processing, or mixing is usually a quality problem. Leave headroom and check the rendered export, not just the waveform preview.

20. Peak and RMS level

Peak level describes the highest instantaneous level reached by a signal; RMS is a measure related to its average energy over time. Two effects with the same peak can sound very different in perceived loudness because their energy is distributed differently. Use meters as guides, then compare assets by listening in context rather than normalizing every sound to the same peak.

When you are preparing assets for a game engine

21. Sample rate

The number of audio samples captured or represented per second, measured in hertz. Sample rate affects the range of frequencies that can be represented and influences file size when other settings are held constant. Choose export settings based on the engine and platform requirements; converting a sound to a higher sample rate does not restore detail that was never present. See the mobile game audio sample rate and format guide.

22. Bit depth

The number of bits used to represent each sample in uncompressed PCM audio. Bit depth affects the available quantization precision and theoretical dynamic range. Higher bit depth is useful during recording and editing because it gives more room for level adjustments, but the best delivery format depends on the target platform and asset pipeline.

23. Codec

A method for encoding and decoding audio. Some codecs compress audio losslessly; others discard information to reduce file size. A codec can affect storage, memory use, CPU cost, and sound quality. Check the actual engine import settings and platform behavior instead of assuming that a filename extension tells the whole story.

24. Loop point

The boundary where a looping file returns from its end to its beginning. A poor loop point creates a click, sudden change in ambience, or obvious rhythmic reset. For a seamless loop, compare the end and beginning, avoid incompatible waveforms at the boundary, and test repeated playback for longer than a few seconds. Crossfades can help, but they are not a substitute for choosing compatible material.

25. Voice (or voice instance)

In many audio engines, a voice is an active playback instance or processing channel used to play a sound. Triggering many separate sounds at once can consume voice resources. If a rapid-fire weapon, crowd, or repeated footstep effect creates dozens of instances, set limits or combine events where appropriate. Exact terminology and resource behavior vary by engine.

26. Voice stealing / voice limit

A voice limit caps how many instances can play at once; voice stealing is a strategy for stopping or replacing an existing instance when a new one needs a slot. The policy matters. A low-priority decorative click may be a sensible candidate to stop, while a critical warning or nearby weapon impact should usually receive higher priority. Test crowded scenes so the chosen policy behaves as intended.

When sounds need to work during gameplay

27. Attenuation

The reduction in perceived level as a sound source becomes more distant, often controlled by a distance curve in the engine. Attenuation helps a nearby door sound prominent while a similar event across the map remains faint. If a sound stays equally loud at every distance, it may feel detached from the world; if it disappears too quickly, players may miss useful information.

28. Spatialization

Processing that helps a sound appear to come from a position in the game world. Depending on the platform and audio system, this may involve left-right panning, distance cues, filtering, or more advanced spatial audio. Use spatialization for sources players should locate, but consider keeping essential UI feedback non-spatial so it remains clear regardless of camera direction.

29. Ducking

Temporarily lowering one audio signal or group when another event needs room. For example, music may dip slightly during a dialogue line or a critical warning. Ducking should be fast enough to protect the important cue but smooth enough not to make the mix pump awkwardly. It is usually better to define clear priorities than to duck every sound whenever anything happens.

30. Randomization and variation

Using a set of related versions or controlled parameter changes so repeated events do not sound mechanically identical. Footsteps can vary between a few recordings; a generated pickup can use small pitch or duration changes; an impact system can choose among several layers. Keep the variations within a recognizable range. Excessive random pitch or volume changes can make one action sound like several unrelated assets. For an example of this issue in practice, see how to design footsteps for different surfaces.

A quick way to use the glossary during a real task

Imagine that a pickup sound is audible in the editor but feels weak during a busy game scene. Rather than asking only for “more punch,” describe the problem with terms that point toward a fix: the transient may be too soft, the decay may be too short to reveal the tonal body, or the sound may be masked by music. Try one change at a time and compare it in the same gameplay situation.

If an explosion sounds powerful on headphones but disappears on a phone, check whether its impact depends too heavily on very low frequencies. A small-speaker test may reveal that the transient and midrange texture need more definition. If footsteps become repetitive, add a small set of similar variations and check the random selection at the actual rate of play. If an ambience loop clicks, inspect the loop point before adding reverb to hide the seam.

For a short synthetic cue, it can help to experiment directly with pitch, duration, and waveform before reaching for a complex plugin. The SfxMaker sound effect generator is a practical place to test those basic parameters and download a WAV version for your prototype. For a more focused example, the coin sound effect generator page is relevant when you are shaping a short collectible or reward cue.

The most useful glossary is one you can apply while listening. When you can identify whether a problem comes from timing, envelope, frequency balance, playback behavior, or implementation, feedback becomes more specific and revisions become easier to evaluate. You do not need technical language for its own sake; use it to make the sound do its job more reliably.