llmrun
IBMGraniteGraniteForCausalLM

Granite 3.1 2B Instruct — Hardware Requirements & GPU Compatibility

ChatFunctions

Granite 3.1 2B Instruct is IBM's 2.5-billion-parameter dense instruction-tuned model, fine-tuned from Granite-3.1-2B-Base on permissively licensed open instruction datasets plus internally generated synthetic data aimed at long-context problems. It targets business-assistant work such as summarization, classification, extraction, question answering, retrieval-augmented generation, code tasks and function calling, and supports twelve languages including English, German, Spanish, French, Japanese, Arabic and Chinese. At this size it runs on almost any consumer GPU, and on a laptop CPU once quantized. Context length is 131,072 tokens. It is released under the Apache 2.0 license, permitting unrestricted commercial and research use, and was published in December 2024. IBM has since superseded it with Granite 3.3 2B Instruct, which keeps the same size class.

2.5B params · dense131K contextApache 2.024.4K downloads57 likes6.2K quant downloads
S

Runs great on a 24 GB GPU

Runs from8 GB Q4_K_M · 64KBest on24 GB Q4_K_M · ~329 tok/s · 128KMacs from8 GB Q4_K_M · ~36 tok/s

Apache 2.0

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run Granite 3.1 2B Instruct

One recommended way. Every other method, OS and quant is in the step-by-step guide.Each way opens a step-by-step guide for your OS and quant.

Recommended

Ollama
one command · needs Ollama installed
$ollama run hf.co/bartowski/granite-3.1-2b-instruct-GGUF:Q4_K_M

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

Download: granite-3.1-2b-instruct-Q4_K_M.gguf1.55 GBbartowski

install, OS, other quants

Ways to runOther ways

each opens step-by-step

Run in cloud

Your own private copy · Q4_K_M · 24 GB GPU

  • The easiest way to try this model
  • Running in a few minutes, easy setup
  • Chat right here or connect any app

$5+ bonus for new users

How Much VRAM Does Granite 3.1 2B Instruct Need?

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

QuantizationVRAM+32KOn RTX 4090 (reference)
1.5 GB4.1 GB2-bit · K-quant — 2-bit quantization with K-quant improvementsFits: 128K context · ~426 tok/s
1.6 GB4.1 GB3-bit small — 3-bit small quantizationFits: 128K context · ~415 tok/s
1.7 GB4.2 GB3-bit medium — 3-bit medium quantizationFits: 128K context · ~385 tok/s
1.7 GB4.3 GB4-bit · legacy — 4-bit legacy quantizationFits: 128K context · ~379 tok/s
2.0 GB4.5 GB4-bit medium — 4-bit medium quantization — most popular sweet spotFits: 128K context · ~329 tok/s
2.3 GB4.8 GB5-bit medium — 5-bit medium quantization — good quality/size tradeoffFits: 128K context · ~289 tok/s
2.6 GB5.1 GB6-bit, very good — 6-bit quantization, very good qualityFits: 128K context · ~256 tok/s
3 GB5.5 GB8-bit, near-lossless — 8-bit quantization, near-losslessFits: 128K context · ~218 tok/s

Selected Q4_K_M

4-bit medium quantization

3.2GBat 16K context

Weights
1.5 GB
KV cache
1.3 GB
Overhead
0.3 GB

Fits RTX 4090 (reference) · 20.8 GB free · ~329 tok/s

≥50 tok/s needs ≥153 GB/s · RTX 5090 ~585, RTX 3090 Ti ~329

Which Hardware Can Run Granite 3.1 2B Instruct?

Q4_K_M · 2.0 GB

Granite 3.1 2B Instruct (Q4_K_M) requires 2.0 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 3+ GB is recommended. Using the full 131K context window can add up to 10.6 GB, bringing total usage to 12.6 GB. 52 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti. 163 devices with unified memory can run Granite 3.1 2B Instruct, including Mac Studio (M3 Ultra, 256GB), Mac Studio (M3 Ultra, 512GB).

By VRAM tier · typical GPUs and Macs at Q4_K_M
8 GB · RTX 4060Q4_K_M · 3.2 GB · ~89 tok/s · 64K8 GB tier →
12 GB · RTX 3060 12GBQ4_K_M · 3.2 GB · ~118 tok/s · 64K12 GB tier →
16 GB · RTX 5060 Ti 16GBQ4_K_M · 3.2 GB · ~146 tok/s · 128K16 GB tier →
24 GB · RTX 4090referenceQ4_K_M · 3.2 GB · ~329 tok/s · 128K24 GB tier →
Mac 32 GB · Mac Mini M4Q4_K_M · 3.2 GB · ~42 tok/s · 128KMacs →
Mac 64 GB · Mac Studio M4 MaxQ4_K_M · 3.2 GB · ~192 tok/s · 128KMacs →

