> For the complete documentation index, see [llms.txt](https://help.gpmloginapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gpmloginapp.com/gpm-login-global-en/getting-started/understanding-fingerprints/webrtc-ip.md).

# WebRTC IP

WebRTC is a technology that allows two devices to connect directly with each other without relying on intermediary connections. It is used in applications that require fast connections, such as video calls.

Before WebRTC, if two Facebook users wanted to video call each other, they had to send/transfer packets through Facebook's server (usually located in the US, so from VN->US->VN was very time-consuming). This not only put a high load on Facebook's servers but also resulted in a poor customer experience due to slow connection times, leading to lag and stutter.

With WebRTC, two devices can establish a direct connection with each other (typically using UDP). This improves connection speed and significantly reduces the load on servers.

Because WebRTC enables direct connections, bypassing intermediary connections, it is also used in security to determine the user's real IP address.

The website will request the computer to connect via WebRTC. Once the connection is established, the computer and the website will have a direct connection, completely bypassing any intermediate proxies if present. This allows the website to obtain the real IP address of the device through two methods:

* Reading the UDP packet (commonly used)
* Requesting a STUN server to retrieve and return the result (eBay uses this method)

Antidetect solutions involve overriding the real IP in the UDP packets as well as handling requests with the STUN server.