Can Gemma 4 26B A4B run on Intel Arc A770 16GB?

YES — With Q3_K_S

A75Great
Estimated from fit model

Gemma 4 26B A4B needs ~18.5 GB VRAM. Intel Arc A770 16GB has 16.0 GB. With Q3_K_S quantization, expect ~26 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: MediumStack: StandardBottleneck: Host offload
Share:

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Gemma 4 26B A4B at Q4_K_M needs 21.5 GB — too much for Intel Arc A770 16GB (16.0 GB). Runs at Q3_K_S (18.5 GB) with low quality. 2 quantization levels fit.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 21.5 GB, exceeds 16.0 GB available
21.5 GB required16.0 GB available
134% VRAM needed

5.5 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

16.4 tok/s

TTFT

11788 ms

Safe context

4K

Memory

21.5 GB / 16.0 GB

Offload

30%

Memory breakdown

Weights15.4 GB
KV Cache3.7 GB
Runtime0.9 GB
Headroom1.6 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsGemma 4 26B A4B on Intel Arc A770 16GB
1st promptCold start — includes initialization
>Write a Python function to sort a list
Here's a Python function that sorts a list using quicksort: def quicksort(arr): if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) # Example usage numbers = [3, 6, 8, 10, 1, 2, 1] print(quicksort(numbers)) # [1, 1, 2, 3, 6, 8, 10] The algorithm picks a pivot, partitions the list into smaller, equal, and larger elements, then recursively sorts each partition and concatenates the results.
2nd promptWarm — model ready, no init overhead
>Now add type hints and a docstring
def quicksort(arr: list[int]) -> list[int]: """Sort a list using the quicksort algorithm. Args: arr: List of integers to sort. Returns: A new sorted list. """ if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) Added type hints for the input and return type, plus a Google-style docstring.
Estimated: 16.4 tok/s decode · 11.8s TTFT (warm) · 41 tok/s prefill

What limits this setup

It fits through host-memory offload, and offload is the main reason performance drops.

CPU or host-memory offload is active

About 10% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.

Very little memory headroom

You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.

Runtime ecosystem is narrower than CUDA

Intel GPUs can look attractive on memory per dollar, but local AI tooling, kernels, and model coverage are still broader and easier on CUDA today.

Best improvement path

Remove offload with more accelerator memory

Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Prefer CUDA if you want the path of least resistance

If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.

Buy headroom, not only minimum fit

A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatFToo heavy19.8 tok/s5333 ms4K
CodingFToo heavy16.4 tok/s11788 ms4K
Agentic CodingFToo heavy11.8 tok/s23865 ms4K
ReasoningFToo heavy16.4 tok/s13932 ms4K
RAGFToo heavy11.8 tok/s29831 ms4K

Quantization options

How Gemma 4 26B A4B (25.200000762939453B params) fits at each quantization level on Intel Arc A770 16GB (16.0 GB usable).

QuantBitsVRAMQualityFit
Q2_KBest for your GPU
2
9.8 GB
LowS86
Q3_K_S
3
12.3 GB
LowF0
NVFP4
4
14.1 GB
MediumF0
Q4_K_M
4
15.4 GB
MediumF0
Q5_K_M
5
18.1 GB
HighF0
Q6_K
6
20.7 GB
HighF0
Q8_0
8
27.0 GB
Very HighF0
F16
16
51.7 GB
MaximumF0

Get started

Copy-paste commands to run Gemma 4 26B A4B on your machine.

Run

ollama run gemma4:26b

アップグレードオプション

Gemma 4 26B A4Bを快適に動かすハードウェア

Frequently asked questions

Can Intel Arc A770 16GB run Gemma 4 26B A4B?

Yes, Intel Arc A770 16GB can run Gemma 4 26B A4B at Q3_K_S quantization (Very compromised (needs ~1.7 GB host RAM)). The recommended Q4_K_M requires 21.5 GB which exceeds available memory, but at Q3_K_S it needs only 18.5 GB. Expected decode speed: 26.1 tok/s.

How much VRAM does Gemma 4 26B A4B need?

Gemma 4 26B A4B (25.200000762939453B parameters) requires approximately 21.5 GB at Q4_K_M quantization. On Intel Arc A770 16GB, it fits at Q3_K_S using 18.5 GB.

What is the best quantization for Gemma 4 26B A4B?

The recommended quantization is Q4_K_M, but on Intel Arc A770 16GB the best fitting quantization is Q3_K_S, which uses 18.5 GB.

What speed will Gemma 4 26B A4B run at on Intel Arc A770 16GB?

On Intel Arc A770 16GB, Gemma 4 26B A4B achieves approximately 26.1 tokens per second decode speed with a time-to-first-token of 7405ms using Q3_K_S quantization.

Can Intel Arc A770 16GB run Gemma 4 26B A4B for coding?

For coding workloads, Gemma 4 26B A4B on Intel Arc A770 16GB receives a F grade with 16.4 tok/s and 4K context.

What context window can Gemma 4 26B A4B use on Intel Arc A770 16GB?

On Intel Arc A770 16GB, Gemma 4 26B A4B can safely use up to 5K tokens of context at Q3_K_S quantization. The model's official context limit is 256K, but available memory constrains the safe maximum.

What should I upgrade first if Gemma 4 26B A4B feels slow on Intel Arc A770 16GB?

Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Would CUDA be a better path than Intel Arc A770 16GB for Gemma 4 26B A4B?

Often yes, if your goal is the easiest setup and the widest runtime support. Intel can offer attractive memory capacity, but CUDA still tends to win on tooling maturity, guides, kernels, and model coverage for local AI.

See all results for Intel Arc A770 16GBSee all hardware for Gemma 4 26B A4B
Embed this result

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/gemma-4-26b-a4b-on-arc-a770-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: