> 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/accessing-files-on-your-device/changes-to-file-storage-in-engage-v3.5.md).

# Changes to file storage in ENGAGE v3.5

With the release of ENGAGE v3.5 (August 3rd, 2023), the following changes have been made to the storage of files on VR devices:

* The location to which ENGAGE-specific files are saved has changed. The affected files are camera pictures, snapshots, recordings, and experiences (formerly sequences).
* Your existing ENGAGE-specific files will be copied to the new location.
* All files will be deleted from the previous file location.
* All newly created files will be saved to the new location only.

{% hint style="danger" %}
If you uninstall the application, all of your ENGAGE-specific files that are stored on the device will be deleted. We recommend that you back up your files to a different device before you uninstall the application.
{% endhint %}

## File locations

ENGAGE v3.4 and earlier saved files to the following location on VR devices:

`\Internal shared storage\Documents\ENGAGE`

ENGAGE v3.5 now saves files to the following location on VR devices:

`\Internal shared storage\Android\data\com.ivre.engage\files\ENGAGE`

{% hint style="info" %}
On some devices, instead of `Internal shared storage`, the root directory may be listed as `sdcard` or some other name.
{% endhint %}

## ENGAGE files and subfolders

In the file location described in the previous section, there are several subfolders. To access files in the ENGAGE application, you must place them in the appropriate subfolder for their file type.

<table><thead><tr><th width="196.33333333333331">Subfolder</th><th width="342">Purpose</th><th>File types</th></tr></thead><tbody><tr><td>IFXSnapshots</td><td>Arrangements of IFX that you have saved for later use. For more information, see <a data-mention href="/engage/experience-editor/working-with-objects/snapshots.md">Snapshots</a>.</td><td>.ifxsnap</td></tr><tr><td>MyLessons</td><td>Experience files. Animations or interactive experiences that you have created in the Experience Editor. For more information, see <a data-mention href="/engage/experience-editor/experience-management/creating-a-new-experience.md">Creating a new experience</a>.</td><td>.engage</td></tr><tr><td>MyRecordings</td><td>Spatial recordings that you have created within Sessions. For more information, see <a data-mention href="/engage/advanced-features/recordings.md">Recordings</a>.</td><td>.myrec</td></tr><tr><td>Pictures</td><td>Images that you have captured with the ENGAGE camera. For more information, see <a data-mention href="/engage/advanced-features/taking-a-picture-with-the-engage-camera.md">Taking a picture with the ENGAGE camera</a>.</td><td>.png</td></tr></tbody></table>

## FAQs

### Why was this change made?

Most stand-alone VR headsets use the Android operating system. To improve security, recent versions of the Android operating system restrict which file locations applications have access to. For more information, refer to [*Storage updates in Android 11*](https://developer.android.com/about/versions/11/privacy/storage). Meta now requires that we use the latest version of Android, for which these restrictions are mandatory. For more information, refer to [*Meta Quest Apps Must Target Android 12L Starting June 30*](https://developer.oculus.com/blog/meta-quest-apps-android-12l-june-30/). To maximize security and stability, we have applied the update across all supported stand-alone VR headsets.

### Does this affect Android phones and tablets?

No. ENGAGE for Android phones and tablets already uses the file location that's required in the latest versions of the Android operating systems. Also, the features that would create files, such as IFX and recordings, are not available on phones or tablets.

### Does this affect Cloud File Manager files?

No. ENGAGE Cloud File Manager files are stored remotely on ENGAGE servers, and so are unaffected by this change. If you have access to the Cloud File Manager, we recommend that you use that as the main location to store important files. You can then easily access your files on any device and restore your files if you need to uninstall the application or factory reset a device.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.engagevr.io/engage/advanced-features/accessing-files-on-your-device/changes-to-file-storage-in-engage-v3.5.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.