Git-based version control directly inside Blender.


Requirements

Prerequisites

Before installing the addon, make sure the following tools are in place:

Requirement Where to get it Notes
Blender 5.x or later blender.org Earlier versions are not tested
Git git-scm.com Must be installed and available system-wide
Git LFS git-lfs.com Required. Handles large .blend files efficiently
Why Git LFS?Standard Git stores the full history of every changed file. A 200 MB .blend with 50 commits would bloat the repository to gigabytes. Git LFS stores large binary files in a separate object store and keeps only small pointer files in Git history, keeping things lean and fast. It is a separate install from Git itself.
Setup

Installation

  1. 1 Download the addon .zip file.
  2. 2 In Blender, go to Edit > Preferences > Add-ons.
  3. 3 Click Install and select the downloaded .zip.
  4. 4 Enable the addon by ticking its checkbox.

The addon adds a Git tab to the 3D Viewport's N-panel. Press N to open the sidebar if it is not visible.

First-time Configuration

Open the addon preferences and check the Requirements section, which shows whether Blender can find Git and Git LFS. Install any missing tools, then restart Blender.

Addon preferences -> Requirements section

Before committing, set your Git author identity from Configuration > Set Identity. Enter your name and email, then save them for the current repository.


Configuration -> Set Identity dialog
No workflow settings need to be configured. Scene snapshots are always captured automatically when you stage a .blend file.
First Steps

Getting Started

Starting a New Project

  1. 1 Save your .blend file to the folder where you want the project to live.
  2. 2 Open the Git panel. It will prompt: "No Git repository found."
  3. 3 Click Initialize Repository.

The addon creates a Git repository, configures Git LFS, prepares .gitignore and .gitattributes, and makes the first commit.


Joining an Existing Project

  1. 1 Open Blender before opening any .blend file.
  2. 2 Click Clone it here (visible when no repository is detected).
  3. 3 Enter the repository URL and choose a destination folder.
  4. 4 After cloning, open your .blend from that folder via File > Open.
Known Limitations

Limitations

Conflict resolution is all-or-nothing per file: Because .blend files are binary, you cannot combine parts of two versions. You choose one complete version of each conflicted file.
Conflicted files should not be reopened before resolution: While a .blend file is unresolved, opening it normally can disturb the binary conflict state.
Staging and discarding apply to entire files: Every staging, unstaging, or discard operation affects the whole file at once.
Git & Git LFS are required: Git LFS must be installed separately before initializing a repository. The addon will refuse to initialize without it.
Blender 5.x only: The addon is built for Blender 5.x and may not function correctly on earlier versions.
Support

Contact

Questions or issues? Reach out through:

Legal

License

GPL-3.0-or-later. See the LICENSE file included with the addon for details.
$14.90

Have questions about this product?
Login to message

Details
Blender Extension Compatible Yes
Dev Fund Contributor
Published 4 months ago
Blender Version 5.0 - 5.1
Extension Type Add-on
Render Engine Used Cycles, Eevee
License GPL