Blender TOHA Setup Explained: Building a Clean Top-of-Hierarchy Armature That Won't Haunt You Later

If you've spent any time in Blender's rigging and animation communities — Reddit threads, Discord servers, YouTube comment sections — you've probably seen the term "TOHA" pop up. It sounds technical and a little intimidating, but the concept itself is pretty straightforward once someone actually explains it.

TOHA stands for Top of Hierarchy Armature. It refers to the root-level control structure that sits at the very top of your rig's bone hierarchy — the master controller that everything else ultimately answers to. Getting this setup right isn't just a nice-to-have. It's the difference between a rig that animators love working with and one that creates constant headaches the moment you try to do anything complex.

Let's break it down.

What Is a TOHA and Why Does It Matter?

Every armature in Blender has a hierarchy — bones parented to other bones, controllers driving deformation bones, constraint chains keeping things in sync. At the very top of that hierarchy, you need a root controller. That's your TOHA.

The TOHA bone typically handles a few core responsibilities:

• Global position and scale — Moving or scaling the entire rig without breaking any internal constraints
• Animation offset — Allowing animators to reposition the character in world space without touching the actual animation data
• Export pivot control — Giving you a clean, consistent origin point when sending your rig to a game engine or another application

Without a proper TOHA, animators end up doing hacky workarounds — moving the armature object itself, manually offsetting every single bone, or fighting constraint systems that weren't designed for the workflow they need. It's messy, and it shows in the final animation.

How to Set Up a Basic TOHA in Blender

Setting up a TOHA doesn't require any special add-ons. Here's a clean, practical approach:

1. Create your root bone first

Before you do anything else in your armature, create a single bone at the world origin (0, 0, 0). Name it something clear — root, TOHA, or master are all common conventions. This bone should sit flat on the ground plane and point upward along the Z-axis.

2. Parent everything to it

Every top-level control in your rig — your COG (center of gravity) bone, your pelvis controller, any floating control rigs — should be parented directly to this root bone, or at least exist as a child of it somewhere down the chain. Nothing in your rig should be able to move independently of the root.

3. Lock what shouldn't move

In Pose Mode, select your root bone and lock off the rotations in the Properties panel if your rig doesn't need the root to rotate (many rigs don't). This prevents accidental transformation and keeps your hierarchy clean.

4. Use a second-level master controller for character offset

A common pattern is to have two levels at the top: the true root (TOHA) that never gets animated and handles the rig's world position, and a "master" or "global" controller just below it that animators can freely keyframe for things like walk cycles and character placement. This separation keeps your animation data clean and makes it much easier to loop or offset animations later.

Common TOHA Mistakes Blender Artists Make

Skipping the root entirely. This is probably the most common issue, especially for artists who learned rigging by following quick tutorials that glossed over hierarchy setup. Without a root, moving your character in a scene becomes a nightmare.

Putting the root off-center. Your TOHA should be at the origin of your character — typically at the base of the feet, centered on the X-axis. If it's offset, your scaling and rotation will behave unexpectedly.

Animating the root directly. The root bone should generally stay put unless you're doing something very specific. Animating it directly mixes your rig's structural data with your animation data, which causes problems when you try to retarget or reuse animations.

Forgetting to account for the TOHA in game engine exports. If you're exporting to Unreal Engine or Unity, the game engine is going to look for a root bone to drive character movement. If your TOHA isn't named correctly or isn't set up as a proper root, your locomotion system is going to have a bad time.

TOHA in the Context of Rigify and Auto-Rigs

If you're using Rigify (Blender's built-in auto-rigging system) or a third-party add-on like Auto-Rig Pro, the TOHA is usually handled for you — but you should still understand what it's doing. Rigify generates a root bone automatically, and its metarig is designed around a proper hierarchy from the start.

The issue comes when artists start customizing these auto-generated rigs without understanding the hierarchy. Moving bones around, adding custom controllers, or merging rigs together can accidentally break the top-of-hierarchy structure in ways that aren't immediately obvious but cause serious problems during animation.

Always check your hierarchy in the Outliner with bone display enabled before you hand a rig off to anyone else — or before you start animating it yourself.

Why This Matters More Than You Think

The TOHA concept isn't just about keeping things tidy. It's about building rigs that are actually usable in a production context. If you're doing freelance work, creating assets for a game, or collaborating with other artists, a rig without a clean top-of-hierarchy setup is going to create friction at every stage.

Animators will complain. Technical directors will ask you to fix it. Game engine imports will behave weirdly. And you'll end up spending time rebuilding the hierarchy instead of actually making things.

Get the root right from the start. It's one of those foundational decisions that costs almost nothing upfront and pays dividends throughout the entire project.