Web Bluetooth Scanner & Connection Test
Use the Web Bluetooth API to scan for nearby devices. Test browser connectivity, pairing, and data transfer capabilities (requires compatible hardware).
Requests Bluetooth only while the test is active and keeps processing in your browser whenever possible.
Works best in current Chrome, Edge, Safari, and Firefox. Support depends on Web Bluetooth API, secure HTTPS, hardware availability, and browser policy.
environment and support
GATT Services/Characteristics
log
How to use this page to quickly locate problems
Bluetooth Guide
Scan, Pair, and explore GATT services via Web Bluetooth.
Confirm environment and browser support
Make sure to access under HTTPS and use a browser that supports Web Bluetooth.
Scan and select devices
Click "Scan Devices" and select your Bluetooth device in the system pop-up window.
Connect and enumerate GATT services/characteristics
After the connection is successful, click "Enumerate Services" to view the list of services and characteristics.
Read/subscribe notifications and export reports
Read characteristic values, enable notifications, and finally copy the report for further troubleshooting.
What this tool checks
This page checks whether the browser can expose Web Bluetooth, open the device chooser, and attempt a usable connection flow.
Web Bluetooth availability
Confirms whether the current browser exposes the Bluetooth APIs required for web access.
device chooser prompt
Helps verify whether the browser can open the nearby-device selection dialog.
device discovery path
Makes it easier to see whether the expected device appears while advertising.
connection attempt
Useful for checking whether the browser can start a pairing or GATT connection flow.
session state changes
Can reveal whether the device disconnects immediately or fails to stay connected.
user-side compatibility hints
Helps separate unsupported browser issues from device visibility or pairing problems.
What this tool cannot confirm
Web Bluetooth support is highly constrained, so this test cannot replace vendor tools or native pairing diagnostics.
not every Bluetooth device is web-compatible
A device may work in native apps and still not expose the services needed for Web Bluetooth access.
browser support is limited
Some browsers and platforms, especially on iOS, do not support Web Bluetooth at all.
pairing rules still depend on the device
Advertising mode, PIN entry, bonding requirements, and service permissions all affect whether a connection succeeds.
not a radio diagnostics tool
The page cannot measure RF quality, antenna issues, or low-level Bluetooth stack errors.
How the result is generated
The result is generated from browser API availability, device chooser behavior, and any local connection state the browser can expose.
API availability check
The page first checks whether Web Bluetooth exists in the current browser.
chooser request
If supported, the browser opens a nearby-device chooser after your explicit action.
device selection
You select a visible compatible device from the chooser list.
connection / service attempt
The browser tries to open a GATT connection or read the requested services.
local session summary
The page reports whether the device could be found, selected, and kept connected.
Interpret your results
Use the result to decide whether the issue is lack of browser support, missing device visibility, or an unstable connection path.
| Observed Bluetooth result | Likely meaning |
|---|---|
| No chooser opens | Unsupported browser, insecure context, or Bluetooth access is blocked before discovery starts. |
| Device not listed | The device is off, not advertising, out of range, or not compatible with the requested filters. |
| Connect fails quickly | Pairing mismatch, unsupported service, busy device state, or unstable radio conditions. |
| Disconnects after connect | Range, power, firmware, or service negotiation problems. |
| Device connects and stays visible | Basic browser Bluetooth access is working with this device and browser. |
Supported browsers and known limitations
Web Bluetooth support is among the most browser-specific web capabilities, especially across desktop and mobile platforms.
| browser | API availability | device chooser | connection path | known limitations |
|---|---|---|---|---|
| Chrome | Strong on supported desktop builds | Strong | Good | Still limited to supported services and secure contexts. |
| Edge | Similar to Chrome | Strong | Good | Enterprise or OS policy can disable Bluetooth access. |
| Firefox | Limited or unavailable on many setups | Limited | Limited | Web Bluetooth support is much weaker than Chromium browsers. |
| Safari | Generally unavailable for Web Bluetooth | No or very limited | No or very limited | Safari support remains highly restricted. |
| iOS Safari | Generally unavailable | No | No | iOS Safari does not offer practical Web Bluetooth support here. |
| Android Chrome | Varies by device and build | Basic to good | Basic to good | Mobile vendor implementations can be inconsistent. |
Use cases
This browser Bluetooth test is useful when you need to know whether the web platform itself can reach the nearby device.
before a web-based hardware demo
Confirm that the browser can see and select the target Bluetooth device.
after pairing a new accessory
Check whether the web app path can discover it, not just the OS settings panel.
when a device never appears
Use the test to separate browser support issues from device advertising issues.
when comparing browsers
See which browser on the same computer exposes the needed Bluetooth flow.
after a system privacy reset
Re-test whether Bluetooth access was revoked by policy or OS permission changes.
FAQ
Have questions? We have the answer! The following is a summary of frequently asked questions about Web Bluetooth scanning, connections, and GATT diagnostics.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Related guides
Read a few practical guides for setup, browser compatibility, and troubleshooting around this test.
Is Your Browser Ready for IoT? A Practical Guide to Web Bluetooth Testing
As the Internet of Things (IoT) expands, web applications increasingly rely on direct hardware communication. However, inconsistent browser support and permission hurdles often disrupt user experiences. This practical guide leverages the Web Bluetooth Scanner & Connection Test tool to help developers and IT professionals diagnose connectivity issues before deployment. We walk through granting necessary permissions, executing live device scans for headsets and peripherals, and interpreting real-time data transfer metrics. Whether you are troubleshooting a failed keyboard pairing or verifying stability for a smart home demo, this article provides a step-by-step workflow to ensure your web apps can reliably discover, pair, and communicate with nearby Bluetooth devices across different environments.
Is Your Browser Ready for IoT? A Practical Guide to Web Bluetooth Testing
As Internet of Things (IoT) applications migrate to the web, ensuring seamless hardware communication is critical. This guide explores the capabilities of the Web Bluetooth API using a dedicated scanner and connection test tool. We walk through practical scenarios including troubleshooting headset connections, diagnosing keyboard pairing issues, and verifying data transfer stability before live demos. By following a structured three-step workflow—granting permissions, executing core tests, and validating metrics—developers and IT professionals can identify compatibility gaps between browsers and peripheral devices. Whether you are building a new smart home interface or resolving workplace connectivity glitches, this article provides actionable steps to confirm your environment is ready for wireless web integration.
Is Your Browser Ready for IoT? A Practical Guide to Web Bluetooth Testing
As Internet of Things (IoT) applications migrate to the web, ensuring reliable browser-to-device communication is critical. This practical guide explores how developers and QA engineers can utilize the Web Bluetooth API to scan, pair, and verify data transfer with nearby hardware without installing native apps. We walk through a step-by-step workflow using the Web Bluetooth Scanner & Connection Test tool to diagnose common connectivity issues, from permission hurdles to unstable scanning results. Whether you are troubleshooting a smart headset, validating a new keyboard peripheral, or preparing for a live product demo, this article provides actionable strategies to confirm your web app's compatibility and stability across different browsers and operating systems.
Feedback / report a bug
Tell us your browser, device, and what happened.
Did this result look wrong?
Comments(0)