SHORT ANSWER
No verified FLUX 3 ComfyUI package is available to document yet.
As of August 10, 2026, we could not verify a public model release named FLUX 3 or FLUX.3 in the checked Black Forest Labs sources, and we found no official FLUX 3 ComfyUI tutorial, checkpoint, dedicated nodes, installation instructions, VRAM requirement or workflow.
That does not prove a future release is impossible. It means a responsible FLUX 3 ComfyUI page should act as a dated status tracker—not fabricate a download, rename an older workflow or copy hardware figures from a different model.
01 / STATUS MATRIX
What is—and is not—publicly verified.
| FLUX 3 ComfyUI item | Status | What would verify it |
|---|---|---|
| Official model release | Not verified | BFL product page, documentation or announcement |
| Official checkpoint weights | Not verified | Verified BFL Hugging Face model card and files |
| ComfyUI model support | Not verified | ComfyUI docs, code, release notes or templates |
| Dedicated custom nodes | Not verified | Official repository and documented dependency chain |
| FLUX 3 workflow JSON | Not verified | BFL or ComfyUI publication with matching model files |
| VRAM requirements | Not verified | Reproducible figures with precision, resolution and offloading |
02 / WEIGHTS & DOWNLOADS
Do not trust a checkpoint name without a verified source.
A filename can be invented in seconds. Names such as flux3-dev.safetensors, flux-3-schnell or FLUX.3-fp8 do not establish that Black Forest Labs published the model. Before downloading any supposed FLUX 3 ComfyUI weights, trace the file back to a verified BFL organization, read the model card and confirm the license.
No official source means no download link on this page. Unknown checkpoints and custom nodes can contain unsafe code, misleading licenses, repackaged weights or files unrelated to the advertised model.
- Confirm the publisher is the verified Black Forest Labs organization.
- Read the model card, license and usage restrictions.
- Match filenames against official documentation.
- Prefer published hashes when an official source provides them.
- Inspect third-party custom-node code before installing it.
03 / NODES & FILE PATHS
Generic ComfyUI nodes do not prove FLUX 3 support.
ComfyUI contains general loaders, text-conditioning nodes, samplers, VAEs and image utilities. Their presence does not show that a new architecture can be loaded correctly. A complete FLUX 3 ComfyUI setup would still need compatible architecture code, verified weights, the correct text encoders and VAE, documented file placement, supported precision and a workflow wired for those components.
Until those details are published, there is no responsible reason to prescribe a directory such as models/diffusion_models, models/unet or a made-up FLUX 3 custom-node package. Instructions copied from FLUX.1 or another release may look plausible while loading the wrong model—or failing entirely.
04 / VRAM
Why a FLUX 3 VRAM number cannot be guessed.
Memory demand is shaped by parameter count, numerical precision, text encoders, VAE, image dimensions, batch size, attention implementation, quantization and CPU offloading. A “12 GB,” “16 GB” or “24 GB” claim without those conditions is not useful.
FLUX 3 ComfyUI requirements should only be published after a verified release can be tested. A useful result would name the GPU, operating system, ComfyUI version, checkpoint format, precision, resolution, batch size, offloading settings, peak VRAM and whether generation completed without out-of-memory errors.
05 / WORKFLOW VERIFICATION
What a real FLUX 3 ComfyUI workflow would need.
- 01
Official model identity
The workflow must point to a release that can be traced to Black Forest Labs, not merely a familiar filename.
- 02
Compatible ComfyUI support
The current ComfyUI code or an auditable node repository must understand the model architecture and conditioning path.
- 03
Complete dependencies
Checkpoint, encoders, VAE, node versions and file locations must be listed without guessing.
- 04
Reproducible test
A clean installation should import the workflow, find every model, queue a prompt and produce output under stated hardware conditions.
06 / WHAT TO USE NOW
A browser workflow avoids speculative local installs.
While FLUX 3 ComfyUI support is not publicly verified, the live flux-3.run workspace provides text-to-image, reference-led editing, text-to-video and image-to-video through the browser. It does not require a checkpoint download, custom nodes or local VRAM planning. The site displays its own Credit cost before submission and tracks recent jobs.
For genuinely local work, use ComfyUI's official tutorials for the FLUX models it currently documents. Keep each model's real name. Do not relabel an existing FLUX.1 or other workflow as FLUX 3 to capture a newer search term.
Open the browser generator07 / OFFICIAL SOURCES
Where this status is checked.
- Black Forest Labs Models ↗Official model catalog and product naming
- Black Forest Labs Docs ↗Published APIs, model details and parameters
- BFL on Hugging Face ↗Verified model cards, licenses and public files
- ComfyUI FLUX Tutorials ↗Officially documented FLUX workflows
- ComfyUI Workflow Templates ↗Official template repository and supported examples
This page will be updated when BFL publishes a verifiable FLUX 3 release or ComfyUI publishes explicit support. Community posts alone will not change the official-support status.