Inclusion AILingBailingMoeV3ForCausalLM

Ling 3.0 Flash — Hardware Requirements & GPU Compatibility

ChatFunctions

Ling 3.0 Flash is a 127.5-billion-parameter Mixture-of-Experts language model from InclusionAI, Ant Group's open-model initiative, with only about 5.6 billion parameters active per token, keeping per-token compute low even though all expert weights must still fit in memory. It is built for chat and agentic workloads such as tool use and multi-step tasks, blending Ant's fast "Flash" line with reasoning techniques from its "Ring" series. Local deployment needs multiple high-VRAM GPUs or a large unified-memory machine. It supports a 262K token context window for long documents and agent sessions. It is released under the MIT license, a permissive option for commercial and research use. Published in August 2026, it activates only a small fraction of its experts per token to approach larger-model quality at lower compute.

127.5B params · MoE5.6B active262K contextMITAug 202610.1K downloads432 likes289.4K quant downloads

Your hardware

Verdicts below are for the reference RTX 4090. Set yours to personalise the page.

Detection reads your browser's GPU name with no data sent anywhere.

Ling 3.0 Flash runs on a 96 GB+ Mac or a workstation GPU

Best local pick → Mac Studio (M3 Ultra, 96GB) · Q4_K_M · 77.6 GB · ~70 tok/s

Macs from 48 GB (IQ2_M · ~77 tok/s)

MIT

Not set up for it?

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run Ling 3.0 Flash

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

Other ways

each opens step-by-step

Run in cloud

Fits on RTX PRO 6000 (96 GB) (18 GB headroom) · Q4_K_M

Generation speed: ~179 tok/s; generation speed
Cost per 1M output tokens: $2.39; per 1M output tokens

Deployon Vast.aiBest optionfrom $1.54/hr

Compare GPUs →

Run Ling 3.0 Flash

77.6 GB VRAM at 16K context · needs offload on the RTX 4090 (53.6 GB short)

Works on macOS, Windows and Linux.

Install Ollama (Linux)
$curl -fsSL https://ollama.com/install.sh | sh
Install Ollama (macOS / Windows)
Download and run the app; it installs the ollama command.
Download Ollama ↗
Run Q4_K_M
$ollama run hf.co/AtomicChat/Ling-3.0-flash-GGUF:Q4_K_M
Raise the context window
Type it inside the chat. For the API server instead, start it with OLLAMA_CONTEXT_LENGTH=16384 ollama serve.
$/set parameter num_ctx 16384
A larger context needs more memory than the weights alone.
Use the API
Ollama serves its API on http://localhost:11434.

Works on macOS, Windows and Linux.

Install LM Studio
Desktop app for macOS (Apple silicon), Windows and Linux.
lmstudio.ai ↗
Download the model
In the app press Ctrl/Cmd + Shift + M and paste https://huggingface.co/AtomicChat/Ling-3.0-flash-GGUF, then pick Q4_K_M. Or use the CLI (run LM Studio once first):
$lms get https://huggingface.co/AtomicChat/Ling-3.0-flash-GGUF@Q4_K_M
Open on Hugging Face ↗
Load and chat
Open the model loader, select the model and set Context Length to 16384. Leave GPU offload at maximum if it fits.
Start the local server (optional)
$lms server start

Works on macOS, Windows and Linux.

Install llama.cpp (macOS)
MacPorts, Nix and conda-forge also work.
$brew install llama.cpp
Install options ↗
Install llama.cpp (Windows)
$winget install llama.cpp
Install llama.cpp (Linux)
Download the prebuilt llama-*-bin-ubuntu-* archive for your GPU backend (CPU, Vulkan) from the releases page, unpack it and run the binaries from that folder. Homebrew (brew install llama.cpp) and conda-forge also work on Linux.
llama.cpp releases ↗
Start the server
Downloads the model on first run. The chat UI and an OpenAI-compatible API are at http://localhost:8080.
$llama-server -hf AtomicChat/Ling-3.0-flash-GGUF:Q4_K_M -c 16384 -ngl 99 --port 8080

