MicrosoftPhi 4Phi3ForCausalLM

Phi 4 Mini Instruct — Hardware Requirements & GPU Compatibility

ChatCodeFunctions

Microsoft Phi 4 Mini Instruct is a 3.8-billion parameter instruction-tuned model from Microsoft Research's Phi 4 family. It applies the Phi series' data-centric training philosophy to a compact model, delivering strong performance in coding, reasoning, and chat tasks relative to its small footprint. The model runs on consumer GPUs with as little as 4-6GB of VRAM when quantized, making it accessible on mainstream and even entry-level hardware. Released under the MIT license.

3.8B params · dense131K contextMITFeb 2025337.3K downloads886 likes258.7K 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.

Runs great on a 24 GB GPU

Runs from 8 GB (Q4_K_M · 32K)Best on 24 GB (Q4_K_M · ~228 tok/s · 128K)Macs from 8 GB (Q4_K_M · ~25 tok/s)

MIT

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run Phi 4 Mini 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.

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

Run Phi 4 Mini Instruct

4.8 GB VRAM at 16K context · fits the RTX 4090 (19.2 GB free)

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/unsloth/Phi-4-mini-instruct-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 search microsoft/phi-4-mini, then pick Q4_K_M. Or use the CLI (run LM Studio once first):
$lms get microsoft/phi-4-mini@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 unsloth/Phi-4-mini-instruct-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/unsloth/Phi-4-mini-instruct-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 unsloth/Phi-4-mini-instruct-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 microsoft/Phi-4-mini-instruct --max-model-len 16384
Runs the original weights, not the Q4_K_M GGUF; needs ~8 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 mlx-community/Phi-4-mini-instruct-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 mlx-community/Phi-4-mini-instruct-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.
$unsloth/Phi-4-mini-instruct-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 3080 Ti (12 GB)CheapestCheapest7 GB free	~207 tok/s	$0.16	Deploy on Vast.aifrom $0.12/hr (opens in new tab)	12 GB · 7 GB free · ~207 tok/s · $0.16 / 1M tokens
RTX 3060 12GB7 GB free	~82 tok/s	$0.21	Deploy on Vast.aifrom $0.061/hr (opens in new tab)	7 GB free · ~82 tok/s · $0.21 / 1M tokens
RTX 3060 Ti (8 GB)3 GB free	~102 tok/s	$0.21	Deploy on Vast.aifrom $0.076/hr (opens in new tab)	8 GB · 3 GB free · ~102 tok/s · $0.21 / 1M tokens
RTX 3070 (8 GB)3 GB free	~102 tok/s	$0.22	Deploy on Vast.aifrom $0.081/hr (opens in new tab)	8 GB · 3 GB free · ~102 tok/s · $0.22 / 1M tokens
RTX 4060 (8 GB)3 GB free	~62 tok/s	$0.39	Deploy on Vast.aifrom $0.086/hr (opens in new tab)	8 GB · 3 GB free · ~62 tok/s · $0.39 / 1M tokens
RTX 3080 (10 GB)5 GB free	~172 tok/s	$0.27	Deploy on RunPodfrom $0.17/hr (opens in new tab)	10 GB · 5 GB free · ~172 tok/s · $0.27 / 1M tokens
RTX 4000 Ada (20 GB)15 GB free	~82 tok/s	$0.68	Deploy on RunPodfrom $0.20/hr (opens in new tab)	20 GB · 15 GB free · ~82 tok/s · $0.68 / 1M tokens
RTX 3090 (24 GB)19 GB free	~212 tok/s	$0.29	Deploy on RunPodfrom $0.22/hr (opens in new tab)	24 GB · 19 GB free · ~212 tok/s · $0.29 / 1M tokens
RTX 4090 (24 GB)19 GB free	~228 tok/s	$0.41	Deploy on RunPodfrom $0.34/hr (opens in new tab)	24 GB · 19 GB free · ~228 tok/s · $0.41 / 1M tokens

Compare GPUs →

Your own private copy of Phi 4 Mini Instruct · Q4_K_M · OpenAI-compatible API

