Liquid AI · VRAM requirements
LFM3 1.7B VRAM requirements: can you run it locally?
- Parameters1.7B
- Context256K
- 4-bit file1.1 GB
- Checked2026-10-31
Quick answer
At the popular 4-bit Q4_K_M quantization, LFM3 1.7B's weights are 1.1 GB, and an 8K-token context adds about 0.10 GB of KV cache, so plan for roughly 1.2 GB plus your engine's overhead.[3][2] The smallest GPU in our list that holds that comfortably is a 8 GB card (RTX 4060). The 8-bit Q8_0 file is 1.8 GB and the 16-bit weights are 3.5 GB.[3]
LFM3 1.7B is Liquid AI's small hybrid model. Hugging Face lists 1,728,801,536 parameters, the repo was created on 2026-10-23, and the license is LFM Open License v1.0 (lfm1.0).[1] Its config.json describes the architecture as: hybrid: 24 layers = 13 convolution, 5 sliding-window attention (256 tokens), 6 full attention; the maximum context is 262,144 tokens.[2] Hugging Face counts about 32,933 downloads in the last 30 days (checked October 31, 2026).[1]
Memory needed at each quantization
Quantization stores each weight in fewer bits. Smaller files fit on smaller GPUs, at some cost in quality, and the cost grows below about 4 bits. Below is every GGUF build in the LiquidAI/LFM3-1.7B-GGUF repo, using the exact file sizes on Hugging Face (1 GB = 1,000,000,000 bytes; split files added together), largest first.[3]
| Quantization | Weights | |
|---|---|---|
BF16 (original) | 3.5 GB | |
Q8_0 | 1.8 GB | |
Q6_K | 1.4 GB | |
Q5_K_M | 1.3 GB | |
Q4_K_M | 1.1 GB | |
Q4_0 | 1.0 GB |
Which quant should you pick? Q4_K_M is the usual balance of size and quality. Use Q5_K_M or Q6_K if you have the memory, and Q8_0 if you want results close to the original. Treat 2-bit and 3-bit builds as a last resort.
Context length adds memory (the KV cache)
On top of the weights, the engine keeps a key/value cache for every token. From config.json (6 full-attention layers, 4 KV heads, head size 128),[2] an FP16 cache takes 2 × 6 × 4 × 128 × 2 bytes = 12,288 bytes per token. Only its 6 full-attention layers keep a cache that grows with the conversation, so the cache is small for the model's size.
| Context | KV cache (FP16, 6 full-attention layers) |
|---|---|
| 4,096 tokens | 50.3 MB |
| 8,192 tokens | 0.10 GB |
| 32,768 tokens | 0.40 GB |
| 262,144 tokens | 3.22 GB |
Some engines can store the cache in 8-bit to roughly halve it.
Which GPUs and Macs it fits on
Each cell compares the weights plus an 8K-token KV cache with the device's memory.[4][5][6][9]
| Device | BF16 (original)3.6 GB | Q8_01.9 GB | Q6_K1.5 GB | Q5_K_M1.4 GB | Q4_K_M1.2 GB |
|---|---|---|---|---|---|
| RTX 40608 GB | Fits | Fits | Fits | Fits | Fits |
| RTX 306012 GB | Fits | Fits | Fits | Fits | Fits |
| RTX 4060 Ti16 GB | Fits | Fits | Fits | Fits | Fits |
| RTX 309024 GB | Fits | Fits | Fits | Fits | Fits |
| Mac8 GB unified | Fits | Fits | Fits | Fits | Fits |
| Mac16 GB unified | Fits | Fits | Fits | Fits | Fits |
| Mac24 GB unified | Fits | Fits | Fits | Fits | Fits |
Column headers show weights + 8,192-token KV cache.
How to read it: "Fits" means weights + 8K cache use under 90% of memory. "Tight" means 90–100%: it may load, but the engine's own working memory or a longer context can push it over. "No" means it won't fit on the GPU alone. The 90% line is our own rule of thumb, not a vendor figure. On a Mac, macOS also needs some of the unified memory, so treat Mac rows as optimistic.
Our recommendations
These follow from the file sizes and the 90% rule.[3]
| Your GPU memory | Best quant that fits comfortably | Total |
|---|---|---|
| 8 GB | BF16 (original) (3.5 GB) | 3.6 GB with an 8K context |
| 12 GB | BF16 (original) (3.5 GB) | 3.6 GB with an 8K context |
| 16 GB | BF16 (original) (3.5 GB) | 3.6 GB with an 8K context |
| 24 GB | BF16 (original) (3.5 GB) | 3.6 GB with an 8K context |
How to run it
With llama.cpp, LM Studio or Ollama, download a GGUF file from the quant list above (for example the Q4_K_M build) from the LiquidAI/LFM3-1.7B-GGUF repo.[3] If the model is bigger than your VRAM, these tools can keep some layers in system RAM, but every token then waits on the slower memory, so expect much lower speed.
Cheapest GPU to rent for LFM3 1.7B
On-demand prices listed on Runpod's pricing page for cards that hold Q4_K_M with an 8K context (checked October 31, 2026; Community Cloud is cheaper but runs on shared hosts):[12]
| GPU (Runpod (on-demand, as listed)) | VRAM | Price |
|---|---|---|
| RTX A5000 (Community) | 24 GB | $0.16/hr |
| RTX 3090 (Community) | 24 GB | $0.22/hr |
| RTX A5000 | 24 GB | $0.27/hr |
| RTX A6000 (Community) | 48 GB | $0.33/hr |
| RTX 4090 (Community) | 24 GB | $0.34/hr |
| A40 (Community) | 48 GB | $0.35/hr |
Prices checked on 2026-10-31. They change often, so confirm on the provider's page. Each of these holds Q4_K_M plus an 8K context (1.2 GB) under our 90% rule. Rent on Runpod Referral link
Don't want to host it yourself? Compare AI APIs and Sandboxes.
See all GPU rental prices for Lambda, Vast.ai and multi-GPU setups, or compare it with other models in the VRAM table.[13]
Where to rent or buy
Run it on a cloud GPU
Vast.ai Affiliate partner Consumer GPU marketplace (4090/3090-class rentals)
Runpod Affiliate partner Pods and serverless GPUs (referral link)
E2E Networks Works with India GPU cloud (official site)
Run it via API instead
Novita AI Affiliate partner Open-model APIs and Sandbox for AI agents (no GPU rental)
Buy this GPU (or a Mac)
- B&H Photo Works with GPUs and computing gear (official site)
Which card? Read our best GPUs with 12 GB buying guide (the smallest size this model fits comfortably).
We may earn from links marked Affiliate partner. Disclosure.
Frequently asked questions
How much VRAM does LFM3 1.7B need at 4-bit?
About 1.2 GB for the Q4_K_M weights (1.1 GB) plus an 8K-token FP16 KV cache (0.10 GB), before engine overhead.[3][2]
What is the smallest GPU that runs LFM3 1.7B?
In our list, a 8 GB card (RTX 4060) holds Q4_K_M with an 8K context under our 90% rule. Smaller cards need a lower-bit quant from the table above.[3]
How much does a 256K context add?
At FP16 the KV cache for 262,144 tokens is about 3.2 GB.[2]
How we calculated
- Weights are the exact GGUF file sizes on Hugging Face, checked October 31, 2026.[3]
- KV cache is calculated from
config.json. We assume an FP16 cache.[2] - Device memory is from NVIDIA and Apple spec pages. We compare in decimal GB, so the results lean conservative.
- Rental prices are the listed on-demand Runpod rates, checked October 31, 2026.[12]
- Not included: engine working buffers, the OS and display. These vary by engine and settings, so leave headroom.
Sources
All sources checked on .
- Hugging Face, LiquidAI/LFM3-1.7B (parameter count, license, repo date, 30-day downloads; checked October 31, 2026). https://huggingface.co/LiquidAI/LFM3-1.7B
- Hugging Face, LiquidAI/LFM3-1.7B config.json (layers, KV heads, head size, context). https://huggingface.co/LiquidAI/LFM3-1.7B/blob/main/config.json
- Hugging Face, LiquidAI/LFM3-1.7B-GGUF file list (exact GGUF sizes; checked October 31, 2026). https://huggingface.co/LiquidAI/LFM3-1.7B-GGUF/tree/main
- NVIDIA, GeForce RTX 4060 family (8 GB / 16 GB). https://www.nvidia.com/en-us/geforce/graphics-cards/40-series/rtx-4060-4060ti/
- NVIDIA, GeForce RTX 3060 family (12 GB). https://www.nvidia.com/en-us/geforce/graphics-cards/30-series/rtx-3060-3060ti/
- NVIDIA, GeForce RTX 3090 specs (24 GB). https://www.nvidia.com/en-us/geforce/graphics-cards/30-series/rtx-3090-3090ti/
- NVIDIA, GeForce RTX 4090 specs (24 GB). https://www.nvidia.com/en-us/geforce/graphics-cards/40-series/rtx-4090/
- NVIDIA, GeForce RTX 5090 specs (32 GB). https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5090/
- Apple, MacBook Pro / MacBook Air tech specs (unified memory options). https://www.apple.com/macbook-pro/specs/
- NVIDIA, RTX 6000 Ada Generation (48 GB). https://www.nvidia.com/en-us/products/workstations/rtx-6000/
- NVIDIA, A100 (80 GB). https://www.nvidia.com/en-us/data-center/a100/
- Runpod, GPU pricing (checked October 31, 2026). https://www.runpod.io/pricing
- VRAMNeeded comparison table (sources listed per model). https://vramneeded.com/compare/