Meta Quest Pro

Meta Quest Pro
File:Meta Quest Pro headset and controllers.jpg
Basic Info
VR/AR	Virtual Reality, Mixed Reality [2, 4, 6, 13, 19, 22]
Type	Head-mounted display (HMD) [2, 3, 4, 6]
Subtype	Standalone VR [13, 19, 22]
Platform	Meta Quest [2, 3, 4, 13, 19, 22]
Creator	Meta Platforms (formerly Facebook) [2, 3, 4, 6]
Developer	Reality Labs (Meta) [3]
Manufacturer	Meta Platforms [22]
Announcement Date	October 28, 2021 (as Project Cambria) [22], Official reveal October 2022 [6]
Release Date	October 25, 2022 [13, 19, 22]
Price	Original: $1,499 / £1,499 / AU$2,499 [2, 3, 4, 7, 13, 19] Reduced: $999 / £999 / AU$1,729.99 [2, 4, 6, 13, 19, 22] Discontinued [20, 21]
Website	Template:URL [21]
Versions	Single model (Black, 256GB) [2, 3, 4, 6, 13, 19, 22]
Requires	Meta account [3, 7, 11]
Predecessor	Meta Quest 2 (conceptually, not directly in product line) [2, 3, 4]
Successor	None direct (Discontinued); Meta Quest 3 is the subsequent consumer/prosumer release. [20, 21]
System
Operating System	Android-based [6, 16, 19, 22]
Chipset	Qualcomm Snapdragon XR2+ [2, 4, 6, 13, 19, 22]
CPU	Octa-core Kryo 585 (1 x 2.84 GHz, 3 x 2.42 GHz, 4 x 1.8 GHz) [22]
GPU	Adreno 650 [19, 22]
HPU	N/A
Storage
Storage	256 GB [2, 4, 6, 13, 19, 22]
Memory	12 GB LPDDR5 [2, 4, 6, 13, 19, 22]
SD Card Slot	No [22]
Display
Display	2 x QLED (LCD with Quantum Dot layer and local dimming) [19, 22]
Subpixel Layout	RGB stripe [22]
Peak Brightness	Not specified in sources
Resolution	1800x1920 per eye [2, 3, 6, 13, 19, 22]
Pixel Density	Average: ~19 PPD; Peak: 22 PPD [22] (Panel offers 37% more pixels per inch than Quest 2 [4])
Refresh Rate	90 Hz (72 Hz mode available) [4, 6, 7, 13, 19, 22]
Persistence	Not specified in sources
Precision	Not specified in sources
Image
Field of View	106° horizontal, 96° vertical [3, 11, 19, 22] (Visible FoV estimates vary slightly [22])
Horizontal FoV	106° [3, 11, 19, 22]
Vertical FoV	96° [3, 11, 19, 22]
Visible FoV	Diagonal: 95.57° [22]
Rendered FoV	Horizontal: 108°, Vertical: 95.57°, Diagonal: 111.24° [22]
Binocular Overlap	~80° [22]
Average Pixel Density	~19 PPD [22]
Peak Pixel Density	22 PPD [22]
Foveated Rendering	Yes, dynamic (requires eye tracking enabled) [3, 6, 19, 22]
Optics
Optics	Pancake lenses [1, 2, 3, 4, 5, 6, 13, 19, 22]
Ocularity	Binocular [22]
IPD Range	55-75 mm hardware adjustable (manual slider) [6, 19, 22] (Visual range in setup may appear slightly smaller [19])
Adjustable Diopter	No [22]
Passthrough	Full-color Mixed Reality passthrough [2, 3, 4, 5, 6, 7, 13, 19, 21, 22]
Tracking
Tracking	6DoF Inside-out tracking via 5 external headset cameras + controller cameras [6, 7, 13, 19, 22]
Tracking Frequency	Not specified in sources
Base Stations	Not required [19, 22]
Eye Tracking	Yes, via internal cameras [3, 4, 5, 6, 7, 13, 19, 21, 22]
Face Tracking	Yes, via internal cameras [1, 3, 4, 5, 6, 7, 13, 19, 21, 22]
Hand Tracking	Yes, improved over Quest 2 [3, 4, 19, 22]
Body Tracking	Yes, via AI-based API (Movement Estimation) [19]
Rotational Tracking	Yes, 6DoF [19, 22]
Positional Tracking	Yes, 6DoF [19, 22]
Update Rate	Not specified in sources
Tracking Volume	Room-scale, defined by Guardian system [7, 13]
Play Space	Minimum 6.5 x 6.5 feet recommended for Quest 2, Pro setup emphasizes arm movement space [2]
Latency	Not specified in sources
Audio
Audio	Integrated stereo speakers with Spatial audio [2, 6, 7, 13, 17, 19, 21, 22]
Microphone	Yes, integrated microphone array [1, 6, 19, 21, 22]
3.5mm Audio Jack	Yes, dual jacks (one on each side) [2, 7, 17, 19, 22]
Camera	5 external cameras for tracking/passthrough, 5 internal cameras for eye/face tracking [6, 7, 13, 17, 19, 22]
Connectivity
Connectivity	Wi-Fi 6E, Bluetooth 5.2 [2, 6, 19, 22]
Ports	USB-C (for data/power), charging contacts [2, 7, 13, 17, 19, 22]
Wired Video	Yes, via Oculus Link (USB-C cable required, sold separately for PC VR) [1, 5, 16, 18, 19, 22]
Wireless Video	Yes, via Air Link or Virtual Desktop [5, 16, 18, 19, 22]
WiFi	Wi-Fi 6E (802.11ax) [2, 6, 19, 22]
Bluetooth	5.2 [6, 19, 22]
Power	Integrated rechargeable battery, Charging dock [2, 3, 4, 6, 13, 17, 19, 21, 22]
Battery Capacity	Not officially specified, estimated ~4500-5300 mAh range
Battery Life	Rated 1-2 hours [3, 4, 19] or 2-3 hours [2, 6] depending on usage (eye/face tracking impacts duration [5])
Charge Time	~2 hours for headset via dock/direct cable [2, 4, 6, 19]
Device
Dimensions	265mm x 127mm x 196mm (strap fully opened) [11]
Weight	722 g (1.59 lbs) [2, 3, 4, 6, 11, 13, 19, 22]
Material	Plastic, foam/leatherette padding [3, 6, 11, 17, 22]
Headstrap	Integrated rigid Halo strap with rear adjustment dial and battery [2, 3, 6, 7, 11, 13, 17, 19]
Haptics	TruTouch Haptics in controllers [2, 6]
Color	Black [2, 4, 6, 11, 13, 17, 19, 21, 22]
Sensors	5 external cameras (tracking/passthrough), 5 internal cameras (eye/face tracking), IMUs, proximity sensor, controller sensors [6, 7, 13, 17, 19, 22]
Input	Meta Quest Touch Pro Controllers, Hand Tracking [2, 3, 4, 6, 11, 13, 17, 19, 22]
Compliance	Not specified in sources
Size	N/A
Cable Length	Charging cable: ~2m (6.5 ft) [2, 19]

