# Wi-Fi Direct

**Wi-Fi Direct** (also called Wi-Fi P2P) is a [Wi-Fi Alliance](https://www.edgepedia.org/wi-fi-alliance) certification and protocol that lets Wi-Fi devices connect directly to one another to form a network without a wireless access point and without the older ad hoc (IBSS) mode. It is defined in the Wi-Fi Peer-to-Peer Technical Specification, and it is used for file transfer between phones, wireless printing, screen casting, and as a proximity link for cameras, printers, TVs, and other devices.<sup>[1](https://learn.microsoft.com/en-us/windows/win32/nativewifi/about-the-wi-fi-direct-api)</sup><sup> • </sup><sup>[2](https://arxiv.org/abs/2002.03144)</sup>

| Key fact | Detail |
|---|---|
| Standardization | Based on the Wi-Fi Peer-to-Peer Technical Specification (v1.1 cited in Windows documentation; the current published specification is v1.9, 2021)<sup>[1](https://learn.microsoft.com/en-us/windows/win32/nativewifi/about-the-wi-fi-direct-api)</sup><sup> • </sup><sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup> |
| Topology | 1:n: one device is the P2P Group Owner, an "AP-like" entity; the others are P2P Clients or legacy clients<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup> |
| Security | WPA2-Personal with AES-CCMP outside DMG; AES-GCMP within DMG; provisioning via Wi-Fi Protected Setup (WSC)<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup> |
| Addressing | The Group Owner acts as a DHCP server, assigning IPv4 addresses, subnet masks to clients<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup> |
| Platform support | Windows Native Wifi API functions since Windows 8 and Windows Server 2012; Android's `WifiP2pManager` API; not all Android devices support it<sup>[1](https://learn.microsoft.com/en-us/windows/win32/nativewifi/about-the-wi-fi-direct-api)</sup><sup> • </sup><sup>[4](https://developer.android.google.cn/reference/android/net/wifi/p2p/package-summary)</sup> |
| Scale | Shipments of Wi-Fi Direct devices reached 1.7 billion in 2016 and were predicted to reach 3 billion by 2019<sup>[2](https://arxiv.org/abs/2002.03144)</sup> |

## How a connection forms

A Wi-Fi Direct device supports both the Group Owner and Client roles and negotiates which it will take.<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup> Formation proceeds in three broad stages:

1. **Discovery.** Devices scan and listen on channels, exchanging Probe Request and Probe Response frames that carry device name, device type, and supported channels. Discovery can also run out of band: two devices with NFC interfaces brought into close proximity exchange Handover Request and Handover Select messages carrying WSC and P2P attributes, agreeing on a channel for group formation before any Wi-Fi exchange.<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup> In one measured study, the time a device spends in each discovery state was randomly distributed, typically between 100 and 300 ms, with implementations trading discovery speed against energy by interleaving sleep cycles.<sup>[5](https://ptacts.uspto.gov/ptacts/public-informations/petitions/1521916/download-documents?artifactId=WB4_whbhbBw1wVIr_EK8l8UaqsbvoxAeQm96JaJzmwyP6PSojYTfelQ)</sup>
2. **Group Owner negotiation.** The two devices exchange negotiation request and response messages and agree on which becomes the Group Owner and which the Client; negotiation fails immediately if provisioning information is not yet available on both sides.<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup> Despite the peer-to-peer name, the outcome is asymmetric: the Group Owner operates like an access point and the other device associates to it as a station.<sup>[6](https://www.sharetechnote.com/html/WLAN_WiFi_Direct.html)</sup>
3. **Provisioning and operation.** Credentials are established with [Wi-Fi Protected Setup](https://www.edgepedia.org/wi-fi-protected-setup) (WSC), for example with a PIN or push-button configuration. After association, the Group Owner and Client run the 802.11 4-way handshake, with the owner as authenticator, and the owner then runs a DHCP server for clients using IP.<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup>

**Persistent groups.** A device that obtains credentials for a group can store the P2P Group ID and credentials so the group can be re-created in later sessions without repeating full negotiation and provisioning; the stored group ID and credentials stay the same across sessions, though the interface address and operating channel may change. Re-forming such a group uses the P2P Invitation procedure instead of a fresh Group Owner negotiation.<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup>

## Services and concurrent operation

Wi-Fi Direct supports service discovery at the [link layer](https://www.edgepedia.org/link-layer): a device can query another device about specific higher-layer services before connecting, using Service Discovery Query and Response frames, and caches responses against a Service Update Indicator that is incremented whenever the advertising device's service information changes.<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup><sup> • </sup><sup>[7](https://www.hsc.com/resources/blog/wi-fi-direct-overview-and-features/)</sup>

A P2P device may operate concurrently with an infrastructure WLAN, and a P2P group may run on the same or a different channel and operating class as the concurrently operating network.<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup> The Group Owner may also provide a data distribution service between all connected clients, signaled by the Intra-BSS Distribution bit; within DMG (directional multi-gigabit operation), clients communicate directly with each other regardless of that setting.<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup>

## Platform implementations

**Windows.** Wi-Fi Direct functions were added to the Native Wifi API starting with [Windows 8](https://www.edgepedia.org/windows-8) and [Windows Server 2012](https://www.edgepedia.org/windows-server-2012), including `WFDStartOpenSession` for on-demand connections to previously paired devices and `WFDOpenLegacySession` for legacy devices. Microsoft's guidance is to use Wi-Fi Direct instead of ad hoc mode from [Windows 8.1](https://www.edgepedia.org/windows-8-1) and Windows Server 2012 R2 onward, since ad hoc mode might not be available in future versions.<sup>[1](https://learn.microsoft.com/en-us/windows/win32/nativewifi/about-the-wi-fi-direct-api)</sup> In Windows 10, the WDI driver and the Wi-Fi Direct WinRT APIs (`Windows.Devices.WiFiDirect`) replaced the NDIS driver and SoftAP APIs, which are deprecated as of Windows 8.1.<sup>[8](https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/partnerapps/wi-fi-direct.md)</sup> The `WiFiDirectLegacySettings` class lets devices without Wi-Fi Direct support connect to a Windows device acting as a Group Owner and communicate over TCP/UDP, with an optional SSID and passphrase or randomly generated ones; Mobile Hotspots, supported from Windows 10 version 1607, take precedence over Wi-Fi Direct scenarios and cannot run at the same time as the legacy Group Owner feature.<sup>[8](https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/partnerapps/wi-fi-direct.md)</sup>

**Android.** The `android.net.wifi.p2p` package centers on `WifiP2pManager`, with methods to initialize, `discoverPeers()`, `connect()`, and `createGroup()`, the last making the current device the group owner without negotiation.<sup>[4](https://developer.android.google.cn/reference/android/net/wifi/p2p/package-summary)</sup><sup> • </sup><sup>[9](https://developer.android.com/develop/connectivity/wifi/wifi-direct?authuser=211)</sup> Apps need the `ACCESS_WIFI_STATE`, `CHANGE_WIFI_STATE`, and `INTERNET` permissions, the last because standard sockets require it even though no internet connection is involved.<sup>[4](https://developer.android.google.cn/reference/android/net/wifi/p2p/package-summary)</sup> Android requires [MAC address](https://www.edgepedia.org/mac-address) randomization: the Wi-Fi Direct device address must be randomized on interface creation when no persistent group is saved, and the interface (group) address must be randomized on every connection; this is implemented in wpa_supplicant.<sup>[10](https://source.android.com/docs/core/connect/wifi-direct?authuser=29)</sup>

**Apple.** Apple platforms do not use Wi-Fi Direct for AirDrop; AirDrop uses [Bluetooth Low Energy](https://www.edgepedia.org/bluetooth-low-energy) together with Apple-created peer-to-peer Wi-Fi technology, with the Wi-Fi radio communicating directly between devices without an access point and the connection encrypted with TLS.<sup>[11](https://support.apple.com/en-euro/guide/security/sec2261183f4/web)</sup> Apple's own peer-to-peer Wi-Fi dates back to iOS 7.<sup>[12](https://developer.apple.com/documentation/technotes/tn3111-ios-wifi-api-overview?changes=_2_8_8%2C_2_8_8&language=objc%2Cobjc)</sup>

## Security

The specification mandates WPA2-Personal encryption for group communication, with AES-CCMP outside DMG and AES-GCMP within DMG, and WPS provisioning is a mandatory capability for P2P devices.<sup>[3](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)</sup><sup> • </sup><sup>[13](https://blackhat.com/docs/eu-17/materials/eu-17-Blanco-WI-FI-Direct-To-Hell-Attacking-WI-FI-Direct-Protocol-Implementations-wp.pdf)</sup> Research has identified weaknesses at several layers. The WPS PIN method is vulnerable to brute-force and dictionary attacks, and the push-button method is vulnerable to the EvilDirect attack, in which a malicious device impersonates a legitimate group; routing in Wi-Fi Direct opportunistic networks is additionally open to the CollusiveHijack attack.<sup>[14](https://oaktrust.library.tamu.edu/handle/1969.1/187560)</sup> Because Probe Response frames must carry WPS information elements for discovery, device fingerprinting is straightforward.<sup>[13](https://blackhat.com/docs/eu-17/materials/eu-17-Blanco-WI-FI-Direct-To-Hell-Attacking-WI-FI-Direct-Protocol-Implementations-wp.pdf)</sup> A 2020 analysis of Android device-to-device file-sharing applications built on Wi-Fi Direct reported 17 CVEs, finding that vendors had prioritized ease of use over security in their implementations.<sup>[2](https://arxiv.org/abs/2002.03144)</sup>

## Adoption and limits

Shipments of Wi-Fi Direct devices reached 1.7 billion in 2016 and were predicted to reach 3 billion by 2019.<sup>[14](https://oaktrust.library.tamu.edu/handle/1969.1/187560)</sup> Stock Android does not provide application-transparent communication across multiple Wi-Fi Direct groups, though a 2025 study showed multi-group communication can be engineered at the application level on non-rooted devices.<sup>[15](https://arxiv.org/abs/2604.07889)</sup>

## References

1. [About the Wi-Fi Direct feature, Microsoft Learn](https://learn.microsoft.com/en-us/windows/win32/nativewifi/about-the-wi-fi-direct-api)
2. [Why is My Secret Leaked? Discovering Vulnerabilities in Device-to-Device File Sharing, arXiv](https://arxiv.org/abs/2002.03144)
3. [Wi-Fi Direct Specification v1.9, Wi-Fi Alliance (2021)](https://tools.barco.com/kb-downloads/4814/Wi-Fi_Direct_Specification_v1.pdf)
4. [android.net.wifi.p2p package summary, Android Developers](https://developer.android.google.cn/reference/android/net/wifi/p2p/package-summary)
5. [Device-to-device communications with Wi-Fi Direct: overview and experimentation](https://ptacts.uspto.gov/ptacts/public-informations/petitions/1521916/download-documents?artifactId=WB4_whbhbBw1wVIr_EK8l8UaqsbvoxAeQm96JaJzmwyP6PSojYTfelQ)
6. [WiFi Direct, ShareTechnote](https://www.sharetechnote.com/html/WLAN_WiFi_Direct.html)
7. [Wi-Fi Direct: Overview and Features, Hughes Systique](https://www.hsc.com/resources/blog/wi-fi-direct-overview-and-features/)
8. [Wi-Fi Direct, Windows driver documentation, Microsoft](https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/partnerapps/wi-fi-direct.md)
9. [Create P2P connections with Wi-Fi Direct, Android Developers](https://developer.android.com/develop/connectivity/wifi/wifi-direct?authuser=211)
10. [Wi-Fi Direct, Android Open Source Project](https://source.android.com/docs/core/connect/wifi-direct?authuser=29)
11. [AirDrop security, Apple Support](https://support.apple.com/en-euro/guide/security/sec2261183f4/web)
12. [TN3111: iOS Wi-Fi API overview, Apple Developer](https://developer.apple.com/documentation/technotes/tn3111-ios-wifi-api-overview?changes=_2_8_8%2C_2_8_8&language=objc%2Cobjc)
13. [Wi-Fi Direct To Hell: Attacking Wi-Fi Direct Protocol Implementations, Black Hat Europe 2017](https://blackhat.com/docs/eu-17/materials/eu-17-Blanco-WI-FI-Direct-To-Hell-Attacking-WI-FI-Direct-Protocol-Implementations-wp.pdf)
14. [On Securing Wi-Fi Direct Based Opportunistic Networks, Texas A&M University (2019)](https://oaktrust.library.tamu.edu/handle/1969.1/187560)
15. [Design and empirical validation of a stock-Android software architecture for Wi-Fi Direct multi-group communication, arXiv](https://arxiv.org/abs/2604.07889)

---
*Topic: Encyclopedia › Technology and the built world › Computing and digital systems › Networks and security › Wireless networking › Wi-Fi standards and security › Wi-Fi Direct*

*Initially written Sep 17, 2026 · Reviewed: Sep 17, 2026; Oct 15, 2026 · Edited: Oct 15, 2026 · Last review: Oct 15, 2026*

*Copyright 2026 EdgeChat AI, a subsidiary of Biostate AI.*

License: Edgepedia Community License 1.0, https://www.edgepedia.org/edgepedia/license
