FLUX.1 in Forge: A First Image Tutorial with Clear Settings

To generate your first FLUX.1 image in Forge, install the WebUI, load the documented FLUX.1-dev NF4 package, and apply the maintainer's sampling settings below. Black Forest Labs develops FLUX.1; lllyasviel develops the Forge interface. FLUX, Forge, Setup

This tutorial follows the packaged FLUX.1-dev route for a first generation. Its focus is the sequence from installation to a reviewed image, with a small set of settings that you can record and repeat.

What are the key facts about FLUX.1 in Forge?

How does Forge simplify a first FLUX.1 generation?

Forge groups FLUX generation controls in a WebUI workflow. Its maintainer documents both a packaged checkpoint route and a separate-components route, so the choice of download can be matched to an explicit loading procedure. README

The packaged route is useful for establishing a first image before managing several files individually. The maintainer's recommended NF4 checkpoint includes the main model and supporting components in a single package. Checkpoint card

Forge also exposes weight allocation and offload controls. These give users ways to investigate resource constraints after the baseline works, although the maintainer cautions against allocating too much GPU memory to weights. FLUX tutorial

Treat those controls as a second stage of setup. A saved baseline gives you something concrete to return to if an adjustment changes stability, generation time, or the appearance of the output.

Which settings and limitations affect FLUX.1 in Forge?

FLUX requires compatible components and settings. Forge's separate-component instructions specify locations for the diffusion model, VAE, and text encoders. Component guide

Quantization does not change the checkpoint's underlying licensing. The publisher's NF4 package retains the dev model's license, so use its model card when assessing access rather than Forge's software license. NF4 card

For the maintainer's FLUX-dev baseline, ordinary CFG is one and distilled guidance is a separate control. At that CFG setting, Forge disables the negative-prompt field. FLUX tutorial

Use that distinction when troubleshooting. A greyed-out field can be expected behavior for this configuration; it is not by itself evidence that the model failed to load.

The model card describes imperfect prompt following. Inspect the generated subject and requested relationships before considering the first run complete, even when Forge finishes without an error. Dev card

How do you generate your first FLUX.1 image in Forge?

Prepare Forge

Download a packaged installation from Forge's official README and extract it into a dedicated directory. The maintainer instructs users to update the package and then run it using its included launchers. Installation

Open a Windows command prompt in the extracted package directory and run these in sequence. Wait for the updater to finish before starting the application. Installation

update.bat
run.bat

Keep the terminal available while opening the local interface. It gives you a place to inspect an error if loading or generation stops; copy the relevant error text into your notes before changing the setup.

Load the documented package

Obtain flux1-dev-bnb-nf4-v2.safetensors from the maintainer-linked repository. Place it in Forge's models/Stable-diffusion directory and select it in the checkpoint control. Package, Loading guide, Directories

Select flux in Forge's UI preset and leave the loading precision on Automatic for the initial run. The tutorial advises against forcing an already quantized FP8 checkpoint through NF4 conversion. Current UI, FLUX tutorial

Write down the exact selected filename. A note that says only “Flux” loses the information needed to distinguish the model version, package, and precision when you return to this setup.

Establish a baseline

Follow the tutorial's FLUX-dev baseline: Euler sampling, Simple scheduling, CFG one, and distilled guidance 3.5. Those are the maintainer's example settings for this route. FLUX tutorial

Keep the preset's other settings initially, and record them. Enter a simple original prompt such as: “A red enamel mug on a pale wooden table, seen from the side, with soft window light.”

Generate one image and save the result with its settings. Check that the mug is red, that the viewpoint is recognizable, and that the table provides the intended setting. Do not start with a complicated scene that is hard to assess.

For the next run, change the mug to blue while keeping the rest of your recorded configuration fixed. Compare what changed beyond the requested color, then decide whether you have a usable baseline for your own work.

Diagnose one problem at a time

If the checkpoint cannot be selected, check its location and filename against the documented directories. If the model loads but the result is unsuitable, compare your configuration to the baseline before adding more prompt instructions.

If generation is slow or memory-limited, consult the maintainer's GPU-weight guidance. Reduce the allocation as directed by that guidance and test again before making unrelated changes. Performance guidance

Keep a short record of each adjustment and its outcome. Restore the baseline between unrelated experiments so a later success does not depend on a collection of changes you can no longer identify.

How does a Forge setup compare with ComfyUI?

The ComfyUI complete guide covers the graph-based alternative. Choose the interface whose workflow is easier for you to inspect and maintain.

If you want to understand the file format before changing packages, use the sibling FLUX.1-dev NF4 guide. Preserve this first-generation setup as a reference while evaluating another precision.

What should you check when setting up FLUX.1 in Forge?

What is the relationship between FLUX.1 and Forge?

Forge is a local WebUI application that can load Black Forest Labs' FLUX.1 image models. Forge's software license and the selected model's license are separate. Forge, FLUX, Dev card

Which FLUX.1 checkpoint does this Forge tutorial use?

This Forge tutorial uses the maintainer-linked flux1-dev-bnb-nf4-v2.safetensors package. Follow Forge's separate-component instructions if your download contains only the diffusion model. NF4 card, Components

Why is the negative-prompt box disabled for FLUX.1-dev?

Forge's FLUX.1-dev tutorial sets ordinary CFG to one, which disables the negative-prompt field. The separate distilled-guidance control uses 3.5 in the documented baseline. Tutorial

How do I troubleshoot slow FLUX.1 generation in Forge?

Forge's maintainer advises checking GPU weight allocation and offloading when FLUX generation is slow. Follow that guidance, change one setting at a time, and measure the result on your hardware. Forge guidance, Tutorial

Sources

• Forge current preset and precision controls
• FLUX.1 launch
• Forge repository and installation
• FLUX.1-dev model card
• Forge FLUX baseline tutorial
• Forge component-loading tutorial
• Packaged NF4 checkpoint
• ComfyUI FLUX tutorial

Related guides on PromptZone

• Realistic Photos with FLUX
• Best SDXL Models in 2026