Recommended Free Tools
Yes, you can retrofit many VR headsets with DIY eye tracking. The practical result is usually an experimental or social-VR tracker—not a drop-in replacement for a validated, integrated eye-tracking headset. A typical build adds one inward-facing camera per eye, diffuse infrared illumination, ESP32-based electronics, a PC tracking application, calibration, and OSC or UDP integration.
The most accessible current open-source route is EyeTrackVR. It can be useful for avatar eye movement, blinking, pupil-related expression features, and experimental gaze interaction. It does not automatically give every VR game system-wide eye tracking, foveated rendering, or research-grade measurements.
As an Amazon Associate I earn from qualifying purchases.
What “DIY eye tracking” can mean
There are three distinct approaches:
- DIY retrofit: You add cameras, infrared emitters, mounts, wiring, controllers, firmware, and software to an existing headset.
- Commercial retrofit: You buy an add-on designed for a supported headset, such as the documented Pupil Labs Vive add-on.
- Purpose-built headset: You use hardware with factory-integrated eye tracking, such as the HTC VIVE Pro Eye.
These options differ in mechanical stability, calibration repeatability, safety documentation, software support, repairability, and research suitability. A homemade tracker can be inexpensive and flexible, but the builder is responsible for assembly, alignment, troubleshooting, and safety.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Should you build one?
DIY is a good fit if you already own a compatible PC VR headset, can make or obtain a stable mount, are comfortable with firmware and USB or Wi-Fi troubleshooting, and mainly want social-VR expression tracking or experimentation.
#1 Best Overall
- All-In-One VR Solution: The VIVE Focus series offers standalone and PC VR experiences. Harness the power of virtual reality with high-resolution displays, versatile tracking features, and immersive applications. Base station-free.
- PC VR Gaming Headset: Immerse yourself in low-latency VIVEPORT andSteamVR gameplay. DisplayPort mode delivers lossless, high-fidelity visuals straight from your PC.(1) Connect your PC directly to your Wi-Fi router using an Ethernet cable for PC VR streaming.
- Make Interactions Real: Connect in VRChat like never before. With built-in eye and low-light, hand tracking plus face and body tracker support, movement in VR is intuitive and lifelike.(2)(3)
- Immersive 5k Headset Display: The immersive display puts you right at the heart of the action with a 5K resolution of 2448 x 2448 pixels per eye, up to 120° field of view, and 90 Hz refresh rate.
- Personalize Your Fit: Auto-IPD adjustment aligns the XR headset's lenses with the centers of your pupils, giving your eyes the clearest, most comfortable viewing experience.(4)
It is a poor fit if you need plug-and-play reliability, validated gaze accuracy, guaranteed support for a particular headset, or formal eye-safety documentation. A tracker that makes an avatar blink convincingly is not automatically suitable for measuring fixations, saccades, pupil diameter, or gaze error in a study.
Quick decision guide
- VRChat avatar tracking on a budget: Consider EyeTrackVR.
- Documented hardware and research-oriented tooling: Consider a commercial add-on such as Pupil Labs hardware.
- Engine-level gaze input: Check OpenXR and vendor support before choosing a retrofit.
- Research data: Use documented hardware and independently validate accuracy, precision, sampling, latency, and calibration stability.
- No interior space or no suitable mount: DIY may be impractical regardless of the electronics.
How a DIY VR eye tracker works
Eye
│
├─ Diffuse infrared illumination
│
└─ Inward-facing IR-sensitive camera
│
└─ ESP32 camera board
│
├─ USB or 2.4 GHz Wi-Fi
│
└─ PC tracking software
│
├─ Pupil and eyelid estimates
├─ Calibration
└─ OSC / UDP / application integrationThe infrared LEDs illuminate the eye while cameras capture the pupil, iris, eyelids, and reflections. Firmware transports the camera data. PC software then estimates eye state or gaze, applies calibration, and sends derived values to an application.
This distinction matters: capturing an eye image is not the same as calculating a gaze ray. A visible pupil may support blink detection or pupil-position tracking, while accurate 3D gaze requires stable geometry, calibration, coordinate transforms, and suitable latency.
What can it track?
| Output | Difficulty | Typical use | Important limitation |
|---|---|---|---|
| Camera image | Low | Debugging | A clear image does not prove tracking quality. |
| Eye openness or blink state | Moderate | Avatar animation | Glasses, eyelashes, eyelids, and lighting affect results. |
| Pupil position in the image | Moderate | Basic gaze features | Camera coordinates are not automatically world gaze. |
| Pupil size | Moderate to high | Expression or research features | Exposure and infrared illumination strongly affect apparent size. |
| 2D gaze direction | Moderate to high | Social VR and interaction | Requires calibration and a stable mount. |
| 3D gaze ray | High | Raycasting and research | Requires geometry, calibration, and coordinate conversion. |
| Foveated rendering | High | Performance optimization | Also requires runtime and application integration. |
EyeTrackVR’s FAQ describes OSC-based output and features including eye openness and pupil-related data. It treats foveated rendering as an advanced or future direction, not an automatic result of installing the tracker.
EyeTrackVR hardware overview
The current V4-style documentation describes a typical build using two supported ESP32 camera boards, two cameras without infrared filters, a V4 infrared-emitter setup, USB-C cables, a USB hub, 3D-printed mounts, and flashed firmware. See the V4 build guide and current parts list before buying components because the hardware and instructions remain subject to change.
One documented configuration recommends two Seeed Studio XIAO Sense ESP32-S3 boards and two 130-degree no-IR cameras. The parts page also discusses 160-degree cameras as another option. A wider lens can help fit the eye inside the frame, but it may add distortion and make calibration harder. Higher resolution alone does not guarantee better gaze tracking; latency, exposure, optics, field of view, and mechanical stability matter just as much.
Documented price signals
Prices shown in the official documentation in August 2026 included approximately $28.92 for two XIAO boards, $10.82 for two 130-degree cameras, and about $37—or approximately $44 for one displayed configuration—for the official V4 mini no-solder emitter option. These are documentation-page estimates, not guaranteed checkout totals.
Rank #2
- All-In-One VR Solution: The VIVE Focus Vision offers standalone and PC VR experiences. Harness the power of virtual reality with high-resolution displays, versatile tracking features, and immersive applications. Base station-free.
- Facial tracking can help improve soft skills in presentation coaching, customer service management, workplace etiquette training, and more. Enable users to track and improve their emotional preparedness, helping to achieve better real-life outcomes
- PC VR Gaming Headset: Immerse yourself in low-latency VIVEPORT and SteamVR gameplay. DisplayPort mode delivers lossless, high-fidelity visuals straight from your PC.(1) Connect your PC directly to your Wi-Fi router using an Ethernet cable for PC VR streaming.
- Animate digital character faces for film, TV, and motion capture for AR and VR experiences with VIVE Focus Series Facial Tracker and VIVE Focus Series Eye Tracker
- Make Interactions Real: Connect in VRChat like never before. With built-in eye tracking and low-light hand tracking; plus face and body tracker support, movement in VR is intuitive and lifelike.(2)(3)
They may exclude shipping, tax, printing, cables, a USB hub, tools, replacement parts, failed components, and your existing headset. A realistic project budget must also account for time spent flashing firmware, changing mounts, calibrating, and troubleshooting.
Camera and mount requirements
Each camera must see the relevant eye at the installed distance, respond to the chosen infrared wavelength, fit without touching the eye or lenses, and maintain acceptable exposure and frame rate. A camera may require an infrared-filter removal procedure; the recommended 130-degree camera documentation specifically notes manual IR-filter removal. That work can permanently damage the camera, so test every camera before mounting it.
The mount is often more important than the nominal camera specification. The camera must remain fixed relative to the headset and eye. Calibration can become invalid when:
- The facial interface compresses differently.
- The strap position changes.
- The camera shifts during use.
- Glasses or prescription inserts alter eye relief.
- A cable pulls on the mount.
- IPD or lens position changes the eye-to-camera geometry.
EyeTrackVR maintains community and headset-specific mounts. Its claim that the system can theoretically work with any headset means that a mount can potentially be made—not that every headset offers equal comfort, image quality, cable routing, calibration stability, or software support.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsDo not attach adhesive to the camera lens or the back of the camera housing. The V4 guide specifically warns against this; attach components to the intended mount or housing surfaces instead.
Mechanical checklist
- Confirm that a suitable headset mount exists or can be designed.
- Check for unobstructed views of both eyes.
- Verify that the emitters illuminate the eyes without harsh hotspots.
- Put on the headset normally and inspect both camera views.
- Move your eyes through the intended range.
- Move your head and tighten the strap as you normally would.
- Check for cable strain, mount movement, eyelash contact, and lens interference.
- Repeat the inspection with glasses or prescription inserts if applicable.
End-to-end build workflow
1. Define the goal
Decide whether you need VRChat avatar animation, blink tracking, pupil-related expression data, gaze interaction, Unity or Unreal input, research data, or foveated-rendering experimentation. The goal determines how much accuracy, latency, validation, and application integration you need.
2. Check the headset
Verify interior clearance, mount availability, facial-interface geometry, cable paths, USB access, and whether processing will run on a PC or a standalone headset. EyeTrackVR’s live documentation should be treated as the authority for current board and mount compatibility.
Rank #3
- All-In-One VR Solution: The VIVE Focus series offers standalone and PC VR experiences. Harness the power of virtual reality with high-resolution displays, versatile tracking features, and immersive applications. Base station-free.
- PC VR Gaming Headset: Immerse yourself in low-latency VIVEPORT andSteamVR gameplay. DisplayPort mode delivers lossless, high-fidelity visuals straight from your PC.(1) Connect your PC directly to your Wi-Fi router using an Ethernet cable for PC VR streaming.
- Make Interactions Real: Connect in VRChat like never before. With built-in eye and low-light, hand tracking plus face and body tracker support, movement in VR is intuitive and lifelike.(2)(3)
- Immersive 5k Headset Display: The immersive display puts you right at the heart of the action with a 5K resolution of 2448 x 2448 pixels per eye, up to 120° field of view, and 90 Hz refresh rate.
- Personalize Your Fit: Auto-IPD adjustment aligns the XR headset's lenses with the centers of your pupils, giving your eyes the clearest, most comfortable viewing experience.(4)
3. Choose wired or wireless transport
Wireless reduces cables but depends on reliable 2.4 GHz networking and can be affected by antenna placement, congestion, and transport variability. Wired is easier to reason about during debugging but adds cables, USB requirements, and strain-management problems. Neither mode is universally faster; the result depends on camera settings, firmware, network conditions, PC processing, and the application pipeline.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →4. Test and prepare the cameras
Confirm that both cameras work before modifying or mounting them. If a camera requires IR-filter removal, follow the current project guidance carefully. Removing the filter changes visible-light behavior and can damage the module. Keep the lens clean and avoid assuming that a camera that works in normal light is suitable for infrared eye imaging.
5. Prepare the ESP32 boards
Follow the live guide for firmware, board selection, drivers, Wi-Fi configuration, device names, and wired setup. Depending on the configuration, the software may identify devices by COM port or network names such as ETVR-left.local. These details can change between versions, so do not treat them as universal commands.
6. Assemble the infrared emitters
Use the recommended emitter type, wiring, resistors, and safety settings. Do not substitute focused emitters, increase current to obtain a brighter image, bypass firmware protections, or assume invisible light is harmless. Use the official emitter kit or components specified by the current documentation wherever possible.
7. Install mounts and route cables
- Install the headset-specific mounts.
- Position each camera at the intended angle.
- Attach the emitter assembly.
- Route wires away from the lenses, eyelids, and moving facial-interface areas.
- Secure slack without pulling the mount out of alignment.
- Check comfort, airflow, facial pressure, and lens clearance.
- Inspect both camera views after reassembling the interface.
8. Flash firmware and identify devices
Each camera should appear to the host, have a unique left or right identity, produce a usable stream, and remain connected without repeated resets. If something fails, test one eye at a time, swap USB cables, swap board positions, reflash the board, verify the selected port, and test with the other transport mode. An unstable USB hub or poorly placed antenna can look like a firmware problem.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
9. Run the tracking software
The PC client receives camera data, processes eye images, applies calibration, and sends output through OSC or UDP. Expect separate stages for device discovery, left/right assignment, image preview, camera adjustment, calibration, output enablement, and application integration. Exact labels may change as the project develops; use the current EyeTrackVR documentation for version-specific instructions.
10. Calibrate and integrate
Calibration is not a one-time installation step. Repeat it after moving the headset, changing IPD or eye relief, replacing the facial interface, changing strap position, adding or removing glasses, moving the cameras, changing users, or modifying exposure and lighting.
Rank #4
- Bundle includes: Crystal Super VR Headset with Micro-OLED + complementary accessory: Studioform Face Cushion Covers Face Pad Kit
- Ultra-HD Micro-OLED Displays: Boasting an impressive 3840 × 3552 pixels per eye, these displays render razor-sharp textures and lifelike environments, setting a new benchmark for visual realism in VR.
- Wide-Angle Optics:The 116° horizontal FOV closely mirrors human peripheral vision, eliminating the "tunnel effect" and pulling you deeper into the action.
- High Refresh Rate Engine:With a 90Hz refresh rate, the display keeps pace with your fastest reactions, virtually eliminating ghosting and reducing eye strain during extended play.
- Sub-Millimeter 6DOF Precision:Leveraging state-of-the-art 6DOF spatial tracking, the headset translates even the slightest head movements into the virtual space with zero latency and absolute accuracy.
Distinguish per-eye calibration from combined-gaze calibration, screen-space calibration from world-space gaze, static accuracy from dynamic accuracy, precision from accuracy, and spatial error from latency. Do not attach a degree-level accuracy claim to a DIY build unless it has been measured under stated conditions.
Application support
Social VR and VRChat
EyeTrackVR is designed around OSC and UDP-style integration and documents VRChat-related routes including VRC Native Eye Tracking and VRCFaceTracking parameters. In practice, you may still need a compatible avatar, correct parameter mappings, middleware such as VRCFaceTracking, correct OSC ports and permissions, and application-specific configuration.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteIf the tracker works in its preview but the avatar does not move, check left/right assignment, output status, destination address and port, middleware connection, avatar parameters, and whether the avatar actually implements the relevant expressions. An exaggerated or unresponsive result can be an avatar-mapping problem rather than a camera problem.
Unity and Unreal
A DIY OSC stream is not automatically equivalent to an OpenXR eye-gaze interaction profile. A developer may need to consume the stream directly, write a bridge, or use middleware. For integrated VIVE hardware, HTC documents eye-tracking access through OpenXR extensions such as XR_EXT_eye_gaze_interaction and vendor APIs:
Standalone headset development
Meta’s OpenXR SDK includes eye-tracking-related extensions for supported devices, including XR_FB_eye_tracking_social for Quest Pro. Those extensions apply to supported built-in hardware and software paths; attaching cameras to a headset does not automatically make the retrofit visible to the headset’s native OpenXR runtime.
Calibration and performance expectations
DIY performance is highly dependent on fit and setup. Expect the center of gaze to be easier than extreme gaze angles, and expect performance to change with glasses, contact lenses, eyelashes, makeup, reflections, sweat, fogging, pupil dilation, and facial-interface movement.
Free tools Windows power users keep installed
One-click scans. No signup required.
Do not confuse these concepts:
- Accuracy: How close the reported gaze is to the true target.
- Precision: How tightly repeated measurements cluster.
- Latency: The delay from eye movement to usable application output.
- Frame rate: How frequently images or estimates are produced.
- Reliability: How consistently the system maintains tracking during real use.
A high camera frame rate does not guarantee low end-to-end latency, and low latency does not guarantee accurate gaze. The full path includes exposure, transport, processing, calibration, middleware, and application response.
Best Value
- INCLUDED - 3 HTC VIVE Trackers (3.0), USB Cables (USB-C), USB Dongles, Dongle Cradles (USB-C), Adorama 1 Year Warranty, Rebuff Reality TrackBelt + 2 TrackStraps.
- FULL BODY IMMERSION - Experience unparalleled VR tracking accuracy with the VIVE Tracker 3.0, capturing your every movement for realistic in-game interactions.
- SEAMLESS INTEGRATION - Effortlessly connect the VIVE Tracker 3.0 via USB and secure it with the included TrackBelt and TrackStraps for stable, low-latency performance.
- EXPANDED VR CAPABILITIES - Unlock new levels of gameplay and creativity with full body tracking, compatible with a wide range of VR games and applications on SteamVR.
- COMFORT AND DURABILITY - The Rebuff Reality TrackBelt and TrackStraps provide a comfortable and secure fit, ensuring long-lasting performance during intense VR sessions.
Troubleshooting
No camera or missing ESP32
- Test one board and one eye at a time.
- Try another USB cable and port.
- Check the selected COM port or network device name.
- Confirm that the board variant matches the firmware.
- Reflash the board using the current project instructions.
- Try a powered or different USB hub if the board resets under load.
No infrared illumination
- Check LED polarity and wiring.
- Verify the emitter kit or documented resistor configuration.
- View the emitters through an IR-sensitive camera.
- Do not increase current as a troubleshooting shortcut.
Image is visible but tracking is poor
- Check that the full eye is visible at normal headset fit.
- Look for eyelid, eyelash, glasses, or lens reflections.
- Adjust camera angle and exposure within the documented software controls.
- Inspect distortion from a wide-angle lens.
- Recalibrate after securing the mount.
- Test whether cable tension or facial-interface movement shifts the camera.
Tracking works but the application does not respond
- Confirm that output is enabled.
- Check the OSC or UDP destination and port.
- Verify left/right channel assignment.
- Confirm that middleware is running and receiving data.
- Check avatar parameters or engine input mappings.
- Determine whether the application expects OpenXR or a vendor SDK rather than OSC.
Wireless instability
Test wired transport to isolate the problem. Check 2.4 GHz congestion, antenna placement, distance, metal obstructions, and power stability. The live parts guidance discusses external antenna considerations for poor ESP-CAM signal quality.
Calibration drift
Recheck headset fit, mount rigidity, facial-interface compression, glasses, IPD, eye relief, and cable strain. If the mount moves between calibration and use, software cannot reliably correct the resulting geometry change.
Eye safety
Do not independently describe a homemade infrared assembly as “eye-safe.” EyeTrackVR says its default configuration is designed around relevant safety thresholds, but it places responsibility on the builder and recommends non-focused emitters, documented components, safety settings, and checking brightness with an IR-capable camera. It also advises stopping immediately if the eyes feel warm or uncomfortable.
The project’s indexed documentation contains different numerical references, including radiant-intensity figures in mW/sr and an electrical-current reference in mA. These are different units and must not be treated as interchangeable. Follow the current safety guidance rather than combining figures from different pages.
Use the official emitter kit or documented components. Never use laser-like or focused emitters, bypass protections, or increase current for brightness. Readers who need formal compliance or documented safety should choose commercially engineered hardware instead of a homemade IR assembly.
Privacy and data handling
Eye tracking can reveal attention, visual exploration, fatigue-related signals, and other sensitive behavioral information. EyeTrackVR presents itself as privacy-focused and PC-hosted, but you should still inspect the actual client, middleware, logs, and network configuration.
- Determine whether raw camera frames remain on the PC.
- Check which derived parameters are sent to VRChat, a game, or middleware.
- Review whether logs store images or tracking data.
- Avoid exposing OSC endpoints unnecessarily to other networks.
- Disable or restrict network services you do not need.
DIY versus commercial alternatives
| Criterion | DIY retrofit | Commercial or integrated tracking |
|---|---|---|
| Initial hardware cost | Potentially low, excluding tools and time | Usually higher |
| Mechanical integration | User-designed and headset-dependent | Factory-aligned or documented |
| Safety validation | Builder responsibility | Vendor-controlled design and documentation |
| Software integration | Often OSC or custom middleware | Vendor SDK or OpenXR path may be available |
| Headset choice | Broad if a stable mount fits | Limited to supported hardware |
| Consistency | Variable | Usually more predictable |
| Repairability | High if parts are available | Often lower |
| Tinkering | Required | Usually minimal |
Pupil Labs
Pupil Labs’ VR and AR documentation provides a more documented add-on route, including a Vive add-on. Its Core DIY instructions require advanced hardware work such as fine soldering, and Pupil Labs states that the DIY kit is not for commercial use. This route is better suited to technically advanced users who value documented tooling and research-oriented workflows.
HTC VIVE Pro Eye and Tobii
The HTC VIVE Pro Eye has integrated tracking and a documented vendor stack. Tobii lists 120 Hz binocular output, five-point calibration, and approximately 0.5°–1.1° stated accuracy for the device. It also documents gaze origin, gaze direction, pupil position, pupil size, eye openness, and timestamps.
Those specifications apply to the VIVE Pro Eye, not to DIY hardware. It is an older, specialized headset, so regional availability, used-market condition, price, and SDK support should be checked before purchase.
Bottom line
Build a DIY tracker if you are a maker who wants affordable social-VR eye and expression tracking and accepts evolving hardware, calibration work, and troubleshooting. Choose a commercial add-on or integrated headset when reliability, safety documentation, vendor integration, or defensible research measurements matter more than experimentation and repairability.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
