HomeAll ToolsBluetooth

Web Bluetooth Scanner

Scan & Connect to BLE devices directly from the browser (Chrome/Edge only).

environment and support

Web Bluetooth
Does not support Web Bluetooth
Security context (HTTPS)
no
Bluetooth availability (getAvailability)
Unknown/not supported
User-Agent
-
Your current browser may not support Web Bluetooth
It is recommended to use the desktop version of Chrome / Edge (HTTPS environment). iOS Safari generally does not support this.
readyequipment:-
current device
name: -
ID:-
connect:Not connected
Recently disconnected:-
Advertising/Broadcasting (optional)
Supported by some Chrome versions/devices for observing RSSI/broadcast persistence.

GATT Services/Characteristics

Total 0 services / 0 characteristics
No data yet. Please Connect first, then click Enumerate Services.

log

No logs yet. It is recommended to click "Scan Device" to start.

How to use this page to quickly locate problems

First look at "Environment and Support": it must be in HTTPS/security context; desktop version Chrome/Edge is recommended. iOS Safari generally does not support Web Bluetooth.
Scanning must be triggered by user gestures such as "clicking a button"; otherwise, it is easy to report NotAllowedError or be intercepted by the browser.
Unable to connect/frequently disconnected: Move closer to the device to reduce obstruction and 2.4GHz interference; turn off the system Bluetooth and then turn on or restart the device; avoid being occupied by other devices/applications.
Unable to enumerate services/features: Add the target service to optionalServices (the browser will restrict access to undeclared services).
Need assistance in troubleshooting: Click "Copy Report" to provide the UA, status, errors and logs to development/customer service.

Bluetooth Guide

Scan, Pair, and explore GATT services via Web Bluetooth.

Step 1

Confirm environment and browser support

about 10 seconds

Make sure to access under HTTPS and use a browser that supports Web Bluetooth.

In the "Environment & Support" card confirm: Web Bluetooth is "Supported" and "Security Context (HTTPS) = Yes".
If it says "Web Bluetooth not supported": Use the desktop version of Chrome/Edge instead; iOS Safari usually doesn't support it.
Tip: Web Bluetooth will be restricted by browser/system policies, which vary greatly on different platforms.
Step 2

Scan and select devices

About 10–20 seconds

Click "Scan Devices" and select your Bluetooth device in the system pop-up window.

Make sure system Bluetooth is on and the target device is discoverable/connectable.
Click "Scan device" (must be triggered by click, cannot scan automatically).
If the device cannot be found: You can check acceptAllDevices first; or use namePrefix/service to filter precise positioning.
Step 3

Connect and enumerate GATT services/characteristics

About 10–30 seconds

After the connection is successful, click "Enumerate Services" to view the list of services and characteristics.

Click "Connect" and the status changes to "Connected".
Click "Enumerate Services" to view the list in the "GATT Services/Characteristics" card.
If the target service cannot be enumerated: Add the service UUID to optionalServices and rescan/connect and try again.
Tip: Many browsers will restrict services not declared in optionalServices and will not be "visible" even if the device actually exists.
Step 4

Read/subscribe notifications and export reports

about 20 seconds

Read characteristic values, enable notifications, and finally copy the report for further troubleshooting.

Click "Read" in the feature list and observe whether the returned hex/text content is reasonable.
If the feature supports notify/indicate, you can click "Turn on notification" to observe whether the log continues to receive data.
If you encounter an error or need assistance: Click "Copy Report" to send the content to development/customer service for positioning.

FAQ

Have questions? We have the answer! The following is a summary of frequently asked questions about Web Bluetooth scanning, connections, and GATT diagnostics.

1.

What can this Bluetooth diagnostic page do?

Based on the Web Bluetooth capability of the browser, it helps you complete "scan and select devices → connect to GATT → enumerate services/features → read/subscribe notifications", and record key logs and errors to facilitate locating pairing failures, disconnections, service invisibility and compatibility issues.

2.

Why does it prompt "Web Bluetooth is not supported"?

Web Bluetooth is not supported by all browsers/platforms. Usually the desktop version Chrome/Edge has better support; iOS Safari usually does not support it. You can change the browser or switch to the desktop and test again.

3.

Why must it be accessed under HTTPS?

Web Bluetooth is a high-privilege capability and the browser requires a secure context (HTTPS). If it is in an http or insecure environment, a SecurityError will be triggered or it will be directly unavailable.

4.

Why is there no response when clicking "Scan Device"/is a NotAllowedError reported directly?

The scan must be triggered by a user gesture (e.g. button click) and the browser/system needs to allow Bluetooth permissions. Please make sure you click to trigger it manually, the system Bluetooth is turned on, and the browser does not block permission pop-ups.

5.

Why can't I scan the device?

Common reasons include: the device is not discoverable/connectable, the distance is too far or blocked, the filtering conditions are too strict (namePrefix/service), or the system Bluetooth is occupied by other applications. It is recommended to check acceptAllDevices first, get close to the device and try again.

6.

Why am I connected but "cannot enumerate services/features"?

Browsers restrict access to undeclared GATT services. Please add the target service UUID to optionalServices (supports keywords such as battery_service, and you can also write the complete UUID), then rescan/connect and enumerate again.

7.

Why are there frequent disconnections (NetworkError/InvalidStateError)?

Common reasons are distance/interference, low battery or device power-saving hibernation, Bluetooth connection being preempted by other devices, or the system Bluetooth stack being unstable. It is recommended to move closer to the device, reduce 2.4GHz interference, restart Bluetooth/device, and try to maintain a single-device connection.

8.

There is no data after turning on "Notifications". Is this normal?

Probably normal. Not all features will proactively push notifications; some require configuration to be written first or events to be triggered on the device. In addition, browsers/devices may also have restrictions on the notify event. You can first try "read" to confirm whether the feature is readable, or change a feature verification link that is known to be pushed.

9.

Is privacy safe? Will my Bluetooth data be uploaded?

This page mainly interacts and parses within the local browser and will not actively upload your Bluetooth data. If you click "Copy Report," the content will go to your clipboard; it's up to you whether you want to share it.

10.

What information does the Replication Report contain?

The report includes test time, browser UA, HTTPS/availability status, scan parameters (filters/optionalServices), device information summary, enumerated services/feature structures, recent errors and logging. Used to quickly reproduce and locate problems.