Original Forge vs Neo vs reForge: identify the repository first
The interface can look familiar while the maintainer, branch, model support and dependencies are different. Use the owner/repository/branch fingerprint before following a tutorial, updating or migrating.
They are related codebases, not interchangeable editions.
Original Forge is the `lllyasviel` upstream. reForge is a direct fork maintained by `Panchovix`. Forge Classic and Forge Neo are the `classic` and `neo` branches inside `Haoming02/sd-webui-forge-classic`.
No downstream project becomes an “official update” merely because it is newer or keeps the interface. Before acting, write four fields: owner, repository, branch and commit.
Paste the source, not the product nickname.
Paste a GitHub URL, `git remote -v` line, folder path or startup text. The matcher only identifies known owner/repository/branch strings; it does not inspect your computer.
Four names. Three repositories. Two branches share one URL.
A product name is not a sufficient technical identifier. These cards pin the verified owner, repository and branch before describing current state.
Original Forge
lllyasviel/stable-diffusion-webui-forge - Branch
- main
- Snapshot
- dfdcbab · 26 Jun 2025
Repository is public and not archived. The last inspected main commit fixes SD Upscale batch handling; the repository push timestamp is 31 Jul 2025.
Keep it when its dated model scope, controls and extensions already complete your work. Do not call it Neo or reForge.Forge Neo
Haoming02/sd-webui-forge-classic - Branch
- neo
- Snapshot
- 4d3444d · 29 Aug 2026
The repository default branch is neo. Release 2.28.1 was published 3 Aug 2026; the inspected neo branch continued changing later in August.
Evaluate it separately when a model or workflow named in the Neo README is required. Neo requirements and removed features are Neo facts only.Forge Classic
Haoming02/sd-webui-forge-classic - Branch
- classic
- Snapshot
- 9cedffa · checked 31 Aug 2026
Classic is a separate branch in the same repository as Neo. A bare repository URL is therefore not enough to identify an installation.
Treat Classic as its own compatibility target when an older SD 1.x or SDXL-oriented workflow depends on that branch.reForge
Panchovix/stable-diffusion-webui-reForge - Branch
- main
- Snapshot
- 739b2e1 · 14 Apr 2026
Public, not archived and directly marked by GitHub as forked from the original. Its README recommends Classic or Neo for stability and describes new work as slow or branch-dependent.
Keep or test it only against the exact reForge branch and dependencies your workflow uses. Do not infer original Forge support from reForge behavior.VERIFIED GitHub’s archive flag is false for all three repositories at the checked time. “Not archived” is not the same claim as active feature development or guaranteed support.
Read “continuation” as relationship, not endorsement.
Forks can preserve or extend a useful code line. They keep their own maintainers, releases, issue trackers and compatibility boundaries.
2024 · original Forge starts
lllyasviel creates the independent upstream repository on top of Stable Diffusion WebUI.
Jun 2024 · reForge fork
Panchovix creates a direct GitHub fork while the original project changes direction.
Aug 2024 · Classic fork
Haoming02 creates sd-webui-forge-classic from original Forge and maintains an older-line branch.
Sep 2025 · Neo announced
The same Haoming02 repository adds the neo line for newer Forge continuation work and newer model families.
2026 · four names coexist
Search results, launchers and local folder names can surface all four; owner, repository and branch remain the reliable identity.
Compare the project boundary before the feature list.
This is a repository snapshot, not a permanent support matrix. A feature named by one branch is not evidence for any other column.
| Boundary | Original Forge | Forge Neo | Forge Classic | reForge |
|---|---|---|---|---|
| Canonical identity | lllyasviel/stable-diffusion-webui-forge · main | Haoming02/sd-webui-forge-classic · neo | Haoming02/sd-webui-forge-classic · classic | Panchovix/stable-diffusion-webui-reForge · main |
| GitHub relationship | Independent upstream | Fork lineage from original Forge | Fork lineage from original Forge | Direct GitHub fork of original Forge |
| Maintainer | lllyasviel | Haoming02 | Haoming02 | Panchovix |
| Checked code snapshot | dfdcbab · 26 Jun 2025 | 4d3444d · 29 Aug 2026 | 9cedffa · checked 31 Aug 2026 | 739b2e1 · 14 Apr 2026 |
| Repository archive flag | Not archived | Not archived | Not archived | Not archived |
| Release signal | latest tag published in 2024; assets are dated | 2.28.1 · 3 Aug 2026 | Shares repository release history; verify target branch | No GitHub releases returned at check |
| Declared direction | Resource management, inference and experimental WebUI work | Usability, optimization and newer popular models | Older Forge line with continued fixes/features | Forge/reForge variants with slow, branch-specific continuation work |
| Model support rule | Only claims documented or reproduced on original commit | Only models listed for the checked Neo branch | Only models supported by the Classic branch | Only models supported by the selected reForge branch |
| Extension rule | Test against original Forge and Gradio/backend snapshot | Neo compatibility does not prove original compatibility | Classic compatibility does not prove Neo compatibility | reForge extensions and samplers remain reForge-specific |
| Install identity | Clone URL resolves to lllyasviel; branch main | Clone Haoming02 repo and explicitly use neo | Clone Haoming02 repo and explicitly use classic | Clone URL resolves to Panchovix; branch must be recorded |
| Update risk | An update moves within original main | Default branch can move rapidly; release and commit matter | Wrong branch can silently turn a Classic plan into Neo | Branch names have represented different backend experiments |
| This site’s scope | Primary product documented throughout the hub | Covered here only as a separate adjacent project | Covered here only as a separate adjacent project | Covered here only as a separate adjacent project |
Start from the requirement that changed.
“Newer” is too vague. Name the model, extension, hardware constraint or maintenance problem that makes a separate candidate worth testing.
My current original Forge workflow already works
Keep the working treeRecord its commit and dependencies before considering any move. A newer downstream commit is not automatically a safer environment.
I need a model explicitly listed by Forge Neo
Test Neo in a separate folderUse Haoming02/sd-webui-forge-classic on branch neo. Confirm Python, Torch, model companions and removed features in the current Neo README.
I need the older Forge backend or SDXL-focused compatibility
Compare Classic and your current treeUse branch classic deliberately. Do not clone the repository default and assume you received Classic.
My established reForge setup is stable
Pin reForge before changing itRecord branch, commit, Python, Torch, extensions and model hashes. Its README describes branches with different backends and stability.
A tutorial says “download the latest Forge”
Stop and resolve the ownerOpen the linked URL. If owner, repository and branch are missing, the instruction is not sufficiently identified to follow safely.
I only want the newest commit date
Change the decision criterionCommit recency does not prove your model, GPU, extension or workflow works. Test the exact job and keep rollback.
A safe switch leaves an audit trail.
Complete all ten fields before replacing a working tree. The receipt records identity and recovery; it does not certify compatibility.
Prepare a rollback pointTen records still missing.
Move assets without collapsing environments.
The safe unit of migration is a whole tested workflow. Copying a folder until the UI opens does not prove model, extension or output compatibility.
Plan shared model storageInstall side by side
Do not switch the remote or branch inside the only working environment. A separate folder keeps dependencies and rollback visible.
Share assets deliberately
Model files may be referenced from shared storage, but each project can expect different folders, companion files or loaders. Start read-only when possible.
Do not copy the venv
Python and Torch requirements can diverge. Let each project build its own environment from its own files.
Inventory extensions
An extension working in one Forge line is not evidence for another. Add extensions one at a time after a clean baseline.
Match the real job
Use the same source assets and record every exposed setting. For newer model families, compare task completion—not impossible cross-family image parity.
Restart before deciding
A candidate passes only after restart, model reload, one edit, output save and a verified rollback path.
Six statements that need a narrower label.
Repository metadata can verify identity and dates. It cannot turn community preference into universal performance or compatibility.
“Forge Neo is the official new version of original Forge.”
Rejected. Neo is maintained by Haoming02 in a downstream fork repository. It may continue a code line; it does not become lllyasviel’s repository.
“Forge Classic and Forge Neo are separate repositories.”
Rejected. They are branches in Haoming02/sd-webui-forge-classic. The branch is part of the product identity.
“reForge development ceased.”
Incomplete. The maintainer announced a pause in April 2025, a limited return in July, and the repository later received a commit in April 2026. Current expectations remain cautious.
“The newest fork is faster and more stable.”
No controlled GPU benchmark or matched workflow test was performed. Newer code can add models while changing dependencies and compatibility.
“All original Forge extensions work in Neo or reForge.”
No universal compatibility evidence exists. Backend, Gradio, Python and integrated components differ by project and branch.
“I should migrate because original Forge looks inactive.”
Maintenance state is one input. If the dated original build completes the job, migration cost and the required feature must still be tested.
Resolve the name, branch and cost.
These answers cover the real question patterns found in current repository discussions and user searches.
What is the difference between original Forge, Forge Neo and reForge?
Original Forge is lllyasviel/stable-diffusion-webui-forge. reForge is Panchovix/stable-diffusion-webui-reForge, a direct downstream fork. Forge Neo is the neo branch of Haoming02/sd-webui-forge-classic. They share lineage and a familiar WebUI shape, but have different maintainers, commits, dependencies, model scope and compatibility.
Is Forge Neo the official successor to Stable Diffusion WebUI Forge?
No official succession was verified. Forge Neo describes itself as a continuation, but it is maintained by Haoming02 in a fork of the original repository. The original remains the lllyasviel repository.
Who maintains Forge Neo?
The checked Forge Neo branch is maintained in Haoming02/sd-webui-forge-classic. Its default branch is neo at the checked date.
Is Forge Neo a separate repository from Forge Classic?
No. Neo and Classic are branches in the same Haoming02/sd-webui-forge-classic repository. Always record the branch because a bare repository URL is ambiguous.
Is reForge a fork of original Forge?
Yes. GitHub identifies Panchovix/stable-diffusion-webui-reForge as forked from lllyasviel/stable-diffusion-webui-forge.
Is reForge still maintained in 2026?
The repository is public and not archived, and the latest inspected main commit is dated 14 April 2026. However, its README recommends Classic or Neo for stability and describes new development as slow and branch-dependent. Treat status as a dated snapshot, not a guarantee.
Is original Stable Diffusion WebUI Forge abandoned?
The original repository is public and not archived. Its latest inspected main commit is from 26 June 2025 and its push timestamp is 31 July 2025. Those facts show a dated code state; they do not by themselves prove future maintenance or that a working installation must be replaced.
Which Forge version is most up to date?
By the checked repository dates, the Neo branch changed most recently. That answers commit recency only. It does not establish compatibility, speed, image quality or suitability for your required model and hardware.
Should I switch from original Forge to Forge Neo?
Switch only when Neo solves a named requirement and passes a separate-install trial. Keep original Forge when its pinned environment completes your work and the migration offers no tested benefit.
Should I switch from reForge to Forge Neo?
Test Neo separately when you need its declared newer-model route or when reForge cannot complete the job. Preserve the reForge folder, branch, commit, extensions and output baseline until Neo survives restart and repeats the workflow.
Should I use Forge Classic or Forge Neo?
Classic follows the older Forge line and is commonly selected for established SD 1.x or SDXL-oriented workflows. Neo follows the newer line and declares support for newer model families. Choose from the exact model and dependency requirement, not the word “latest.”
Can original Forge run the same models as Forge Neo?
Do not assume so. Neo’s README lists models and companion requirements that are Neo-specific. Original support must be verified in original code, documentation or a reproduced test on the original commit.
Can Forge Neo run SDXL and SD 1.5 models?
The current Neo README says most base A1111 features should still function and documents advanced SDXL work, but exact checkpoints, LoRAs, ControlNet and extensions remain version-specific. Test the exact files and workflow.
Does Forge Neo support newer image and video models?
The inspected Neo README declares several newer image and video families. Those claims apply only to the checked Neo branch and its listed limitations, companion files and runtime—not to original Forge, Classic or reForge.
Can Forge Neo and original Forge be installed together?
Yes, as separate application folders with separate environments. Shared model storage can reduce duplication, but first verify folder mappings and keep configuration, outputs and extensions separate.
Can Forge Neo and reForge share model folders?
Potentially, but sharing files does not guarantee loader compatibility. Verify each project’s model paths, supported formats, companion encoders and VAE requirements. Do not share virtual environments.
Can I copy extensions from original Forge to Forge Neo?
Do not bulk-copy them. Start Neo without third-party extensions, verify a baseline, then install one extension at a time from its actual repository and record the tested commit.
How do I tell which Forge I installed?
Check git remote -v, the current branch and git rev-parse HEAD. For packaged installations, inspect the download URL and startup log. Folder names and similar interfaces are not reliable identifiers.
Why does my folder say Forge but the console says version neo?
The folder name is chosen locally and can be anything. A Neo checkout can live in a folder called Forge. Trust the remote owner/repository, branch and commit printed or queried from Git.
What does the neo branch mean in the Forge Classic repository?
It identifies Forge Neo inside Haoming02/sd-webui-forge-classic. The classic branch represents the older continuation line; neo represents the newer continuation line. Branch selection changes the code you install.
Is a Forge Neo release an original Forge release?
No. A release in Haoming02/sd-webui-forge-classic belongs to that downstream repository. Original Forge releases are published under lllyasviel/stable-diffusion-webui-forge.
Where should I download original Forge, Forge Neo or reForge?
Use the exact project repository: lllyasviel/stable-diffusion-webui-forge for original Forge, the neo branch of Haoming02/sd-webui-forge-classic for Neo, and Panchovix/stable-diffusion-webui-reForge for reForge. This site does not mirror or relabel binaries.
Does Forge Neo have an official one-click installer?
The checked Neo README documents a Git clone on branch neo, a separate uv or Python environment, and webui-user.bat. Release 2.28.1 has no attached binary assets. A third-party portable package or manager is not an official Neo release and must be evaluated under its own owner.
Which Forge is fastest or uses the least VRAM?
No universal result is supported here. Compare exact commits with the same supported model, dimensions, batch, precision, attention, warm-up and extension state on your hardware. Newer model families cannot be compared as if they were the same workload.
Will my prompts and images transfer between Forge variants?
Images and prompt text can be preserved, but behavior may not. Save model hashes, VAE and encoders, LoRAs, sampler, scheduler, seed, dimensions, extensions and project commit before expecting reproduction.
What is the safest way to migrate between Forge forks?
Use a new folder, a new virtual environment and a pinned commit. Reference or copy model files deliberately, rebuild extensions one at a time, reproduce one real task, restart, and keep the old installation untouched until rollback is proven.
Repository facts first. Community vocabulary second.
Primary repositories and maintainer statements establish identity and dated state. Videos and community threads reveal confusion and migration needs, not product guarantees.
Local research catalog used · 9 records
Canonical product identity, installation and dated status.
Maintenance snapshot; commit recency is not a feature score.
Original project direction and rewrite boundary.
Direct fork identity; never imported into original features.
Two branch identities under one repository.
Maintainer-authored lineage and newer-model intent.
Pause signal requiring a later-status recheck.
Community migration and extension questions only.
Search vocabulary and confusion; no features transferred to original Forge.
No speed, VRAM or image-quality winner is claimed.
The three candidates were not installed on a GPU machine for this page.
Branches, commits, releases and README scope can change after 31 Aug 2026.
No Neo, Classic or reForge feature is attributed to original Forge.