A good thud is more about perceived weight and space than volume. When browsing clips or writing prompts, focus on the transient (how the hit starts), the low-end bloom (how heavy it feels), and the tail (how the room responds). Use the tips below to get thuds that sync cleanly, don't mask dialogue, and still feel physical on phones and headphones.
Match the surface and object
Thuds change drastically depending on what hits what. "Body on carpet" reads soft and rounded, while "crate on wood" needs a harder edge and a slightly boxy midrange.
- Name both materials: "sandbag on plywood", "backpack on concrete"
- Specify if it's padded, hollow, or dense to shape the midrange
- Ask for "no sharp click" if you want a pure thump without clacks
Choose the right punch vs. boom
Editors usually need either a tight punch that cuts through or a boomy hit that sells scale. Prompting for transient and low-end balance helps you avoid muddy impacts.
- For tight timing: "tight transient, short decay, dry"
- For weight: "deep low-end bloom, controlled boom, no distortion"
- If it masks speech: request "less low-end, more mid punch"
Set perspective with tail and reflections
A thud in a small bedroom ends quickly; a hallway or warehouse leaves reflections. Tail length is what makes a hit feel close or far even at the same loudness.
- Close action: "minimal room tone, very short tail"
- Off-screen hits: "distant, softened highs, audible reflections"
- Avoid over-wet results by prompting "subtle reverb only"
Avoid common thud problems
Bad thuds often have an obvious click at the start, a flabby low-end that swallows everything, or an unrealistic tail that doesn't match the scene.
- If you hear a click: request "rounded attack, no snap"
- If it feels small: ask for "more low-end weight, thicker body"
- If the tail sounds wrong: specify the space or ask for "shorter decay"
