Aumiqx Technologies
AUM
Open menu

Stable Diffusion WebUI Setup: A1111, Forge and ComfyUI

Choose a local image workflow, install the right runtime, match models and LoRAs, and avoid outdated GPU flags or accidental cloud processing.

Guides|Aumiqx Team|Updated |8 min read
stable diffusionstable diffusion webuiautomatic1111

What's Changed Since April 2026

The biggest change to the recommendation is that ComfyUI is no longer just a manual-install node editor for experts. Its official repository recommends a desktop app for Windows and macOS, offers templates and App Mode, and documents newer local model families including Flux.2, Qwen Image and Z-Image. It also offers optional paid partner nodes, so a ComfyUI workflow is not automatically local or free.

The AUTOMATIC1111 repository still identifies 1.10.1 as its latest release in this check. Forge documents its A1111 1.10.1 base and specific Flux support. Follow each project's own compatibility instructions rather than applying one Python/CUDA recipe to all three. This November update is documentation-based; no new GPU performance tests were run.

What Is Stable Diffusion and Why Run It Locally?

Stable Diffusion is a family of downloadable image-generation models. A WebUI is the application that loads a supported model, accepts prompts and settings, and saves images. The interface and the checkpoint are separate choices, with separate licenses and compatibility requirements.

Local execution can keep prompts and images on your hardware and avoid per-generation service fees. It still costs hardware, electricity, storage and maintenance time. Extensions, downloads and cloud nodes can make network requests, so privacy depends on the complete workflow.

Start locally when you need reproducibility, a particular checkpoint, custom adapters or a pipeline you can inspect. Use a hosted service when occasional image creation matters more than maintaining an environment. Neither choice guarantees better images for every task.

A1111, Forge or ComfyUI: Choose by Workflow

InterfaceBest reason to choose itMain caution
AUTOMATIC1111Existing SD workflows and specific extensionsDo not assume support for every newer architecture
ForgeFamiliar form-based UI with resource-management changes and documented Flux optionsExtension compatibility and quantization support are version-specific
ComfyUITemplates, reusable graphs, current model workflows and automationCustom nodes and remote partner nodes need review

Forge's own README calls the original WebUI nearly static and links its extension replacement list. That is a reason to check maintenance, not proof of a universal speed improvement. The earlier claims of 30–75% faster generation and an 85% extension-compatibility rate were not established by the current documentation.

ComfyUI is the starting point we would evaluate for a new multi-model setup. Use a maintained template first rather than constructing every node yourself. Choose Forge if its form-based interface and documented model support suit you better. Keep an existing A1111 installation if a required extension works reliably there; migration is not an end in itself.

Installation: Follow the Runtime, Not a Universal Recipe

Before installing

Check your GPU, driver, available RAM and disk space against the chosen runtime and checkpoint. There is no single VRAM minimum for all image models. Resolution, batch size, precision, offloading and auxiliary models change memory use. Start with one small supported workflow and batch size one.

Windows

For ComfyUI, the official repository recommends its desktop app and also supplies portable builds. Select the package for your actual GPU generation; do not mix instructions from an old portable release with a new one. For Forge, its README links a one-click package that includes Git and Python; extract it, follow the documented update step and run its launcher.

For manual A1111 installation, the current README specifies Python 3.10.6, Git, cloning the repository and launching webui-user.bat as a normal non-administrator user. This is A1111-specific guidance, not a rule for ComfyUI. Do not replace a working environment's Python merely because another project's guide recommends a newer version.

macOS

ComfyUI documents a desktop app for macOS and manual Apple Silicon support. Start with that supported path if your hardware meets its requirements. A1111 links a separate Apple Silicon guide. CUDA-only extensions will not become compatible simply because the base application runs on Metal.

Linux

Use the selected project's manual instructions and the PyTorch build appropriate for your GPU. A1111 documents its Linux dependencies and webui.sh; ComfyUI documents separate hardware support paths. Do not copy the old guide's pinned NVIDIA driver package or unsupported blanket --use-rocm advice. AMD and Intel setups need their documented backend and dependency versions.

First launch and validation

  1. Install in a dedicated directory and environment, without administrator privileges unless an OS dependency specifically requires them.
  2. Download a trusted checkpoint and the exact text encoders/VAE required by its workflow.
  3. Put files in the folders the workflow documents; not every model is a single checkpoint file.
  4. Launch on localhost and generate one low-resolution sample.
  5. Save the model revision, workflow and environment versions.
  6. Add extensions one at a time, testing after each change.

Do not expose a development WebUI to the public internet. Avoid --listen or share links unless you understand access controls and network exposure. For private use, ComfyUI documents --offline to disable optional paid API nodes and keep built-in functionality offline; separately review any custom nodes.

Models: Match Architecture, Files and License

SD 1.5 and SDXL remain useful starting points for existing adapters and established workflows. SDXL's larger native image workflow generally needs more resources, but exact memory use depends on runtime and settings. Do not buy hardware from a single model-file-size estimate.

SD3.5, Flux, Qwen Image and Z-Image are separate architectures or families. ComfyUI's current README lists these among supported image workflows. That does not imply A1111 or original Forge can load every one of them. Use the maintained template for the exact model rather than dropping an arbitrary file into an old checkpoint folder.

