> For the complete documentation index, see [llms.txt](https://help.movin3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.movin3d.com/movin-studio-usage-guide/retargeting/pose-matching.md).
# Pose Matching
In the Pose Matching Sub-Mode, you can modify a character’s Rest Pose and adjust its Bone Hierarchy.\
For the retargeting system to perform correctly, the character must have a proper rest pose and a well-structured bone hierarchy.
Pose Matching Sub-Mode
### Recommended Bone Hierarchy
You can edit the Bone Hierarchy directly by dragging and dropping bones in the Hierarchy panel.\
To ensure accurate retargeting, organize the character’s bones so they follow a structure similar to the human body.
MOVIN Studio’s retargeting system performs best with characters that follow this structure:
* The **Pelvis** acts as the root bone, connecting both leg chains.
* A central spine runs from the **Waist** to the **Chest**, where the **Chest** bone connects both arms and the head chains.
* Each arm chain is structured as **Shoulder → Elbow → Wrist**, and each **Finger** chain should connect directly to the **Wrist** bone.
* Each leg chain is organized as **Hip → Knee → Ankle → Toe**.
Recommended Bone Heirarchy
### Proper Rest Pose
The Rest Pose can be modified by clicking on each joint and adjusting it using the displayed Gizmo.\
MOVIN Studio uses a T-Pose as the default Rest Pose. Adjust your character so that both arms and legs are aligned along the X and Y axes, respectively.
{% columns %}
{% column width="50%" %}
Before T-Pose Alignment
{% endcolumn %}
{% column width="50%" %}
After T-Pose Alignment (Default Rest Pose)
{% endcolumn %}
{% endcolumns %}
#### Mirror Mode
In Pose Matching, the **Mirror Mode** allows you to create perfectly symmetrical poses more quickly and accurately.
Once you enable the Mirror Mode option at the top center of the screen and adjust the character’s pose, any changes made to one side will be automatically applied to the opposite side—eliminating the need to edit the left and right sides separately.
The Mirror feature identifies the character’s left–right symmetry based on **bone naming rules****,** and will automatically pair bones when any of the following conditions are met:
1\. Prefix or postfix differs only by left/right notation
* `leftArm` ↔ `rightArm`
* `leftHand` ↔ `rightHand`
* `leftLeg` ↔ `rightLeg`
2\. Left/right indicated by *l* and *r* separated by delimiters
*(Delimiters: `.`, `_`, `-`, or a space — followed by lowercase `l` or `r`)*
* `l.foot` ↔ `r.foot`
* `l_hand` ↔ `r_hand`
* `l-foot` ↔ `r-foot`
* `l foot` ↔ `r foot`
3\. Bone names ending with uppercase L or R
* `ThighL` ↔ `ThighR`
* `ArmL` ↔ `ArmR`
* `LegL` ↔ `LegR`
Mirror Mode
#### Finger Pose
Fingers should generally point in the X-axis direction.\
However, the first thumb bone (Metacarpal) is an exception — it should be slightly rotated so that the thumb naturally rests alongside the palm.
{% columns %}
{% column %}
{% endcolumn %}
{% endcolumns %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.movin3d.com/movin-studio-usage-guide/retargeting/pose-matching.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.