Open the llama.cpp listing on RunPod
Open on RunPodServerless (opens in new tab)
New to RunPod? Sign up and add credit first.
2
Fill in the form
Press Deploy and fill in:
Model
unsloth/Phi-4-mini-instruct-GGUF
Quantization
Q4_K_M
Context Size
16384
After pasting the model press Esc — don’t pick a suggestion. Press Next.
Create the endpoint
Keep the default 24 GB and 48 GB, then Create Endpoint. Right away: Manage → Edit endpoint → Max workers 1 → Save (changing settings later restarts the worker).
The first start downloads the model, usually 5–15 min. After that, replies after a pause come in seconds.
Create an API key
RunPod → Settings → API Keys → Create. Pick “Restricted” with access to this endpoint only.

Use it

Copy the endpoint URL from its page on RunPod (any of its links works) and paste it with the key. Both stay in this browser.

Endpoint URL

API key

Chats and keys stay only in this browser.

https://api.runpod.ai/v2/<ENDPOINT_ID>/openai/v1

Put your endpoint ID in place of <ENDPOINT_ID>. The API key is the one from step 2.

from openai import OpenAI
client = OpenAI(base_url="https://api.runpod.ai/v2/<ENDPOINT_ID>/openai/v1", api_key="rpa_...")
r = client.chat.completions.create(
    model="any",
    messages=[{"role": "user", "content": "Hello!"}])
print(r.choices[0].message.content)

Works with any OpenAI client.

https://api.runpod.ai/v2/<ENDPOINT_ID>/openai/v1

Put your endpoint ID in place of <ENDPOINT_ID>. The API key is the one from step 2.

Free on Windows, macOS, Linux, iOS, Android and the web.

Open the web app ↗ (opens in a new tab)Download ↗ (opens in a new tab)

1. Settings → Model Provider → Add → Add Custom Provider
2. API Mode OpenAI API Compatible; paste the API key and the base URL as API Host
3. Model → Fetch, pick the model
4. New chat → pick the provider → start chatting

Free and open source for Windows, macOS and Linux.

Download Jan ↗ (opens in a new tab)

1.Settings → next to Model Providers press +
2.API format OpenAI-compatible; Base URL is the base URL above (with /v1); API key is your key; Create
3.If no model appears, click + in Models and type any
4.New chat → pick the model → start chatting

How Much VRAM Does Phi 4 Mini Instruct Need?

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

VRAM	+32K	+128K	File	Quality	On RTX 4090 (reference)
1.6 GB	5.7 GB	18.5 GB	1.3 GB	2-bit · i-quant extreme compression — Importance-weighted 2-bit, extreme compression — significant quality loss	Fits: 128K context · ~404 tok/s
1.7 GB	5.8 GB	18.6 GB	1.4 GB	2-bit · i-quant extra small — Importance-weighted 2-bit, extra small	Fits: 128K context · ~381 tok/s
1.8 GB	5.8 GB	18.7 GB	1.4 GB	2-bit · i-quant small — Importance-weighted 2-bit, small	Fits: 128K context · ~370 tok/s
1.9 GB	5.9 GB	18.8 GB	1.5 GB	2-bit · i-quant medium — Importance-weighted 2-bit, medium	Fits: 128K context · ~352 tok/s
2.0 GB	6.1 GB	19 GB	1.7 GB	3-bit · i-quant — Importance-weighted 3-bit	Fits: 128K context · ~320 tok/s
2.1 GB	6.2 GB	19.1 GB	1.8 GB	3-bit · i-quant extra small — Importance-weighted 3-bit, extra small	Fits: 128K context · ~305 tok/s
2.2 GB	6.2 GB	19.1 GB	1.7 GB	2-bit · K-quant — 2-bit quantization with K-quant improvements	Fits: 128K context · ~298 tok/s
2.2 GB	6.2 GB	19.1 GB	1.9 GB	3-bit · i-quant small — Importance-weighted 3-bit, small	Fits: 128K context · ~298 tok/s
2.3 GB	6.3 GB	19.2 GB	1.9 GB	3-bit small — 3-bit small quantization	Fits: 128K context · ~291 tok/s
2.3 GB	6.3 GB	19.2 GB	2 GB	3-bit · i-quant medium — Importance-weighted 3-bit, medium	Fits: 128K context · ~286 tok/s
2.4 GB	6.5 GB	19.4 GB	2.1 GB	3-bit medium — 3-bit medium quantization	Fits: 128K context · ~269 tok/s
2.5 GB	6.5 GB	19.4 GB	2.3 GB	4-bit · legacy — 4-bit legacy quantization	Fits: 128K context · ~263 tok/s
2.5 GB	6.6 GB	19.4 GB	2.2 GB	3-bit large — 3-bit large quantization	Fits: 128K context · ~259 tok/s
2.6 GB	6.7 GB	19.5 GB	2.2 GB	4-bit · i-quant compact — Importance-weighted 4-bit, compact	Fits: 128K context · ~249 tok/s
2.7 GB	6.8 GB	19.6 GB	2.5 GB	4-bit · legacy+ — 4-bit legacy quantization with offset	Fits: 128K context · ~240 tok/s
2.7 GB	6.8 GB	19.6 GB	2.3 GB	4-bit small — 4-bit small quantization	Fits: 128K context · ~240 tok/s
2.7 GB	6.8 GB	19.6 GB	2.3 GB	4-bit · i-quant non-linear — Importance-weighted 4-bit, non-linear	Fits: 128K context · ~240 tok/s
2.9 GB	6.9 GB	19.8 GB	2.5 GB	4-bit medium — 4-bit medium quantization — most popular sweet spot	Fits: 128K context · ~228 tok/s
2.9 GB	7 GB	19.8 GB	2.6 GB	4-bit large — 4-bit large quantization	Fits: 128K context · ~224 tok/s
3.0 GB	7 GB	19.9 GB	2.7 GB	5-bit · legacy — 5-bit legacy quantization	Fits: 128K context · ~221 tok/s
3.2 GB	7.2 GB	20.1 GB	2.7 GB	5-bit small — 5-bit small quantization	Fits: 128K context · ~204 tok/s
3.3 GB	7.3 GB	20.2 GB	2.8 GB	5-bit medium — 5-bit medium quantization — good quality/size tradeoff	Fits: 128K context · ~199 tok/s
3.4 GB	7.4 GB	20.3 GB	3 GB	5-bit large — 5-bit large quantization	Fits: 128K context · ~196 tok/s
3.7 GB	7.8 GB	20.6 GB	3.2 GB	6-bit, very good — 6-bit quantization, very good quality	Fits: 128K context · ~176 tok/s
4.4 GB	8.4 GB	21.3 GB	4.1 GB	8-bit, near-lossless — 8-bit quantization, near-lossless	Fits: 128K context · ~149 tok/s
8.2 GB	12.3 GB	25.2 GB	7.7 GB	16-bit · bfloat — Brain floating point 16 — preferred for training	Fits: 64K context · ~80 tok/s

Selected Q4_K_M

4-bit medium quantization

4.8GBat 16K context

Weights: 2.3 GB
KV cache: 2.2 GB
Overhead: 0.3 GB

Fits RTX 4090 (reference) · 19.3 GB free · ~228 tok/s

≥50 tok/s needs ≥221 GB/s · RTX 5090 ~406, RTX 3090 Ti ~228

Which Hardware Can Run Phi 4 Mini Instruct?

Q4_K_M · 2.9 GB

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

By VRAM tier · typical GPUs and Macs at Q4_K_M

Typical hardwareQuantVRAMtok/sContext that fits

8 GB · RTX 4060Q4_K_M · 4.8 GB · ~62 tok/s · 32K4.8~6232K8 GB tier →

12 GB · RTX 3060 12GBQ4_K_M · 4.8 GB · ~82 tok/s · 64K4.8~8264K12 GB tier →

16 GB · RTX 5060 Ti 16GBQ4_K_M · 4.8 GB · ~102 tok/s · 64K4.8~10264K16 GB tier →

24 GB · RTX 4090referenceQ4_K_M · 4.8 GB · ~228 tok/s · 128K4.8~228128K24 GB tier →

Mac 32 GB · Mac Mini M4Q4_K_M · 4.8 GB · ~29 tok/s · 128K4.8~29128KMacs →

Mac 64 GB · Mac Studio M4 MaxQ4_K_M · 4.8 GB · ~133 tok/s · 128K4.8~133128KMacs →

How good is Phi 4 Mini 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

MMLU-Pro
TIGER-LabIndependent
52.8%
#68/146 open
Independent
SciCode
Epoch AI · Feb 2025Lab-reported
10.8%
#72/72 open
Lab-reported
CritPt
Epoch AI · Feb 2025Lab-reported
0.0%
#70/84 open
Lab-reported

All 3 Phi 4 Mini Instruct benchmarks

Alternatives to Phi 4 Mini Instruct

Phi 4 family · 7 models →

Similar models

6tok/s on RTX 4090

Model	Score	VRAM	tok/s	Why it is similar
Spark X2.6 4BXHToken	—	4.3 GB	~221	same size
NVIDIA Nemotron Labs Dory1.0 4B BF16NVIDIA	—	5.7 GB	~214	same size
Granite Vision 4.1 4BIBM	—	4 GB	~228	same size
Qwen3 4B Instruct 2507Alibaba	—	4.2 GB	~226	same size
MiniCPM V 4OpenBMB	—	3.1 GB	~236	same size
Qwen2.5 VL 3B InstructAlibaba	—	3.2 GB	~249	same size

Fine-tunes & variants(1)community builds of Phi 4 Mini Instruct

Phi 4 Mini Instruct

Specifications

Publisher: Microsoft
Family: Phi 4
Parameters: 3.8B
Architecture: Phi3ForCausalLM
Context Length: 131,072 tokens
Vocabulary Size: 200,064
Release Date: 2025-02-19
License: MIT

Resources

Frequently Asked Questions

How much VRAM does Phi 4 Mini Instruct need?

Phi 4 Mini Instruct requires 2.9 GB of VRAM at Q4_K_M, or 8.2 GB at BF16. Full 131K context adds up to 16.9 GB (19.8 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 3.8B × 4.8 bits ÷ 8 = 2.3 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 ≈ 17.5 GB (at full 131K context)

VRAM usage by quantization

Q4_K_M

2.9 GB

Q4_K_M + full context

19.8 GB

Learn more about VRAM estimation →

What's the best quantization for Phi 4 Mini Instruct?

For Phi 4 Mini Instruct, Q4_K_M (2.9 GB) offers the best balance of quality and VRAM usage. Q4_K_L (2.9 GB) provides better quality if you have the VRAM. The smallest option is IQ2_XXS at 1.6 GB.

VRAM requirement by quantization

IQ2_XXS

1.6 GB~53%

Q2_K

2.2 GB~75%

IQ4_XS

2.6 GB~87%

Q4_K_M ★

2.9 GB~89%

Q5_0

3.0 GB~90%

BF16

8.2 GB~100%

★ Recommended — best balance of quality and VRAM usage.

Learn more about quantization →

Can I run Phi 4 Mini Instruct on a Mac?

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

Can I run Phi 4 Mini Instruct locally?

Yes — Phi 4 Mini Instruct can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is Phi 4 Mini Instruct?

At Q4_K_M, Phi 4 Mini Instruct can reach ~1673 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~228 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 ÷ 2.87 × 0.65 = ~1812 tok/s

Estimated speed at Q4_K_M (2.9 GB)

NVIDIA B200

~1812 tok/s

NVIDIA GeForce RTX 4090

~228 tok/s

NVIDIA B300

~1812 tok/s

AMD Instinct MI350X

~1673 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 Phi 4 Mini Instruct?

At Q4_K_M, the download is about 2.30 GB. The full-precision BF16 version is 7.67 GB. The smallest option (IQ2_XXS) is 1.05 GB.

Which GPUs can run Phi 4 Mini Instruct?

52 consumer GPUs can run Phi 4 Mini 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 Phi 4 Mini Instruct?

163 devices with unified memory can run Phi 4 Mini Instruct at Q4_K_M (2.9 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.