How good is Granite 3.1 2B Instruct?

llmrun Score blends public benchmark boards into one number; 100 = the average open model.

Not enough data yet for an llmrun Score.

A Score needs results on enough independent boards. How the Composite Score is built

Benchmarks

Here are all 2 boards that have results for this model, sorted by their weight in the llmrun Score; badges show who ran the test.

  • LMArena Text

    LMArena · Oct 2026Arena

    1178.9

    #157/188 open

    Arena
  • MMLU-Pro

    TIGER-LabIndependent

    32.0%

    #117/146 open

    Independent

Alternatives to Granite 3.1 2B Instruct

Granite family · 28 models →

Similar models

6
ModelScoreVRAMtok/sWhy it is similar
WeVisOne VL 2BTencent—3.6 GB~328same size
MiniCPM5 2BOpenBMB—2.5 GB~345same size
North Micro Vision InstructCohere—3.7 GB~323same size
LFM2.5 2.6BLiquid AI—2.3 GB~321same size
Gemma 2 2B ITGoogle—2.5 GB~379same size
Ouro 2.6B ThinkingByteDance—12.1 GB~102same size

Specifications

Publisher
IBM
Family
Granite
Parameters
2.5B
Architecture
GraniteForCausalLM
Context Length
131,072 tokens
Vocabulary Size
49,155
Release Date
2024-12-06
License
Apache 2.0

Frequently Asked Questions

How much VRAM does Granite 3.1 2B Instruct need?

Granite 3.1 2B Instruct requires 2.0 GB of VRAM at Q4_K_M, or 5.5 GB at BF16. Full 131K context adds up to 10.6 GB (12.6 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 2.5B × 4.8 bits ÷ 8 = 1.5 GB

KV Cache + Overhead ≈ 0.5 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 ≈ 11.1 GB (at full 131K context)

VRAM usage by quantization

2.0 GB
12.6 GB

Learn more about VRAM estimation →

What's the best quantization for Granite 3.1 2B Instruct?

For Granite 3.1 2B Instruct, Q4_K_M (2.0 GB) offers the best balance of quality and VRAM usage. Q4_K_L (2.0 GB) provides better quality if you have the VRAM. The smallest option is IQ2_XXS at 1.2 GB.

VRAM requirement by quantization

IQ2_XXS
1.2 GB
Q2_K
1.5 GB
IQ4_XS
1.8 GB
Q4_K_M ★
2.0 GB
Q5_0
2.0 GB
BF16
5.5 GB

★ Recommended — best balance of quality and VRAM usage.

Learn more about quantization →

Can I run Granite 3.1 2B Instruct on a Mac?

Yes — MacBook Air 13" M3 (8 GB) and 145 other Macs can run Granite 3.1 2B Instruct. Apple Silicon uses unified memory, so the model shares RAM with the system. At Q4_K_M you need at least 2.0 GB of usable unified memory (RAM minus macOS overhead).

Can I run Granite 3.1 2B Instruct locally?

Yes — Granite 3.1 2B Instruct can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is Granite 3.1 2B Instruct?

At Q4_K_M, Granite 3.1 2B Instruct can reach ~2412 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~329 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 ÷ 1.99 × 0.65 = ~2613 tok/s

Estimated speed at Q4_K_M (2.0 GB)

~2613 tok/s
~329 tok/s
~2613 tok/s
~2412 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 Granite 3.1 2B Instruct?

At Q4_K_M, the download is about 1.52 GB. The full-precision BF16 version is 5.07 GB. The smallest option (IQ2_XXS) is 0.70 GB.

Which GPUs can run Granite 3.1 2B Instruct?

52 consumer GPUs can run Granite 3.1 2B Instruct at Q4_K_M. Top options include AMD Radeon RX 6700 XT, AMD Radeon RX 6800, AMD Radeon RX 6800 XT. 52 GPUs have plenty of headroom for comfortable inference.

Which devices can run Granite 3.1 2B Instruct?

163 devices with unified memory can run Granite 3.1 2B Instruct at Q4_K_M (2.0 GB), including AMD Ryzen AI 9 HX 370 (Strix Point) Laptop, ASUS Ascent GX10, Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB), Framework Desktop (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.