NodeSync
Never lose a node setup again.
NodeSync gives your Geometry and Shader node trees a full save history — snapshot your work, go back to any previous version instantly, and branch off to experiment without touching your main setup. All from a panel inside Blender.
- Save snapshots of your node trees at any point
- Restore any previous version in seconds - Branch to experiment, then switch back whenever you want
- Visual diff overlay — nodes highlighted in green (added), orange (modified), red (deleted)
- Push your entire node history to any Git remote (GitHub, GitLab, Codeberg, Gitea, Bitbucket, self-hosted, ...) for backup or collaboration
- Automatically saves image textures alongside shader nodes
- Works with Geometry Nodes and all Shader trees — materials, worlds, and lights
Under the hood NodeSync uses Git. You'll need to install it once from git-scm.com, but you never have to touch it — NodeSync handles everything from inside Blender.
Source code and issue tracker: https://github.com/sneeezed/nodesync
What's New
1.3.1 May 20th, 2026
NodeSync 1.3.1
Faster reverts on large projects
- Checking out an older commit used to clear and rebuild every tracked node group through Blender's Python API, even ones that were byte-identical to the target commit. NodeSync now uses the diff it already computes to reimport only the node groups that actually changed between your current state and the target commit (unchanged groups stay in bpy.data untouched). Reverts that only modify a handful of trees in a project with many tracked groups now complete dramatically faster.
Commit operator no longer freezes Blender
- Auto-push on commit previously ran on a background thread, which could conflict with Blender's main-thread-only data access and occasionally hang the UI. The commit pipeline has been rewritten as a modal operator that drives Git as a sequence of subprocess steps — each git add, git commit, git log, git rev-parse, git branch, and git push runs as its own non-blocking process polled from a timer. The UI stays responsive during long pushes, errors from any individual step are reported cleanly instead of disappearing into a thread, and commits no longer race against texture export or screenshot capture.
very cool. im always changing random stuff in my nodes and losing it so having it all in one place and seeing the progress is very cool. the only thing is the remotes are hard to figure out but otherwise its perfect.
Catastrophic first impression, but I believe it is the right approach. It managed to fail an leave a ghost file that I couldn't delete. Every method I tried failed, then I realized the file name was ending with a space character 😂. So the first 3rd method worked. You didn't reinforced my opinion of vibe coding. And please, if you could do the effort of talking to other people making the same thing before it would be great. I know 3 Add-ons doing node to JSON transcription, 3 with different approaches, none of them work ! (At least for my use case)