If you’re a software developer, using Git as your version control tool is a no-brainer (I’m ignoring the people who still use SVN 👴🏻). However, storing non-text assets brings unique challenges, especially when managing large art assets like 3D models, textures, and audio files. Git alone struggles here, and while Git LFS, Perforce, and Plastic SCM offer solutions, each comes with trade-offs.
Git LFS: Git with Limits
Git LFS extends Git to handle large files by storing them outside the main repo. It’s easy to adopt if you’re already using Git and works well for small teams or early-stage projects. However, it struggles with large or frequently changing files and can become slow as asset libraries grow. Also, artists may find Git’s workflow cumbersome without additional tools.
Perforce: Built for Large Teams and Assets
Perforce (Helix Core) is the industry standard for AAA studios, built specifically to manage huge binary files efficiently. Its centralized system and tight integrations with engines like Unreal and Unity make it ideal for large, asset-heavy projects. The downside? It requires dedicated infrastructure, has a steep learning curve, and may be overkill for smaller teams.
Plastic SCM: A Flexible Middle Ground
Plastic SCM blends the best of Git and Perforce. It handles large files natively and offers user-friendly graphical tools, making it great for teams with many artists. It supports both centralized and distributed workflows, but isn’t as widely adopted, meaning fewer community resources. Still, for mid-sized teams, it strikes a good balance between power and usability.
Conclusion
If you’re a small team already on Git, Git LFS can work—until it doesn’t. It seems like Perforce is the safest bet for big studios and massive asset libraries. Plastic SCM offers a flexible alternative, especially for teams that want strong asset management without Perforce’s complexity. Ultimately, the right tool depends on your team size and project needs.
