> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/advanced-settings/setup-parameters/and-accelerometer.md).

# \&accelerometer

Reference for the \&accelerometer URL parameter in VDO.Ninja including behavior examples and related options.

**Also known as:** `&sensors`, `&sensor`, `&gyro`, `&gyros`

#### **Description**

Enables device motion and orientation sensor data transmission, allowing real-time sharing of accelerometer, gyroscope, and other sensor information.

#### **Sender-Side Option**

This parameter activates sensor data collection and transmission from devices that support motion sensors.

#### **Usage**

* **`&accelerometer`** - Enable at default rate (30 Hz)
* **`&accelerometer=60`** - Enable at 60 Hz update rate
* **`&sensor=10`** - Enable at 10 Hz update rate
* **`&gyro=30`** - Alias usage

#### **Examples**

```
https://vdo.ninja/?push=streamID&accelerometer
https://vdo.ninja/?push=streamID&sensor=60
https://vdo.ninja/?room=roomname&gyro=30
```

#### **Sensor Data Included**

* **Accelerometer**: Linear acceleration (x, y, z)
* **Gyroscope**: Rotational velocity
* **Orientation**: Device orientation in space
* **Magnetometer**: Compass heading (if available)
* **Linear Acceleration**: Acceleration without gravity
* **Absolute Orientation**: Quaternion orientation

#### **Update Rates**

* **Default**: 30 Hz (30 updates per second)
* **Minimum**: 1 Hz
* **Maximum**: 60 Hz (device dependent)
* **Recommended**: 10-30 Hz for most applications

#### **Device Support**

* **Smartphones**: Full support (iOS/Android)
* **Tablets**: Full support
* **Laptops**: Limited (some have accelerometers)
* **Desktop**: Usually no sensors

#### **Browser Requirements**

* Requires HTTPS connection
* User permission required
* Not all browsers support all sensors

#### **Data Format**

Sensor data is transmitted as structured data containing:

* Timestamp
* Sensor type
* X, Y, Z values
* Additional sensor-specific data

#### **Use Cases**

* Motion-controlled applications
* VR/AR experiences
* Game controllers
* Motion analysis
* Remote device monitoring
* Interactive presentations

#### **Performance Notes**

* Higher rates increase bandwidth usage
* Can impact battery life on mobile
* May affect device performance
* Consider network latency

#### **Privacy Considerations**

* Requires explicit user permission
* Can reveal device movement patterns
* May be disabled by privacy settings
* Use responsibly

#### **Related Parameters**

* [`&sensorfilter`](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-sensorfilter.md) - Filter specific sensors
* [`&remote`](https://docs.vdo.ninja/advanced-settings/settings-parameters/remote.md) - Remote control features
* [`&ptz`](https://docs.vdo.ninja/advanced-settings/video-parameters/ptz.md) - Pan-tilt-zoom control
* [`&api`](https://docs.vdo.ninja/advanced-settings/api-and-midi-parameters/api.md) - API for sensor data access


---

# 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://docs.vdo.ninja/advanced-settings/setup-parameters/and-accelerometer.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.