Works on macOS, Windows and Linux.

Option A: Docker Model Runner
Docker Desktop: Settings > AI > Enable Docker Model Runner. Docker Engine on Linux: install the docker-model-plugin package.
$docker model run hf.co/AtomicChat/Ling-3.0-flash-GGUF:Q4_K_M
Model Runner docs ↗
The quant tag after the repo is how Hugging Face cards write it; if your Docker version rejects it, drop the tag and pick the quant by repo.
Option B: llama.cpp server image (NVIDIA)
Needs the NVIDIA Container Toolkit. Models are cached in the llama-cache volume. Open http://localhost:8080.
$docker run --gpus all -p 8080:8080 -v llama-cache:/root/.cache ghcr.io/ggml-org/llama.cpp:server-cuda -hf AtomicChat/Ling-3.0-flash-GGUF:Q4_K_M -c 16384 -ngl 99 --host 0.0.0.0 --port 8080
Image tags (cuda13, vulkan, rocm) ↗
Cache path inside the image is not in the docs; remove the -v flag if the volume complains.

Linux only.

Install vLLM
Linux only; on Windows run it inside WSL2. NVIDIA GPU shown; AMD ROCm, Intel and CPU builds have their own install pages.
$uv venv --python 3.12 --seed
$source .venv/bin/activate
$uv pip install vllm --torch-backend=auto
vLLM installation ↗
Serve the model
OpenAI-compatible API at http://localhost:8000/v1.
$vllm serve inclusionAI/Ling-3.0-flash --max-model-len 16384
Runs the original weights, not the Q4_K_M GGUF; needs ~280 GB of GPU memory.

macOS only.

MLX supports only macOS, so follow these steps for that setup.

Install mlx-lm
$pip install mlx-lm
Chat in the terminal
$mlx_lm.chat --model TensorFold/Ling-3.0-flash-MLX-4bit
Downloads the model on first run. The MLX repo has its own quantisation; it may not match the quant selected above.
Or start a local server
Listens on http://localhost:8080.
$mlx_lm.server --model TensorFold/Ling-3.0-flash-MLX-4bit

Works on macOS, Windows and Linux.

Install Jan
jan.ai ↗
Find the model
Open the Hub tab, paste this model ID in Search, and choose Q4_K_M if offered.
$AtomicChat/Ling-3.0-flash-GGUF
Use the local API (optional)
Settings > Local API Server > Start Server. It listens on http://127.0.0.1:1337.

Rent GPUs hourly to run Q4_K_M right there. Pricing comes from partner marketplaces and varies.

Available GPU rentals for Q4_K_M, prioritized by value
GPU	Speed	$/1M tokens	Rent
RTX PRO 6000 Server (96 GB)CheapestCheapest18 GB free	~179 tok/s	$2.39	Deploy on Vast.aifrom $1.54/hr (opens in new tab)	96 GB · 18 GB free · ~179 tok/s · $2.39 / 1M tokens
RTX PRO 6000 Max-Q (96 GB)18 GB free	~191 tok/s	$2.28	Deploy on Vast.aifrom $1.56/hr (opens in new tab)	96 GB · 18 GB free · ~191 tok/s · $2.28 / 1M tokens
RTX PRO 6000 Server (96 GB)18 GB free	~179 tok/s	$2.63	Deploy on RunPodfrom $1.69/hr (opens in new tab)	96 GB · 18 GB free · ~179 tok/s · $2.63 / 1M tokens
RTX PRO 6000 (96 GB)18 GB free	~191 tok/s	$2.72	Deploy on Vast.aifrom $1.87/hr (opens in new tab)	96 GB · 18 GB free · ~191 tok/s · $2.72 / 1M tokens
H200 SXM (141 GB)63 GB free	~294 tok/s	$3.40	Deploy on RunPodfrom $3.59/hr (opens in new tab)	141 GB · 63 GB free · ~294 tok/s · $3.40 / 1M tokens
H200 NVL (141 GB)63 GB free	~294 tok/s	$3.92	Deploy on Vast.aifrom $4.15/hr (opens in new tab)	141 GB · 63 GB free · ~294 tok/s · $3.92 / 1M tokens
B200 (192 GB)114 GB free	~337 tok/s	$4.93	Deploy on RunPodfrom $5.98/hr (opens in new tab)	192 GB · 114 GB free · ~337 tok/s · $4.93 / 1M tokens
B300 (288 GB)210 GB free	~337 tok/s	$5.72	Deploy on RunPodfrom $6.94/hr (opens in new tab)	288 GB · 210 GB free · ~337 tok/s · $5.72 / 1M tokens

