# 1. Quest 2 Support Status Part of [[Meta Quest 2]]. Requires Unity 6.3 LTS (6000.3.27f2) and newer. Next: [[2.Quest 2 SDK Stack]]. > [!important] Version requirement > Unity 6.3 LTS (6000.3.27f2) and newer. Status below is as of 2026-11-03. ## 1.1 The short version | Question | Answer (as of Nov 2026) | Source | |---|---|---| | Is Quest 2 still supported? | Yes, in maintenance. Horizon OS **v2.13** is the last feature OS. Security updates continue through **Dec 2027**. | [Meta legacy support](https://developers.meta.com/horizon/resources/quest-2-quest-pro-legacy-support/) | | Last SDK that supports it | **Meta VR OS SDK v213** | same | | Can I still publish a Quest 2 app? | New Quest 2 app submissions are accepted through **Dec 2027**. | same | | Do I have to drop Quest 2 for new work? | No. But new features in Meta tooling target newer devices first, so budget for it. | inference, see 1.4 | The announcement was widely reported at the time of writing ([UploadVR](https://www.uploadvr.com/meta-ends-quest-2-and-quest-pro-feature-development/), [Engadget](https://www.engadget.com/ar-vr/meta-quest-2-and-quest-pro-get-their-final-software-updates-this-month-134521336.html)). The exact announcement date is **(unverified)**; Meta's page was last updated 2026-11-02, and the Meta Help article is [here](https://www.meta.com/help/quest/1587159486071016/). ## 1.2 Targeting Quest 2 in the manifest Meta's release-manifest rules use device-targeting meta-data so your store listing hits the right headsets: | Value of `com.meta.store.defaultDeviceTargets` | Meaning | |---|---| | `quest2only\|questproonly` | Quest 2 / Quest Pro only | | `quest3+` | Quest 3 and newer | `com.oculus.supportedDevices` lists supported headsets (for example `quest2`; see the Meta manifest page for the current full list). Source: [Meta publish manifest requirements](https://developers.meta.com/horizon/resources/publish-mobile-manifest/) (page updated 2026-10-15). > [!tip] One APK or two? > If you ship one APK for Quest 2 and Quest 3, list both devices and use the runtime profile in [[5.Quest 2 Performance and Rendering]]. If Quest 2 needs a much cheaper content tier, ship it as its own build with its own targets. ## 1.3 Store requirements that affect your Unity project From the [Horizon Store VRC list](https://developers.meta.com/horizon/resources/publish-quest-req/) (updated 2026-08-19): | VRC | Required? | What it means for Unity | |---|---|---| | `Packaging.1` manifest conforms to release rules | Required | Follow [[3.Quest 2 Project and Build Setup]]; `debuggable=false` for release | | `Packaging.2` APK signature scheme v2 | Required | Use a release keystore; Unity signs v2 for Android | | `Packaging.4` supported SDK and engine version | Required | Do not ship on an old Unity or Oculus XR plugin | | `Packaging.5` APK < 1 GB, OBB < 4 GB | Required | Watch texture size; use ASTC | | `Packaging.6` 64-bit binaries | Required | IL2CPP + ARM64 only | | `Performance.1` run at the stated refresh rates | Required | See [[5.Quest 2 Performance and Rendering]] | | `Performance.3` head-tracked graphics in 4 s or a VR loading indicator | Required | Use a lightweight boot scene | | `Performance.4` at least 85% render scale most of the time | Recommended | Do not lower render scale below 0.85 | | `Functional.2` pause when Horizon OS requests it | Required (single player) | Handle `OnApplicationPause` / focus | | `Functional.10` avoid head-locked UI | Recommended | Use world-space panels, not head-locked | | `Input.4` focus-aware | Required | Keep rendering when focus is lost; hide hands; ignore input | | `Input.7`/`Input.8` hand-tracking behaviour | Required if you support hands | Respect controller/hand switches; reserve the system gesture | **Target API level.** Meta's page states apps created since **2026-03-01** must target API **34** (Android 14). Recommended values: `minSdkVersion` 32, `targetSdkVersion` 34, `compileSdkVersion` 34. Meta announced the change in [this blog post](https://developers.meta.com/horizon/blog/meta-quest-apps-android-14-march-1/). > [!warning] Unity's default is not Meta's requirement > The Meta Quest build profile in Unity 6000.3 sets **Target API level = Android 12L (API 32)** and Minimum API = Android 10 (API 29) ([Unity build profile page](https://docs.unity3d.com/6000.3/Documentation/Manual/xr-meta-quest-build-profile.html)). For a new store submission you need to raise the target to 34. See [[3.Quest 2 Project and Build Setup]]. **Vulkan.** The VRC list above requires 64-bit but does **not** list Vulkan as a separate packaging VRC. Unity's Quest profile defaults to Vulkan, and Application SpaceWarp needs it, so use Vulkan anyway. I did not find a Meta page stating Vulkan is mandatory **(unverified)**. ## 1.4 What the end of feature development means in practice - Do not rely on any Meta SDK feature newer than v213 working on a Quest 2. The Meta Core SDK was at **v207.0** on 2026-09-22, which is below 213, but whether every v20x feature works on Quest 2 is **(unverified)**; check the release notes per feature. - Plan to test on a real Quest 2 for every release, not just the simulator. - Treat Quest 2 as your **performance floor**. If it runs at 72 fps there, Quest 3 will too. ## Official references - [Meta: Quest 2 and Quest Pro legacy support](https://developers.meta.com/horizon/resources/quest-2-quest-pro-legacy-support/) - [Meta: Manifest requirements](https://developers.meta.com/horizon/resources/publish-mobile-manifest/) - [Meta: VRC guidelines](https://developers.meta.com/horizon/resources/publish-quest-req/) Next: [[2.Quest 2 SDK Stack]] ## Choosing a Unity Version Which editor build to install, given the 2025-2026 Unity security advisories, is covered in [[0.Choosing a Unity Version]]. Short version: 6000.3.27f2+ (6.3 LTS) or 6000.6.8f1+; avoid 6000.4.x and 6000.5.x.