Microsoft Research Asia / Microsoft team released Mage-Flow today, a 4B compact text-to-image + instruction-editing unified stack, with code and weights fully open-sourced (github.com/microsoft/Mage). The core idea is counter-intuitive: don't stack parameters, stack tokenizer + backbone + system. Mage-VAE uses one-step diffusion-style encoding/decoding + anchor-latent regularization, matching FLUX.2-VAE in reconstruction quality, but cutting per-pixel encoding/decoding MACs to 1/12 and 1/22, directly rescuing VAE from the high-resolution bottleneck. The native-resolution MMDiT (NR-MMDiT) uses rectified flow trained in Mage-VAE latent space, paired with variable-length FlashAttention + per-sample 2D RoPE packing, and stack-level CUDA operator fusion — end-to-end training throughput improves ~2.5x, and the CFG conditional/unconditional two branches only need one packed forward. On results, Mage-Flow faces off against larger models head-on: on standard generation/editing benchmarks it ties or slightly beats Qwen-Image 20B, Z-Image 6B, FLUX.2 32B, FireRed-Image-Edit 20B; the Turbo variant on a single A100, at 1024² resolution, generates images in 0.59s and edits in 1.02s, peak memory ~18–20 GB, the lowest among all compared systems. The native-resolution packing also supports any aspect ratio between 512 and 2048, including extreme 4:1 — a single checkpoint handles everything. Mage-Flow also ships three tiers — Base, RL-aligned, and 4-step Turbo — plus an independent Mage-Flow-Edit editing model, the latter doing semantic editing, appearance transfer, inpainting, and structure-aware output in the same image-text conditional framework. The whole pipeline uses Diffusion-NFT for post-training; prompt following, text rendering, aesthetics, and editing consistency all see significant gains; Turbo uses adversarial-aware distillation to deliver 4-step output, with latency low enough for interactive applications. What's worth discussing is the paradigm significance of this path: text-to-image / editing models going from 20B+ back to 4B isn't simple distillation — it's accounting for the tokenizer's compute, the backbone's capacity, and the engineering stack's cost as a whole. Compress the VAE once, compress the attention once, then piece the kernels together, and 4B can catch up with 32B. For developers it means a deployable version can run on a single consumer-grade or cloud entry-level card; for the open-source ecosystem it means, after Qwen-Image, Microsoft has added another truly open-source, commercially-usable compact foundation model. The key question going forward: can the Mage-Flow "compact + system co-design" path continue to be eaten down to 1B–2B, and will the gap with Qwen-Image and FLUX.2 widen again with RL and data iteration.