← All modelsMODEL CHECK

Can I run Gemma 3 27B?

Gemma 3 27B by Google needs around 24 GB of RAM at the recommended 4-bit quantization (16.6 GB download). Your hardware is checked below — instantly, nothing leaves your browser. Expect roughly ~21 tok/s on a Apple M-series Max.

Reading your hardware signals…

Real-world notes

Gemma 3 27B is the model you reach for when an 8B class assistant feels too thin and you have the memory to spare. It is a 27.4B chat-and-vision model from Google, which means it reads images as well as text, and that capability is the main reason to pick it over a same-size text-only model. At a 4-bit quant it lands around 16.6 GB, so a 12 GB card like an RTX 3060 simply will not hold it, and you will want at least 24 GB of RAM or unified memory before it runs comfortably. A 24 GB RTX 4090 or an M-series Mac with plenty of unified memory is the natural home for it.

In daily use it feels like a noticeably more grounded conversationalist than the small models, with the multimodal angle making it genuinely useful for describing or reasoning over screenshots and photos. On a 4090 at 4-bit you can expect around 52 tokens per second, which streams faster than you read; an M Max Mac sits closer to 21 tok/s, still very usable, while CPU-only on DDR5 drops to roughly 3 tok/s and is really only for batch jobs. The 128K context is real but expensive here: filling it pushes total memory to about 45.8 GB, well past what a single 24 GB device holds, so keep working context modest unless you have headroom.

Against its own family it is the heavyweight, with Gemma 3 4B being the lighter pick when memory is tight and you still want vision. The more interesting comparison is Qwen 3.5 27B, a near-identical-size model that adds dedicated reasoning and coding strengths; for structured math or code tasks it generally edges Gemma out, so reach for Gemma 3 27B more for solid chat plus image understanding than for hard reasoning. Its standout trait is that vision-plus-chat balance at a manageable single-GPU size. One caveat: the Gemma license is open-weight, not open-source, so read Google's terms before shipping it in a commercial product.

Specifications

Parameters27.4B
Context window128K tokens
ProviderGoogle
LicenseGemma
Released2025-03
Best forChat, Vision

Size by quantization

QuantizationBits/weightDownloadMin RAMQuality
Q2_K3.3511.5 GB16 GBNoticeable loss
Q4_K_MRecommended4.8516.6 GB24 GBRecommended
Q5_K_M5.6519.4 GB32 GBHigh
Q8_08.529.1 GB48 GBNear-original
F161654.8 GB96 GBOriginal

Sizes are estimates from parameter count × bits per weight; real GGUF builds vary slightly. · Data updated: 2026-06-11 · How we calculate these numbers →

Memory needed by context length

ContextKV cache (est.)Total memory (Q4)
4K tokens~0.9 GB~17.5 GB
8K tokens~1.8 GB~18.4 GB
32K tokens~7.3 GB~23.9 GB
128K tokens~29.2 GB~45.8 GB

The KV cache grows with context length — a model that fits at 4K can run out of memory at 32K. Estimates assume an FP16 cache with grouped-query attention; actual usage varies by runtime.

Estimated speed by hardware

HardwareBandwidth~Speed
NVIDIA RTX 3060 12GB360 GB/sWon't fit in VRAM
NVIDIA RTX 4090 24GB1008 GB/s~52 tok/s
Apple M-series (base)100 GB/s~5 tok/s
Apple M-series Pro270 GB/s~14 tok/s
Apple M-series Max410 GB/s~21 tok/s
CPU only (dual-channel DDR5)60 GB/s~3 tok/s

Token generation is memory-bandwidth bound: tok/s ≈ bandwidth × 0.85 ÷ model size at Q4. Real-world numbers vary by runtime and context length.

Run it locally

The easiest path is Ollama — one command and you're chatting:

ollama run gemma3:27b

Frequently asked questions