LLMs 101
If you're in the AI space, you must already be aware of the fact that language models are basically giant webs of numbers (parameters) that compute some configuration of matrix multiplications (inference) to predict words or chunks of words (tokens) in sequence. This process is quite computational, and can tax some of the highest-end consumer-grade GPUs.
Generally, across models within a single fleet (think: the GPT-5.5 lineup), more parameters makes a model has, the smarter it behaves. This is because larger models perform less compression on the knowledge space, so they can retain more information. However, notice how I said "within a single fleet" — this is because with better training methods (developed over time), you can compress higher-quality knowledge into less parameters; and we see this happen across generations of models of the same size (27B models of today outperform 27B models of a year ago).
In order to run a model on a computer, you need to load all the model's weights into RAM* — the larger the model, the more RAM you'll need. Additionally, larger param count means more of those matrix multiplications, so inference is really driven by two factors: size is limited by the amount of RAM you have, and token speed is limited by how fast your GPU/CPU is.
* technically, you could load params on your disk, but the read/write times on disk are often so abysmally slow that we can rule this out as a viable option in most cases.
All other variables (context engineering, pruning, harness quality, etc.) we can think of as noise, since we're analyzing the base intelligence of these models, and these harnesses can often be applied to any model (with varying success).
So, we've recapped. From the above descriptions, we can draw two conjectures:
- Better training is bringing model sizes of comparative intelligence down.
- Consumer hardware is improving (more RAM/VRAM, faster throughput), bringing the maximum model size runnable on local hardware up.
From these conjectures, my theory to you (which I originally posited almost half a year ago) is that these two trends are graphs in the space of "parameter size" plotted against "time". And they're moving in opposite directions. Meaning they will intersect.
To be more pedantic, the "consumer hardware" graph is a family of graphs, all trending upward. There will always be a delta between what high-end PCs can do and what laptops and mobile phones can, but the weaker ones will simply lag behind chronologically from the high-end; meaning they too will eventually cross all the same thresholds.
And to be even more pedantic, technically the "model size" graph is a family of graphs too, all trending downward. For simpler tasks like line completion, the necessary amount of parameters required to do it well (with diminishing returns beyond that amount) has already been encapsulated by consumer hardware many months ago. And more complex tasks (like deep coding agents) have yet to intersect, but will soon. Right now is the pivotal moment where general chatbot-level intelligence can now be accomplished by 27B models, which is just about small enough to run on higher-end consumer GPUs, and will only become more comfortably nestled in that spot.
Here's a graph to visually explain what I'm getting at:

