Blog
How Many Trackers Do You Need for Full Body Tracking
Jul
For a standard SlimeVR role plan, the official placement table gives a practical starting ladder: five trackers cover Chest, both Upper Legs, and both Lower Legs; six adds Hip; eight adds both Feet; and ten adds both Upper Arms. Choose the first row that includes every body segment you can name as necessary, then stop. These are SlimeVR example layouts, not a guarantee that a larger count will be more accurate or that a FBTKit product option arrives with those roles preconfigured.
If you have not settled the headset and application route, do that before counting trackers. The full body tracking buying workflow handles the broader decision, while the Quest route check and VRChat buyer and setup guide handle two common platform questions.
Use the SlimeVR placement rows as a body-point map
The count becomes useful when every number is translated into physical roles. In the official SlimeVR `Recommended Tracker Placement` table, plural body parts use paired trackers. That is why the five-tracker row can represent Chest plus two Upper Legs and two Lower Legs.
| Tracker count | Official SlimeVR example roles | What changes from the previous row shown here | Decision question |
|---|---|---|---|
| 5 | Chest, both Upper Legs, both Lower Legs | Baseline row in this comparison | Are those five body points the complete plan? |
| 6 | Chest, Hip, both Upper Legs, both Lower Legs | Adds one Hip role | Does the plan explicitly require Hip? |
| 8 | Chest, Hip, both Upper Legs, both Lower Legs, both Feet | Adds paired Foot roles | Are Foot roles required for the intended sessions? |
| 10 | Chest, Hip, both Upper Legs, both Lower Legs, both Feet, both Upper Arms | Adds paired Upper Arm roles | Are Upper Arm roles required, rather than merely interesting? |
This is a role map, not a performance ranking. SlimeVR documents other counts and other roles as well. A user may need a different combination, and a count alone does not explain which physical device is assigned to which body part.
Separate FBTKit options from SlimeVR examples
On August 11, 2026, Woo Store API product 1064 and the public FBTKit LSM6DSV SlimeVR-Compatible Full Body Tracking Kit page both exposed 5-, 6-, 8-, and 10-tracker options. That confirms which counts were selectable on that date. It does not turn the SlimeVR table above into fixed package assignments.
Keep two notes side by side: `product count selected` and `body roles planned`. The first comes from the product option. The second comes from the roles you intend to assign in SlimeVR Server. Before ordering, verify that the count is sufficient for the role list; after delivery, use the kit contents checklist for package verification rather than trying to infer accessories from the number.
Choose the first row that covers required body segments
- Write the body segments. Start with Chest, Upper Legs, Lower Legs, Hip, Feet, and Upper Arms. Mark a segment required only when you can connect it to a real session need.
- Find the first matching row. Read upward from five. Stop at the first official example containing every required segment; do not begin at ten and search for reasons to keep it.
- Check the wearing plan. Confirm that each role has a physical location and that you are prepared to label, wear, charge, and configure that number of devices.
Use the roles-first placement guide for physical mounting points and the wear sequence. This count page only decides which roles need a tracker in the first place.
Stop before optional roles become hypothetical
A first purchase does not need to anticipate every future dance, avatar, world, or recording idea. Stop increasing the count when the first matching row covers the body segments needed for the sessions you already plan to run. A role described only as “maybe later” is not yet a requirement.
| Observation before purchase | Decision |
|---|---|
| Every required segment appears in the current row | Stop increasing the count |
| A named required segment first appears in the next row | Evaluate that next row |
| The reason for adding trackers is “more must be better” | Stop; count alone is not an accuracy claim |
| You already use a setup and repeatedly miss one specific body role | Use the later upgrade decision guide |
Keep the first-purchase question separate from a later upgrade decision. Choose an initial count from required roles. After you have used that setup, reassess only when repeated sessions reveal a specific gap.
Do not use quantity to solve configuration problems
Adding trackers is not a substitute for correct role assignment, mounting orientation, calibration, or application output. If a five- or six-tracker setup is mapped incorrectly, buying two more devices does not identify the original mistake. It adds two more devices to the same unresolved workflow.
SlimeVR’s setup process treats connection, body locations, mounting direction, calibration, proportions, and application output as separate stages. Finish those stages for the chosen count before judging whether a body role is genuinely absent.
Carry the chosen count into the setup
Before configuring anything, make a one-line map such as `6 = Chest + Hip + L/R Upper Leg + L/R Lower Leg`. Give each physical tracker a temporary identity and confirm that the saved role matches the worn body point. Then follow the complete setup and calibration workflow.
Evaluate the chosen count in ordinary sessions before reconsidering it. A body segment that is absent from the role map is a count question; a device that drifts, jitters, appears late, or maps incorrectly is a setup or troubleshooting question. Keeping that distinction clear makes the next decision smaller and easier to verify.
FAQ
What is the smallest row in SlimeVR’s standard tracker-placement table?
The smallest row in the official table is five trackers: one Chest tracker, paired Upper Leg trackers, and paired Lower Leg trackers. It is an example SlimeVR layout, not a universal minimum for every tracking ecosystem.
What body point changes between the five- and six-tracker rows?
The official six-tracker example adds one Hip role to the five-tracker Chest, Upper Leg, and Lower Leg roles. Product count alone does not assign that role automatically.
What do the eight- and ten-tracker rows add to the SlimeVR example?
The eight-tracker example adds paired Feet to the six-tracker layout. The ten-tracker example adds paired Upper Arms. These examples describe body roles, and the physical trackers still need assignments during setup.
Do FBTKit’s 5, 6, 8, and 10 options prove which body roles are configured?
No. The current product selector proves the available tracker counts on the evidence date. The body-role examples come from SlimeVR documentation, and the user assigns physical trackers to roles during setup.
When should a first-time buyer stop increasing the tracker count?
Stop at the first example row that contains every body segment required for the planned sessions. Add nothing for an unnamed future use; reconsider later only after real sessions reveal a specific missing role.
Official sources
