TL;DR
- Your apps keep working. People on Quest 2 and Quest Pro can still find, buy, download, and play your apps, and cross-play with Quest 3 and Quest 3S remains.
- You can keep shipping updates to existing Quest 2 and Quest Pro apps.
- v2.13 is the final OS release for Quest 2 and Quest Pro, reaching all devices in March 2027. Quarterly security patches and critical bug fixes continue through the end of 2027.
- New app submissions for Quest 2 and Quest Pro close December 2027.
When Quest 2 launched in October 2020, it brought millions of people into VR and gave developers an initial audience large enough to sustain a business. Quest Pro followed in 2022 and put eye tracking, face tracking, and color passthrough in developers' hands early. Many of you shipped your first VR titles on these devices. VR is about to take another leap forward with the launch of Meta VR Glasses next spring.
So, with Quest 3 and Quest 3S now the baseline for Meta VR gamers, and Meta VR Glasses coming soon, Quest 2 and Quest Pro are reaching the end of feature development. We're sharing the full timeline today so you have a runway to decide how you want to support these players.
What's changing
Feature development for Quest 2 and Quest Pro ends with v213, which reaches all Quest 2 and Quest Pro devices by March 2027. v2.13 is the final OS release and v213 is the last supported SDK version for these devices. New OS features, platform capabilities, and APIs released after v213 will only be available on Quest 3, Quest 3S, and newer devices.
After v213, we'll keep shipping security patches and critical bug fixes through the end of 2027. We won't test new OS and SDK releases against Quest 2 and Quest Pro, so if your app keeps targeting them, please test on those devices.
New apps that support Quest 2 or Quest Pro can be submitted through December 2027. After that, new titles can still launch on Quest 3, Quest 3S, and newer devices, but won't be offered on Quest 2 or Quest Pro.
What's staying the same
- Your apps and your revenue. Apps and games on Quest 2 and Quest Pro keep working, solo and multiplayer alike. The Store stays open on these devices, people keep access to everything they've purchased, and no apps will be removed from the Store because of this change.
- Your updates. You can keep publishing updates to existing Quest 2 and Quest Pro apps, whether that's a bug fix, a content drop, or a seasonal event.
- Cross-play. Multiplayer between Quest 2, Quest Pro, and Quest 3/3S stays supported, so player communities don't get split by device.
- Platform features your app relies on. Platform SDK features, the last release of Meta Avatars SDK, and PC VR via Link continue to work on Quest 2 and Quest Pro.
Key dates
| Date | Milestone |
|---|---|
March 2027 | v2.13, the final OS release, and v213, the last supported SDK version, reaches all Quest 2 and Quest Pro devices |
December 2027 | Final security patch; last day to submit new apps for Quest 2 and Quest Pro |
Plan your next steps
Start by checking how much of your active audience is on Quest 2 and Quest Pro. Go to your Developer Dashboard, select your app > Analytics > User engagement and select “Devices” under Breakdown.
To keep supporting Quest 2 and Quest Pro, you can either keep one build that stays compatible with v213, or split into separate builds with device targeting so your main build can adopt newer features on Quest 3 and Quest 3S. With a single build, keep your minSdkVersion at or below what v213 supports, and avoid SDK versions or APIs that need a newer OS unless you check for them at runtime and fall back gracefully. That approach works well in the near term, but as newer devices move the minimum OS version forward, staying on a single v213-compatible build will become increasingly limiting so plan for splitting builds in the long term. Either way, you’ll need to continue to test your app on Quest 2 and Quest Pro.
To end support for Quest 2 or Quest Pro, our App Policies require at least 180 days' notice to your customers before you end support in a way that causes them to lose access to content or essential services. Device targeting lets you freeze a final build for those devices, and you can stop selling the app on them through your app submission.
For multiplayer titles, test sessions across your Quest 2 and Quest 3/3S builds every time you update either one. Meta keeps cross-play working at the platform level, but compatibility between your own builds depends on how you manage them.
Looking ahead
Quest 2 and Quest Pro laid the foundation for this platform, and millions of people still play on them. Quest 3 and Quest 3S give your apps more performance headroom and mixed reality built in, and apps built for them carry forward to Meta VR Glasses, which run on the same OS and SDKs.
If you're focusing on Quest 3 and Quest 3S, grab the latest SDK (Unity | Unreal | Native) and look for quick GPU wins like Dynamic Resolution (Unity | Unreal). To get your app ready for Meta VR Glasses, start with Get started with Meta VR Glasses.
Resources
If you have a dedicated Developer Relations contact at Meta, reach out if you have questions specific to your titles. Otherwise, bring your questions to the Developer Forum.
Tune in for all of the latest developer updates: subscribe to our monthly newsletter and follow us on X and Facebook.