netcode.io
github.com
- Free plan
- Windows
- macOS
- Linux
- Self-hosted
What netcode.io is
netcode.io is a free, open-source client/server protocol for real-time multiplayer games. It carries unreliable, unordered packets over UDP, without TCP head-of-line blocking. A game backend can issue connect tokens to authorize clients, and servers assign those clients to slots, rejecting connections when all slots are occupied. Clients and servers can disconnect cleanly; timeouts cover hard disconnects. Packets are encrypted and signed using libsodium, with protections against crafted packets, replay attacks, and amplification attacks. The protocol supports IPv4 and IPv6, and packet tagging intended to reduce Wi-Fi jitter. The repository lists implementations for C, C#, Go, Rust, Unity, Unreal Engine 4, and TypeScript. The project uses the BSD 3-Clause license and lists no paid plans or usage limits. Its documented build uses CMake 3.16 or later on Windows, macOS, or Linux, with a vendored libsodium subset by default. Matchmaking is not included; the documented flow has a client request a token from the game's backend.
Who it suits
It suits developers building real-time multiplayer games who need a UDP client-server protocol with backend-issued authorization. Teams should be prepared to handle matchmaking separately and build the library with CMake.
Good to know, and what to watch
- Free library under the BSD 3-Clause license
- Supports IPv4 and IPv6 connections
- Packets are encrypted and signed with libsodium
- Implementations are listed for seven languages and engines
- Matchmaking is not included
- Building requires CMake 3.16 or later
- Nonce-reuse issue affected versions 1.3.5 and earlier
Plans
Every plan and pricenetcode
Open source
The verdict
netcode.io provides a focused UDP connection and security layer for multiplayer games, including token-based client authorization and server slot management. Check the version history and build requirements before integrating it.
What the maker publishes
- Authorized access
- Connect tokens let a game backend authorize which clients can connect to a server. source
- Backend integration
- The documented connection flow has a client request a connect token from a REST API on the game's backend. source
- Build platforms
- The maker says netcode builds with CMake on Windows, macOS, and Linux. source
- Build requirements
- The default build uses a vendored libsodium subset and requires no additional installation; CMake 3.16 or later is specified. source
- Build requirements
- The C library builds with CMake 3.16 or later on Windows, macOS, and Linux, and includes a vendored libsodium subset. source
- Client authorization
- Connect tokens let a game backend authorize which clients may connect to a server. source
- Client slots
- Servers assign clients to slots and deny connections when all slots are occupied. source
- Connection model
- It provides a minimal connection-oriented protocol over UDP for exchanging unreliable, unordered packets. source
- Disconnects
- The protocol supports clean client- or server-side disconnects and timeouts for hard disconnects. source
- Encryption
- Packets are encrypted and signed using the libsodium cryptography library. source
- Implementations
- The repository lists implementations in C, C#, Go, Rust, Unity, Unreal Engine 4, and TypeScript. source
- Implementations
- The repository provides a C implementation and links to C#, Go, Rust, Unity, Unreal Engine 4, and TypeScript implementations. source
- Intended users
- The maker describes the protocol for real-time multiplayer games and shows a backend issuing connect tokens after matchmaking. source
- Known version issue
- The project says a nonce-reuse issue affected versions 1.3.5 and earlier and was fixed in 1.4.0. source
- License
- The repository publishes netcode under the BSD 3-Clause license. source
- License
- The C implementation is released under the BSD 3-Clause license. source
- Network support
- The protocol supports IPv4 and IPv6 connections and packet tagging intended to reduce Wi-Fi jitter. source
- Network support
- The protocol supports IPv4 and IPv6 connections and packet tagging to reduce Wi-Fi jitter. source
- Packet delivery
- It lets applications exchange unreliable, unordered packets over UDP without TCP head-of-line blocking. source
- Packet security
- Packets are encrypted and signed, with protections against crafted packets, replay attacks, and amplification attacks; cryptography uses libsodium. source
- Purpose
- netcode is a secure client/server protocol for multiplayer games built on UDP. source
- Purpose
- netcode is a secure, connection-oriented client/server protocol for multiplayer games built on UDP. source
- Security reporting
- Vulnerability reports can be submitted privately through GitHub or by email, and fixes are made on the latest release without backports to older release lines. source
- Server slots
- Servers assign connecting clients to a configured slot and deny connections when all slots are occupied. source
Checked against the maker's pages on 9 Oct 2026.