Compare GPUs →

How Much VRAM Does Ling 3.0 Flash Need?

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

VRAM	+32K	+128K	File	Quality	On RTX 4090 (reference)
36.2 GB	36.9 GB	41.7 GB	39.2 GB	2-bit · i-quant extreme compression — Importance-weighted 2-bit, extreme compression — significant quality loss	Does not fit: needs 36.2 GB
39.4 GB	40.1 GB	44.9 GB	44.7 GB	2-bit · i-quant extra small — Importance-weighted 2-bit, extra small	Does not fit: needs 39.3 GB
41.0 GB	41.7 GB	46.5 GB	46.9 GB	2-bit · i-quant small — Importance-weighted 2-bit, small	Does not fit: needs 40.9 GB
44.2 GB	44.9 GB	49.7 GB	49.1 GB	2-bit · i-quant medium — Importance-weighted 2-bit, medium	Does not fit: needs 44.1 GB
50.6 GB	51.3 GB	56 GB	57.1 GB	3-bit · i-quant — Importance-weighted 3-bit	Does not fit: needs 50.5 GB
53.8 GB	54.5 GB	59.2 GB	58.9 GB	3-bit · i-quant extra small — Importance-weighted 3-bit, extra small	Does not fit: needs 53.7 GB
55.4 GB	56.1 GB	60.8 GB	57.8 GB	3-bit · i-quant small — Importance-weighted 3-bit, small	Does not fit: needs 55.3 GB
55.4 GB	56.1 GB	60.8 GB	~54.2 GB	2-bit · K-quant — 2-bit quantization with K-quant improvements	Does not fit: needs 55.3 GB
57.0 GB	57.7 GB	62.4 GB	56.3 GB	3-bit small — 3-bit small quantization	Does not fit: needs 56.9 GB
58.5 GB	59.3 GB	64 GB	62.2 GB	3-bit · i-quant medium — Importance-weighted 3-bit, medium	Does not fit: needs 58.5 GB
63.3 GB	64 GB	68.8 GB	62.6 GB	3-bit medium — 3-bit medium quantization	Does not fit: needs 63.2 GB
64.9 GB	65.6 GB	70.4 GB	72.8 GB	4-bit · legacy — 4-bit legacy quantization	Does not fit: needs 64.8 GB
66.5 GB	67.2 GB	72 GB	61.4 GB	3-bit large — 3-bit large quantization	Does not fit: needs 66.4 GB
69.7 GB	70.4 GB	75.2 GB	66.4 GB	4-bit · i-quant compact — Importance-weighted 4-bit, compact	Does not fit: needs 69.6 GB
72.9 GB	73.6 GB	78.4 GB	80.2 GB	4-bit · legacy+ — 4-bit legacy quantization with offset	Does not fit: needs 72.8 GB
72.9 GB	73.6 GB	78.4 GB	74.2 GB	4-bit small — 4-bit small quantization	Does not fit: needs 72.8 GB
72.9 GB	73.6 GB	78.4 GB	79.3 GB	4-bit · i-quant non-linear — Importance-weighted 4-bit, non-linear	Does not fit: needs 72.8 GB
77.7 GB	78.4 GB	83.1 GB	75.3 GB	4-bit medium — 4-bit medium quantization — most popular sweet spot	Does not fit: needs 77.6 GB
79.3 GB	80 GB	84.7 GB	84 GB	4-bit large — 4-bit large quantization	Does not fit: needs 79.2 GB
88.8 GB	89.5 GB	94.3 GB	87.4 GB	5-bit small — 5-bit small quantization	Does not fit: needs 88.7 GB
92.0 GB	92.7 GB	97.5 GB	88.3 GB	5-bit medium — 5-bit medium quantization — good quality/size tradeoff	Does not fit: needs 91.9 GB
93.6 GB	94.3 GB	99.1 GB	95.3 GB	5-bit large — 5-bit large quantization	Does not fit: needs 93.5 GB
106.4 GB	107.1 GB	111.8 GB	107.5 GB	6-bit, very good — 6-bit quantization, very good quality	Does not fit: needs 106.3 GB
128.7 GB	129.4 GB	134.1 GB	133.1 GB	8-bit, near-lossless — 8-bit quantization, near-lossless	Does not fit: needs 128.6 GB
256.1 GB	256.9 GB	261.6 GB	248.9 GB	16-bit · bfloat — Brain floating point 16 — preferred for training	Does not fit: needs 256.1 GB

