Brief
Ollama 0.30 adds GGUF support through llama.cpp alongside its MLX engine
Ollama 0.30 is out, with the company saying it improves performance and adds GGUF model compatibility through llama.cpp. The evidence is a short announcement: it names the change but gives no benchmark figures, model list or hardware detail.
The release note describes GGUF compatibility arriving via llama.cpp, layered on top of the MLX engine Ollama already used on Apple silicon. The stated consequence is coverage: more models, on a wider range of hardware.
That is the useful detail for anyone whose model choice was previously limited by what the runtime would load. It is a support and compatibility change rather than a new model, and the performance claim is asserted without numbers or method, so treat it as a direction of travel rather than a measured gain.
Everything else a migration decision would need — which specific models are now reachable, and on what hardware — is not in this evidence.
Our reading
For people running local models, the runtime's model coverage is often the binding constraint, so a change framed as broader model support on broader hardware is more consequential than a version bump. The audience that should care is anyone who previously ruled out an Ollama setup because a model they wanted would not load. The performance half of the claim is the weaker half, since no measureme…
What to do or watch
Try loading a GGUF model that your setup previously could not run, and note what actually changed on your hardware; watch for method and numbers behind the performance claim, which this announcement does not supply.
Source details and supporting facts
Each line is stated by the page named above it.
Stated by ollama.com
- Ollama 0.30 is now available with improved performance and GGUF model compatibility through llama.cpp.
- This augments Ollama's MLX engine on Apple silicon, bringing support to more models on a wider range of hardware.
Sources
- Ollama blogText stored 17 September 2026
How this story was checked. Written from the 1 page listed above, stored 17 September 2026; claims checked against that stored text on 17 September 2026.
What that means
- 2 of 2 reported statements were confirmed against the page that carries them; the rest were removed rather than published.
- Figures in the text were required to appear in the stored source text: yes. Identifiers: yes.
- The check reads stored text only: no claim rests on a fresh look that did not happen.
- Where the reporting was silent, the text says so instead of filling the gap.