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

Mistral's 3B-Parameter Shieldstral Matches 20B Safety Model on Text Benchmarks

Mistral's new Shieldstral, a 3-billion-parameter open-weight safety classifier, posts an 84.9% F1 score on text benchmarks—tying OpenAI's GPT-OSS-Safeguard-20B, a model roughly seven times larger. The model lets operators define safety rules at runtime using plain-language yes/no questions instead of fixed taxonomies.

model release

Mistral AI Releases Shieldstral-1.0-3B, a 3B-Parameter Policy-Adaptive Safety Classifier

Mistral AI has released Shieldstral-1.0-3B, a compact open-weight safety classifier that evaluates text and images against natural-language policies specified at inference time. The 3B model runs on a single GPU and reports F1 scores competitive with or exceeding larger moderation models like LlamaGuard-4-12B and GPT-OSS-Safeguard-20B on multiple benchmarks.

model release

Liquid AI Releases LFM2.5-2.6B, a 2.6B-Parameter Agentic Model with 128K Context for On-Device Use

Liquid AI has released LFM2.5-2.6B, a 2.6B-parameter model trained on 34 trillion tokens with a 128K context window, built for on-device agentic workloads. The company claims it is competitive with models four times its size on tool use and instruction following.

model release

Liquid AI Releases LFM2.5-2.6B, a 2.6B-Parameter Agent Model for On-Device Deployment

Liquid AI has released LFM2.5-2.6B, a 2.6B-parameter model designed to run capable tool-calling agents locally on laptops and phones. The company claims it matches or beats models up to 4x its size on instruction-following and tool-use benchmarks while running under 2.5GB of memory.

Comments

Loading...