Google Fast Pair Service
Stay organized with collections
Save and categorize content based on your preferences.
Introduction
The Google Fast Pair Service (GFPS) utilizes Bluetooth Low Energy (BLE) to
discover nearby Bluetooth devices without using significant phone battery,
enabling “magical” scenarios based on device proximity.
Features
GFPS is aimed at facilitating the pairing of Bluetooth and BLE devices, such as
speakers, headphones, car kits, mice and keyboards, with as little user
interaction required as possible. By implementing the following spec, Google
will continue to release additional features that build upon it. This includes:
- Displaying a half page notification when the device is in pairing mode to
facilitate easy initial pairing. Additionally companion apps are easily
marketed to users.
- Associating the device with the user's account after the initial pairing has
completed.
- Displaying a
subsequent pairing notification when the
device is turned on and near another phone, tablet, or desktop that the user
owns, so that the user does not need to know how to put the device back into
pairing mode before pairing with their other devices.
- Associating a personalized name with the device.
- Battery notifications are displayed for the headphones.
- Shows device details in Android 11+.
- Ability for users to locate a lost headset or buds.
- Offline pairing is available for low-network situations.
- Support Audio switch to seamlessly transition headset connections between
devices based on user activity (e.g. starting a movie) and prioritized events
(e.g. an incoming call).
- Support Hearable Controls to provide better access controls for
important Hearable features.
Feature Requirements
Based on the device type , the requirement for feature support would differ.
See the Device Feature Requirements for more
details.
Profile dependencies
The GFPS implementation is compatible with the Bluetooth Core
Specification v4.2 or later.
Octet order
Wherever a field consists of multiple bytes, the byte ordering is big-endian,
that is, network byte order (most-significant octet to least-significant octet).
Note that while this is standard for bytes transferred over networks, it is
different from the byte ordering for multi-byte fields in Bluetooth SIG
specifications (for example, a service UUID in an advertisement is
little-endian).
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-12 UTC.
[null,null,["Last updated 2025-08-12 UTC."],[[["\u003cp\u003eGoogle Fast Pair Service (GFPS) uses Bluetooth Low Energy to easily pair devices like headphones, speakers, and keyboards with minimal user interaction.\u003c/p\u003e\n"],["\u003cp\u003eGFPS allows devices to be automatically paired with other devices logged into the same Google account, simplifying the connection process.\u003c/p\u003e\n"],["\u003cp\u003eThe service offers additional features like personalized device names, battery notifications, and seamless audio switching between devices.\u003c/p\u003e\n"],["\u003cp\u003eGFPS is compatible with Bluetooth 4.2 or later and utilizes a big-endian octet order for data transmission.\u003c/p\u003e\n"],["\u003cp\u003eDevice feature requirements and a reference implementation are available for developers to integrate GFPS functionality.\u003c/p\u003e\n"]]],[],null,["# Google Fast Pair Service\n\nIntroduction\n------------\n\nThe Google Fast Pair Service (*GFPS* ) utilizes Bluetooth Low Energy (*BLE*) to\ndiscover nearby Bluetooth devices without using significant phone battery,\nenabling \"magical\" scenarios based on device proximity.\n\n### Features\n\nGFPS is aimed at facilitating the pairing of Bluetooth and BLE devices, such as\nspeakers, headphones, car kits, mice and keyboards, with as little user\ninteraction required as possible. By implementing the following spec, Google\nwill continue to release additional features that build upon it. This includes:\n\n1. Displaying a half page notification when the device is in pairing mode to facilitate [easy initial pairing](/nearby/fast-pair/specifications/configuration#DeviceDiscovery \"Device Discovery\"). Additionally companion apps are easily marketed to users.\n2. Associating the device with the user's account after the initial pairing has completed.\n3. Displaying a [subsequent pairing notification](/nearby/fast-pair/specifications/service/provider#AdvertisingWhenNotDiscoverable \"Advertizing when not discoverable\") when the device is turned on and near another phone, tablet, or desktop that the user owns, so that the user does not need to know how to put the device back into pairing mode before pairing with their other devices.\n4. Associating a [personalized name](/nearby/fast-pair/specifications/extensions/personalizedname \"Extensions - Personalized name\") with the device.\n5. [Battery notifications](/nearby/fast-pair/specifications/extensions/batterynotification \"Extensions - Battery Notifications\") are displayed for the headphones.\n6. Shows device details in Android 11+.\n7. Ability for users to locate a lost headset or buds.\n8. Offline pairing is available for low-network situations.\n9. Support [Audio switch](/nearby/fast-pair/specifications/extensions/sass \"Audio Switch\") to seamlessly transition headset connections between devices based on user activity (e.g. starting a movie) and prioritized events (e.g. an incoming call).\n10. Support [Hearable Controls](/nearby/fast-pair/specifications/extensions/hearablecontrols \"Hearable Controls\") to provide better access controls for important Hearable features.\n\n### Feature Requirements\n\nBased on the device type , the requirement for feature support would differ.\nSee the [Device Feature Requirements](/nearby/fast-pair/specifications/devicefeaturerequirement \"Link to the Device feature requirement.\") for more\ndetails.\n\n### Profile dependencies\n\nThe GFPS implementation is compatible with the Bluetooth Core\nSpecification v4.2 or later.\n\n### Octet order\n\nWherever a field consists of multiple bytes, the byte ordering is big-endian,\nthat is, network byte order (most-significant octet to least-significant octet).\n\nNote that while this is standard for bytes transferred over networks, it is\ndifferent from the byte ordering for multi-byte fields in Bluetooth SIG\nspecifications (for example, a service UUID in an advertisement is\nlittle-endian)."]]
