> For the complete documentation index, see [llms.txt](https://handtracking.lightbuzz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handtracking.lightbuzz.com/hand-tracking-unity-plugin/system-requirements.md).

# System Requirements

Supported platforms & system specifications.

### Supported Platforms

The Hand Tracking Unity plugin supports the most popular development platforms both for desktop and mobile. You can also test your software directly in the Unity Editor before deploying.

{% hint style="info" %}
All packages support Unity Editor on Mac and Windows.
{% endhint %}

<table data-full-width="false"><thead><tr><th>Platform</th><th width="296">Runtime</th><th>Version</th></tr></thead><tbody><tr><td>Android</td><td>Android ARM64, ARM32, x86, x64</td><td>Android API Level 33 or higher</td></tr><tr><td>iOS</td><td>iOS, iPadOS, Mac Catalyst</td><td>iOS 14+</td></tr><tr><td>macOS</td><td>macOS M1, M2, M3, Intel</td><td>macOS Monterey 12+</td></tr><tr><td>visionOS</td><td>visionOS</td><td>visionOS 1.0+</td></tr><tr><td>Windows</td><td>Windows x64</td><td>Windows 10+</td></tr><tr><td><em>Unity Editor</em></td><td><em>Mac, Windows</em></td><td><em>Unity 2020+</em></td></tr></tbody></table>

These requirements ensure that the Hand Tracking Unity plugin runs smoothly across the various platforms for a wide range of devices.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://handtracking.lightbuzz.com/hand-tracking-unity-plugin/system-requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.