Can a Mac run Recursive Flint?

Yes, with 36 GB of unified memory or more. Recursive Flint has 39.8B parameters, 2.5B of them active for each token; here is the memory it needs at each precision and how fast every Apple chip runs it. Recursive’s own engine, Rec, needs an M4 Pro, M5 Pro or M5 Max with at least 48 GB of unified memory (maker’s requirement). The memory and speed figures on this page are estimates for a generic MLX build.

Updated

Memory at 4-bit24.2 GBweights 22.4 GB + context
Smallest Mac36 GB4-bit estimate · Rec needs 48 GB
Fastest Mac200–356tokens/s · M5 Ultra 96 GB (estimate)

Memory at each precision

VersionWeightsWith contextSmallest Mac
8-bit42.3 GB45.7 GB64 GB
6-bit32.3 GB34.9 GB48 GB
4-bit22.4 GB24.2 GB36 GB
3-bit lower quality17.4 GB18.9 GB32 GB
2-bit lower quality12.4 GB13.9 GB24 GB

On every Apple chip

The smallest memory size of each chip that runs Recursive Flint, the best version that fits it, and the writing speed you can expect.

ChipNeedsVersionTokens/s
M624 GB2-bit Runs well96–170
M5 Ultra96 GB8-bit Runs well200–356
M5 Max36 GB4-bit Runs well148–263
M5 Pro48 GB6-bit Runs well69–123
M524 GB2-bit Runs well86–153
M4 Max36 GB4-bit Runs well132–234
M4 Pro48 GB6-bit Runs well61–109
M424 GB2-bit Runs well68–120
M3 Ultra96 GB8-bit Runs well137–243
M3 Max36 GB4-bit Runs well96–171
M3 Pro36 GB4-bit Runs well48–86
M324 GB2-bit Runs well56–100
M2 Ultra64 GB8-bit Runs well133–237
M2 Max64 GB8-bit Runs well67–119
M2 Pro32 GB3-bit Runs well82–145
M224 GB2-bit Runs well56–100
M1 Ultra64 GB8-bit Runs well133–237
M1 Max64 GB8-bit Runs well67–119
M1 Pro32 GB3-bit Runs well82–145
M116 GB2-bit Only just38–68

Measured by others

Decode speeds for Recursive Flint that other people measured on their own Macs and posted publicly. These are third-party measurements, not ours, and not the estimates above.

MacRuntimePrecisionDecode tok/sSource
Mac Studio M3 UltraOllama (MLX engine)INT4 (QAT)107median of 7 prompts × 3 runs, reasoning onAlec Kloss @aleckloss
Mac Studio M3 Ultramlx-lm (PR #1998)INT4 (QAT)104.5median of 5 runs, 19-token prompt, 512 tokens outAlec Kloss @aleckloss
Mac Studio M3 Ultramlx-vlmBF1651.3at 1K contextPrince Canuma @Prince_Canuma
Mac Studio M3 Ultramlx-vlmBF1633at 128K contextPrince Canuma @Prince_Canuma
Mac mini M5 Pro 64 GBOllama4-bit115short promptPratik Gandhi @pratikg
Mac mini M5 Pro 64 GBOllama4-bit87at 20K contextafter reading a 20K-token codebase (prefill took 11 s)Pratik Gandhi @pratikg

Results vary by runtime and settings: its version, the precision, the context length, the prompt and reasoning on or off all change the speed.

How to run it

  1. In Terminal with Rec, the maker’s own engine:curl -fsSL https://raw.githubusercontent.com/recursive-oss/rec/main/install.sh | bashrec launch piNeeds: M4 Pro, M5 Pro or M5 Max · at least 48 GB unified memory · about 30 GB free disk · Node.js 22 and npm (for pi)Build: RecursiveSI/flint-int4 on Hugging Face. Other precisions sit next to it.

Step by step: download and run LLMs on a Mac · how to use MLX Harness · MLX vs Ollama vs llama.cpp

About Recursive Flint

Made byRecursive
Parameters39.8B total · 2.5B active (mixture of experts)
Context256K tokens
LicenceApache-2.0
Released2026-10
InputText
WeightsRecursiveSI/flint

Questions

How much memory does Recursive Flint need?
About 22.4 GB of weights at 4-bit, plus room for the context: 24.2 GB in all. On a Mac that means 36 GB of unified memory or more, since macOS lets the GPU use about 75% of it by default. Recursive’s own engine, Rec, needs an M4 Pro, M5 Pro or M5 Max with at least 48 GB of unified memory (maker’s requirement).
How fast is Recursive Flint on a Mac?
Writing speed depends on memory bandwidth. The fastest Mac for it here is an M5 Ultra with 96 GB at about 200–356 tokens a second (8-bit). The smallest Mac that runs it, with 36 GB, manages about 148–263 on an M5 Max.
Why does Recursive Flint run faster than its size suggests?
It is a mixture-of-experts model: it holds 39.8B parameters in memory but reads only 2.5B for each token, so it writes at the speed of a much smaller model.

Similar models

Every model · Every Mac · Compare your Mac

For your model card or README

Runs on a Mac: Recursive Flint Shows the smallest Mac that runs Recursive Flint well and links here.

[![Runs on a Mac](https://mlx.app/badge/run/flint.svg)](https://mlx.app/run/flint)

How it’s worked out

Memory: the model’s parameters at 8, 6, 4, 3 or 2 bits per weight plus MLX’s group scales (half a bit per weight), or its native format, with room for the context on top. By default macOS lets the GPU use about 75% of unified memory. Speed: memory bandwidth divided by the bytes read per token is the ceiling for one conversation; in llama.cpp’s public Apple Silicon benchmarks real runs reach about 45% to 80% of it, which is the range shown. These are estimates, not measurements: measure your own Mac on MLX Bench. Model figures from each official model card, chip figures from Apple’s Tech Specs. Checked 2026-10-19. Same data as mlx.app/compare.

Open data: mlx.app/data (JSON, CSV)

Can a Mac run Recursive Flint? RAM and speed