Link Search Menu Expand Document
Personal Projects

Accessing a USB Webcam from WSL on Windows

tools

wsl

webcam

Overview

Windows Subsystem for Linux (WSL) allows Linux applications to run directly within Windows. However, USB devices connected to Windows are not automatically exposed to the Linux environment in WSL 2.

To access a USB webcam from WSL, use usbipd-win to connect the physical device to the Linux environment. Then, verify device recognition, load the appropriate Linux kernel driver, and inspect the available video interfaces using Video4Linux2(V4L2) utilities.

This workflow covers USB webcam passthrough, device detection, driver initialization, permission management, and video capability inspection.

Prerequisites

Before starting, verify the following requirements:

  • Windows 10 or Windows 11 with WSL 2 installed.
  • A Linux distribution installed in WSL, such as Ubuntu.
  • A USB webcam connected to the Windows host.
  • Administrator access to install and configure USB device passthrough.
  • A WSL 2 kernel with USB and webcam driver support.

The procedure uses Windows Command Prompt, PowerShell, and the WSL Linux terminal. Run each command in the environment specified in the corresponding section.

Update WSL

Open Windows Command Prompt or PowerShell and update WSL.

  wsl --update

This updates the WSL components and kernel to the latest version available through the configured update channel.

Restart WSL if the update requires it. To stop running WSL distributions before restarting, execute:

  wsl --shutdown

Open the Linux distribution again after the shutdown completes.

Install usbipd-win

usbipd-win provides USB/IP functionality for attaching USB devices from Windows to WSL 2.

Open PowerShell as Administrator and run:

  winget install --interactive --exact dorssel.usbipd-win

Verify the installation:

  usbipd --version

If PowerShell cannot find usbipd, reopen the terminal and verify that the installation directory is included in the system PATH.

Identify the USB Webcam

Connect the webcam to the Windows host. Open Command Prompt or PowerShell and list the available USB devices.

  usbipd list

Example output:

  BUSID  VID:PID    DEVICE
  2-3    046d:0825  USB Camera

Identify the webcam using its device name, vendor ID, product ID, and bus ID. Record the webcam’s BUSID. In this example, the bus ID is 2-3. Your actual value will differ. If multiple USB cameras are connected, identify the correct device before proceeding.

Attach the Webcam to WSL

Bind the USB Device

In an elevated Windows terminal, bind the webcam to the USB/IP service.

  usbipd bind --busid 2-3

Replace 2-3 with the bus ID obtained from usbipd list. Binding authorizes the device for USB/IP sharing. Administrative privileges may be required.

Attach the USB Device

Attach the webcam to the running WSL 2 distribution.

  usbipd attach --wsl --busid 2-3

The command transfers access to the USB device from the Windows host to WSL. While attached, the device may no longer be available to Windows applications. Detach it from WSL when Windows applications need to use it again.

If the attachment fails, check the device status using usbipd list. Confirm that the WSL distribution is running and that the device is available for attachment.

Verify USB Detection in WSL

Open the Linux terminal and install the USB utilities package.

  sudo apt update
  sudo apt install usbutils

List the USB devices visible to Linux.

  lsusb

Confirm that the webcam appears in the output. If it does not, the USB passthrough connection may not have succeeded.

Check the running Linux kernel version:

  uname -r

Inspect recent kernel messages for USB enumeration or driver errors.

  sudo dmesg | tail -n 100

Look for messages indicating that the webcam was detected and assigned a USB device address. Errors involving USB enumeration, unsupported devices, or missing drivers may explain why the camera is unavailable.

Load the Webcam Driver

Most standard USB webcams use the USB Video Class (UVC) protocol. Linux commonly supports these devices through the uvcvideo kernel module.

Load the driver:

  sudo modprobe uvcvideo

Inspect the available video device nodes:

  ls -l /dev/video*

If the webcam is recognized and the driver initializes successfully, Linux may expose one or more device nodes, such as:

  /dev/video0
  /dev/video1

The number and purpose of these interfaces depend on the webcam hardware and driver.

