> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/advanced-features/recordings/spatial-recordings.md).

# Spatial recordings

When you create a spatial recording in ENGAGE, you capture every action that takes place. This includes your movements within a scene, your voice, any media that you share, and any 3D models that you add or manipulate. You can choose to record just yourself, selected people, or everyone that's present in the scene.

When you play back a spatial recording, you are immersed in the events that took place, as though you were there in the location at the time of recording.

{% hint style="info" %}
You can create and playback spatial recordings only on Windows and macOS desktop devices and VR headsets.
{% endhint %}

The following video provides an overview of the spatial recording feature in ENGAGE:

{% embed url="<https://www.youtube.com/watch?v=8rR1xp_8aP8>" %}
Spatial recordings in ENGAGE
{% endembed %}


---

# 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.engagevr.io/engage/advanced-features/recordings/spatial-recordings.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.