ZBrush Tip: Standardized SubTool Naming for Pipeline Reliability

Consistent, incremental SubTool naming removes friction across exports, baking, and handoffs in large pipelines.

Adopt a schema your entire team understands and automate as much as possible. If you’re building out your ZBrush environment or expanding licenses, consider sourcing through NOVEDGE for expert advice and flexible purchasing.

• Define a clear schema
  • Tokens: ASSET_CONTEXT-ELEMENT_SIDE-SEQUENCE_LOD_MAT_STATE_VERSION
  • Example: CHR_HeroA-Arm_L-S001_LOD0_MAT-Skin_WIP_v003
  • Common tokens:
    • ASSET_CONTEXT: CHR, PROP, ENV
    • ELEMENT: Head, Torso, Arm, Panel, Bolt
    • SIDE: L, R, C (left, right, center)
    • SEQUENCE: S001, S002 (zero-padded)
    • LOD: LOD0, LOD1 (if applicable)
    • MAT: material hint for downstream grouping
    • STATE: WIP, FIN, HI, LO
    • VERSION: v001, v002 for topology-impacting changes
• Naming rules that survive export
  • Use underscores or hyphens; avoid spaces and special characters.
  • Zero-pad numbers (S001 vs S1) to keep lists ordered across apps.
  • Keep names stable once maps are baked; only bump the version when topology or UVs change.
  • Reserve STATE (WIP/FIN) for review gates; strip WIP when publishing.
• Operational workflow in ZBrush
  • Group related parts into SubTool folders first; review visibility to stage renaming passes.
  • Use SubTool palette Rename for surgical fixes; for batches, leverage ZPlugin utilities (e.g., SubTool Master) to apply prefixes/suffixes and propagate patterns to visible SubTools.
  • Append sequential indices per element: Arm_L-S001, Arm_L-S002, etc. Zero-padding pays off later in FBX/OBJ imports.
  • Multi Map Exporter uses SubTool names as map prefixes; consistent names keep AO/Normal/Displacement sets aligned across DCCs and engines.
  • FBX/OBJ exporters preserve SubTool names as object nodes, which your lookdev, rigging, and game integration teams rely on for assignments.
• Quality control checklist
  • No duplicates; scan the SubTool list alphabetically to spot collisions.
  • Spot-check an export in your target DCC (Maya/Blender) or engine to confirm object and material slot names match expectations.
  • Keep names human-scannable: put the most distinguishing tokens up front (ASSET and ELEMENT).
  • Document your schema in the project README and pin a cheat sheet in your studio wiki.
• Automation tips
  • Standardize separators (e.g., hyphen between major tokens, underscores within tokens: MAT-Skin_Pores).
  • Use a quick regex in external renamers when needed:
    • Find: (S)(\d+)
    • Replace: S${zeroPad($2,3)} (use your tool’s zero-pad function or run a numeric sequence pass)
  • Lock a prefix per folder (e.g., CHR_HeroA-Arm_L-) and iterate only the sequence and version.

Why this matters: stable, incremental naming reduces re-bakes, preserves material bindings, and keeps Multi Map Exporter outputs predictable for texture artists and TDs. For studio rollouts, align your ZBrush setup and licensing through NOVEDGE and circulate the schema template with your team before production ramps up.

You can find all the ZBrush products on the NOVEDGE web site at this page.