Create GPT-OSS, Apertus (1.0, 1.1 Mini, 1.5 Omni), and
Gemma 4 models locally from their Hugging Face safetensors for
supported Ollama MLX preview builds.
Before you start
Use the latest signed preview DMG unless you
are reproducing an older release. GPT-OSS and Apertus 1.0 are available
in every listed MLX preview build. Gemma 4 and Apertus 1.5 Omni require
v0.31.2 or newer. Apertus 1.1 Mini requires v0.32.6 or newer.
Capability chips summarize the validated behavior of each recipe.
Support and answer quality can differ for larger or more heavily
quantized variants. Accept each model repository's license on Hugging
Face, install the hf CLI, and authenticate before
downloading gated weights.
Known Apertus Mini limitation: the currently published
and locally imported v1.1 Mini artifacts can produce nonsensical chat
responses and may disregard supplied conversation information. This affects
all 0.5B, 1.5B, and 4B BF16/NVFP4 variants. Do not use them for
conversational workloads while the cause is investigated.
1. Prepare the model tools
Run these commands from the directory where you keep local model snapshots and Modelfiles.
brew install hf
hf auth login
mkdir -p models
A Python installation of the CLI also works:
python3 -m pip install -U "huggingface_hub[cli]".
2. Import the model
Choose a locally imported model recipe or a published model family below.
Local recipes download a Hugging Face snapshot, create a Modelfile, then
import it into Ollama. Published models can be pulled directly.
GPT-OSS needs its full Harmony template for reasoning levels, tools,
and correct message formatting. Use the prepared portable Modelfile,
which retains that full template and points at the local HF snapshot.
Apertus 1.5 Omni adds native image and audio tokenizers to the Apertus
runtime. Tool calls require thinking to be disabled. Review and accept
its license and acceptable-use policy first.
Available in 0.5B, 1.5B, and 4B sizes, but not recommended for
conversational use: all current BF16 and NVFP4 variants can produce
nonsensical chat responses or disregard supplied conversation information.
Select a source below only for investigation or reproduction.
Reproduce the 4B BF16 import from its Hugging Face model card
for investigation. Use the equivalent 0.5B or 1.5B Instruct source
when reproducing those sizes.
Pull a currently published artifact from the Ollama Registry
for investigation only. These models require an MLX preview build with
ApertusForCausalLM support (v0.32.6 or newer) and do not
run in the regular Ollama app.
To pin a validated artifact instead of a moving convenience tag, use
a tag such as pd95/apertus-mini-mlx:4b-nvfp4-v0.32.15-r2.
See the full tag list.
Apertus 1.0 8B
Text
Apertus 1.0 is the text-generation path supported by the older
Apertus MLX previews. It uses the apertus renderer, not
the newer apertus1p5 renderer. Tool calling is not
advertised for this model path because it was never validated
reliably.
Pull a validated prebuilt artifact from the Ollama Registry.
Pull the recommended NVFP4 model
ollama pull pd95/apertus-mlx:8b
Pin the validated r2 artifact
ollama pull pd95/apertus-mlx:8b-nvfp4-v0.32.15-r2
3. Run and test the models
Start the selected preview server in one terminal:
ollama serve
Then use another terminal for text, image, or audio prompts:
ollama run gptoss-mlx:20b-mxfp4 "Reply with exactly OK"
ollama run apertus-mlx:8b-nvfp4 "Hello"
ollama run gemma4:e4b-mlx "Hello"
ollama run gemma4:e4b-mlx "Describe ./photo.webp"
ollama run gemma4:e4b-mlx "Summarize ./recording.mp3"
ollama run apertus-1.5:8b-mlx "Compare ./photo.png and ./recording.wav"
File paths are resolved locally and may be combined in one prompt in
the order the model should receive them. Keep audio clips at 30 seconds
or shorter for these preview builds.
Apertus 1.1 Mini BF16 and NVFP4 artifacts are retained for investigation only because of a known conversation-quality issue across all published sizes. They use the apertus1p1 renderer and parser.
The importer also accepts published MLX affine layouts at INT2, INT3, INT4, INT5, INT6, and INT8 directly. Use that workflow only when evaluating a specific upstream MLX checkpoint rather than the published Mini artifacts.
When importing a BF16 source, omit the -q ... option to retain BF16 precision; this uses considerably more disk and memory. Do not pass -q when directly importing a published affine checkpoint.
For GPT-OSS, mxfp4 is the validated compact default; do not substitute a minimal Modelfile for the full official Harmony template.
A 401 or 403 download error usually means the repository terms have not been accepted or hf auth login has not completed.
A missing shard or config.json means the local snapshot is incomplete; rerun hf download before calling create.
Published prebuilt test models remain available at ollama.com/pd95.