Find the exact Forge term, file, flag, or boundary

Here, Forge means only the original lllyasviel/stable-diffusion-webui-forge repository. It is a Python and Gradio WebUI for local generative-image workflows. Forks such as reForge, Forge Classic, and Forge Neo are separate projects and are not covered by these reference claims.

At inspected commit dfdcbab, core constructs Txt2img, Img2img, Spaces, Extras, PNG Info, Checkpoint Merger, Settings, and Extensions. Extensions can add tabs, while settings can hide or reorder them, so another installation may look different.

First check Settings for hidden or reordered tabs, then disable extensions and reload. Extensions can register their own tabs, and an older or modified commit can construct a different interface. Record the full commit before comparing screenshots.

GPU Weights belongs to the global Forge memory controls. Its visibility depends on UI preset; the all preset exposes the complete top control set at the inspected commit. Use the memory-controls guide before changing it.

A VAE translates between latent data and image pixels. A text encoder converts prompt text into conditioning. Some model families bundle these components; others use separate files. The glossary defines the labels, and the model-family guide establishes the required file set.

Use the paths reference because the answer changes with the artifact and any launch overrides. It separates default locations from --data-dir, --models-dir, --ckpt-dir, and related command-line changes.

Yes. The command-line reference records 167 unique core arguments found at commit dfdcbab: 126 from the base WebUI parser, 35 from the Forge backend, and 6 from built-in preload hooks. Third-party extensions can add more.

Put the flag in the launcher appropriate to the installation, not in a Python source file. The command-line reference maps Windows and shell launchers, explains whether a value is required, and warns when a flag changes network exposure.

Spaces contains wrappers for optional local mini-apps. Installation can download code, launch imports that code into the Forge process, and individual apps may download more models. Treat a Space as executable code, not as a harmless webpage.

Core inference can work offline after the exact environment, model files, companion files, and workflow assets are available. There is no universal offline switch. Prove the specific workflow with a blocked-network test.

No. Localhost limits where the server listens; it does not prove that Python, Git, dependencies, installers, or extensions make no outbound requests. It also does not remove prompts or metadata that you choose to save or transmit.

The inspected repository contains GNU AGPL Version 3. The license permits broad use and modification, including commercial activity, while distribution and modified network use can create source and notice duties. Read the exact license and obtain legal advice for consequential decisions.

Not automatically. Forge code, checkpoints, LoRAs, VAEs, text encoders, input assets, and outputs can have different licenses or rights. Keep their provenance and terms separate.

Use the First Run route to verify the installation, place a compatible model set, and make a baseline image. Return here when a specific term, path, flag, Space, network boundary, or license question blocks that task.

No. Similar names and inherited UI do not make their releases, flags, fixes, binaries, or maintenance status facts about Original Forge. Use each fork’s own repository and documentation.