Install Stable Diffusion WebUI Forge on Windows
Download the official CUDA 12.1 / PyTorch 2.3.1 archive, verify the completed file, extract it, run update.bat, then run.bat. Stop at the first console error instead of stacking fixes.
The official Windows route
The project calls this a one-click package because Git and Python are included. It is still a multi-stage local setup: a large archive, complete extraction, a source update, environment preparation, and a browser UI served by the console process.
The package files were uploaded on 11 August 2024. Treat their CUDA and PyTorch versions as a dated environment, especially on hardware released later. This page was verified against current public sources on 24 August 2026 but could not be executed on a Windows/NVIDIA machine in this workspace.
Does this package fit your machine?
Choose the closest case before downloading almost two gigabytes.
The one-click archive is the shortest documented Windows path.
Start with the CUDA 12.1 / PyTorch 2.3.1 file recommended in the original README. The package includes its own Git and Python environment; you still need a compatible NVIDIA driver, internet access for setup, and a model after launch.
Start the Windows procedureA dated package may not recognize a new GPU architecture.
Do not assume that the August 2024 PyTorch environment supports hardware released later. If the console reports an unsupported CUDA architecture, stop changing random flags and use the controlled Git-install route with a verified compatible PyTorch build.
Review the controlled routeThe official one-click files are CUDA packages.
This page cannot convert CUDA archives into an AMD or Intel support promise. Windows DirectML, ROCm, WSL and CPU-only procedures have different dependencies and evidence; keep them outside this NVIDIA package workflow.
Review the platform boundaryDevice policy can block scripts and downloads.
Forge setup executes batch files, Git and Python code and downloads dependencies. On a managed device, do not bypass organizational controls. Ask the administrator whether local development tools and unsigned scripts are permitted.
Read the security checkpointMatch the filename before the version number.
The GitHub tag is literally named latest; it is not a promise that every embedded dependency is current. The release API returned no published digest for these assets.
webui_forge_cu121_torch231.7z
- Embedded stack
- CUDA 12.1 · PyTorch 2.3.1
- Exact size
- 1,870,203,670 bytes
- Display size
- ≈ 1.87 GB
webui_forge_cu121_torch21.7z
- Embedded stack
- CUDA 12.1 · PyTorch 2.1
- Exact size
- 1,863,595,741 bytes
- Display size
- ≈ 1.86 GB
webui_forge_cu124_torch24.7z
- Embedded stack
- CUDA 12.4 · PyTorch 2.4
- Exact size
- 1,891,112,892 bytes
- Display size
- ≈ 1.89 GB
Seven gates to a running local UI.
Do not add models, extensions or launch flags until the base process reaches its local address.
Compare with the original README ↗- 01
Confirm the repository owner
Open the original GitHub repository and verify the address contains lllyasviel/stable-diffusion-webui-forge. This guide does not mirror the archive.
- 02
Download the recommended archive
Open the official release and choose webui_forge_cu121_torch231.7z unless you have a specific, tested reason to use another published environment.
Open release page - 03
Verify the completed download
Confirm the filename and exact byte count before extraction. A shorter file is incomplete even if the browser labels the download finished.
(Get-Item "C:\Users\YOU\Downloads\webui_forge_cu121_torch231.7z").Length - 04
Extract the whole 7z archive
Use 7-Zip’s Extract command into a short writable path such as C:\AI\Forge. Do not run files from the archive preview or install under Program Files.
- 05
Run update.bat once
Let the window finish. The README explicitly requires this step because the packaged repository snapshot may be older than available source changes.
RUN ONCEupdate.bat - 06
Run run.bat
Keep the console open while the environment is prepared. First launch can download dependencies and take substantially longer than later launches.
NORMAL LAUNCHrun.bat - 07
Verify the local server
The console must stay open and print a local URL. Open that exact URL in the browser; then continue to First Run to add and validate one model.
Keep security decisions narrow.
A warning is a reason to verify the artifact, not an instruction to disable protection.
Confirm the origin before opening anything.
The browser address must be the original GitHub owner and repository. Avoid third-party bundles, shortened download links and repackaged “Forge” installers.
An unfamiliar file can trigger a reputation warning.
Microsoft documents that SmartScreen checks known unsafe files and file reputation. It does not make our guide capable of declaring a warning false. Verify first; follow device policy.
Read Microsoft’s explanation ↗Extract into a writable local directory.
C:\AI\Forge is an operational example, not an official required path. Avoid protected system folders, the archive preview and a cloud-synced folder while establishing the baseline.
Do not create a permanent broad exclusion.
If security software blocks a file, record the exact filename and detection. Recheck the source and submit a suspected false positive through the security vendor’s process instead of disabling protection globally.
The console is the progress indicator.
The browser is only the interface. Closing the console terminates the local Forge process.
- 01Update completes
update.batexits without a Git or network error. - 02Environment prepares
run.batcalls the packaged environment and Forge launcher. - 03Dependencies settle
Packages and code assets may be checked or downloaded.
- 04Server starts
The process stays alive instead of returning to “Press any key.”
- 05Local URL appears
Open the exact address printed in the console, commonly on port 7860.
The console remains running, the local Forge page loads, and refresh works while the process is open. An empty checkpoint list is a First Run task—not proof that installation failed.
Continue to First RunRoute by the first failed gate.
Preserve the first useful console message, package filename, GPU, driver and available disk space before making changes.
| Symptom | Minimum check | Next action |
|---|---|---|
| Download stops or archive will not open | Compare the exact Length value with the asset table; use 7-Zip’s extract/test operation. | Delete only the incomplete archive and download the same official asset again. Do not switch to a mirror. |
| update.bat closes immediately | Open Command Prompt in the extracted package folder and run cmd /k update.bat. | Capture the first Git, certificate, network or disk error. Do not proceed to run.bat yet. |
| run.bat closes immediately | Run cmd /k run.bat so the error stays visible. | Save the first traceback and route it by Python, Torch/CUDA, network, disk or extension symptom. Route an environment error → |
| Unsupported CUDA architecture | Record the GPU model and exact sm_* message. | Use a controlled environment only after current PyTorch documentation supports that architecture. Check the architecture boundary → |
| Browser says localhost refused connection | Check whether the console is still running and printed a local URL. | If there is no URL, troubleshoot the process error; changing browsers cannot start the server. Open the startup decision tree → |
| UI opens but no model is listed | Confirm the Forge UI itself loads and refreshes. | Installation succeeded. Continue to the model-file task and add one compatible baseline model. |
Questions before changing the environment.
Which Forge file should I download for Windows?
For the documented NVIDIA package route, start with webui_forge_cu121_torch231.7z. The original README marks CUDA 12.1 / PyTorch 2.3.1 as recommended. The label is dated evidence, not a guarantee for every GPU and driver.
Do I need to install Python or Git before using the one-click package?
No. The original README says the package includes Git and Python. They remain inside the packaged environment rather than becoming a general system installation.
Does original Forge install on Windows 10 or Windows 11?
The original project documents a Windows one-click package, but it does not publish a current Windows 10 versus Windows 11 certification matrix. This source-verified procedure should therefore be treated as a baseline to test on your exact Windows build, GPU and security policy.
Do I need to install the full CUDA Toolkit?
The prebuilt PyTorch package carries the CUDA runtime it was built to use, so the separate developer toolkit is not normally part of this one-click procedure. A compatible NVIDIA driver is still required. Building or replacing packages can introduce different toolkit requirements.
How much free disk space does Forge need on Windows?
The recommended archive alone is exactly 1,870,203,670 bytes, but extraction, the Python environment, downloaded dependencies, models and outputs require substantially more. There is no honest fixed total without naming the models and workflow you plan to store.
Does the Windows package work with AMD or Intel graphics?
This page cannot verify that. All three official package names are CUDA builds, so they are the documented NVIDIA route. AMD, Intel, DirectML, ROCm and CPU paths need separate evidence and instructions.
Will the package work with an RTX 50-series or another new NVIDIA GPU?
Do not assume it will. The package assets were uploaded in August 2024, and community reports describe unsupported sm_120 architecture errors on newer GPUs. Verify current PyTorch support for the exact GPU before choosing a route.
Why must I run update.bat before run.bat?
The original README explicitly says the update step is important because the archive may contain an older repository snapshot with unfixed bugs. Updating also changes software state, so record the working commit once your installation is stable.
Is update.bat the file I use every time?
No. Use run.bat for ordinary launches. Run update.bat deliberately when you intend to change the installed source, and keep a rollback plan before updating a working setup.
What should I do if Windows SmartScreen warns about the batch file?
Do not disable Windows security globally. Verify the GitHub owner, release URL, filename and completed download first. SmartScreen uses reputation and can warn about unfamiliar downloads; managed-device policy may prevent bypassing the warning.
Why does 7-Zip say it cannot open the Forge archive?
The download may be incomplete. Compare its exact byte count with the release metadata, use 7-Zip’s test or extract operation, and download again from the original release if the size or archive test fails.
Why does the first Forge launch take so long?
The first run may prepare the Python environment, check or download packages and fetch code assets before the local server starts. Watch the console rather than repeatedly opening run.bat.
What if Forge runs but the browser does not open?
Look for the local URL printed in the still-running console and paste that exact address into the browser. If there is no local URL, setup has not reached the server stage; capture the first error shown above the final line.
Why is the checkpoint list empty after installation?
The interface can be installed successfully without a usable image model. Continue to the First Run guide, add one compatible model and its required companion files, then refresh the model list.
Can I keep Forge beside AUTOMATIC1111, and how do I uninstall it?
Keep each application and Python environment in its own folder. After backing up any models, outputs and configuration stored inside the Forge directory, a self-contained package installation can be removed by deleting only that verified Forge folder.
Source truth and tutorial observations stay separate.
Official repository data determines filenames and procedure. Tutorials reveal where users hesitate; they do not override the current release record.
Dated tutorial and community research · 6 records
- A01 · Stable Diffusion Art install guide Dated secondary walkthrough; used to map beginner questions, not current package truth.
- V01 · Pixaroma full install and run guide Transcript checked: archive, update/run, first-start wait, model boundary and self-contained folder.
- V02 · Sebastian Kamph install guide Transcript checked: one-click versus Git routes and included environment.
- V03 · Pixaroma Forge and FLUX guide Transcript checked: NVIDIA/Windows scope, extraction verification and rollback rationale.
- V04 · PromptGeek long-form guide Transcript checked: owner verification, package steps, local URL and model separation.
- Community archive interruption report A 2025 report of a partial GitHub asset download; diagnostic signal only.