Selected Q4_K_M

4-bit medium quantization

77.6GBat 16K context

Weights: 76.5 GB
KV cache: 0.8 GB
Overhead: 0.3 GB

Doesn't fit RTX 4090 (reference) · needs 53.6 GB more

≥50 tok/s needs ≥297 GB/s · M3 Ultra ~70, M2 Ultra ~69

Or rent RTX PRO 6000 from $1.54/hr.

Which Hardware Can Run Ling 3.0 Flash?

Q4_K_M · 77.7 GB

Ling 3.0 Flash (Q4_K_M) requires 77.7 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 101+ GB is recommended. Using the full 262K context window can add up to 11.8 GB, bringing total usage to 89.5 GB. No consumer GPU has enough memory. 30 devices with unified memory can run Ling 3.0 Flash, including Mac Studio (M3 Ultra, 256GB), Mac Studio (M3 Ultra, 512GB), Mac Studio (M3 Ultra, 96GB).

By VRAM tier · typical GPUs and Macs at Q4_K_M

Typical hardwareQuantVRAMtok/sContext that fits

8–16 GB · RTX 4060, RTX 3060 12GB, RTX 5060 Ti 16GBDoesn't fit — smallest quant needs 36.2 GB8 GB tier →12 GB tier →16 GB tier →

24 GB · RTX 4090referenceDoesn't fit — smallest quant needs 36.2 GB24 GB tier →

Mac 32 GB · Mac Mini M4Doesn't fit — smallest quant needs 36.2 GBMacs →

Mac 64 GB · Mac Studio M4 MaxIQ3_M · 58.5 GB · ~66 tok/s · 32K58.5~6632KMacs →

Alternatives to Ling 3.0 Flash

Ling family · 4 models →

Similar models

4tok/s on RTX 4090

Model	Score	VRAM	tok/s	Why it is similar
Qwen3.5 122B A10BAlibaba	109.4	75.5 GB	—needs > 24 GB	same size
NVIDIA Nemotron 3.5 Super VL 120B A12B BF16NVIDIA	—	87.7 GB	—needs > 24 GB	same size
Leanstral 1.5 119B A6BMistral AI	—	84 GB	—needs > 24 GB	same size
XORTRON.CriminalComputing.LARGE.2026.3darkc0de	—	79.8 GB	—needs > 24 GB	same size

Fine-tunes & variants(1)community builds of Ling 3.0 Flash

