Instructions to use Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- MLX
How to use Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx with MLX:
# Make sure mlx-lm is installed # pip install --upgrade mlx-lm # Generate text with mlx-lm from mlx_lm import load, generate model, tokenizer = load("Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx") prompt = "Write a story about Einstein" messages = [{"role": "user", "content": prompt}] prompt = tokenizer.apply_chat_template( messages, add_generation_prompt=True ) text = generate(model, tokenizer, prompt=prompt, verbose=True) - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- LM Studio
- Pi
How to use Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx with Pi:
Start the MLX server
# Install MLX LM: uv tool install mlx-lm # Start a local OpenAI-compatible server: mlx_lm.server --model "Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx"
Configure the model in Pi
# Install Pi: npm install -g @mariozechner/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "mlx-lm": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Hermes Agent new
How to use Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx with Hermes Agent:
Start the MLX server
# Install MLX LM: uv tool install mlx-lm # Start a local OpenAI-compatible server: mlx_lm.server --model "Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx"
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx
Run Hermes
hermes
- MLX LM
How to use Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx with MLX LM:
Generate or start a chat session
# Install MLX LM uv tool install mlx-lm # Interactive chat REPL mlx_lm.chat --model "Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx"
Run an OpenAI-compatible server
# Install MLX LM uv tool install mlx-lm # Start the server mlx_lm.server --model "Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx" # Calling the OpenAI-compatible server with curl curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx", "messages": [ {"role": "user", "content": "Hello"} ] }'
Gemma-4-26B-A4B-IT — UD-Q4_K_XL (mlx-node)
4-bit affine quantization of google/gemma-4-26b-a4b-it for Apple Silicon, using the Unsloth Dynamic quantization strategy via mlx-node.
| Original (BF16) | UD-Q4_K_XL (this model) | |
|---|---|---|
| Size | ~49 GB | 17 GB |
| Format | SafeTensors | SafeTensors |
| Precision | BF16 uniform | 4-bit affine + mixed bits + BF16 |
| FFN group size | — | 64 |
| Biases | — | yes |
All Variants
| Repo | Bit budget | Size | Decode (tok/s) |
|---|---|---|---|
| Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q3_K_XL-mlx | 3-bit base | 14 GB | 60.6 |
| Brooooooklyn/Gemma-4-26B-A4B-IT-UD-MXFP4_K_XL-mlx | mxfp4 | 16 GB | 58.4 |
| Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx (this model) | 4-bit base | 17 GB | 58.6 |
| Brooooooklyn/Gemma-4-26B-A4B-IT-UD-NVFP4_K_XL-mlx | nvfp4 | 17 GB | 57.9 |
| Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q5_K_XL-mlx | 5-bit base | 20 GB | 50.3 |
| Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q6_K_XL-mlx | 6-bit base | 23 GB | 51.9 |
| Brooooooklyn/Gemma-4-26B-A4B-IT-UD-MXFP8_K_XL-mlx | mxfp8 | 26 GB | 49.8 |
| Brooooooklyn/Gemma-4-26B-A4B-IT-UD-Q8_K_XL-mlx | 8-bit base | 27 GB | 49.8 |
Benchmarked on Apple M3 Max 128GB via examples/lm.ts (best decode tok/s across turns 2–4, steady-state, capitals chat with reasoningEffort: 'low').
Note: No Q2 variant is published — Gemma-4-26B-A4B-IT has only ~4B active parameters per token, which is below the architectural redundancy needed for 2-bit quantization to remain coherent. Both unsloth and mixed_2_6 recipes produced gibberish at Q2 on this model.
Performance
Steady-state decode: 58.6 tok/s on Apple M3 Max 128GB (best of turns 2–4, examples/lm.ts capitals chat with reasoningEffort: 'low'). Decode is memory-bandwidth bound on Apple Silicon — fewer bytes per token directly translates to higher throughput. The MoE architecture activates only top-K of 128 experts per token (~4B active out of ~26B total), and the compiled C++ forward graph fuses the per-layer dispatch.
Per-Tensor Bit Assignments (N=4)
| Weight | Mode | Bits | Group | Rationale |
|---|---|---|---|---|
embed_tokens |
6-bit affine | 6 | 64 | Tied with lm_head (Gemma4 shares weights); affine-only loader |
self_attn.q_proj |
6-bit affine | 6 | 64 | AWQ-corrected via input_layernorm |
self_attn.k_proj |
6-bit affine | 6 | 64 | AWQ-corrected via input_layernorm |
self_attn.v_proj |
6-bit affine | 6 | 64 | AWQ-corrected via input_layernorm (only on full-attention layers) |
mlp.gate_proj |
4-bit affine | 4 | 64 | Shared dense MLP (top-level default) |
mlp.up_proj |
4-bit affine | 4 | 64 | Shared dense MLP (top-level default) |
mlp.down_proj |
5-bit affine | 5 | 64 | Shared dense MLP; "slightly more sensitive" (unsloth base+1) |
experts.switch_glu.gate_proj |
4-bit affine | 4 | 64 | MoE expert gate (per-expert across all 128); base bits (top-level default) |
experts.switch_glu.up_proj |
4-bit affine | 4 | 64 | MoE expert up (per-expert across all 128); base bits (top-level default) |
experts.switch_glu.down_proj |
5-bit affine | 5 | 64 | MoE expert down (per-expert across all 128 + routing); unsloth base+1 |
router.proj |
8-bit affine | 8 | 64 | MoE routing — low-bit noise breaks top-K expert selection |
self_attn.o_proj |
bf16 | — | — | NOT AWQ-correctable; kept full-precision |
Quantization Strategy
Built on Unsloth Dynamic 2.0 per-tensor KLD analysis. At --q-bits 4 the unsloth recipe assigns the base bits to MLP gate/up projections (the bulk of the parameter budget), base+1 to down_proj (slightly more sensitive), base+2 (snapped to a valid bit width) + AWQ pre-scaling to attention q/k/v projections, base+2 to embed_tokens, base+3 (capped/snapped) to the routing-critical paths, and keeps self_attn.o_proj as bf16 (AWQ-uncorrectable — its inputs come from the attention compute, not from a norm layer). The MoE router (router.proj) is forced to 8-bit affine to preserve top-K expert selection accuracy.
imatrix AWQ pre-scaling amplifies important weight channels and fuses inverse scales into preceding layer norms (zero inference overhead).
Architecture
| Parameter | Value |
|---|---|
| Total parameters | |
| Hidden size | 2,816 |
| Layers | 30 (sliding-window attention) |
| Attention heads | 16 (8 KV heads, GQA 2:1) |
| Head dimension | 256 |
| Experts | 128 per MoE layer |
| MoE intermediate size | 704 |
| Vocab size | 262,144 |
| Max context | 262,144 tokens |
| Vision | yes (Gemma4ForConditionalGeneration) |
Usage
import { loadSession } from '@mlx-node/lm';
const session = await loadSession('./Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx');
for await (const event of session.sendStream('Explain the MoE architecture in Gemma-4.', {
config: { maxNewTokens: 2048, temperature: 0.6, reasoningEffort: 'low' },
})) {
if (!event.done) process.stdout.write(event.text);
}
How It Was Made
mlx convert \
-i gemma-4-26b-a4b-it \
-o Gemma-4-26B-A4B-IT-UD-Q4_K_XL-mlx \
-q --q-bits 4 --q-recipe unsloth \
--imatrix-path imatrix_unsloth.gguf
Acknowledgments
- Unsloth — Quantization strategy based on their per-layer KLD benchmarks and Dynamic 2.0 methodology
- Google DeepMind — For the Gemma-4 model family
- Apple MLX — For the Metal-accelerated ML framework
License
Gemma Terms of Use (inherited from base model).
- Downloads last month
- 282
4-bit