The Takeaway
The key point to note here is not when exactly these graphs will intersect (although that can also be predicted, see below for more), but that we basically know for certain that they will. That essentially means Cloud Inference is an ever-receding pocket of the AI market share, that will soon be dominated by local models running on people's PCs (and eventually phones).
For the interested: Can we actually predict when this will happen?
Yes, actually! Take any metric (for this exercise I chose LLMStats), and pick a score of that metric you wish to attain (I chose 50). Then choose a device (I chose iPhone). We will be predicting when an iPhone will be able to run a model that scores 50 on this metric.
First, let's plot the raw parameter counts of open source models that got a score near that target score, over time.
| Model | Released | Parameters | Leaderboard score |
|---|---|---|---|
| Kimi K2-Thinking-0905 | Sep. 2025 | 1000B | 45.7 |
| GLM-4.6 | Sep. 2025 | 357B | 38 |
| GLM-4.7 | Dec. 2025 | 358B | 44.2 |
| DeepSeek-V3.2-Speciale | Dec. 2025 | 685B | 42.7 |
| MiniMax M2.1 | Dec. 2025 | 230B | 41.3 |
| MiMo-V2-Flash | Dec. 2025 | 309B | 38.8 |
| Kimi K2.5 | Jan. 2026 | 1000B | 50.3 |
| Qwen3.5 397B | Feb. 2026 | 397B | 49.5 |
| Step-3.5-Flash | Feb. 2026 | 196B | 49.5 |
| GLM-5 | Feb. 2026 | 744B | 51.8 |
| MiniMax M2.5 | Feb. 2026 | 230B | 52.8 |
| Qwen3.5-122B-A10B | Feb. 2026 | 122B | 43.3 |
| Qwen3.5-27B | Feb. 2026 | 27B | 42.3 |
| DeepSeek-V4-Flash-Max | Apr. 2026 | 284B | 52.1 |
| Qwen3.6-27B | Apr. 2026 | 27.8B | 45.7 |
| Gemma 4 31B | Apr. 2026 | 30.7B | 45.2 |
| GLM-5.1 | Apr. 2026 | 754B | 54.9 |
| DeepSeek-V4-Pro-Max | Apr. 2026 | 1600B | 57.3 |
| Kimi K2.6 | Apr. 2026 | 1000B | 58.8 |
| Gemma 4 26B-A4B | Apr. 2026 | 25.2B | 36.6 |
| Month | Estimated parameters | Models that month |
|---|---|---|
| Sep. 2025 | 2099.9B | 2 |
| Dec. 2025 | 1301.6B | 4 |
| Jan. 2026 | 959.6B | 1 |
| Feb. 2026 | 283B | 6 |
| Apr. 2026 | 255.5B | 7 |
Using the scores near 50, we can make a prediction of how many parameters would be required to achieve a score of 50, in that time sample. Assuming incremental score changes require exponentially more effort, we use the following equation to calculate a "50-score Param Mean":
Alright, now let's do the counter-graph — let's plot the estimate for param size that can be run on an iPhone based on its specs:
For the phone-side estimate, we can use the recent iPhone RAM steps and a simple Q4 quantization density. A 4-bit model takes about 0.5 bytes per parameter; adding a rough 20% runtime overhead gives:
| Year | Base iPhone | Base RAM | Base estimated capacity | Highest-RAM iPhone | Highest RAM | Highest-RAM estimated capacity |
|---|---|---|---|---|---|---|
| 2022 | iPhone 14 / 14 Plus | 6GB | 10B | iPhone 14 Pro / Pro Max | 6GB | 10B |
| 2023 | iPhone 15 / 15 Plus | 6GB | 10B | iPhone 15 Pro / Pro Max | 8GB | 13.3B |
| 2024 | iPhone 16 lineup | 8GB | 13.3B | iPhone 16 Pro / Pro Max | 8GB | 13.3B |
| 2025 | iPhone 17 | 8GB | 13.3B | iPhone Air / 17 Pro / Pro Max | 12GB | 20B |
Putting it all together
Now we can fit both sides with exponential regressions. The first curve is the estimated parameter count required for an open model to score 50 on LLMStats. The second curve is the estimated number of Q4 parameters that can fit into the highest-RAM iPhone of each year. Where they intersect would be a rough estimate of when iPhones can support the RAM necessary to run a model that gets 50 on this benchmark.
The fitted lines cross around Nov 2026, at about 23.9B parameters.
| Month | Score-50 model size fit | Highest-RAM iPhone fit |
|---|---|---|
| Sep 2025 | 2540.1B | 18.7B |
| Oct 2025 | 1821B | 19.1B |
| Nov 2025 | 1305.5B | 19.4B |
| Dec 2025 | 935.9B | 19.7B |
| Jan 2026 | 670.9B | 20.1B |
| Feb 2026 | 481B | 20.4B |
| Mar 2026 | 344.8B | 20.8B |
| Apr 2026 | 247.2B | 21.2B |
| May 2026 | 177.2B | 21.5B |
| Jun 2026 | 127B | 21.9B |
| Jul 2026 | 91.1B | 22.3B |
| Aug 2026 | 65.3B | 22.7B |
| Sep 2026 | 46.8B | 23.1B |
| Oct 2026 | 33.6B | 23.5B |
| Nov 2026 | 24.1B | 23.9B |
| Dec 2026 | 17.2B | 24.3B |
| Jan 2027 | 12.4B | 24.7B |
| Feb 2027 | 8.9B | 25.2B |
| Mar 2027 | 6.4B | 25.6B |
With these assumptions, the curves intersect around November 2026, at roughly 24B parameters. In plainer terms: if the recent open-model compression trend and the recent high-end iPhone RAM trend both continue, then the first iPhone capable of holding a score-50 open model in memory would arrive at EOY 2026. (Of course, iPhones don't launch at small enough timesteps for this to be totally accurate, but it is potentially a conservative estimate on the next generation of iPhones.)
There's a ton of small details not gone over in this article, but to me, the fact that we can make these predictions is a strong sign that the AI landscape is about to shift dramatically. The kings of the industry are sitting on pretty wobbly thrones right now; especially as the frontier prioritizes peak intelligence over affordability, their domain will very soon cover things like research, academia, and perhaps as singular oracles within large companies — leaving the rest of the market for smaller open models to sweep in.
We're in the era of open-source small language models, and the best part about it is that a step forward in any domain actually brings us closer, not further, to this reality. And that gets me fired up.