VRChat Eye Tracking Setup: How It Works and What It Means for Your Webcam Mic

The short answer

Eye tracking in VRChat moves your avatar's eyes and eyelids from real eye-movement data instead of the default automatic eye behavior. It needs three things: hardware that can measure your eyes, software that sends that data into VRChat, and an avatar built to receive it. Eye tracking does not capture sound and does not change how VRChat picks up your voice. Your microphone, whether it is built into a webcam, a headset or a standalone unit, is selected and configured separately.

One limitation applies throughout this guide. No verified details were supplied on specific headsets, software versions, menu names or performance figures, so it explains the general setup and points out what you should confirm in current documentation for your own equipment.

How eye tracking reaches your avatar

VRChat can accept external tracking data through OSC (Open Sound Control), a messaging protocol that lets other programs on your computer send values into the game. Eye-tracking data usually arrives this way. Either a headset's own software sends it, or a community bridge application translates it. VRCFaceTracking is a widely used open-source example of such a bridge.

The data comes from one of two broad kinds of source:

• Headsets with built-in eye-tracking cameras, where the manufacturer's software or a bridge module provides the data.
• Add-on or do-it-yourself camera rigs mounted inside a headset, which use dedicated small cameras pointed at the eyes.

Whether a particular headset or camera works with a particular bridge depends on module support at the time you install it. That support was not in the supplied evidence, so check the bridge's current compatibility list before buying hardware.

General setup sequence

• Confirm your hardware can track eyes, and install and calibrate its own software first.
• Turn on OSC in VRChat's settings so the game accepts external data.
• If your hardware does not talk to VRChat directly, install a bridge application and the module for your device.
• Use an avatar set up for eye tracking. Avatars need properly configured eye bones, eyelid shapes or matching parameters, and not every avatar has them.
• Test in a mirror and adjust calibration if the eye movement looks offset or jittery.

Exact menu labels and avatar parameter names change between versions. Follow the current documentation for VRChat and for your bridge software rather than relying on fixed names.

Where your microphone fits in

Since this setup often involves cameras, people sometimes expect it to affect audio. In general it does not. A webcam normally shows up in your operating system as two separate devices, a video device and an audio input. Eye-tracking software uses camera images, not the microphone stream. VRChat takes voice from whichever audio input you select in its own settings.

• Select your microphone explicitly in VRChat rather than relying on the system default. This matters if a webcam mic, headset mic and other inputs are all connected.
• If a tracking app takes over a webcam's video, the webcam's microphone usually stays available to other apps. This is a general behavior of how operating systems separate devices. It was not tested for any specific model here.
• By default, VRChat drives avatar mouth shapes (visemes) from your voice audio. A clear, steady mic signal therefore still matters for lip sync even when your eyes are tracked.
• If you later add mouth or face tracking, mouth movement can come from camera data instead of audio. Check how your avatar and bridge handle that, because the two methods can overlap.

A webcam mic sits at arm's length or more, so it typically picks up more room sound than a headset mic. That is a general property of microphone distance, not a measured result for any device. If your voice sounds thin or echoey in VRChat, check mic placement and input selection before changing any tracking setting.

What the supplied evidence could not confirm

• Which headsets and camera kits are currently supported, and by which bridge modules.
• Current VRChat menu names, OSC addresses and avatar parameter names.
• Accuracy, latency or CPU cost of any tracking method.
• Whether desktop (non-VR) users can use webcam-only eye tracking in a supported way.
• How any specific webcam's microphone performs in VRChat.

For each of these, rely on current official VRChat documentation, your hardware maker's guidance and the bridge project's own notes.