User spotlight: Making of Fahrenheit 451 (a UE5 short film)
Motion graphics artists Dave Weinstock and Seiji Anderson break down how they created the cinematics of the short film Fahrenheit 451, using Unreal Engine.
December 19, 2025
5
min read
Git Version Control for Godot
Learn how to use GitHub on a Godot project in a 5 minutes. We will use the free version of Anchorpoint to push and pull our files to GitHub.
TL;DR: Learn how to set up Godot Git version control with GitHub and Anchorpoint in under five minutes. This guide covers essential Godot 4.6+ setup, explains how to automatically manage binary assets with Git LFS, and demonstrates why a visual Git solution is ideal for artists and non-technical contributors who want to avoid the command line.
Why should I use version control?
Version control is a cornerstone of your workflow with Godot or any other game engine. Game engines do not understand incremental saving and you don’t want to copy and paste your “backup files” on your desktop. Version control solves that problem and allows you:
- To do backups for your project, in case your files get corrupted
- To sync between computers
- To share your files with your team
- It forces you to work in a proper way by committing your work at least once a day
- Adds documentation to your work
- It facilitates team collaboration with features such as file locking, so that you prevent losing work due to the fact that two people have worked on the same file at the same time
The difference between Git and GitHub?
Git is a version control systems. Alternative solutions to Git are Perforce, Unity Version Control or SVN. Git is free and open source and has a huge ecosystem of cloud providers, applications and knowledge. GitHub is a cloud provider, that is based on Git. You can even download the Godot source code from there. GitHub will act like a “Dropbox alternative” where you will push and pull files.
If you want to work purely offline, of course you don’t need GitHub. But everywhere on the internet, people will recommend it’s usage for solo developers as well, because you have a free backup solution.
Why do I need Anchorpoint for Godot?
Although you can use the command line or a basic Godot Git plugin, Anchorpoint is specifically designed for the game development pipeline. Unlike standard Git clients designed for software developers, Anchorpoint caters to the needs of artists and non-technical team members. It streamlines the Godot Git workflow by automating complex tasks, such as Git LFS configuration and file locking, so you can concentrate on developing your game.
Set up Godot, GitHub and Anchorpoint
The whole setup requires just 3 minutes. We will use the GitHub integration in Anchorpoint, so that we can create repositories directly from it, which is faster than doing this on GitHub.
Syncing local files with GitHub
For the first time, we need to commit all of our files to GitHub. “Commit” means just to create a version that we can go back later on. It’s like creating a checkpoint of your project. In Anchorpoint you will sync the files, which is a combination of a commit and a push to GitHub.
Now, make a change in Godot by e.g. adding a comment to your code or by adding a new asset.
When should I commit?
There is no hard rule when you should commit your work. The recommendation is when you made a meaningful change to your project. E.g., you implemented a new input system or your made a significant update to that input system. Once you are done, commit that as a new version.
You should at least commit your files when you finish your daily work.
FAQs
How much storage can I have on GitHub?
GitHub Git LFS offers users 10 GB of free storage and bandwidth. Any additional usage is charged at $0.07 per GB for storage and $0.0875 per GB for outbound data transfer. If you think, that you need a lot of storage (more than 150GB) then it makes sense to switch to Azure DevOps, because as of today, there are no storage limitations.
What is a .gitignore file?
A .gitignore file is a central component for managing your Godot projects using Git. It is a set of rules that tells Git which files to exclude from version control. When you adjust the version control settings in Godot, it will automatically create the .gitignore file. Each game engine such as Unity and Unreal have different .gitignore settings.
What is Git LFS?
Git was made to deal with code, which is basically a bunch of text files. Games require a lot of binary files like 3D models, textures, sound files, etc. To keep the efficiency and to not download the whole history of your 3D models and textures, Git introduces an add-on in 2014 called Git LFS (Large File Storage). This add-on is now part of almost every Git product and service out there. With Anchorpoint, you don’t encounter any Git LFS related commands, because that happens in the background. If you use other clients, you will need to configure Git LFS at the beginning of your project.
Can I use file locking with my Godot project?
One of the core problems that Anchorpoint solves is collaboration friction. Its custom file locking system allows you to lock specific Godot scenes or assets, preventing two team members from working on the same file simultaneously and avoiding painful merge conflicts. If needed, you just have to add them. Right-click Project Settings > Git > Auto lock binary files.
Where to learn more
- Git with Unreal Engine 5: https://www.anchorpoint.app/blog/git-with-unreal-engine-5
- How to use GitHub on a Unity project: https://www.anchorpoint.app/blog/github-and-unity
- Git vs Perforce for Unreal and Unity projects: https://www.anchorpoint.app/blog/git-vs-perforce-for-game-development
- Push and pull files with Git LFS: https://www.anchorpoint.app/blog/push-and-pull-files-with-git-lfs
