llmrun
MicrosoftQwen3VLForConditionalGeneration

AesCode 32B — Hardware Requirements & GPU Compatibility

VisionCodeFunctions

AesCode-32B is a Microsoft research model that writes slides, posters, dashboards, and infographics as editable HTML and CSS. It starts from Qwen3-VL-32B-Instruct and is trained with supervised fine-tuning followed by reinforcement learning on several reward signals. It can take an image generated from the same prompt as a style reference, which it uses for layout and look while taking the content from the text prompt. On the paper's 300-sample infographic test, it scored 85.89 overall, ahead of GPT-5.5 and Claude Opus 4.8 given the same reference. At about 33 billion parameters, a Q4 quant fits a 24 GB GPU. The context window is 262,144 tokens. It is released under the Apache 2.0 license. Because it is a vision-language model, it reads images as well as text. It is a specialist for design-to-code output rather than a general chat model, and the card pitches it for generating editable visual documents and for research on multimodal code generation. A smaller AesCode-8B sibling is also available.

33.4B params · dense262K contextApache 2.0611 downloads52 likes10.3K quant downloads
B

Decent on a 24 GB GPU

Runs from16 GB IQ3_XXS · 16KBest on24 GB Q4_K_M · ~32 tok/s · 16KMacs from32 GB ~4 tok/s

Apache 2.0

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run AesCode 32B

One recommended way. Every other method, OS and quant is in the step-by-step guide.

Recommended

Ollama
one command · needs Ollama installed
$ollama run hf.co/bartowski/AesCode-32B-GGUF:Q4_K_M

Q4_K_M fits fully on the RTX 4090 · 1.0 GB free · 16K context

Download: AesCode-32B-Q4_K_M.gguf20.49 GBbartowski

install, OS, other quants

Other ways

each opens step-by-step

Run in cloud

Fits on RTX A6000 (48 GB) (25 GB headroom) · Q4_K_M

Generation speed
~24 tok/s
generation speed
Cost per 1M output tokens
$3.79
per 1M output tokens

How Much VRAM Does AesCode 32B Need?

Select a quantization level; the listed hardware adheres to it.

QuantizationVRAM+32KOn RTX 4090 (reference)
14.8 GB19.8 GB2-bit · K-quant — 2-bit quantization with K-quant improvementsFits: 32K context · ~44 tok/s
15.2 GB20.3 GB3-bit small — 3-bit small quantizationFits: 32K context · ~43 tok/s
16.9 GB21.9 GB3-bit medium — 3-bit medium quantizationFits: 32K context · ~39 tok/s
17.3 GB22.3 GB4-bit · legacy — 4-bit legacy quantizationFits: 32K context · ~38 tok/s
20.6 GB25.7 GB4-bit medium — 4-bit medium quantization — most popular sweet spotFits: 16K context · ~32 tok/s
24.4 GB29.4 GB5-bit medium — 5-bit medium quantization — good quality/size tradeoffDoes not fit: needs 26.8 GB
28.2 GB33.2 GB6-bit, very good — 6-bit quantization, very good qualityDoes not fit: needs 30.5 GB
34.0 GB39 GB8-bit, near-lossless — 8-bit quantization, near-losslessDoes not fit: needs 36.3 GB

Selected Q4_K_M

4-bit medium quantization

23.0GBat 16K context

Weights
20.0 GB
KV cache
2.7 GB
Overhead
0.3 GB

Fits RTX 4090 (reference) · 1.0 GB free · ~32 tok/s

≥50 tok/s needs ≥1.59 TB/s · RTX 5090 ~56

Which Hardware Can Run AesCode 32B?

Q4_K_M · 20.6 GB

AesCode 32B (Q4_K_M) requires 20.6 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 27+ GB is recommended. Using the full 262K context window can add up to 42.6 GB, bringing total usage to 63.3 GB. 7 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti. 103 devices with unified memory can run AesCode 32B, including NVIDIA DGX H100, NVIDIA DGX A100 640GB, Mac Studio M1 Max (32 GB).

By VRAM tier · typical GPUs and Macs at Q4_K_M
8–12 GB · RTX 4060, RTX 3060 12GBDoesn't fit — smallest quant needs 12.2 GB8 GB tier →12 GB tier →
16 GB · RTX 5060 Ti 16GBIQ3_XXS · 15.9 GB · ~22 tok/s · 16K16 GB tier →
24 GB · RTX 4090referenceQ4_K_M · 23 GB · ~32 tok/s · 16K24 GB tier →
Mac 32 GB · Mac Mini M4Q4_K_M · 23 GB · ~4 tok/s · 32KMacs →
Mac 64 GB · Mac Studio M4 MaxQ4_K_M · 23 GB · ~19 tok/s · 128KMacs →

