USB Hardware & Protocol Inspector

Deep USB specification analysis, topology tree inspector (endpoints), and live I/O console

Connected WebUSB Devices

Deep USB specification analysis, topology tree inspector (endpoints), and live I/O console

No WebUSB devices detected yet. Click "Request USB Access" to select a device.

Online USB Device Diagnostics, Port Testing & Protocol Inspector via WebUSB API

This interactive online USB diagnostic workbench allows you to perform deep hardware inspection of USB ports, Type-C connectors, and connected peripheral devices directly inside your web browser using the modern WebUSB API standard. Instantly retrieve hardware metadata, identify Vendor ID (VID) and Product ID (PID), analyze endpoint topology trees, and test active byte transfers in real time.

Key Advantages of Browser-Based USB Diagnostics

Traditionally, analyzing USB hardware requires installing heavy desktop utilities (such as USBDeview, Device Manager, or custom driver suites). Our WebUSB Inspector works natively in all Chromium-based browsers (Google Chrome, Microsoft Edge, Opera, Brave, Vivaldi) on Windows, macOS, Linux, and Android:

  • Instant Vendor ID & Product ID Identification: read 16-bit VID (manufacturer) and PID (product model) hexadecimal codes (HEX).
  • USB Specification & Firmware Release Audit: inspect supported protocol speeds (USB 1.1, USB 2.0 High Speed, USB 3.0 SuperSpeed, USB 3.1, USB 3.2, Type-C) and internal firmware revision numbers.
  • Real-Time Hot-Plug Event Monitoring: track connect and disconnect events instantly to catch loose cable contacts, faulty port connections, or power supply drops.
  • Comprehensive Endpoint Topology Inspector: build visual configuration trees listing Configurations, Alternate Interface Settings, and Endpoints (Bulk, Interrupt, Control) with direction badges (IN/OUT) and packet sizes.
  • Interactive Data Transfer Console: open device connection (open), claim interface (claimInterface), and trigger raw byte transfers via transferIn / transferOut with live HEX dump and ASCII preview.
  • One-Click JSON Diagnostic Export: download complete hardware dumps formatted as structured JSON files for service engineers and embedded hardware developers.

Which Devices Work with WebUSB?

WebUSB enables web applications to communicate directly with physical USB controllers. This tool is ideal for inspecting and debugging the following device categories:

  • Microcontrollers & Development Boards: Arduino (Uno, Nano, Mega, ESP32 with native USB), STM32, Raspberry Pi Pico, Teensy.
  • Industrial & Point-of-Sale (POS) Hardware: barcode scanners, thermal receipt printers, cash drawers, RFID/NFC card readers.
  • Programmable Peripherals: hardware programmers, custom mechanical keyboards, flight controllers (Betaflight / iNav passthrough), medical diagnostic sensors.
  • Serial Adapters & Security Dongles: USB-to-UART / Serial chips (FTDI, CH340, CP2102, PL2303), hardware crypto tokens, and security keys.

Why Doesn't the Browser Detect My USB Flash Drive or Mouse?

When conducting USB diagnostics, it is important to understand the W3C security restrictions embedded into WebUSB:

  • Protected System HID Class (Mice & Keyboards): operating systems (Windows, macOS) lock HID class drivers to prevent malicious websites from injecting keystrokes or logging user input (Keyloggers).
  • Protected Mass Storage Devices: USB flash drives, external HDDs, and SSDs connected to the operating system's file system are blocked from raw byte write operations by browser security policy.
  • Mandatory Secure HTTPS Context: WebUSB requires a valid SSL/TLS HTTPS connection to ensure end-to-end security against middle-man packet manipulation.

How to Troubleshoot USB Port & Cable Failures

If a USB peripheral frequently disconnects or fails to register on your PC, follow these simple diagnostic steps:

  • Click "Request USB Access" and plug in your device. If no device appears in the browser selection prompt, check your USB cable or try a different port on your motherboard.
  • Click "Inspect Device" and verify the Vendor ID and Product ID. If IDs show 0x0000 or return initialization errors, the USB controller may suffer from insufficient power delivery or physical chip damage.
  • Review the "Topology" tab: if no Endpoints are populated or claimInterface fails, another system application or native OS driver has claimed exclusive lock over the interface.

Call Master: