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:

Name	Description
Meta XR SDKs	Provide functionality for XR applications built with virtual reality or mixed reality components for Meta Quest devices. These SDKs enable you to create immersive user experiences, facilitate social connection, and optimize display hardware.
Meta XR Development Tools	Packages that enable you to develop, build, and test XR applications quickly.

For the full list of Meta XR packages offered as UPM packages, see the Developer Center, the Unity Asset Store, or the Meta NPM Registry.

Import packages

Meta XR packages are created and managed using Unity’s package management system, Unity Package Manager (UPM).

We recommend downloading Meta XR packages from the Unity Asset Store, which contains all the Meta XR packages. Packages and dependencies are automatically managed, making it easy to get started with XR development. For instructions, see Download and import packages from the Unity Asset Store.

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.

To set up a new Unity project for XR development, see Set up Unity for XR development.

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.

To update or switch to different package versions on Unity Asset Store, see Unity’s documentation for your respective editor version. Note that the package must be “Added to My Assets” in order to browse package versions.

Migrate to Meta XR SDKs from Oculus Integration SDK

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 on Copying a Unity Package from the Cache.

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. See Install a UPM package from a local folder for more information.