Ling 3.0 Flash Fin

Specifications

Publisher: Inclusion AI
Family: Ling
Parameters: 127.5B
Active parameters: 5.6B per token
Architecture: BailingMoeV3ForCausalLM
Context Length: 262,144 tokens
Vocabulary Size: 157,184
Release Date: 2026-08-02
License: MIT

Resources

Frequently Asked Questions

How much VRAM does Ling 3.0 Flash need?

Ling 3.0 Flash requires 77.7 GB of VRAM at Q4_K_M, or 256.1 GB at BF16. Full 262K context adds up to 11.8 GB (89.5 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 127.5B × 4.8 bits ÷ 8 = 76.5 GB

KV Cache + Overhead ≈ 1.2 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 ≈ 13 GB (at full 262K context)

VRAM usage by quantization

Q4_K_M

77.7 GB

Q4_K_M + full context

89.5 GB

Learn more about VRAM estimation →

Can NVIDIA GeForce RTX 5090 run Ling 3.0 Flash?

No — Ling 3.0 Flash requires at least 36.2 GB at IQ2_XXS, which exceeds the NVIDIA GeForce RTX 5090's 32 GB of VRAM.

What's the best quantization for Ling 3.0 Flash?

For Ling 3.0 Flash, Q4_K_M (77.7 GB) offers the best balance of quality and VRAM usage. Q4_K_L (79.3 GB) provides better quality if you have the VRAM. The smallest option is IQ2_XXS at 36.2 GB.

VRAM requirement by quantization

IQ2_XXS

36.2 GB~53%

IQ3_S

55.4 GB~75%

Q3_K_L

66.5 GB~86%

Q4_K_M ★

77.7 GB~89%

Q4_K_L

79.3 GB~90%

BF16

256.1 GB~100%

★ Recommended — best balance of quality and VRAM usage.

Learn more about quantization →

Can I run Ling 3.0 Flash on a Mac?

Yes — Mac Studio M5 Max (48 GB) and 55 other Macs can run Ling 3.0 Flash, the smallest at IQ2_M. Apple Silicon uses unified memory, so the model shares RAM with the system. At Q4_K_M you need at least 77.7 GB of usable unified memory (RAM minus macOS overhead), from Mac Studio (M3 Ultra, 96GB).

Can I run Ling 3.0 Flash locally?

Yes — Ling 3.0 Flash can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is Ling 3.0 Flash?

At Q4_K_M, Ling 3.0 Flash can reach ~110 tok/s on AMD Instinct MI350X. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = 1000 ÷ (active GB ÷ (bandwidth GB/s × efficiency) × 1000 + layers × routing ms)

Mixture-of-Experts: just the active experts get read for each token, along with a fixed routing cost per layer.

Example: NVIDIA B200 → 3.4 GB active ÷ (8000 × 0.65) = 0.66 ms, plus 42 layers × 0.055 ms = 2.31 ms, so 1000 ÷ 2.97 ms = ~337 tok/s

Estimated speed at Q4_K_M (77.7 GB)

NVIDIA B200

~337 tok/s

NVIDIA B300

~337 tok/s

NVIDIA GH200 Grace Hopper Superchip

~296 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 Ling 3.0 Flash?

At Q4_K_M, the download is about 76.49 GB. The full-precision BF16 version is 254.97 GB. The smallest option (IQ2_XXS) is 35.06 GB.

Which GPUs can run Ling 3.0 Flash?

No single consumer GPU has enough VRAM to run Ling 3.0 Flash at Q4_K_M (77.7 GB). Multi-GPU or professional hardware is required.

Which devices can run Ling 3.0 Flash?

30 devices with unified memory can run Ling 3.0 Flash at Q4_K_M (77.7 GB), including ASUS Ascent GX10, Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB), Framework Desktop (Ryzen AI Max+ 395, 128 GB), GMKtec EVO-X2 (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.