Some devices expose separate interfaces for image capture, metadata, or other functions. Therefore, do not assume that every /dev/video* entry represents an independently usable camera stream.

If no video device appears, inspect the kernel messages again:

  sudo dmesg | tail -n 100

Confirm that the kernel supports the required USB webcam driver and that the device is attached correctly.

Install Video4Linux2 Utilities

Install v4l-utils to inspect camera interfaces and supported video formats.

  sudo apt update
  sudo apt install v4l-utils

List the video devices recognized by Video4Linux2:

  v4l2-ctl --list-devices

The output identifies available video devices and their associated /dev/video* paths. Use this output to determine which device node corresponds to the webcam’s capture interface.

Configure Video Device Permissions

Linux device nodes are governed by filesystem permissions and ownership. A user may be unable to access a webcam even when the device is correctly detected. Inspect the current permissions:

  ls -l /dev/video*

For example, the output may show that the device belongs to the video group. A preferred approach is to add the Linux user to that group:

  sudo usermod -aG video "$USER"

Close the current shell session and reopen it for the group membership change to take effect. Depending on the environment, logging out and back in or restarting the WSL session may be necessary. Verify the effective group membership:

  id

Avoid using chmod 666 as the default permission fix. It grants read and write access to every local user for the selected device node and may expose the camera to unintended processes.

For temporary troubleshooting, changing device permissions may help determine whether access restrictions are responsible. However, device nodes can be recreated when the device is detached, reattached, or the WSL environment restarts. Group-based access is generally preferable.

Inspect Webcam Capabilities

After identifying the correct video device, inspect its configuration and supported formats.

Display Device Information

For /dev/video0:

  v4l2-ctl -d /dev/video0 --all

For /dev/video1:

  v4l2-ctl -d /dev/video1 --all

Review the output for device identity, driver information, video capture capabilities, supported controls, and other interface properties. If a device reports no video capture capability, it may represent a non-capture interface rather than a usable webcam stream.

List Supported Video Formats

Run the following command for each relevant video device:

  v4l2-ctl -d /dev/video0 --list-formats-ext
  v4l2-ctl -d /dev/video1 --list-formats-ext

The output lists the formats, resolutions, and frame intervals supported by each interface.

Common formats include:

  • MJPG: Motion JPEG, which can reduce USB bandwidth requirements at higher resolutions.
  • YUYV: An uncompressed pixel format that generally requires more bandwidth.
  • Other formats: Availability depends on the camera hardware and Linux driver.

Use the reported capabilities to select an appropriate resolution and frame rate for computer vision, image processing, or machine learning applications.

A format listed by V4L2 indicates that the device advertises that capability. It does not, by itself, prove that a complete video stream can be captured successfully.

Troubleshooting

Symptom Likely cause Recommended action
Webcam does not appear in usbipd list Windows does not detect the USB device Check the cable, USB port, and Windows Device Manager.
Webcam appears in Windows but not in lsusb USB passthrough is not active Verify the bus ID and rerun the attachment command.
Webcam appears in lsusb but no /dev/video* exists Driver initialization failed or kernel support is missing Run sudo modprobe uvcvideo and inspect dmesg.
/dev/video* exists but V4L2 cannot access it Wrong interface or insufficient permissions Check device capabilities and group membership.
One device node reports no capture capability The node may serve a different camera function Inspect v4l2-ctl --list-devices and test another node.
Windows cannot use the webcam after attachment The device is attached to WSL Detach the device from WSL before using it in Windows.
Webcam access fails after restarting WSL The USB device is no longer attached Check usbipd list and attach the device again if necessary.

Conclusion

USB webcam access in WSL 2 requires both USB device passthrough and Linux video-device support. usbipd-win handles the Windows-to-WSL connection, while the Linux kernel’s uvcvideo driver and V4L2 utilities provide access to the camera interface.

Treat USB detection, driver initialization, device permissions, and video capture as separate validation stages. This approach isolates failures and provides a reproducible foundation for webcam-based computer vision and machine learning workflows in WSL.