<br />

The Google Fast Pair Service (GFPS), or Fast Pair (FP), is a component of the
[Nearby Platform](https://developers.google.com/nearby "Link to the Nearby Platform page.") that enables quick and power-efficient device
pairing utilizing BlueTooth Classic or BlueTooth Low Energy (BLE).

The GFPS is designed to accommodate a wide range of devices, from earbuds to
speakers, enabling Partners to implement FP features across families of
products. The specification also includes several [extensions](https://developers.google.com/nearby/fast-pair/specifications/extensions/batterynotification "Link to the Fast Pair Extensions page.") Partners
can implement to provide customers with additional capabilities.

## Overview

## Getting Started

Partners planning to adopt or modify the GFPS must submit a
Project Proposal Form to the Google Fast Pair Business Development
(BD) team. BD's approval is required before Partners can begin integrating the
GFPS into their device. BD is also critical of ensuring effective communication
through the GFPS adoption process. If you are interested in Hearables Suite
support to over-the-ear or TWS headphones, complete the
[Fast Pair Project Proposal Form](https://docs.google.com/forms/d/1-QLoVRkxZQQtk14lGvgs88laM9zC1p35pzYwXBLosFk/viewform "Link to the Business Proposal submission form.").
If you are interested in integrating your location tag or non hearable device
with Find Hub Network Accessory,
complete a [Find Hub Project Proposal Form](https://docs.google.com/forms/d/e/1FAIpQLSekmYsXwVhPofdonOBtUU4O3Lbr_gQ-o2sCm6LHocehXKiM1A/viewform "Link to the FH Business Proposal submission form.") instead. More
details on integrating Find Hub can be found in the
[Find Hub Network section](https://developers.google.com/nearby/fast-pair/specifications/extensions/fmdn "FHN").

Google works with Google Certified Fast Pair System Integrators (SIs) to provide
Partners with prebuilt solutions to common [chipsets](https://developers.google.com/nearby/fast-pair/chipsets "Link to the list of supported Chipsets."). Partners
seeking ready-made solutions should work closely with their [SI partner](https://developers.google.com/nearby/fast-pair/system-integrator-roles-and-responsibilities "Link to the Roles and Responsibilities page.")
throughout the FP adoption process.

Some Partners, particularly those who don't rely on prebuilt solutions, may work
directly with Google during the FP adoption process. BD ensures Partners know
which path they're on as part of the [Project Proposal Form](https://docs.google.com/forms/d/1-QLoVRkxZQQtk14lGvgs88laM9zC1p35pzYwXBLosFk/viewform "Link to the Business Proposal submission form.") discussion.

Finally, a device must be [certified](https://developers.google.com/nearby/fast-pair/certification-process "Link to the Certification Process page.") before it can utilize GFPS
features in the market. Partners should account for the certification process
when planning GFPS adoption schedules.

### The GFPS Adoption Process

In general, Partners follow this process when adopting and modifying or updating
the GFPS into a product:

![](https://developers.google.com/static/nearby/fast-pair/images/FP_Process_Overview.png)

Textually, the GFPS adoption process is described in the following steps:

#### Pre-submission

1. Create a [Google Cloud Project](https://cloud.google.com/docs/overview/#projects "Link to the Google Cloud projects page.") for your devices if one does not exist.
   1. Create a device page for your specific device.
   2. See [the Model ID page](https://developers.google.com/nearby/fast-pair/specifications/service/modelregistration#CreateModelId "How to register a Fast Pair Model ID.") for details on this process.
   3. Record the Model ID of your device from the device page.
2. Submit a [Project Proposal Form](https://docs.google.com/forms/d/1-QLoVRkxZQQtk14lGvgs88laM9zC1p35pzYwXBLosFk/viewform "Link to the Business Proposal submission form.") describing your project.
3. Sign any NDAs required for the GFPS specification (such as early access).
4. Establish a relationship with your Partner.
   1. If working with an SI, discuss the [SI Process](https://developers.google.com/nearby/fast-pair/system-integrator-roles-and-responsibilities "Link to the Roles and Responsibilities page.") with them.
5. Start Integrating with help from your Partner.

#### Certification

1. Integrate and verify the GFPS on your device with help from your Partner.
2. Prepare either the [BT Classic](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_-_Google_Fast_Pair_Self_Test_Report_10142020.zip "Link to the Fast Pair Bluetooth Classic Self-Test Report sheet.") or [BT LE Audio](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/LE_Audio_Dual_mode_-_Google_Fast_Pair_Self_Test_Report_2025_Q4.zip "Link to the Fast Pair LE Audio Self-Test Report sheet.") Self-Test Report form.
   1. You may need additional Self-Test Reports based on your features, like the Audio switch [BT Classic](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_SASS_Certification_Test_Report_04302026.zip "Link to the Bluetooth Classic Audio switch Self-Test Report sheet.") or [BT LE Audio](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_LEA_SASS_Certification_Test_Report_04302026.zip "Link to the LE Audio Audio switch Self-Test Report sheet.") Self- Test Report forms.
3. Submit your device for [Certification](https://developers.google.com/nearby/fast-pair/certification-process "Link to the Certification Process page.").
   1. Google recommends using the [Validator App](https://play.google.com/apps/testing/com.google.location.nearby.apps.fastpair.validator "Link to the Validator App on the Google Play Store.") for self-testing to verify your implementation. The Validator App is a self-verification tool and does not replace official 3rd Party Lab certification.
4. Receive official Certification from Google and permission to enable GFPS.

## FP DevSite Overview

The Fast Pair DevSite is divided into sections to better assist Partners in
developing, adopting, and integrating the GFPS into their system.

- The [FP Specification](https://developers.google.com/nearby/fast-pair/specifications/introduction "Link to the FP Specification.") describes the formal GFPS requirements.
- The [extensions](https://developers.google.com/nearby/fast-pair/specifications/extensions/batterynotification "Link to the Fast Pair Extensions page.") section describes various extensions available for the GFPS.
- The [certification](https://developers.google.com/nearby/fast-pair/certification-process "Link to the Certification Process page.") section describes how to prepare a device for formal certification, including any pre-certification steps.
- The [Working with Google and Partners](https://developers.google.com/nearby/fast-pair/system-integrator-roles-and-responsibilities "Link to the Roles and Responsibilities page.") section describes process details for development and integration.
- The Appendix describes other useful information, such as the version of FP supported by various [chipsets](https://developers.google.com/nearby/fast-pair/chipsets "Link to the list of supported Chipsets.") and [FP FAQs](https://developers.google.com/nearby/fast-pair/fast-pair-faq "Link to the Fast Pair FAQ page.").

## Approved Fast Pair System Integrators:

| SI Name | Contact |
|---|---|
| Airoha | sales@airoha.com |
| Bestechnic | Email: [Jennifer Li, Dir. of Business Development](mailto:jennifer@bestechnic.com) |
| Qualcomm | [Qualcomm Contact Form](https://www.qualcomm.com/support/contact/forms/contact-sales-audio) |
| Realtek | rtksi@realtek.com |