Original Forge Project Status
The repository is public and not archived. The last inspected main commit is from June 2025, and the release files are dated 2024. That is enough to describe the evidence—not enough to claim active maintenance.
Is Forge still maintained?
We found no newer main commit than dfdcbab from 26 June 2025 and no newer release page than the tag published on 5 February 2024. The repository is not archived, but that flag only tells us it remains writable.
Do not call the project definitively abandoned without an official declaration. For installation and update decisions, treat Original Forge as a dated, low-activity snapshot and verify the exact task on the exact commit you intend to keep.
dfdcbab26 Jun 2025What does this GitHub signal actually prove?
Select the signal you found. The reader separates the observation from the conclusion people commonly stretch it into.
The repository is not archived.
- What it proves
- At the checked time, GitHub did not mark the repository read-only. Source, Issues, pull requests and Discussions can still receive activity.
- What it does not prove
- It does not prove a maintainer is reviewing reports, merging changes, publishing releases, or promising future compatibility.
- Use it correctly
- Use the archive flag as an identity and access signal. Use dated commits, releases and maintainer statements for maintenance decisions.
“Updated” is not “new code.”
- What it proves
- The repository record changed on GitHub. Public activity such as issue, pull-request or repository metadata changes can move this timestamp.
- What it does not prove
- It does not identify a commit on the default branch and must not be displayed as the software’s last update date.
- Use it correctly
- Open the main commit history and inspect the latest commit SHA and date instead.
The repository-level push is newer than main.
- What it proves
- GitHub’s repository API reported a push on 31 July 2025 when this snapshot was captured.
- What it does not prove
- It does not prove that the push changed the default branch, shipped a release, or changed the build a user downloads.
- Use it correctly
- Pair repository-level pushed_at with the named branch history. Here, main still ends on 26 June 2025.
This is the strongest code-activity signal in the snapshot.
- What it proves
- The latest commit returned for the default main branch was dfdcbab, “Fix SD upscale Batch count,” committed on 26 June 2025.
- What it does not prove
- One commit does not establish a release cadence, support policy, response time, or compatibility with models and extensions released later.
- Use it correctly
- Record the full SHA of the build you test. Refresh this signal before any consequential update guide is published.
The word “latest” is the tag name—not a freshness claim.
- What it proves
- The release page tagged latest was published on 5 February 2024. Its three current Windows archives were uploaded or replaced on 11 August 2024.
- What it does not prove
- It does not prove the archives contain the June 2025 main commits or that they match current drivers, hardware and third-party extensions.
- Use it correctly
- Check the release publication date, asset upload date, filename and tested environment separately.
New reports are evidence of users—not maintenance.
- What it proves
- Users can still open Issues, Discussions and pull requests because the repository is public and unarchived.
- What it does not prove
- A recent report or proposed patch does not prove acknowledgement, triage, merge, release, or support by the original maintainer.
- Use it correctly
- For a support claim, look for a maintainer response, merged commit, release note or current official test—not the report date alone.
The evidence changes by layer.
Release pages, asset uploads, announcements, NEWS, branch commits and repository-level pushes are different clocks. This timeline keeps them separate.
- 01
Release page published
The tag named latest points to f11456e and a release page created in February 2024.
- 02
Experimental direction announced
The maintainer warned about extension breakage, recommended backups, and described Forge as an experimental repository for costly features.
- 03
Announcement clarified
The maintainer said the repository was not being eliminated and explained that Gradio-version changes drove the extension warning.
- 04
Previous version provided
The announcement added a previous-version route; the previous release page was published on 22 July.
- 05
Current binary assets uploaded
The three archives now attached to the latest release page have August 2024 asset timestamps.
- 06
NEWS roadmap entries
NEWS mentioned Flux work, an SD3.5 branch and a planned Gradio 5 attempt. These dated plans are not proof of completion.
- 07
Five inspected main commits
The latest five API results include FLUX sampling repair, Chroma, soft-inpainting, fp8 scaled support and the SD upscale fix.
- 08
Snapshot checked
No newer main commit or release was found. Maintenance remains UNKNOWN rather than inferred from silence.
Official tests are still dated 2024.
The README’s component table is useful historical evidence, not a live compatibility matrix. “Normal” means the component was reported normal on its listed test date.
STALE SNAPSHOT| Component | Reported status | Official last test | Current conclusion |
|---|---|---|---|
| Basic diffusion | Normal | 26 Aug 2024 | Retest on your commit and environment |
| GPU memory management | Normal | 26 Aug 2024 | Retest on your commit and environment |
| LoRAs | Normal | 26 Aug 2024 | Retest on your commit and environment |
| Preprocessors / ControlNets / IP-Adapters | Normal | 26 Aug 2024 | Retest on your commit and environment |
| Integrated and popular extensions | Normal | 27 Jul 2024 | Retest on your commit and environment |
| Gradio 4 UI / Forge Canvas | Normal | 27 Jul–26 Aug 2024 | Retest on your commit and environment |
| Surface touch pressure | Broken; pending fix | 29 Jul 2024 | Retest on your commit and environment |
| ControlNet Union | Not implemented; pending | 26 Aug 2024 | Retest on your commit and environment |
One release page, three different dates.
The tag name, publication timestamp and asset timestamps answer different questions. The release API also returned digest: null for all three current archives.
latestA label chosen by the project. It is not a semantic version or rolling freshness guarantee.
The release record’s publication time.
The three attached CUDA/Torch archives were added or replaced later.
digest: null is an absence of GitHub release metadata—not evidence that a file is corrupt.
“Forge” is not one maintenance stream.
Repository owner, repository name and branch are part of the product identity. Similar interfaces and shared history do not merge their current features.
Original Forge
lllyasviel/stable-diffusion-webui-forge- Branch
- main
- Relationship
- This page’s only product scope
reForge
Panchovix/stable-diffusion-webui-reForge- Branch
- repository-specific branches
- Relationship
- Separate fork and maintainer
Forge Classic
Haoming02/sd-webui-forge-classic- Branch
- main
- Relationship
- Separate continuation based on older Forge work
Forge Neo
Haoming02/sd-webui-forge-classic- Branch
- neo
- Relationship
- A branch in the Classic repository, not Original Forge
Act on your risk, not the project name.
Project status matters because it changes how carefully you install, update, report and migrate.
You have a working Original Forge install
Keep it intact. Record the commit, model hashes, Python/Torch, launch arguments and extensions. Test updates in a separate copy, then compare the same task before changing the working environment.
Freeze and test separatelyYou are considering a fresh install
Confirm that the dated feature and model evidence covers your actual task. Use only the original GitHub source, establish a baseline without extensions, and keep a rollback point.
Verify task fit firstYou need newer model or video support
Do not infer support from a similarly named fork. Compare current tools, then verify the exact owner/repository, branch, commit, requirements and model documentation.
Choose the repository firstYou rely on Forge in production
Treat every update as a change-controlled migration. The June 2024 announcement is historical context, but its backup and pinned-environment discipline remains a sensible operational precaution.
Pin the tested environmentQuestions the timestamps cannot answer alone.
Is Stable Diffusion WebUI Forge abandoned in 2026?
There is no verified official abandonment declaration in the inspected sources, and the original repository is not archived. However, the latest inspected main commit is from 26 June 2025 and the release page is older. We therefore label current maintenance UNKNOWN and advise treating Original Forge as a dated, low-activity snapshot.
Is original Forge still actively maintained?
This guide cannot verify active maintenance. A public, unarchived repository and new community reports are insufficient. Evidence for active maintenance would include recent main-branch commits, maintainer responses, merged fixes, releases, or a current roadmap.
What is the latest original Forge version?
The official release uses the tag name latest rather than a semantic version. The release page was published on 5 February 2024, while its current three Windows archives were uploaded on 11 August 2024. A Git checkout should be identified by its commit SHA instead.
Why does the latest Forge release say 2024 when main has 2025 commits?
GitHub releases and the main branch are separate evidence streams. New commits do not automatically replace release assets. The inspected main branch ends at dfdcbab from 26 June 2025, while the latest release page and its archives remain dated 2024.
What is the last commit in original Forge?
At the 24 August 2026 check, the latest commit returned for main was dfdcbab685e57677014f05a3309b48cc87383167, committed on 26 June 2025 with the message “Fix SD upscale Batch count.” Recheck the official history before relying on this snapshot.
Does “not archived” mean Forge is maintained?
No. GitHub uses archival to make a repository read-only and signal that it is no longer actively maintained. A repository that is not archived remains writable, but the owner may still publish rarely or not at all.
Do new Forge Issues in 2026 prove the project is supported?
No. They prove that users can submit reports. Look for acknowledgement, triage, a merged commit, a release note, or a current official test before describing an issue as fixed or officially supported.
Should I update a working Forge installation?
Do not update it in place without a rollback. Record the working commit and environment, copy or back up the installation, then reproduce the same fixed task in a separate updated copy before switching.
Are the files on the latest Forge release current?
They are the files currently attached to the official release page, but their upload timestamps are 11 August 2024 and GitHub release metadata did not publish digest values when checked. Current availability is not the same as current compatibility.
Did the Gradio 5 roadmap in NEWS happen?
The NEWS file described planned attempts around March and June 2025. This page found no inspected source that converts that dated plan into a verified completion claim, so the outcome remains UNKNOWN here.
Is Forge Neo the same project as original Forge?
No. Original Forge is lllyasviel/stable-diffusion-webui-forge. Forge Neo is the neo branch of Haoming02/sd-webui-forge-classic. Its features, fixes, requirements and maintenance must not be attributed to Original Forge.
How can I check Forge project status myself?
Confirm the repository owner, archive flag, default branch, latest main commit, repository-level pushed_at, release publication and asset dates, current announcements, and maintainer responses. Record the check date and never use one signal as a complete maintenance verdict.
Refresh from the source, not this page.
This is a static snapshot. Refresh it when main changes, release assets change, the archive flag changes, or a maintainer publishes a new status statement.
Adjacent identity sources · 3 records
- X01 · reForge Confirms a separate owner and fork relationship.
- X02 · Forge Classic / Neo Confirms a separate repository and neo branch.
- X03 · Forge Neo introduction Community announcement useful for name-confusion intent; not Original Forge evidence.