model releaseMicrosoft

Microsoft Releases Mage-Flow, a 4B Open-Weight Model That Matches 20B+ Rivals on Image Generation and Editing

TL;DR

Microsoft has released Mage-Flow, a 4B-parameter open-weight foundation model for text-to-image generation and instruction-based editing. The company claims it matches or beats much larger open systems like Qwen-Image (20B) and FLUX.2 (32B) while running faster and using less memory.

3 min read
0

Microsoft has released Mage-Flow, a 4-billion-parameter open-weight foundation model for text-to-image generation and instruction-based image editing, available now on Hugging Face. According to Microsoft, the compact model matches or exceeds the benchmark performance of open systems five to eight times its size, including Qwen-Image (20B), FLUX.2-dev (32B), and FireRed-Image-Edit (20B).

What was released

The Mage-Flow stack consists of two shared components: Mage-VAE, a one-step diffusion latent tokenizer, and NR-MMDiT, a 4B Native-Resolution Multimodal Diffusion Transformer trained with rectified flow matching. Six checkpoints are available, split across two model lines — Mage-Flow (text-to-image) and Mage-Flow-Edit (instruction-based editing) — each shipping in Base, RL-aligned, and 4-step Turbo variants.

Model Task Steps Hugging Face
Mage-Flow-Base text→image 30 microsoft/Mage-Flow-Base
Mage-Flow text→image 20 microsoft/Mage-Flow
Mage-Flow-Turbo text→image 4 microsoft/Mage-Flow-Turbo
Mage-Flow-Edit-Base editing 30 microsoft/Mage-Flow-Edit-Base
Mage-Flow-Edit editing 30 microsoft/Mage-Flow-Edit
Mage-Flow-Edit-Turbo editing 4 microsoft/Mage-Flow-Edit-Turbo

Benchmark claims

On GenEval, Mage-Flow scores 0.90, ahead of Qwen-Image (0.87), Z-Image-Base (0.84), and FLUX.2-dev (0.87), all of which use far more parameters. On DPG-Bench, Mage-Flow posts 86.49 versus Qwen-Image's 88.32. For editing, Mage-Flow-Edit-Turbo scores 8.271 on GEdit-EN and 8.264 on GEdit-CN, ahead of FireRed-Image-Edit-1.0 (7.943/7.887) and Qwen-Image-Edit-2511 (7.877/7.819), according to Microsoft's reported figures. These numbers come from Microsoft's own technical report; they have not been independently verified.

Efficiency claims

Microsoft says Mage-VAE matches FLUX.2-VAE reconstruction fidelity while using roughly 12x fewer encode MACs and 22x fewer decode MACs per pixel. The company also reports that native-resolution packing combined with fused CUDA kernels cut per-step training time from approximately 1.93 seconds to 0.78 seconds — a claimed 2.5x training speedup. At 1024x1024 resolution on a single A100 GPU, Microsoft claims Mage-Flow-Turbo generates an image in 0.59 seconds and Mage-Flow-Edit-Turbo completes an edit in 1.02 seconds, with peak memory usage of 18-20 GB — described as the lowest among compared systems.

The model supports native resolution generation from 512 to 2048 pixels across arbitrary aspect ratios, including extreme 4:1 ratios such as 512x2048. Mage-Flow-Edit supports semantic content editing, appearance transformation, image restoration, and structure-aware editing within a single unified model, and can reportedly generate diverse outputs from a single reference image.

Pricing is not applicable — the model weights are freely available on Hugging Face under Microsoft's repository. Training data cutoff and license terms were not specified in the released materials.

What this means

Mage-Flow's core pitch is parameter efficiency: matching or beating models 5-8x larger through tokenizer-backbone co-design rather than brute-force scaling. If Microsoft's benchmark numbers hold up under independent testing, a 4B open-weight model that runs on a single A100 with sub-second inference and under 20GB of memory would meaningfully lower the barrier for developers who want competitive image generation and editing without renting multi-GPU clusters. The real test is whether third-party evaluations on GenEval, GEdit-Bench, and similar suites confirm Microsoft's self-reported scores, and whether the efficiency gains translate to production deployments rather than just controlled A100 benchmarks. For now, treat the head-to-head comparisons against Qwen-Image, FLUX.2, and FireRed-Image-Edit as vendor-reported until reproduced elsewhere.

Related Articles

model release

Meta's Muse Spark 1.3 Claims #3 Global Ranking, Matches OpenAI's GPT-5.6-Sol on Coding Benchmarks

Meta Superintelligence Labs shipped Muse Spark 1.3, which the company claims ranks #3 globally on the Artificial Analysis Intelligence Index and matches OpenAI's GPT-5.6-Sol on coding and agentic benchmarks. The model is available now via Muse Code and Meta's API, with open weights and a follow-up model promised soon.

model release

OpenAI Launches GPT-6 Astra With Half the Message Allowance of GPT-5.6 Sol

OpenAI has begun rolling out GPT-6 Astra to top-tier ChatGPT plans, the API, Azure, and AWS Bedrock. The model delivers roughly half the usage allowance of GPT-5.6 Sol across comparable plans, with Plus and Business users gaining access in the coming days.

model release

Alibaba Releases Qwen3.8 Max (0902), a 2.4-Trillion-Parameter MoE Model With 1M-Token Context

Alibaba's Qwen team released Qwen3.8 Max (0902), a 2.4-trillion-parameter mixture-of-experts model with a 1M-token context window that accepts text, image, and video input. The snapshot is post-trained for coding, agentic workflows, and long-horizon task execution, priced at $2/$6 per 1M input/output tokens.

model release

OpenAI's GPT-6 Astra Cuts Hallucinations, But Indirect Prompt Injection Attacks Still Succeed 8.5% of the Time

OpenAI's new GPT-6 Astra model shows major improvements in hallucination rates and jailbreak resistance over predecessor GPT-5.6 Sol, according to OpenAI's system card. However, indirect prompt injection attacks hidden in documents still succeed 8.5% of the time in external testing by Gray Swan, down from 27% but still above rival Claude Opus 5's 4.8% rate.

Comments

Loading...