What GPU do I need to run microsoft/Mage-VL-Cowork?

4.7B parameters, published in BF16. View on Hugging Face

4.7B
Parameters
BF16
Native precision
Unknown
Architecture
image-text-to-text
Pipeline

Mage-VL-Cowork is published by microsoft on Hugging Face, with 3,714 downloads and 215 likes to date. It's a unlisted-architecture model built for image-text-to-text, published natively in BF16.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
BF168.8 GB10.6 GBRTX 30601$0.110/hr
FP8 (quantized)4.4 GB5.3 GBRTX 5060 Ti1$0.145/hr
INT4 (quantized)2.2 GB2.6 GBRTX 30701$0.088/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run Mage-VL-Cowork at its published (BF16) precision: 1× RTX 3060, at $0.110/hr per GPU ($0.110/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

Mage-VL-Cowork: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Grouped-query attention: every layer caches keys and values for a few shared KV heads. Cached per token: 147,456 bytes at 16-bit.

ContextKV cache, one sequence
4K0.56 GB
32K4.5 GB
128K18.0 GB
256K (model maximum)36.0 GB

Computed from the layer, head and window counts in the model's own configuration (microsoft/Mage-VL-Cowork), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

Mage-VL-Cowork: common questions

Does Mage-VL-Cowork fit on a 12 GB GPU?

Yes. At BF16 it needs 10.6 GB of VRAM, so a 12 GB card holds it with 1.4 GB to spare. An 8 GB card is not enough for it at BF16.

What is the least VRAM Mage-VL-Cowork can run in?

2.6 GB, at INT4 (quantized), which fits a 6 GB card, against 10.6 GB at BF16. That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.

Does quantizing Mage-VL-Cowork lower the GPU bill?

Yes. At BF16 the cheapest live fit is one RTX 3060 at $0.110/hr. At INT4 (quantized) it drops to one RTX 3070 at $0.088/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More microsoft models

All 7 microsoft models: VRAM and GPU requirements

Lineage

Based on Mage-VL.

Alternatives at this size

Other models for image-text-to-text within about a third of Mage-VL-Cowork's 4.7B parameters, from other model lines.

More on Mage-VL-Cowork

Related reading: H100 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.

Your own GPU cloud accounts

One console for the GPU clouds you already rent from. Your keys stay on your machine.

$20 a month, flat

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.