Speed up your release timelines
Unity Version Control is a scalable, engine-agnostic version control and source code management tool for game development studios of all sizes. Built with powerful Plastic SCM technology, Unity Version Control offers optimized workflows for artists and programmers, and superior speed working with large files and binaries.
Plastic SCM is now Unity Version Control, a component of Unity DevOps
Unity Version Control web experience in the Unity dashboard
New Unity Version Control web experience
Unity Version Control users now have access to powerful VCS functionality directly from the Unity web dashboard. You can onboard and grant permissions to new users, view content across both org and repo levels, and kick off and conduct code reviews without downloading or opening a separate client.
For programmers
Minimize conflicts and accelerate production with powerful branching and merging capabilities. Work centralized or distributed with a system built to handle large files and repos.
For artists
Created for more than just code, Unity Version Control minimizes conflicts with locking to let you work independently in a separate workspace connected to your main project repo.
For Git users
Unity Version Control just works. Migration is simple, so you can work with big files out of the box and commit carefree. Everyone can use it – regardless of technical skill level.
For Perforce users
A solution that works for the whole team. Keep devs happy with robust branching and merging, plus the ability to work distributed while enabling simpler artist and non-dev workflows.
“The speed of pulling and pushing sizable repos is impressive, and the system is considerably faster than our previous solution. The UI is intuitive for both developers and artists.”
“We have done some really, really huge merges over the years – the kind of merges that you would have ended up having to do by hand with other tools. It just works.”
Version control integrations
Unity Version Control works with any engine and easily integrates into your DevOps toolchain. It plays well with tools for issue tracking, communication, collaboration, CI, IDEs, and more.
Games making it happen
Goodbye Volcano High
How does a worker-owned cooperative studio get both artists and engineers aligned on a production process? Read how KO_OP powered collaboration with Unity’s version control solution.
Return to Nangrim
Read how Sycoforge leveraged Unity tools to manage the growing scope of their project and integrate player feedback for rapid, iterative game development.
Subnautica
Find out why Unknown Worlds chose Unity solutions for version control to help bring Subnautica to life.
Resources
Project organization and VCS best practices
Learn the key concepts of version control, as well as tips and tricks you can use when setting up your Unity project to help ensure that team collaboration is smooth and efficient.
Getting started
Want to dive in to Unity Version Control but don’t know where to begin? Check out our introductory course on Unity Learn and start collaborating more efficiently today.
Frequently asked questions
No, you can combine Unity Version Control with almost any other software in your stack to unlock a powerful VCS. However, the Unity Version Control package for Unity makes using version control within the core game engine extra intuitive.
To begin using Unity Version Control, you need to sign up for the service using your Unity account. You can find a helpful guide for getting started in the Unity Editor or another engine here. If you have more questions before you get started, please feel free to contact us.
Unity Version Control is a hosted, multi-tenant, cloud-based server that organizations can use to store their Plastic repositories in the cloud.
Unity Version Control is source control for game development teams working with large repositories and files who only need a cloud server (and optional local cloned repos). You can push/pull (or directly check in) to a cloud server. Unity Version Control includes the client and the cloud service.
You’ll need a Unity DevOps subscription to store your repositories in our hosted service.
Unity Version Control is our new brand for Plastic SCM. It is still the same great solution with all of the features you have come to enjoy, simply under a new brand name.
No. Unity Version Control is a hosted service that runs in the cloud. The version control client can be downloaded locally, but still connects to the cloud service.
You push your data from your local server to the Cloud.
Yes, you can check in and merge directly to the cloud.
Yes, you can. You can also configure the files that will be locked on checkout from your Unity Version Control organization’s dashboard.
Unity Version Control can encrypt your code and data before uploading it to the cloud. When you request a new Unity Version Control organization to host your repositories, you can set it as “encrypted.” This means that whenever you upload data to it, the cloud requires data encryption.
Unity Version Control only allows SSL connections.
Unity Version Control includes a free tier with three free seats and 5 GB of storage. After the fourth user, you pay monthly per seat. If you exceed 5 GB of storage, you pay for extra storage per team, not per user. See pricing for details.
Yes. For licensing purposes, we only count the number of active users, regardless of the number of devices used or the number of servers installed.
No. For licensing purposes, we only count the number of active users, regardless of the number of devices used or the number of servers installed.
No. A user is considered read-only when they do not perform write operations, such as a checkin.
Yes. You can activate and deactivate users any time you want. Unity Version Control keeps the history of every user, active or deactivated. A user must be active to access the system.
- Support response in less than 24 hours by email
- Remote support connection to solve more complex problems
- Priority for code “hotfixes” from the development team
Learn more here.
A user is considered active when they do any of the following in a given month:
1. Write to a repository to:
- Checkin
- Do a code review
- Create an object like a label, changeset (push or checkin), branch, attribute or repo
2. Upload or download 5 MB of data