Layer naming is not a “nice-to-have” detail.
For VTubers, layer naming conventions directly affect tracking accuracy, export stability, troubleshooting speed, and long-term scalability.
Poor naming causes:
- Broken mouth and eye tracking
- Physics behaving incorrectly
- Export errors
- Impossible debugging
- Artist–rigger conflicts
- OBS and plugin confusion
Correct naming gives you:
- Faster rigging
- Cleaner physics
- Easier fixes
- Lower maintenance cost
- Professional-grade workflow
This VTuber model layer naming conventions guide goes deeper than the Top 1–3 Google results and shows exact, copy-ready naming systems for Live2D and 3D VTuber models.
You can copy this directly to your website.
Why Layer Naming Matters More Than You Think
Layer names are used by:
- Rigging software
- Physics engines
- Export pipelines
- Debug tools
- Collaborating artists
- Future you (months later)
Bad names don’t break things immediately.
They break them later, when fixing costs 10× more time.
Related foundation:
👉 vtuber model file size optimization
👉 vtuber model texture compression guide
What Happens When Layer Naming Is Done Wrong
Common real-world problems:
- Mouth opens but doesn’t sync
- Eyes blink randomly
- Hair physics apply to wrong parts
- Toggles break after export
- Parameters become unreadable
These often get misdiagnosed as:
- Software bugs
- Tracking problems
- OBS issues
In reality, the root cause is layer chaos.
Core Principles of VTuber Layer Naming (Universal Rules)
These rules apply to Live2D and 3D.
Golden Rules
- Never use spaces
- Never use special characters
- Be consistent, not clever
- Names must explain function
- Future-proof everything
Allowed Characters
✅ a–z
✅ A–Z
✅ 0–9
✅ underscore _
Avoid:
❌ spaces
❌ emojis
❌ symbols
❌ mixed languages
Live2D VTuber Layer Naming Conventions (Industry Standard)
Recommended Structure
category_part_function_detail
Example:
eye_L_upper_lid
mouth_open_inner
hair_back_physics
This structure makes sorting, filtering, and debugging effortless.
Live2D Face Layer Naming (Critical Section)
Eyes
eye_L_white
eye_L_pupil
eye_L_upper_lid
eye_L_lower_lid
eye_R_white
eye_R_pupil
eye_R_upper_lid
eye_R_lower_lid
Why this matters:
- Eye tracking relies on consistent left/right mapping
- Physics and blink parameters depend on grouping
Related tracking guide:
👉 vtuber eye tracking setup accuracy
Eyebrows
brow_L_base
brow_L_raise
brow_L_angry
brow_R_base
brow_R_raise
brow_R_angry
Do NOT name eyebrows creatively.
They are functional components.
Mouth (Most Common Failure Point)
mouth_base
mouth_open
mouth_open_inner
mouth_smile
mouth_frown
mouth_teeth
mouth_tongue
Avoid:
cute_mouth
mouth_v2
mouth_final_final
These break:
- Lip sync
- Auto-mapping
- Future edits
Related fix:
👉 vtuber mouth tracking delay fix
Live2D Body & Outfit Layer Naming
Body Core
body_base
body_shadow
body_highlight
Outfits
outfit_top_base
outfit_top_shadow
outfit_bottom_base
outfit_bottom_shadow
Accessories
acc_glasses
acc_hat
acc_earring_L
acc_earring_R
Prefixing with acc_ allows:
- Easy toggles
- Clean exports
- Fast debugging
Live2D Hair Layer Naming (Physics-Friendly)
Hair must be readable at a glance.
hair_front
hair_side_L
hair_side_R
hair_back
hair_back_physics
For segmented hair:
hair_back_01
hair_back_02
hair_back_03
Never name hair:
hair_new
hair_test
hair_fix
These destroy physics workflows.
Live2D Toggle & Expression Layers
Expressions
expr_blush
expr_sweat
expr_angry
expr_shy
Toggles
toggle_hat
toggle_glasses
toggle_jacket
This ensures:
- Clear parameter mapping
- Clean UI in tracking software
3D VTuber (VRM) Layer / Object Naming Conventions
Mesh Naming
face_mesh
eye_L_mesh
eye_R_mesh
body_mesh
hair_mesh
Never export with:
Mesh_01
Cube
Object.004
Bone Naming (Extremely Important)
Follow humanoid standards where possible.
head
neck
spine
upper_arm_L
lower_arm_L
hand_L
Facial bones:
eye_L
eye_R
jaw
Consistent bone names improve:
- Face tracking
- Retargeting
- Plugin compatibility
Related:
👉 3d vtuber model facial tracking options
Naming for Physics & Performance
Physics-based layers should be obvious.
hair_back_phys
skirt_phys
sleeve_L_phys
Never mix physics and non-physics layers without naming distinction.
OBS & Export Compatibility Considerations
Clean naming:
- Prevents plugin confusion
- Simplifies scene layering
- Reduces crash risk
Related OBS guides:
👉 vtuber obs vtuber model layer setup
👉 vtuber obs source order optimization
Artist–Rigger Collaboration Naming Rules
If you commission a model:
You Should Request
- Layer naming documentation
- English-only names
- Consistent prefixes
Artist Should Provide
- Clean PSD or source file
- Final naming before rigging
- No temporary names
Related contract topic:
👉 vtuber model commission contract template
Beginner vs Professional Naming Standards
Beginner
- Simple but consistent
- No shortcuts
- Avoid abbreviations
Professional
- Scalable naming
- Version-safe
- Team-readable
Bad naming is a hidden technical debt.
Common Layer Naming Myths
❌ “It doesn’t matter after export”
❌ “Only riggers care”
❌ “I’ll remember what this means”
❌ “Software will fix it”
Naming errors always resurface.
Quick Layer Naming Checklist
Before final export, confirm:
✔ No spaces
✔ No special characters
✔ Clear left/right distinction
✔ Face layers prioritized
✔ Physics layers labeled
✔ Toggles obvious
✔ No temp names
If any fail → fix before rigging.
Final Thoughts
Layer naming is invisible when done right—and disastrous when done wrong.
Professional VTubers treat naming as:
- Part of performance optimization
- Part of tracking accuracy
- Part of long-term sustainability
If you want your model to:
- Scale
- Upgrade
- Survive re-rigging
- Avoid costly rebuilds
Naming conventions are non-negotiable.