Can the Raspberry Pi 4 (4 GB) run Ideogram 4?

No, it doesn’t fit

No. Ideogram 4 needs about 6.1 GB even at NF4; the Raspberry Pi 4 (4 GB) has 2.8 GB usable.

Download Ideogram 4

Quantized files · GGUF for ComfyUI

Smaller GGUF versions for ComfyUI (with the ComfyUI-GGUF node). No sign-in needed; the model’s license still applies.

huggingface.co/leejet/ideogram-4-GGUF (opens in a new tab)

Original weights · Hugging Face

Full-precision files from Ideogram, for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.

huggingface.co/ideogram-ai/ideogram-4-fp8 (opens in a new tab)

Free Hugging Face account needed: accept the license on the model page and the download starts right away.

Official repo · GitHub

Reference code, inference scripts and docs from Ideogram. The weights themselves download from Hugging Face.

github.com/ideogram-oss/ideogram4 (opens in a new tab)

git clone https://github.com/ideogram-oss/ideogram4

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 85Excellent quality (A+) · 85 of 100: how capable the model is at NF4, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at NF4, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Won't run: How well it runs on the Raspberry Pi 4 (4 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	11.6 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.	0.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	0.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	0.0 / 15
Match score	11.6 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

It doesn’t fit, so only a reduced share of the quality points counts and fit, speed and memory use score zero.

Every precision on the Raspberry Pi 4 (4 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	15.4 GB	2.8 GB	—	—	Won't run	92Excellent quality (A+) · 92 of 100: how capable the model is at FP16, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	8.9 GB	2.8 GB	—	—	Won't run	90Excellent quality (A+) · 90 of 100: how capable the model is at FP8, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`Q4 GGUF`	6.3 GB	2.8 GB	—	—	Won't run	85Excellent quality (A+) · 85 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`NF4`	6.1 GB	2.8 GB	—	—	Won't run	85Excellent quality (A+) · 85 of 100: how capable the model is at NF4, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)

Hardware that can run it

92Excellent quality (A+) · 92 of 100: how capable the model is at FP16, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell FP16 · 18 s · Runs well
90Excellent quality (A+) · 90 of 100: how capable the model is at FP8, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 FP8 · 19 s · Runs well (tight fit)
85Excellent quality (A+) · 85 of 100: how capable the model is at NF4, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4090 NF4 · 28 s · Runs well (tight fit)
85Excellent quality (A+) · 85 of 100: how capable the model is at NF4, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX NF4 · 31 s · Runs well (tight fit)
85Excellent quality (A+) · 85 of 100: how capable the model is at NF4, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 9070 XT NF4 · 38 s · Runs well (encoder in RAM)
85Excellent quality (A+) · 85 of 100: how capable the model is at NF4, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5080 NF4 · 38 s · Runs well (encoder in RAM)

Models that do run on the Raspberry Pi 4 (4 GB)

28Basic quality (D) · 28 of 100: how capable the model is at FP16, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. SD Turbo FP16 · 21 s
42Fair quality (C) · 42 of 100: how capable the model is at FP16, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking. Realistic Vision V5.1 FP16 · 5.2 min
40Fair quality (C) · 40 of 100: how capable the model is at FP16, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking. DreamShaper 8 FP16 · 5.2 min
30Basic quality (D) · 30 of 100: how capable the model is at FP16, whatever it runs on. Match score 52/100 (quality, fit, speed and memory use) sets the ranking. LCM DreamShaper v7 FP16 · 65 s
50Fair quality (C) · 50 of 100: how capable the model is at FP16, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking. PixArt-Σ XL 1024 FP16 · 8.0 min

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.