Which file.
Mage-Flow is the image half of Microsoft’s Mage research family, released on 22 July 2026: a 4B MMDiT with its own one-step VAE, prompted through Qwen3-VL 4B. There are six checkpoints, three for making images and three for editing them.
- Mage-Flow (
mage_flow_bf16) is the RL-aligned model and the one to start with. 20 steps at CFG 5. - Mage-Flow Turbo makes an image in exactly 4 steps at CFG 1, no negative prompt.
- Mage-Flow Base is the plain pretrained model, for training and variety. 30 steps.
- Edit, Edit Base and Edit Turbo take a reference picture and an instruction.
The licence is MIT, which allows commercial use. Microsoft’s Responsible AI note adds that the models are released for research and not meant for products or services. That note is guidance, not a licence term, but read it before you build on it.
Files you need.
One model, one encoder, one VAE. Comfy-Org ships each model in bf16 and in int8_convrot, a newer int8 format that is half the size.
-
Model4.2 GB Download
mage_flow_int8_convrot.safetensorsComfyUI/models/diffusion_models/ or mage_flow_bf16.safetensors, 8.2 GB -
Turbo4.2 GB Download
mage_flow_turbo_int8_convrot.safetensorsComfyUI/models/diffusion_models/ optional. bf16 is 8.2 GB -
Text encoder8.9 GB Download
qwen3vl_4b_bf16.safetensorsComfyUI/models/text_encoders/ -
VAE0.3 GB Download
mage_flow_vae_bf16.safetensorsComfyUI/models/vae/
The VAE is Mage-Flow’s own one-step decoder, and the templates load it by name. No GGUF builds exist.
models/
├── diffusion_models/
│ └── mage_flow_int8_convrot.safetensors
├── text_encoders/
│ └── qwen3vl_4b_bf16.safetensors
└── vae/
└── mage_flow_vae_bf16.safetensors
What fits your computer.
At 1024 × 1024. The encoder runs first and ComfyUI moves it out of the way before sampling, so the model file sets the limit. Few people have posted numbers yet, so treat the lower tiers as estimates from file sizes.
- 8 GBTight
int8 model (4.2 GB). The 8.9 GB encoder is bigger than the card, so ComfyUI keeps part of it in system RAM while it encodes.
- 12 GBFits
int8 comfortably. bf16 fits with little room at larger sizes.
- 16 GBFits
bf16. An underclocked RTX 5070 Ti runs Turbo quickly.
- 24 GBFits
bf16 at 1536 to 2048 px, where Mage-Flow looks best. Microsoft measured an 18 to 20 GB peak in its own code.
- Older GPUsUpdate
Cards without bf16, such as a GTX 1660, gave corrupt images until ComfyUI PR #15081. Update ComfyUI.
- MacUntested
No Mac reports yet. The bf16 files are the safer bet on Apple Silicon; int8 files have caused trouble on MPS with other models.
Set it up.
-
Update ComfyUI
Mage-Flow is native from ComfyUI 0.29.0. Older versions don’t have
TextEncodeMageFlowEdit. ComfyUI Desktop updates itself; in a manual install:Terminal, in the ComfyUI foldergit pull pip install -r requirements.txt
-
Download the three files
Model, encoder and VAE from Comfy-Org/Mage-Flow, using the list above.
-
Put them in their folders
Model in
diffusion_models, encoder intext_encoders, VAE invae. Restart ComfyUI. -
Open a template
Pick Mage-Flow: Text to Image or Mage-Flow Turbo: Text to Image in the template browser. The Mage-Flow-Edit templates are for the edit files.
-
Check the loaders
Load CLIP gets
qwen3vl_4b_bf16with typemage. TextEncodeMageFlowEdit encodes the prompt and makes the latent in one node, so there is no separate empty-latent node. -
Set steps and run
The text-to-image template starts at 30 steps. That suits Base; for the regular Mage-Flow file, 20 is Microsoft’s setting. Turbo stays at 4 steps and CFG 1.
Settings that work.
Mage-Flow uses the plain KSampler. ComfyUI sets its shift to 6 automatically, which matches Microsoft’s, so there is no ModelSampling node to add.
Mage-Flow and Base
- Steps
- 20Base: 30
- CFG
- 5
- Sampler
- euler
- Scheduler
- simple
- Shift
- 6, built in
- Size
- 1024 to 2048multiples of 16
- Negative
- yes
- Text encoder
- Load CLIP, mage
Turbo
- Steps
- 4
- CFG
- 1
- Sampler
- euler
- Scheduler
- simple
Any aspect ratio works, up to 4:1. Comfy’s template note suggests 1024 for tests and 1536 to 2048 for quality, and users report much better results at 2048 × 2048 than at 1024. Turbo is strict: Comfy’s template note says it must run at 4 steps and CFG 1.
How fast.
Microsoft’s figures, in its own code rather than ComfyUI.
When it goes wrong.
- Missing node
TextEncodeMageFlowEdit - ComfyUI is older than 0.29.0. Update it, or switch to the nightly build.
- Turbo gives a cloudy mess after the first step
- A bug on GPUs without bf16 (GTX 16xx and similar), fixed in ComfyUI PR #15081. Update ComfyUI, and keep Turbo on
eulerwithsimple. - Turbo images look soft or muddy
- Turbo needs exactly 4 steps and CFG 1. Also try 1536 px or more.
- Edit ignores the reference image
- Reported on AMD with ROCm, from the Comfy Kitchen attention backend. Switch ComfyUI to another attention backend.
- The microsoft/Mage-Flow download link returns 401
- Microsoft removed those repos. Download from Comfy-Org/Mage-Flow instead.
The original Microsoft repository seems to be gone. What happened to it?
At 1024 the results looked poor; at 2048 × 2048 they were much better.
Questions.
Where can I download Mage-Flow now?
From Comfy-Org’s repackaged copy on Hugging Face (Comfy-Org/Mage-Flow), which has the models, the Qwen3-VL 4B encoder and the VAE. Microsoft’s own Hugging Face repos were removed in early August 2026; the GitHub repository is still up.
Can I use Mage-Flow commercially?
The licence is MIT, which allows it. Microsoft’s Responsible AI note says the models are released for research and are not intended for products or services, so read that before you rely on it for paid work.
How many steps does Mage-Flow need?
20 for the regular (RL) model, 30 for Base and exactly 4 for Turbo, according to Microsoft’s README. CFG is 5, and 1 for Turbo. The Comfy template starts the regular model at 30, which also works but takes longer.
Why do my Mage-Flow images look bad at 1024?
Mage-Flow is a native-resolution model and several users get much better results at 1536 to 2048 px. On Turbo, also check it’s at exactly 4 steps and CFG 1.
Why is Mage-Flow Turbo a cloudy mess on my older GPU?
Cards without bf16 support, such as the GTX 1660, fell back to fp32 and produced corrupt images. ComfyUI fixed this in PR #15081, so update ComfyUI and keep Turbo on euler with the simple scheduler.
Sources: Mage-Flow README [1], Microsoft Mage repository, Comfy-Org Mage-Flow files, Turbo and resolution thread, TextEncodeMageFlowEdit thread, ROCm reference thread, stable-diffusion.cpp note on the removal.