Meta Sets a Final OS Update Date for Quest 2 and Quest Pro
Meta plans to release the last operating system update for its Quest 2 and Quest Pro headsets by March 2027, according to The Verge. The planned final build is version v213.
The update would close out feature development for both devices, but support does not end there. Meta plans to keep shipping security patches and critical bug fixes for Quest 2 and Quest Pro through the end of 2027. Developers have a longer window: apps that support either headset can be submitted through December 2027.
The schedule also runs alongside new hardware. Meta's new VR Glasses are set to launch in spring 2027. They run on the same OS and SDKs (software development kits, the toolkits developers use to build apps) as the Quest 3 and Quest 3S. The glasses are therefore not a separate software stack, and the Quest 3 line is the reference point for the platform going forward.
The broader context here is the shape of the sunset. The plan is split into three dates: a final feature OS release in early 2027, a security and critical-fix tail through the end of that year, and an app submission cutoff in December 2027. For organizations running Quest 2 or Quest Pro in managed deployments, meaning fleets of headsets that an IT team configures and controls centrally, the first date sets the end of platform change, and the second defines how long the installed base remains patched. Ten months of security coverage after the last OS build is a bounded window that fleet operators can plan around. It is also a fixed end point that will require a hardware or software decision before it arrives.
For developers, the timeline is a planning horizon rather than an immediate cutoff. Titles built against the Quest 2 or Quest Pro runtime have until December 2027 to reach those devices through submission. Because the OS and SDK base is shared with the Quest 3 and Quest 3S, work done for the newer headsets also applies to the glasses. Teams that maintain a single codebase across the Quest line may find that the main variable is the older hardware's performance envelope, rather than a separate API surface.
In my view, the more useful reading is that a defined end date gives owners of older headsets something concrete to weigh, which is better than an open-ended support posture that leaves everyone guessing. Hardware generations in consumer VR have always ended this way, and the important question for buyers is whether the announced dates are kept. The plan itself is still a plan. The final OS release, the security tail, and the glasses launch are each described as forthcoming, and their outcomes will be known only as they arrive.