Flux is not a Stable Diffusion release. Nor are all Flux models interchangeable: downloadable weights and hosted proprietary variants have different availability and terms. Read the particular model card before commercial deployment or redistribution.

Obtain weights from the publisher's official repository or linked model card. Prefer safetensors over pickle-based checkpoint formats where available, but remember that a safe tensor container does not make downloaded Python extensions trustworthy. Save the license and revision alongside the workflow.

Add Controls Only After the Base Workflow Works

Structural conditioning can guide generation using edges, depth or poses. Inpainting can replace a selected area; upscaling can enlarge an output, sometimes adding synthesized detail rather than recovering real information. These are useful capabilities, not guarantees of exact geometry or identity.

A1111 lists a broad extension ecosystem. Forge publishes its own extension/replacement guidance, while ComfyUI combines built-in nodes with optional custom packages. Do not install an A1111 extension into another runtime simply because both generate images.

Before adding ControlNet, a face-detailing workflow or tiled upscaling, confirm the base architecture, required weights and compatible versions. Add one component at a time. Custom nodes and extensions execute code with your user's permissions; review their source and maintenance rather than installing every dependency suggested by an unfamiliar workflow.

For troubleshooting, keep a minimal configuration without third-party extensions. Reproduce the problem there before changing drivers or replacing the entire environment.

LoRAs and Embeddings Must Match the Base Model

A LoRA is an adapter trained for a particular model family or checkpoint. A textual-inversion embedding changes how a compatible text encoder represents a token. Neither is a universal image-style file.

In A1111-style interfaces, LoRAs commonly live in models/Lora/ and use a prompt reference such as <lora:filename:weight>. ComfyUI uses workflow nodes and its documented folders instead. Follow the adapter's recommended base model, trigger words and strength; the same numerical weight is not a guarantee of the same visual effect across implementations.

For training, choose a supported training tool for the architecture and use images you have rights to process. Training memory and duration vary widely, so this guide does not promise a fixed dataset size or a one-hour run on a generic GPU. Hold out evaluation images and compare identity/style preservation against overfitting.

Prompting and Parameters: Start With the Model's Defaults

Describe the subject, setting, lighting and composition clearly. Older SD checkpoints may respond well to tags; newer text encoders often accept descriptive sentences. Do not assume adding “8k” changes the actual output resolution.

Use the model's suggested sampler, step count and guidance settings first. Distilled models can require different settings from full models. Negative prompts and weighted syntax are runtime- and architecture-dependent, not universal requirements.

  1. Fix the model, resolution and seed for a comparison.
  2. Change one prompt or setting at a time.
  3. Inspect the image at full size, including text and anatomy.
  4. Save the complete workflow and model revisions with successful outputs.
  5. Increase resolution or add refinement only after the composition works.

A seed alone does not guarantee identical output across GPU backends, software updates, precision changes or different implementations. Reproducibility requires preserving the environment as well as the seed.

Local Workflows vs Hosted Image Tools

The older comparison with Midjourney V7 is out of date. Midjourney V8.2 is now the documented default, with an Edit Model replacing older reference/retexture controls. Hosted tools also offer editing and reference workflows, so local software is not the only way to maintain a subject or composition.

Adobe Firefly offers limited free daily generations and paid credit plans, including Standard at $9.99/month as of November 2026. It includes partner models, whose terms must be evaluated separately from Adobe's own models.

Local tools offer checkpoint choice, inspectable workflows and the possibility of offline processing. Hosted tools reduce environment maintenance and can provide managed editing features. Compare actual output, rights, privacy controls and total cost rather than fabricated per-thousand-image electricity figures or universal quality rankings.

ComfyUI can sit on either side of this boundary: a local graph can run entirely on your GPU, while partner nodes call remote services and consume paid credits. Inspect every node before describing a workflow as private or free.

A Practical Starting Recommendation

For a new user: evaluate ComfyUI Desktop with one maintained local template, or Forge if you prefer its form-based interface. For an existing A1111 user: keep a working environment pinned while evaluating alternatives separately. For developers: choose an API workflow only after licensing, authentication and resource limits are clear.

Begin with one model and one repeatable task. Record the setup, save an output, restart the app and confirm you can reproduce the workflow. Then add inpainting, adapters or automation. This is less exciting than installing dozens of extensions, but much easier to maintain.

Local generation is worthwhile when control and repeatability justify the upkeep. It is not inherently costless, legally unrestricted or immune to data leakage. The best setup is the smallest documented workflow that reliably solves your problem.

Key Takeaways

  1. 01ComfyUI now offers desktop installation, templates and App Mode; evaluate it for new multi-model workflows.
  2. 02A1111, Forge and ComfyUI need their own dependency and model-compatibility instructions.
  3. 03Optional partner nodes use remote services; local installation alone does not ensure offline processing.
  4. 04Match checkpoints, LoRAs, encoders and control models to the same supported architecture.
  5. 05Review model licenses and extension code, and keep WebUIs on localhost unless secured.

Frequently Asked Questions