How to name your sound effect files

A good filename is a tiny description. When you search a library six months from now, the name is often the only thing you have. Here's a pattern that works.

The pattern

category_subject_detail_detail_variation.wav

Read from general to specific. Examples:

impact_metal_heavy_dark_01.wav
whoosh_air_fast_pass_02.wav
footsteps_snow_crunch_slow.wav
ui_click_soft_confirm.wav
ambience_city_night_traffic_distant_loop.wav

Rules that keep names useful

Lowercase and underscores. door_slam_heavy.wav works in every app and on every system. Avoid spaces and special characters like #, & and /.
Describe what you hear, not where it came from. glass_break_small_bottle beats pack3_track14.
Put the most important word first. Files sort alphabetically, so the category groups similar sounds together.
Add the words you'd search for. Material (wood, metal, glass), size (small, heavy), speed (slow, fast), distance (close, distant), mood (dark, bright).
Use two-digit variations. _01, _02, _03 keep takes in order.
Mark loops. Add _loop to sounds that repeat cleanly.
Keep it under about 60 characters. Long names get cut off in panels and timelines.

What about other languages?

Pick one main language for filenames and stay consistent. If you work in two languages, tags are a better place for translations than the filename.

Renaming an existing library

Don't try to rename everything at once. Rename sounds as you use them, and sort new downloads before they enter the library. Batch rename tools in Finder (select files ▸ Rename) help with simple patterns.

Renaming changes file paths, so projects that already use those files may lose their links. Rename only sounds that aren't in active projects, or relink afterwards.

How SFX L'Builder helps

SFX L'Builder analyses each sound and tags it by what it sounds like, so search works by meaning even when filenames are messy. You can describe a sound in English or Portuguese, and renaming is always a separate action you choose.

Join the private beta