Tracking by .referenceobject allows you to recognize known items and track their pose. Understand capture, limits and application in the field.
Direct answer
Current ARKit documentation describes using .referenceobject files to recognize and track known real objects in iOS apps. The session can separate objects that have only been detected from those that must continue to be monitored, with a combined limit of up to 10 references per session. This favors visual assistance on tools and equipment, but requires subject preparation, testing in real light and angles, and fallback when the pose is lost.
Recognizing and monitoring are different tasks
Detection finds the item and creates an anchor; tracking maintains pose updates. Choosing the modality avoids costs when an object only needs to trigger content.
Reference needs to represent reality
Texture, stiffness, scale, origin, and captured angles affect robustness. Smooth, reflective or deformable surfaces tend to offer fewer stable characteristics.
Ten references require context cutting
The combined limit per session favors specific sets per task or area. Carrying all inventory reduces clarity and can compromise operation and maintenance.
Tracking loss must be explicit
The interface needs to freeze, hide, or request re-alignment when trust drops. Instruction that drifts to another part creates a greater risk than a temporary absence.
Nexus Reading
Reference objects work best on repeatable tasks and known equipment. The pilot must measure time to recognition, stability, recovery and error by light, distance and operator.
FAQ
Is the file a visible 3D model?
Not necessarily. The reference stores spatial characteristics for recognition; visual content is provided by the application.
Does any object work well?
No. Rigid, textured objects tend to be more reliable than smooth, reflective, or flexible items.
Can I mix old and new formats?
The documentation states that .arobject and .referenceobject cannot be used in the same session.
Essential guides to delve deeper into the decision
This editorial analysis was produced by Nexus from the official sources below, consulted on September 15, 2026. The text is original and interprets practical implications for companies.
- Apple Developer — Using a reference object with ARKit in iOS: current format, detection, tracking, configuration and limit of references per session.
- Apple Developer — Scanning and Detecting 3D Objects: capture, lighting, texture, origin, test and previous format of reference objects.
Date reported by main source: documentation consulted on September 15, 2026.