Meta XR Packages
Updated: Feb 11, 2025
Oculus Integration SDK Release Deprecation
Oculus Integration SDK releases have been deprecated since version 57. For more information, including instructions on migrating from Oculus Integration SDK to Meta XR SDKs, see Import Oculus Integration SDK.Meta develops and maintains the following Unity packages for extended reality (XR) application development:
Meta XR SDKs are individual SDK packages that provide functionality for XR applications built with virtual reality or mixed reality components for Meta Quest devices. These SDKs offer features that enable you to create immersive user experiences, facilitate social connection, and optimize display hardware.
Meta XR Development Tools are software packages that enable you to develop, build, and test XR applications more quickly.
To import Meta XR packages into a Unity project, you must you meet all of the hardware and software requirements detailed in
Before You Begin.
You also need a new 3D Unity project configured for XR development. For instructions on setting up a Unity project for XR development, see
Set Up Unity for XR Development.
For advanced workflows, Meta XR packages can be downloaded as raw tarball files from
Meta’s NPM Registry, then imported into Unity via the
Unity Package Manager UI. Note that you must manage package dependencies manually by downloading and importing them from the NPM registry first.
Note: When packages are imported via UPM, package content is read-only by default. This ensures that package installations are complete replacements, reducing the risk of harming the recipient project. If you need to customize this behavior, see
Make Local Changes to Packages.
Download and import packages from the Unity Asset Store To download the latest version of Meta XR Packages from the Unity Asset Store and import them into an existing project:
- Open your project in the Unity Editor.
- Go to the Unity Asset Store and sign in using your Unity credentials.
- Navigate to the SDK package that you want to install. Select Add to My Assets. You may choose to see all your assets on the My Asset page before selecting Open in Unity, which opens the Package Manager window in the Unity Editor. Enter Unity credentials if prompted.
- On the Package Manager window, select the SDK you wish to download. Select the latest version, and then on the upper-right side of the window, select Install.
- If prompted to update OVRPlugin (a plugin that allows Unity to communicate with the VR Runtime of Meta Quest), follow the prompt to restart the Unity Editor.
Oculus Integration SDK releases have been deprecated since version 57. We recommend that you migrate your projects to Meta XR SDKs as soon as possible in order to access the latest features and improvements, including new SDKs such as
Mixed Reality Utility Kit.
Note: Migrating from the Oculus Integration SDK to Meta XR SDKs requires the removal of existing content. We recommend creating a backup of your existing Unity project before upgrading.
To migrate to Meta XR SDKs:
- Close Unity, if open.
- On your computer, go to the folder where you’ve saved the project. For example,
/username/sample-project/. - In your project, open the
Assets folder, and then delete the Oculus folders. - In your project, open the
Library folder, and then delete /Library/PackageCache/. - Re-open the project. Open in Safe Mode if prompted, as the project is likely to have compile errors.
- Follow the steps here to install Meta XR SDKs as UPM packages. We recommend starting with the Meta XR All-in-One SDK, as that package includes a similar feature set to the legacy Oculus Integrations SDK.
- If your project has errors or missing assets, this is likely because larger sample assets (such as SampleFrameworks) have been moved to Github as Unity StarterSamples. Follow the instructions here to import the assets into your project.
Common issues with migration If you followed the migration steps and are still running into issues, try the following:
- If any custom modifications were made to existing Meta XR SDK files, these custom changes must be manually merged into the new UPM-distributed Meta XR SDK files. For more information, see Import Meta XR Packages.
- There may be legacy Oculus files being referenced outside of the
Assets/Oculus folder. To clean these up, search for files beginning with the following text and manually remove them: Oculus and OVR. In addition, if you’re building an Android app, search for filenames starting or matching with AndroidManifest, vrapi, vrlib, and vrplatlib. These files are usually located in different folders of your project so it’s best to search by the filename and then remove them.
Make local changes to packages
UPM Packages are read-only by default. To make local changes, you need to make a local copy or fork of the package. This can be done in two ways:
- Copy the existing installed read-only package from the
PackageCache into the project’s Packages folder as an embedded package. For more information, see Unity’s documentation. - Download the package tarball from Meta’s NPM Registry, extract the files, and import the package as a “Local Package on Disk” via the Unity Package Manager window. For more information, see Unity’s documentation.
In the sections below, we list some of the Meta XR SDKs and tools available for download.
The
Meta XR All-in-One SDK is the easiest and fastest way to get started. The All-in-One SDK bundles several Meta XR SDKs together, such as Core SDK, Audio SDK, Interaction SDK, Platform SDK, and Voice SDK, providing a comprehensive set of features to jumpstart XR development in a single install.
If the All-in-One SDK comes with too much unnecessary content for your project, you can leverage the UPM format to pick and choose specific Meta XR packages to be included in your project. This simplifies the setup process and streamlines maintenance for developers that only need a specific subset of SDKs.
When installing from the Unity Asset Store, dependencies are resolved automatically, so you don’t need to worry about unexpected disruptions when updating any package.
The Meta XR Core SDK leverages the essential functionality of Meta XR headsets, including the following:
The Meta XR Interaction SDK adds interactions like ray, poke, locomotion, grab for controllers, hands, and controller driven hands. Each interaction is designed to be modular and work in both simple and complex VR applications. Interaction SDK also has features just for hands, including hand-specific interactions, pose and gesture detection, and debug visuals.
The Meta XR Audio SDK provides spatial audio functionality including head-related transfer function (HRTF) based object and ambisonic spatialization, as well as room acoustics simulation.
Use the Meta XR Voice SDK to bring voice interactions to your app and enhance the AR/VR experience with more natural and flexible ways for people to interact with their surroundings and each other.
Use the Meta XR Platform SDK to create social VR applications. Add Matchmaking, DLC, In-App Purchases, Cloud Storage, Voice Chat, Custom Items, Achievements, and more to your experience using the individual components of the SDK.
Meta XR Simulator is a lightweight OpenXR runtime built for developers that enables the simulation of Meta Quest headsets and features on the API level. It makes day-to-day development easier by enabling testing and debugging of apps without the need to put on and take off a headset frequently and helps scale automation by simplifying your testing environment setup.
The Mixed Reality Utility Kit provides a rich set of utilities and tools on top of Scene API to perform common operations when building spatially-aware apps.
To learn more about Meta XR packages, see the following resources:
