Netcode for GameObjects
docs.unity.com
- Free plan
- Windows
- macOS
- Linux
- Web
- iPhone and iPad
- Android
What Netcode for GameObjects is
Netcode for GameObjects is a Unity networking library for synchronizing GameObjects and world data during multiplayer sessions. Unity describes it as a fit for games with smaller player counts and less complex game logic, including multiplayer additions to existing GameObject-based single-player games. Developers can use client- or server-authoritative networking. NetworkBehaviour components use NetworkVariables to synchronize state and RPCs to send network messages. Integrated scene management is enabled by default and keeps scenes synchronized across connected clients. Unity Transport is the default transport, and Unity Relay can provide Relay networking for GameObject and MonoBehaviour workflows. Unity Multiplayer Services sessions are compatible with the package, which handles gameplay-state replication after players connect. The package is free, but installation requires an active Unity account with a valid license, a supported Unity version, and an existing Unity project. Supported systems include Windows, macOS, Linux, iOS, Android, XR platforms on those systems, most closed platforms, and WebGL for specified package versions. It does not include matchmaking.
Who it suits
It suits Unity developers building multiplayer games with smaller player counts and less complex logic, especially when extending an existing GameObject-based project. Teams needing matchmaking or full client-side prediction and reconciliation must build or provide those capabilities separately.
Good to know, and what to watch
- Free Unity package with client- or server-authoritative models.
- Synchronizes state through NetworkVariables and RPCs.
- Scene management synchronizes scenes across connected clients.
- Unity Transport is the default transport.
- Compatible with Unity Relay and Multiplayer Services sessions.
- Requires a valid Unity account and license.
- Requires a supported Unity version and existing Unity project.
- Matchmaking must be implemented with third-party services.
- Full client-side prediction and reconciliation must be built by developers.
Plans
Every plan and priceNetcode for GameObjects
Free plan
Getting started
- Create an existing Unity project.
- Use a supported Unity version; the listed plan requires Unity Editor 2021.3 or later.
- Sign in with an active Unity account and valid license.
- Install the Unity package in the project.
- Choose Unity Transport by default, or use compatible Unity Relay and Multiplayer Services sessions as needed.
Limits to check
The package is free, but requires a valid Unity account and license, an existing project, and a supported Unity version. It has no matchmaking functionality, and the developer must build a full client-side prediction and reconciliation system.
The verdict
Netcode for GameObjects covers core synchronization and scene management for Unity multiplayer projects. Account, license, project, matchmaking, and prediction requirements are important to factor into an implementation plan.
Questions people ask
How much does Netcode for GameObjects cost?
The package is free: free. It requires a valid Unity account and license, and the listed plan specifies Unity Editor 2021.3 or later.
What do I need to install it?
Installation requires an active Unity account with a valid license, a supported Unity version, and an existing Unity project.
Which platforms are supported?
The installation guide lists Windows, macOS, Linux, iOS, Android, XR platforms on those systems, most closed platforms, and WebGL with specified package versions.
Does it include matchmaking?
No. Matchmaking must be implemented using third-party services.
Which networking models and transports does it support?
It supports client- or server-authoritative models and uses Unity Transport by default. Listed protocols include UDP, DTLS, and secure WebSocket (WSS).
What the maker publishes
- Company
- Unity’s SEC filing states that Unity was founded in Denmark in 2004 and has principal corporate offices in San Francisco, California. source
- Core synchronization
- NetworkBehaviour components use NetworkVariables to synchronize state and RPCs to send messages over the network. source
- Default transport
- Netcode for GameObjects uses Unity Transport by default. source
- Headquarters
- San Francisco, California, United States source
- Install requirements
- Installation requires an active Unity account with a valid license, a supported Unity version, and an existing Unity project. source
- Intended games
- Unity describes it as suited to games with smaller player counts and less complex game logic, including adding multiplayer to an existing GameObject-based single-player game. source
- Matchmaking limit
- Netcode for GameObjects has no matchmaking functionality; Unity’s FAQ says matchmaking must be implemented using third-party services. source
- Network model
- Its networking can use client- or server-authoritative models. source
- Prediction limit
- The documented anticipation components provide building blocks, but a full client-side prediction and reconciliation system must be built by the developer. source
- Purpose
- Netcode for GameObjects is a high-level networking library for synchronizing GameObjects and world data across multiplayer sessions. source
- Scene management
- The package includes integrated scene management that is enabled by default and synchronizes scenes across connected clients. source
- Security and trust
- Unity’s Trust Center lists a SOC 2 Type II badge, a PCI badge, and a vulnerability reporting and bug bounty program; these are Unity-level disclosures, not a Netcode-specific certification claim. source
- Service integration
- Unity Relay works with Netcode for GameObjects to provide Relay networking for GameObject and MonoBehaviour workflows. source
- Session integration
- Unity Multiplayer Services sessions are compatible with Netcode for GameObjects, which handles gameplay state replication after players connect. source
- Supported platforms
- The installation guide lists Windows, macOS, Linux, iOS, Android, XR platforms on those systems, most closed platforms, and WebGL with specified package versions. source
Checked against the maker's pages on 7 Oct 2026.