This document shows the implementation status of Web Bluetooth on the different browsers.
Work is in progress:
- Know How to file Web Bluetooth Bugs.
- In Chrome OS, Android, & Mac, the GATT Communication API is shipped without any flag.
- Linux & Windows are partially implemented, but not supported. The
chrome://flags/#enable-experimental-web-platform-features
flag must be enabled. - New Windows implementation is available in Chrome 70.0.3526.0.
- Root Issue 419413: Web Bluetooth and blocking issues are most authorative on status.
- Some Bluetooth GATT operations can't be run in parallel yet. See #188 (comment)
Feature/Platform | Chrome OS | Android | Mac | Linux | Windows |
---|---|---|---|---|---|
getAvailability() | |||||
Referring Device (Physical Web) | |||||
Discovery | ✓ | ✓ | ✓ | ✓ | ✓ |
└ Service list | ✓ | ✓ | ✓ | ✓ | ✓ |
└ Name or prefix | ✓ | ✓ | ✓ | ✓ | ✓ |
└ Manufacturer/Service data | |||||
└ acceptAllDevices | ✓ | ✓ | ✓ | ✓ | ✓ |
Chooser UI | ✓ | ✓ | ✓ | ✓ | ✓ |
permissions.request() | |||||
permissions.query() | |||||
permissions.revoke() | |||||
watchAdvertisements() | |||||
Persistent Device IDs | |||||
GATT Server Connect | ✓ | ✓ | ✓ | ✓ | ✓ |
GATT Server Disconnect | ✓ | ✓ | ✓ | ✓ | ✓ |
Hanging connect() abortable by disconnect() | |||||
getPrimaryService*() | ✓ | ✓ | ✓ | ✓ | ✓ |
getIncludedService*() | |||||
getCharacteristic*() | ✓ | ✓ | ✓ | ✓ | ✓ |
Characteristic Properties | ✓ | ✓ | ✓ | ✓ | 70 |
Read Characteristic | ✓ | ✓ | ✓ | ✓ | ✓ |
Write Characteristic | ✓ | ✓ | ✓ | ✓ | ✓ |
Start/Stop Notifications | ✓ | ✓ | ✓ | ✓ | 70 |
Descriptors | ✓ | ✓ | ✓ | ✓ | 70 |
Event bubbling | |||||
Device Disconnected Event | ✓ | ✓ | ✓ | ✓ | 70 |
Service Changed Event | |||||
BluetoothUUID | ✓ | ✓ | ✓ | ✓ | ✓ |
TypeError for bad UUIDs | ✓ | ✓ | ✓ | ✓ | ✓ |
Invalidate GATT attributes upon disconnect | ✓ | ✓ | ✓ | ✓ | ✓ |
GATT Blocklist | ✓ | ✓ | ✓ | ✓ | ✓ |
Low-latency Blocklist Updates | ✓ | ✓ | ✓ | ✓ | ✓ |
Feature/Platform | Chrome OS | Android | Mac | Linux | Windows |
---|---|---|---|---|---|
Advertisements Scanning |
Tip: Chrome channel releases are tracked at https://googlechromelabs.github.io/current-versions/.
- Android: Requires Android 6.0 Marshmallow or later.
- Mac: Requires OS X Yosemite or later.
- Some MacBooks may not work: Check "About this Mac" / "System Report" / "Bluetooth" and verify that Low Energy is supported.
- Linux: Requires Kernel 3.19+ and BlueZ 5.41+ installed. Read How to get Chrome Web Bluetooth working on Linux.
- Note that Bluetooth daemon needs to run with experimental interfaces if BlueZ version is lower than 5.43:
sudo /usr/sbin/bluetoothd -E
- Note that Bluetooth daemon needs to run with experimental interfaces if BlueZ version is lower than 5.43:
- Windows: Requires Windows 8.1 or later.
- To discover devices the user hasn't yet manually paired, requires Windows 10.
- A third-party Windows 10 Polyfill (Chrome Extension + Native Executable) has been created while Windows support is not implemented yet.
- Android WebView: Will be supported in the future.
- iOS: Uses the web exposed APIs as provided by the WKWebView, no implementation planned in the Chromium codebase.
Note: WebBLE is an app for iOS that supports the GATT Communication API. It was created initially for the Puck.js project.
In Samsung Internet v6.4, the GATT Communication API is shipped without any flag.
- https://medium.com/samsung-internet-dev/lets-connect-with-samsung-internet-v6-4-stable-1f197d43a812
- https://samsunginter.net/docs/web-bluetooth
Available behind a flag opera://flags/#enable-web-bluetooth
.
https://szeged.github.io/servo/
- https://bugzilla.mozilla.org/show_bug.cgi?id=1204396
- https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%5Bweb-bluetooth%5D
https://dev.windows.com/en-us/microsoft-edge/platform/status/webbluetooth
https://bugs.webkit.org/show_bug.cgi?id=101034
Node.js ports are available: