llmrun
tiny-randomGPT-OSSGptOssForCausalLM

GPT OSS BF16 — Hardware Requirements & GPU Compatibility

ChatFunctions

GPT OSS BF16 is a 7M-parameter open language model from tiny-random in the GPT-OSS family. It supports a context window of up to 131,072 tokens. At Q4_K_M it needs about 0.30 GB of VRAM — see which GPUs and Macs can run it below.

7M params · dense131K context32.1K downloads1 likes
Based on GPT OSS 120B
S

Runs great on a 24 GB GPU

Runs from8 GB Q4_K_M · 128KBest on24 GB Q4_K_M · ~2184 tok/s · 128KMacs from8 GB Q4_K_M · ~239 tok/s

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run GPT OSS BF16

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

vLLM
one command · needs vLLM installed
$vllm serve tiny-random/gpt-oss-bf16 --max-model-len 16384

vLLM repo with its own quantisation

Download: Weights on Hugging Face

install, OS, other quants

Ways to runOther ways

each opens step-by-step

Run in cloud

Runs on RTX 3060 12GB (11 GB headroom) · Q4_K_M

Generation speed
~780 tok/s
generation speed
Cost per 1M output tokens
$0.021
per 1M output tokens

How Much VRAM Does GPT OSS BF16 Need?

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

QuantizationVRAM+32KOn RTX 4090 (reference)
0.3 GB0.3 GB2-bit · K-quant — 2-bit quantization with K-quant improvementsFits: 128K context · ~2184 tok/s
0.3 GB0.3 GB3-bit medium — 3-bit medium quantizationFits: 128K context · ~2184 tok/s
0.3 GB0.3 GB4-bit medium — 4-bit medium quantization — most popular sweet spotFits: 128K context · ~2184 tok/s
0.3 GB0.3 GB5-bit medium — 5-bit medium quantization — good quality/size tradeoffFits: 128K context · ~2114 tok/s
0.3 GB0.3 GB6-bit, very good — 6-bit quantization, very good qualityFits: 128K context · ~2114 tok/s
0.3 GB0.3 GB8-bit, near-lossless — 8-bit quantization, near-losslessFits: 128K context · ~2114 tok/s
0.3 GB0.3 GB16-bit · bfloat — Brain floating point 16 — preferred for trainingFits: 128K context · ~2114 tok/s
est.calculated, no published file yet

Selected Q4_K_M

4-bit medium quantization

0.3GBat 16K context

Weights
0.1 GB
KV cache
0.0 GB
Overhead
0.3 GB

Fits RTX 4090 (reference) · 23.7 GB free · ~2184 tok/s

≥50 tok/s needs ≥23 GB/s · RTX 5090 ~3883, RTX 3090 Ti ~2184

Which Hardware Can Run GPT OSS BF16?

Q4_K_M · 0.3 GB

GPT OSS BF16 (Q4_K_M) requires 0.3 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 1+ GB is recommended. 52 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti. 163 devices with unified memory can run GPT OSS BF16, 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 · 0.3 GB · ~589 tok/s · 128K8 GB tier →
12 GB · RTX 3060 12GBQ4_K_M · 0.3 GB · ~780 tok/s · 128K12 GB tier →
16 GB · RTX 5060 Ti 16GBQ4_K_M · 0.3 GB · ~971 tok/s · 128K16 GB tier →
24 GB · RTX 4090referenceQ4_K_M · 0.3 GB · ~2184 tok/s · 128K24 GB tier →
Mac 32 GB · Mac Mini M4Q4_K_M · 0.3 GB · ~280 tok/s · 128KMacs →
Mac 64 GB · Mac Studio M4 MaxQ4_K_M · 0.3 GB · ~1274 tok/s · 128KMacs →

Alternatives to GPT OSS BF16

GPT-OSS family · 14 models →

Specifications

Publisher
tiny-random
Family
GPT-OSS
Parameters
7M
Architecture
GptOssForCausalLM
Context Length
131,072 tokens
Vocabulary Size
201,088
Release Date
2025-08-06

Frequently Asked Questions

How much VRAM does GPT OSS BF16 need?

GPT OSS BF16 requires 0.3 GB of VRAM at Q4_K_M, or 0.3 GB at BF16.

VRAM = Weights + KV Cache + Overhead

Weights = 7M × 4.8 bits ÷ 8 = 0 GB

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

VRAM usage by quantization

0.3 GB
0.3 GB

Learn more about VRAM estimation →

What's the best quantization for GPT OSS BF16?

For GPT OSS BF16, Q4_K_M (0.3 GB) offers the best balance of quality and VRAM usage. Q5_K_M (0.3 GB) provides better quality if you have the VRAM. The smallest option is Q2_K at 0.3 GB.

VRAM requirement by quantization

Q2_K
0.3 GB
Q4_K_M ★
0.3 GB
Q5_K_M
0.3 GB
Q6_K
0.3 GB
Q8_0
0.3 GB
BF16
0.3 GB

★ Recommended — best balance of quality and VRAM usage.

Learn more about quantization →

Can I run GPT OSS BF16 on a Mac?

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

Can I run GPT OSS BF16 locally?

Yes — GPT OSS BF16 can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is GPT OSS BF16?

At Q4_K_M, GPT OSS BF16 can reach ~16000 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~2184 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 ÷ 0.3 × 0.65 = ~17333 tok/s

Estimated speed at Q4_K_M (0.3 GB)

~17333 tok/s
~2184 tok/s
~17333 tok/s
~16000 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 GPT OSS BF16?

At Q4_K_M, the download is about 0.01 GB. The full-precision BF16 version is 0.01 GB. The smallest option (Q2_K) is 0.01 GB.

Which GPUs can run GPT OSS BF16?

52 consumer GPUs can run GPT OSS BF16 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 GPT OSS BF16?

163 devices with unified memory can run GPT OSS BF16 at Q4_K_M (0.3 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.