Web Bluetooth API allows web applications to communicate with nearby Bluetooth Low Energy (BLE) devices directly from the browser. This scanner uses the navigator.bluetooth.requestDevice() method to discover devices and navigator.bluetooth.getDevices() to retrieve previously authorized devices. When you click the scan button, the browser opens a native device chooser dialog showing all discoverable BLE devices in range. After selecting a device, you can connect to it and explore its GATT services and characteristics.

Key Features:

• Scan for nearby BLE devices via native browser dialog
• View previously authorized devices automatically
• Connect/disconnect with one click
• Explore GATT services & characteristics
• Persistent scan history via local storage

Supported Browsers: Google Chrome (desktop & Android), Microsoft Edge, Opera, Samsung Internet, and Brave. Not supported: Firefox, Safari (limited experimental support in recent versions).

Platform Requirements:

• Desktop: Windows 10+, macOS 10.14+, ChromeOS, Linux (with BlueZ 5.41+)
• Mobile: Android 6.0+ with Chrome; iOS support is limited and requires enabling experimental features
• Security: Must be served over HTTPS (or localhost for development)
• Bluetooth: Computer must have Bluetooth 4.0+ hardware (BLE support)

This is a deliberate privacy and security design of the Web Bluetooth API. Unlike native apps, web browsers require explicit user consent before revealing any Bluetooth devices. The requestDevice() method opens a browser-controlled dialog where you choose which device to share with the website. The website never gets a list of all nearby devices without your explicit selection. This prevents malicious websites from tracking your location or profiling your devices without your knowledge.

Workarounds: The newer requestLEScan() API (experimental in Chrome) allows continuous scanning with RSSI data, but still requires user permission and is not widely supported yet. Once you've authorized a device, getDevices() can retrieve it without additional prompts.

No. The Web Bluetooth API is designed exclusively for Bluetooth Low Energy (BLE / Bluetooth 4.0+) devices. Classic Bluetooth devices (such as older headphones, speakers, file transfer, Bluetooth 2.0/3.0 peripherals) are not discoverable through this API. If you need to interact with classic Bluetooth devices, you'll need a native application or a platform-specific solution.

Common BLE devices that work well:

• Fitness trackers & smartwatches (Fitbit, Garmin, Apple Watch)
• BLE beacons & proximity tags (Tile, AirTag-compatible)
• Smart home sensors (temperature, humidity, motion)
• Heart rate monitors & health devices
• BLE-enabled smart locks & lights

Your privacy is protected by design:

• No data leaves your browser: All device information is stored locally using localStorage. No data is sent to any server.
• Explicit consent required: The browser forces a user gesture (click) before any Bluetooth scan can start. You choose which device to reveal.
• Limited scope: Each device connection requires separate authorization. The site can only access GATT services you've allowed.
• Revocable: You can revoke Bluetooth permissions at any time via your browser's site settings (click the lock icon in the address bar).
• No location tracking: While Bluetooth scanning can theoretically be used for proximity detection, browsers implement rate limiting and user prompts to prevent abuse.

Common issues and solutions:

1. Bluetooth is off: Ensure Bluetooth is enabled on both your computer and the target device.
2. Device not in pairing mode: Many BLE devices only broadcast when in pairing/discovery mode. Check the device manual.
3. Not a BLE device: This tool only works with Bluetooth Low Energy devices (BLE 4.0+). Classic Bluetooth devices won't appear.
4. Browser not supported: Use Chrome, Edge, or Opera. Firefox and Safari don't support Web Bluetooth.
5. Not HTTPS: Web Bluetooth requires a secure context. Ensure the URL starts with https://.
6. Android location permission: On Android, Bluetooth scanning may require Location Services to be enabled (system setting).
7. Device out of range: BLE typically works within 10-30 meters, depending on obstacles and interference.
8. Too many devices: If many devices are nearby, the dialog may take longer to populate. Wait a few seconds and try again.

GATT (Generic Attribute Profile) is the standard way BLE devices organize and expose their data. Think of it as a hierarchical database:

• Profile → A collection of services (e.g., "Heart Rate Profile")
• Service → A functional unit (e.g., "Heart Rate Service" with UUID 0x180D)
• Characteristic → A data point within a service (e.g., "Heart Rate Measurement" with UUID 0x2A37)
• Descriptor → Metadata about a characteristic (e.g., format, units, notification settings)

Common standard services:

0x1800	Generic Access
0x1801	Generic Attribute
0x180A	Device Information
0x180F	Battery Service
0x180D	Heart Rate
0x1812	Human Interface Device

• Keep Bluetooth off when not in use to minimize attack surface.
• Use "Non-Discoverable" mode on your personal devices when not pairing.
• Regularly review paired devices and remove ones you no longer use.
• Keep firmware updated on all Bluetooth devices to patch known vulnerabilities.
• Be cautious in public spaces — Bluetooth signals can be intercepted (Bluejacking, Bluesnarfing).
• Use BLE Secure Connections (LE SC) when available for encrypted pairing.
• Verify device names before connecting — attackers may spoof familiar device names.
• Revoke browser permissions for sites you no longer trust (browser Settings → Site Settings → Bluetooth).