How do I update Forge Neo?

Two ways. If you used a one-click installer, drop the Forge Neo update file into your existing install folder and run the included .bat, which pulls the latest version. If you installed manually, run git pull in your Forge Neo folder.

Do I have to reinstall Forge Neo to update it?

No. Both update methods work in place against your existing install folder, so your models, LoRAs and settings stay where they are.

Which branch should I be updating?

The Neo branch. The repository also has a Classic/Main branch, which is an archive built on an older stable Forge release and does not receive the new features.

How often is Forge Neo updated?

Frequently — it is actively developed, which is why an in-place update path is worth setting up rather than reinstalling each time.

How to Update Forge Neo on Windows (2026)

Forge Neo is updated frequently, so keeping it current matters more here than with most Stable Diffusion frontends. The good news: you never need to reinstall. There are two in-place update paths, and which one you use depends entirely on how you installed Forge Neo in the first place.

Short answer: one-click install → use the Forge Neo update file and run its .bat. Manual install → run git pull in your Forge Neo folder.

Which update method do I need?

How you installed	How you update
One-click Windows installer	Update file → drop into the install folder → run the included `.bat`
Manual install (cloned the repo yourself)	`git pull` inside your Forge Neo folder

Method A — The update file (one-click installs)

If you set Forge Neo up with the one-click Windows installer, use the Forge Neo update file to stay current without reinstalling:

Drop it into your existing install folder — the same folder the one-click installer created, alongside your current Forge Neo files.
Run the included .bat — it pulls the latest version of Forge Neo in place.

Because this updates your existing folder rather than creating a new one, your models, LoRAs and settings stay exactly where they are. The update file is also available with Local Lab Pro.

Method B — git pull (manual installs)

If you installed Forge Neo manually by cloning the repository, you already have everything you need: open your Forge Neo folder and run git pull. That fetches the latest commits into the install you already have.

💡 Neo branch vs Classic branch The repository has two branches. The Neo branch carries all the new features (WAN 2.2, Nunchaku, Flux Context) and is actively developed. The Classic/Main branch is an archive built on an older stable Forge release. If you are pulling manually, make sure you are on the Neo branch — pulling Classic will quietly keep you on the old feature set.

FAQ

Do I have to reinstall to update? No — both methods update your existing install folder in place.

Will updating wipe my models or LoRAs? No. Both paths update the application files in the folder you already have.

Which branch should I be on? The Neo branch. Classic/Main is an older archive.

How do I install Forge Neo in the first place? See how to install Forge Neo on Windows.

New to Forge Neo? The complete Forge Neo guide covers supported models, extensions, requirements and how it compares to ComfyUI. Every Forge Neo installer is in the store or included with Local Lab Pro.