A good naming convention is not bureaucracy, it is what lets the next artist (or the render farm, or Unreal) find the right file without asking you. In Houdini, where a project is full of caches, versions and exports, consistent names are the difference between a browsable project and a guessing game.
What a name should tell you
A useful asset name encodes what it is, which version it is, and where in the sequence it belongs - without needing the artist who made it. The pieces that matter most:
- Asset or shot. A stable identifier like
SHOT010orhero_rockthat stays the same across versions. - Descriptor. What the file is -
pyro,collision,proxy,render. - Version. A zero-padded
v001token that increments, never a barefinalornew. - Frame padding. For sequences, consistent padding such as
.$F4so frames sort correctly.
Good and bad, side by side
| Avoid | Prefer |
|---|---|
test_final_FIX2.bgeo.sc | hero_rock_proxy_v003.bgeo.sc |
smoke.vdb | SHOT010_pyro_smoke_v002.$F4.vdb |
export.fbx | SHOT010_env_props_v005.fbx |
The left column depends on memory; the right column is self-documenting. The moment a project is shared or archived, the difference stops being cosmetic.
Rules that hold up over time
- No spaces or special characters. Use underscores; spaces and punctuation break on the farm, on Linux, and on export to game engines.
- Lower case, consistent separators. Pick a case and a separator and never mix them -
hero_rock, notHero-Rockthenhero rock. - Always version. Every cache and export carries a padded version token, so nothing overwrites and history is legible.
- Descriptive, not incremental hacks.
v002, never_v2_real_final.
Enforce it without policing it
Conventions drift the instant a deadline hits. Hive validates every asset in a project folder against a naming convention in your browser and flags the ones that break it - spaces, missing versions, inconsistent separators, names that will not survive a game-engine import. It works alongside the cache naming validator for File Cache output and the Unreal handoff checklist for exports. Nothing is uploaded; the scan is local.
Frequently asked questions
Why do Houdini asset names matter so much?
Houdini projects fill up with caches, versions and exports. Consistent names let the next artist, the farm and game engines find the right file without asking, and they prevent overwrites.
Should I use spaces in Houdini file names?
No. Use underscores. Spaces and special characters break on render farms, on Linux and on export to Unreal or Unity.
Can Hive enforce a naming convention?
Yes. Hive scans a project folder in your browser and flags assets that break the convention - spaces, missing version tokens, inconsistent separators - without uploading anything.