Alternatives to AesCode 32B

Similar models

6
ModelScoreVRAMtok/sWhy it is similar
Qwen3.6 35B A3BAlibaba107.122 GB~151same size
MiniCPM V 4.7 35B A3BOpenBMB—22.1 GB~169same size
Ornith 1.5 35B A3Bornith-ai—22 GB~151same size
NVIDIA Nemotron 3.5 Lightning 30B A3B BF16NVIDIA—19.3 GB~197same size
Agents A1InternScience—21.5 GB~171same size
EXAONE 4.5 33BLGAI-EXAONE—23.9 GB~33same size

Specifications

Publisher
Microsoft
Parameters
33.4B
Architecture
Qwen3VLForConditionalGeneration
Context Length
262,144 tokens
Vocabulary Size
151,936
Release Date
2026-09-29
License
Apache 2.0

Frequently Asked Questions

How much VRAM does AesCode 32B need?

AesCode 32B requires 20.6 GB of VRAM at Q4_K_M, or 67.3 GB at BF16. Full 262K context adds up to 42.6 GB (63.3 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 33.4B × 4.8 bits ÷ 8 = 20 GB

KV Cache + Overhead ≈ 0.6 GB (at 2K context + ~0.3 GB framework)

Fit ratings and hardware model lists check this model with room for a 16K-token context, which needs a little more memory.

KV Cache + Overhead ≈ 43.3 GB (at full 262K context)

VRAM usage by quantization

20.6 GB
63.3 GB

Learn more about VRAM estimation →

Can NVIDIA GeForce RTX 4090 run AesCode 32B?

Yes, at Q5_K_S (23.6 GB) or lower. Higher quantizations like Q5_K_M (24.4 GB) exceed the NVIDIA GeForce RTX 4090's 24 GB.

What's the best quantization for AesCode 32B?

For AesCode 32B, Q4_K_M (20.6 GB) offers the best balance of quality and VRAM usage. Q4_K_L (21.1 GB) provides better quality if you have the VRAM. The smallest option is IQ2_XXS at 9.8 GB.

VRAM requirement by quantization

IQ2_XXS
9.8 GB
IQ3_XS
14.4 GB
Q4_0
17.3 GB
Q4_K_M ★
20.6 GB
Q4_K_L
21.1 GB
BF16
67.3 GB

★ Recommended — best balance of quality and VRAM usage.

Learn more about quantization →

Can I run AesCode 32B on a Mac?

Yes, but only at lower quantizations. The smallest Mac that can run AesCode 32B is iPad Pro M5 13" (16 GB) at IQ2_XXS; 136 of the 156 Macs we list can run it at some quantization. For Q4_K_M (20.6 GB) you need a Mac with more unified memory.

Can I run AesCode 32B locally?

Yes — AesCode 32B can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is AesCode 32B?

At Q4_K_M, AesCode 32B can reach ~232 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~32 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = (bandwidth GB/s ÷ model GB) × efficiency

Example: NVIDIA B200 → 8000 ÷ 20.6 × 0.65 = ~252 tok/s

Estimated speed at Q4_K_M (20.6 GB)

~252 tok/s
~32 tok/s
~252 tok/s
~232 tok/s

Real-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.

Learn more about tok/s estimation →

What's the download size of AesCode 32B?

At Q4_K_M, the download is about 20.01 GB. The full-precision BF16 version is 66.71 GB. The smallest option (IQ2_XXS) is 9.17 GB.

Which GPUs can run AesCode 32B?

7 consumer GPUs can run AesCode 32B at Q4_K_M. Top options include NVIDIA GeForce RTX 5090, AMD Radeon RX 7900 XTX, NVIDIA GeForce RTX 3090. 1 GPU have plenty of headroom for comfortable inference.

Which devices can run AesCode 32B?

103 devices with unified memory can run AesCode 32B at Q4_K_M (20.6 GB), including AMD Ryzen AI 9 HX 370 (Strix Point) Laptop, ASUS Ascent GX10, Asus ROG Flow Z13 (2025, Ryzen AI Max+ 395, 128 GB), Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.