Property "VR/AR" (as page type) with input value "Mixed Reality]] [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Type" (as page type) with input value "Head-mounted display]] (HMD) [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Subtype" (as page type) with input value "Standalone VR]] [13" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Platform" (as page type) with input value "Meta Quest]] [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Creator" (as page type) with input value "Meta Platforms]] (formerly Facebook) [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Developer" (as page type) with input value "Reality Labs]] (Meta) [3" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Manufacturer" (as page type) with input value "Meta Platforms]] [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. <ul><li>Property "Announcement Date" (as page type) with input value "2021 (as Project Cambria) [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li> <!--br--><li>Property "Announcement Date" (as page type) with input value "Official reveal October 2022 [6" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li></ul> Property "Release Date" (as page type) with input value "2022 [13" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. <ul><li>Property "Price" (as page type) with input value "499 [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li> <!--br--><li>Property "Price" (as page type) with input value "19] Reduced: $999 / £999 / AU$1" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li> <!--br--><li>Property "Price" (as page type) with input value "729.99 [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li> <!--br--><li>Property "Price" (as page type) with input value "22] Discontinued [20" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li></ul> Property "Website" (as page type) with input value "Template:URL]] [21" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Versions" (as page type) with input value "256GB) [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Requires" (as page type) with input value "Meta account]] [3" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. <ul><li>Property "Predecessor" (as page type) with input value "Meta Quest 2]] (conceptually" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li> <!--br--><li>Property "Predecessor" (as page type) with input value "not directly in product line) [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li></ul> Property "Successor" (as page type) with input value "None direct (Discontinued); Meta Quest 3 is the subsequent consumer/prosumer release. [20" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Operating System" (as page type) with input value "Android-based [6" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Chipset" (as page type) with input value "Qualcomm Snapdragon XR2+]] [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "CPU" (as page type) with input value "4 x 1.8 GHz) [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "GPU" (as page type) with input value "Adreno 650]] [19" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Storage" (as page type) with input value "256 GB [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Memory" (as page type) with input value "12 GB LPDDR5 [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "SD Card Slot" (as page type) with input value "No [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Display" (as page type) with input value "2 x QLED (LCD with Quantum Dot layer and local dimming) [19" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Subpixel Layout" (as page type) with input value "RGB stripe [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Resolution" (as page type) with input value "1800x1920 per eye [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Refresh Rate" (as page type) with input value "90 Hz (72 Hz mode available) [4" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Pixel Density" (as page type) with input value "Average: ~19 PPD; Peak: 22 PPD [22] (Panel offers 37% more pixels per inch than Quest 2 [4])" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. <ul><li>Property "Field of View" (as page type) with input value "96° vertical [3" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li> <!--br--><li>Property "Field of View" (as page type) with input value "22] (Visible FoV estimates vary slightly [22])" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li></ul> Property "Horizontal FoV" (as page type) with input value "106° [3" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Vertical FoV" (as page type) with input value "96° [3" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Visible FoV" (as page type) with input value "Diagonal: 95.57° [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Rendered FoV" (as page type) with input value "Diagonal: 111.24° [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Binocular Overlap" (as page type) with input value "~80° [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Average Pixel Density" (as page type) with input value "~19 PPD [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Peak Pixel Density" (as page type) with input value "22 PPD [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Foveated Rendering" (as page type) with input value "dynamic (requires eye tracking enabled) [3" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Optics" (as page type) with input value "Pancake lenses]] [1" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Ocularity" (as page type) with input value "Binocular [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. <ul><li>Property "IPD Range" (as page type) with input value "55-75 mm hardware adjustable (manual slider) [6" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li> <!--br--><li>Property "IPD Range" (as page type) with input value "22] (Visual range in setup may appear slightly smaller [19])" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li></ul> Property "Adjustable Diopter" (as page type) with input value "No [22" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Passthrough" (as page type) with input value "Full-color Mixed Reality passthrough [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Tracking" (as page type) with input value "6DoF]] Inside-out tracking via 5 external headset cameras + controller cameras [6" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Base Stations" (as page type) with input value "Not required [19" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Eye Tracking" (as page type) with input value "via internal cameras [3" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Face Tracking" (as page type) with input value "via internal cameras [1" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Hand Tracking" (as page type) with input value "improved over Quest 2 [3" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Body Tracking" (as page type) with input value "via AI-based API (Movement Estimation) [19" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Rotational Tracking" (as page type) with input value "6DoF [19" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Positional Tracking" (as page type) with input value "6DoF [19" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Tracking Volume" (as page type) with input value "defined by Guardian system [7" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Play Space" (as page type) with input value "Pro setup emphasizes arm movement space [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Audio" (as page type) with input value "Integrated stereo speakers with Spatial audio [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Microphone" (as page type) with input value "integrated microphone array [1" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Audio Jack 3-5mm" (as page type) with input value "dual jacks (one on each side) [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Camera" (as page type) with input value "5 internal cameras for eye/face tracking [6" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Connectivity" (as page type) with input value "Bluetooth]] 5.2 [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. <ul><li>Property "Ports" (as page type) with input value "USB-C]] (for data/power)" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li> <!--br--><li>Property "Ports" (as page type) with input value "charging contacts [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li></ul> <ul><li>Property "Wired Video" (as page type) with input value "via Oculus Link (USB-C cable required" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li> <!--br--><li>Property "Wired Video" (as page type) with input value "sold separately for PC VR) [1" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li></ul> Property "Wireless Video" (as page type) with input value "via Air Link or Virtual Desktop [5" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "WiFi" (as page type) with input value "Wi-Fi 6E (802.11ax) [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Bluetooth" (as page type) with input value "5.2 [6" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Power" (as page type) with input value "Charging dock [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. <ul><li>Property "Battery Life" (as page type) with input value "Rated 1-2 hours [3" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li> <!--br--><li>Property "Battery Life" (as page type) with input value "19] or 2-3 hours [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li> <!--br--><li>Property "Battery Life" (as page type) with input value "6] depending on usage (eye/face tracking impacts duration [5])" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.</li></ul> Property "Charge Time" (as page type) with input value "~2 hours for headset via dock/direct cable [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Dimensions" (as page type) with input value "265mm x 127mm x 196mm (strap fully opened) [11" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Weight" (as page type) with input value "722 g (1.59 lbs) [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Material" (as page type) with input value "foam/leatherette padding [3" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Headstrap" (as page type) with input value "Integrated rigid Halo strap with rear adjustment dial and battery [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Haptics" (as page type) with input value "TruTouch Haptics]] in controllers [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Color" (as page type) with input value "Black [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Sensors" (as page type) with input value "controller sensors [6" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Input" (as page type) with input value "Hand Tracking [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Cable Length" (as page type) with input value "Charging cable: ~2m (6.5 ft) [2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

The Meta Quest Pro (codenamed Project Cambria during development, sometimes referred to as Oculus Quest Pro) is a standalone mixed reality (MR) and virtual reality (VR) head-mounted display (HMD) developed by Reality Labs, a division of Meta Platforms. Announced initially as Project Cambria in October 2021 and fully unveiled in October 2022, it was released on October 25, 2022. It represented Meta's first major push into the high-end and enterprise VR market, positioned above the consumer-focused Meta Quest 2. The headset was officially discontinued by Meta in late 2024/early 2025.

History

Development of the Quest Pro was first publicly mentioned under the codename "Project Cambria" at Meta Connect 2021 on October 28, 2021. Meta positioned it as a high-end device incorporating next-generation technologies. The final product, named Meta Quest Pro, was officially revealed at Meta Connect 2022 and launched on October 25, 2022.

The initial launch price was set at $1,499 / £1,499 / AU$2,499, significantly higher than the Quest 2, reflecting its target market of professionals, developers, and early adopters. In March 2023, Meta permanently reduced the price to $999 / £999 / AU$1,729.99, citing a desire to make the technology more accessible to businesses and professionals, likely also influenced by market competition like the HTC Vive XR Elite.

Despite the price reduction, the headset reportedly failed to gain significant market traction. In September 2024, Meta announced it was phasing out sales of the Quest Pro alongside the Quest 2. By January 2025, the Meta Quest Pro was officially listed as "no longer available" on Meta's website, with the Meta Quest 3 recommended as the alternative for mixed reality experiences.

Hardware

Design and Comfort

The Meta Quest Pro features a distinct design compared to the Quest 2, opting for a sleek, all-black finish with a glossy front panel housing external cameras. It utilizes a Halo strap design, similar to the PlayStation VR or the optional Quest 2 Elite Strap, with padded cushions resting on the forehead and the back of the head. The battery is integrated into the rear padding, counterbalancing the weight of the front visor for improved ergonomics compared to the front-heavy Quest 2. This design makes the headset feel more balanced and secure during use for many users. The strap tightness is adjusted via a dial on the rear.

Despite the balanced design, the Quest Pro is heavier than the Quest 2, weighing 722 grams (1.59 lbs). Some users reported discomfort or pressure on the forehead during extended use, potentially requiring careful adjustment or leading to headaches. A top strap, common on other headsets for additional support, is notably absent and not offered as a first-party accessory, although third-party solutions emerged.

Unlike the Quest 2's fully enclosed design, the Quest Pro has an open periphery by default, allowing users to see their real-world surroundings below and to the sides. This is intended to enhance mixed reality use cases and reduce feelings of claustrophobia. It also improves airflow around the face, reducing lens fogging and heat buildup compared to fully sealed designs. Magnetic partial light blockers for the sides are included in the box to increase immersion. A separate "Full Light Blocker" accessory was sold by Meta for $50 to create a more traditional, fully sealed VR experience, though some reviews noted it needed to be removed for dock charging.

The headset accommodates users wearing glasses, featuring an adjustable lens depth dial to move the optics further from the face.

Optics and Display

A key innovation in the Quest Pro is its use of Pancake lenses. This multi-element optical design allows for a significantly thinner visor (40% slimmer optical stack than Quest 2) and provides improved visual clarity across a larger portion of the lens compared to the Fresnel lenses used in Quest 2. This results in a larger "sweet spot" and reduced edge distortion and god rays. Text legibility is notably improved across the entire field of view.

The headset features two QLED displays (LCD panels enhanced with a Quantum dot layer) with a resolution of 1800x1920 pixels per eye. While the per-eye resolution is similar to Quest 2, the Quest Pro incorporates local dimming technology with 500 individual zones, significantly improving contrast and enabling deeper black levels than typical LCDs. The Quantum Dot layer also allows for a wider color gamut (130% larger than Quest 2's according to Meta), resulting in more vibrant colors. The display refresh rate is 90 Hz, with a 72 Hz mode available.

The Field of view (FoV) is approximately 106° horizontal and 96° vertical, an improvement over the Quest 2. Interpupillary distance (IPD) is manually adjustable via a continuous slider mechanism, supporting a range from 55mm to 75mm. While the headset uses eye tracking to guide users to the correct IPD setting, the adjustment itself is not motorized, unlike some competitors. Some users noted the IPD slider could feel loose and occasionally shift during active use.

Processor and Memory

The Quest Pro is powered by the Qualcomm Snapdragon XR2+ SoC. Meta claimed this offered 50% more sustained performance compared to the Snapdragon XR2 found in the Quest 2, primarily due to improved thermal dissipation allowing the chip to run faster for longer. However, many reviews noted that in practice, performance felt largely similar to the Quest 2 for existing applications, as the underlying GPU (Adreno 650) remained the same and most software wasn't optimized specifically for the 'Plus' variant.

The headset is equipped with 12 GB of LPDDR5 RAM, double the 6 GB found in the Quest 2. This increased memory allows for smoother multitasking, such as keeping a web browser open while running a VR application. It comes with a single storage option of 256 GB.

Audio

The Quest Pro features integrated speakers built into the head strap arms, providing Spatial audio. Reviewers generally found the audio quality to be clear, crisp, and an improvement over the Quest 2, particularly for voice clarity. Positional audio cues were effective for immersion. However, some noted a lack of bass response, resulting in a "thin" sound profile for certain content. For users preferring external audio solutions, the headset includes dual 3.5mm headphone jacks, one on each side. An integrated microphone array is used for voice input and communication.

Controllers

The Quest Pro includes redesigned controllers called Meta Quest Touch Pro Controllers. A major change is the removal of the tracking rings seen on previous Quest controllers. Instead, each controller incorporates three built-in cameras and its own Qualcomm Snapdragon 662 mobile processor, enabling independent self-tracking. This allows for full 360-degree tracking, even when the controllers are outside the headset's direct line of sight (e.g., behind the user's back), and prevents the controllers from occluding each other when held close together. Tracking accuracy was generally praised as excellent and robust.

The controllers feature improved haptic feedback, termed "TruTouch Haptics," including primary motors in the handle and secondary motors under the index trigger and thumb grip area, allowing for more localized and nuanced feedback. They retain capacitive sensors on the buttons, thumbstick, and trigger for partial finger tracking. A new pressure sensor on the thumb rest enables pinching gestures.

The controllers have built-in rechargeable batteries, replacing the AA batteries of the Quest 2 controllers. They are charged via metal contacts, typically using the included charging dock. Battery life is estimated around 8 hours. A minor drawback noted was a slight delay (a few seconds) for the controllers to sync their position with the headset upon pickup.

Attachable stylus tips are included, allowing the controllers to be flipped over and used for writing or drawing on virtual surfaces, with haptic feedback simulating surface resistance. The Touch Pro controllers are also sold separately and are compatible with the Quest 2 and Quest 3 headsets.

Sensors

The Quest Pro headset is equipped with a total of ten cameras/sensors. Five external cameras are used for 6DoF Inside-out tracking of the headset's position and orientation, Hand tracking, and capturing the mixed reality passthrough view. Five internal cameras are dedicated to Eye tracking (one per eye) and Face tracking (capturing upper and lower facial expressions). These internal sensors enable features like Foveated rendering and more expressive avatars.

Battery and Charging

The Quest Pro's integrated battery is located in the rear of the head strap. Battery life estimates vary between sources, with Meta and some reviews suggesting 2-3 hours, while others consistently found it closer to 1-2 hours, or 1.5-2 hours, particularly when features like eye/face tracking and passthrough were active. This was considered short, especially for a "Pro" device, and lower than the Quest 2's typical runtime. The headset can be used while plugged in via its USB-C port for extended sessions.

A charging dock is included, designed to charge both the headset and the controllers simultaneously via contact points. A full charge for the headset takes approximately 2 hours. Some users found positioning the headset and controllers correctly on the dock could be finicky.

Features

Mixed Reality (Color Passthrough)

One of the headline features of the Quest Pro is its full-color Mixed Reality passthrough capability, a significant upgrade from the monochrome passthrough on the Quest 2. This allows users to see their real-world environment in color while wearing the headset, enabling experiences that blend virtual elements with physical surroundings. The passthrough provides a stereoscopic, depth-correct view of the environment.

While considered a major step forward, reviews consistently noted that the image quality of the passthrough was grainy, somewhat fuzzy, and lacked detail, especially in lower light conditions. Reading text on phone screens or documents through passthrough was difficult or impossible. Moving objects like hands could exhibit ghosting or lag effects. While sufficient for environmental awareness and basic navigation, the quality was deemed not high enough for seamless interaction with fine details in the real world.

The headset initially lacked automatic room meshing capabilities due to the absence of a dedicated depth sensor (reportedly planned but cut before launch). Users needed to manually define walls and furniture using a controller-based setup tool for room-aware MR applications, which was considered cumbersome.

Eye and Face Tracking

The Quest Pro was Meta's first headset to incorporate integrated Eye tracking and Face tracking, utilizing five internal cameras. Eye tracking enables Foveated rendering, an optimization technique where the headset renders the area the user is directly looking at in higher detail, potentially improving performance and visual quality without increasing processing load. Eye tracking also helps with automatic IPD calibration guidance.

Face tracking captures the user's facial expressions (mouth movements, smiles, frowns, eyebrow raises, etc.) and maps them onto their virtual avatar in real-time. This is intended to make social interactions in VR feel more natural and expressive.

While the technology was considered impressive by some, its practical application at launch and throughout the headset's life was limited. Few applications took full advantage of these features. Some users found the avatar facial expressions could appear uncanny or inaccurate at times, especially over network connections. Tongue tracking was not supported at launch. Concerns were also raised regarding the privacy implications of collecting eye and facial data, though Meta stated this data was processed on-device and deleted, and the features were opt-in.

Hand Tracking

The Quest Pro supports controller-free Hand tracking, leveraging its external cameras. The tracking quality was considered slightly improved compared to the Quest 2, likely due to better cameras. Meta also introduced experimental interaction models like "Direct Touch," allowing users to "press" virtual buttons and keyboards with their fingers. However, hand tracking performance could degrade in suboptimal lighting conditions and some found it could still feel jittery or required unnatural hand positions.

Software and Ecosystem

The Meta Quest Pro runs on an Android-based operating system, sharing the same core platform and app store as the Meta Quest 2 and Quest 3. It is fully backward compatible with the existing Quest library of games and applications.

While compatible with the large Quest library, a dedicated section for Quest Pro-optimized apps existed but remained sparsely populated throughout its availability. Few apps were specifically designed to leverage the Pro's unique features like advanced MR, eye tracking, or face tracking.

Meta heavily promoted Horizon Workrooms, its virtual collaboration platform, as a key use case for the Pro. Workrooms allows users to meet as avatars, use virtual whiteboards, and project their computer screens onto multiple virtual monitors. However, reviewers often found the Workrooms software clunky, unintuitive, or buggy, particularly the setup process and integration with real-world devices. Horizon Worlds, Meta's social VR platform, also supported the Pro's face tracking features.

The user interface (UI) and user experience (UX) received some criticism for being unintuitive or buggy at times, with some long-standing issues seemingly carried over from the Quest 2 platform.

For PC VR experiences, the Quest Pro supports both wired Oculus Link (requiring a suitable USB-C cable, not included for this purpose) and wireless Air Link connectivity. This allows access to PC VR content libraries like SteamVR. Some users reported issues with Air Link stability or performance without optimized network conditions.

Reception

The Meta Quest Pro received mixed reviews upon release. Praise was commonly directed towards its hardware innovations:

• Display Clarity & Optics: The Pancake lenses and improved display quality (clarity, color, contrast) were frequently highlighted as significant upgrades over the Quest 2.
• Comfort & Design (for some): The balanced Halo strap design was found comfortable by many, especially compared to the Quest 2's default strap. The open periphery design was appreciated for reducing claustrophobia and improving airflow.
• Controllers: The self-tracking Touch Pro controllers were lauded for their accuracy, improved haptics, and compact design.
• Standalone Performance: As a powerful standalone device without PC tethering requirements, its convenience was noted.

However, the headset also faced significant criticism:

• Price: The initial $1,500 price point was widely considered excessive, especially given the limited software taking advantage of its advanced features, making it poor value for most consumers. Even after the price cut to $1,000, it remained expensive compared to alternatives like the Quest 2 or the later Quest 3.
• Battery Life: The short battery life (often 1-2 hours in practice) was a frequent complaint.
• Mixed Reality Quality: The color passthrough, while novel, was criticized for its grainy, low-resolution image quality, limiting its practical use.
• Comfort (for others): Despite the balanced design, the headset's weight and pressure on the forehead caused discomfort or headaches for some users.
• Software and Use Cases: A major recurring criticism was the lack of compelling software and clear use cases that justified the Pro's advanced features and high cost. Eye/face tracking felt underutilized, and productivity software like Horizon Workrooms was often described as clunky or unfinished.
• Target Audience Confusion: Many questioned who the headset was truly for, feeling it was caught between the consumer gaming market (better served by Quest 2/3) and a professional market that wasn't fully ready for its specific feature set or found its implementation lacking.
• Privacy Concerns: The inclusion of eye and face tracking raised privacy concerns among some users and reviewers, given Meta's history with data collection.

Overall, the Quest Pro was seen as an technologically impressive but ultimately niche product – a showcase of future VR/MR technologies that arrived too early, at too high a price, and without the software ecosystem needed to make it essential.

Discontinuation

In September 2024, Meta confirmed it would stop selling the Quest Pro once existing inventory ran out, alongside the original Quest 2. By January 2025, the product was marked as "no longer available" on official channels. The Meta Quest 3, launched in October 2023, incorporated some of the Pro's advancements (like pancake lenses and improved color passthrough) at a much lower price point ($499), effectively superseding the Pro for most potential users interested in mixed reality. While Meta CTO Andrew Bosworth hinted a future "Pro" model wasn't entirely ruled out, reports suggested plans for a direct successor had been cancelled.