> ## Documentation Index
> Fetch the complete documentation index at: https://docs.holos.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Object tracking
> Make a 3D model trackable so Holos Capture can recognize and follow the real thing.
**Object tracking** lets Holos Capture recognize a specific real-world object and record its position throughout a session. Not all objects are trackable by default — trackable objects display a scan icon on their tile in the library, and the **Trackable** stat on the detail page shows **Yes** or **No**.
## Why it's necessary
A 3D model on its own is just geometry — the app has no way to spot the matching physical object in the room. To bridge that gap, the platform builds a **reference object**: a compact descriptor trained from the model that the Capture app matches against the live camera feed to find and follow the real thing.
Building a reference object is a compute-heavy job that runs on Holos infrastructure, so it isn't instant. You enable it once per object; afterwards the object is permanently trackable and ready to use in any capture.
You only need to enable tracking for objects you want the app to follow during a session. Models used purely as course content or for reference don't need it.
## Enabling object tracking
1. Open the object from the library
2. Click the **scan** icon in the action row (top right of the detail page)
3. Choose your tracking settings (see below)
4. Click **Enable object tracking**
The **Trackable** stat reads **No** with tracking *queued* or *in progress* until the job completes, and a small dot on the scan icon indicates an active request. You can reopen the dialog any time to update the settings while the job is still queued.
Tracking is also requested automatically when you link an object to a [skill](/dashboard/skills) from the skill's **Tracked objects** section: if the object isn't yet trackable, the platform submits the request for you and shows a confirmation toast.
Reference objects are built by the Holos team's processing pipeline. Once the job finishes, the **Trackable** field flips to **Yes** and the object becomes available in Holos Capture.
## Tracking settings
The settings you choose describe how the object is handled in the real world, which helps the pipeline build an accurate reference object.
**View mode** — how the object is approached during a session:
Front
Viewed only from the front. Wall-mounted panels, controls, screens.
Upright
Stays upright, approached from any side. Benchtop equipment, freestanding machines.
All angles
Picked up and rotated freely. Handheld parts and tools.
**All angles** takes longer to train and carries a higher false-positive risk. Only choose it for objects that are genuinely handled from every direction.
**Training mode** — how much compute the pipeline spends building the reference object:
| Mode | Typical runtime | Best for |
| ------------ | --------------- | ---------------------------------------------- |
| **Standard** | \~8 hours | Most objects |
| **Extended** | \~18 hours | Small, handheld objects that need extra detail |
**Objects to avoid** — optionally pick look-alike objects from your organization's library so the tracker doesn't confuse them with this one. Most useful when you have several visually similar models. Only objects that have a USDZ file can be selected, and only your own objects are listed: an object to avoid is something physically present in the room, which a catalogue model never is.
Once an object is trackable, link it to a skill so it's prepared automatically when a session starts. See [Tracked objects](/capture/tracked-objects) for how linking and in-session tracking work.