Best local AI models for NVIDIA GT 1010
2 GB GDDR5. At a 4k context, 56 of the 233 models in our catalog with verified parameter counts fit fully, up to Allegro at 2.8B parameters.
Check your own machine against every model →The largest models that fit fully
The 30 largest of the 56 models that fit; every smaller model in the catalog fits too. Best quant means the highest quality compression whose weights and 4k context both sit inside the memory.
| Model | Parameters | Best quant that fits | Memory used at 4k |
|---|---|---|---|
| Allegro | 2.8B | Q4_K_M | 2 GB |
| Open-Sora Plan | 2.7B | Q4_K_M | 2 GB |
| LFM2 1.2B / 2.6B | 2.6B | Q4_K_M | 1.9 GB |
| Playground v2.5 | 2.6B | Q4_K_M | 1.9 GB |
| Stable Diffusion 3.5 Medium | 2.5B | Q4_K_M | 1.8 GB |
| Canary 1B / Qwen-2.5B | 2.5B | Q4_K_M | 1.8 GB |
| SeamlessM4T v2 | 2.3B | Q5_K_M | 2 GB |
| Parler-TTS | 2.2B | Q5_K_M | 1.9 GB |
| Kimi K3 DSpark | 2.2B | Q5_K_M | 2 GB |
| SmolVLM 256M / 500M / 2B | 2B | Q6_K | 2 GB |
| Stable Diffusion 3 Medium | 2B | Q6_K | 2 GB |
| Pyramid Flow | 2B | Q6_K | 2 GB |
| Wav2Vec2 / XLS-R | 2B | Q6_K | 2 GB |
| Moondream 2 | 1.9B | Q6_K | 1.9 GB |
| Qwen3 1.7B | 1.7B | Q6_K | 1.7 GB |
| SmolLM2 135M / 360M / 1.7B | 1.7B | Q6_K | 1.7 GB |
| StableLM 2 1.6B | 1.6B | Q8_0 | 2 GB |
| Sana 0.6B / 1.6B | 1.6B | Q8_0 | 2 GB |
| Zonos 0.1 | 1.6B | Q8_0 | 2 GB |
| Dia 1.6B | 1.6B | Q8_0 | 2 GB |
| Whisper Large v3 | 1.55B | Q8_0 | 2 GB |
| ControlNet / T2I-Adapter / IP-Adapter | 1.5B | Q8_0 | 1.9 GB |
| Hunyuan-DiT | 1.5B | Q8_0 | 1.9 GB |
| Stable Video Diffusion | 1.5B | Q8_0 | 1.9 GB |
| Whisper Large v2 / turbo | 1.5B | Q8_0 | 1.9 GB |
| AudioGen | 1.5B | Q8_0 | 1.9 GB |
| AudioLDM 2 | 1.5B | Q8_0 | 1.9 GB |
| Tango 2 | 1.4B | Q8_0 | 1.8 GB |
| TinyLlama 1.1B | 1.1B | Q8_0 | 1.4 GB |
| SantaCoder 1.1B | 1.1B | Q8_0 | 1.4 GB |
Close, but only with CPU offload
These need more than the card holds at their smallest practical quant, so part of the model runs from system memory (figures assume 32 GB of it). They work, several times slower.
| Model | Parameters | Memory at Q4_K_M | System RAM at 4k |
|---|---|---|---|
| SmolLM3 3B | 3B | 2.2 GB needed | 4.2 GB |
| Replit Code v1.5 3B | 3B | 2.2 GB needed | 4.2 GB |
| Kandinsky 3.1 | 3B | 2.2 GB needed | 4.2 GB |
| Voxtral Mini / Small | 3B | 2.2 GB needed | 4.2 GB |
| Orpheus TTS | 3B | 2.2 GB needed | 4.2 GB |
| Higgs Audio v2 | 3B | 2.2 GB needed | 4.2 GB |
| MusicGen small/medium/large | 3.3B | 2.4 GB needed | 4.4 GB |
| Stable Diffusion XL | 3.417B | 4.1 GB needed | 6.1 GB |
| SDXL Turbo | 3.5B | 2.6 GB needed | 4.6 GB |
| SDXL Lightning | 3.5B | 2.6 GB needed | 4.6 GB |
How to read this
The NVIDIA GT 1010 is an entry level graphics card equipped with 2 GB of GDDR5 video memory. This hardware memory limit determines which local AI models you can run directly on the graphics processing unit. To run a model entirely on this card the model files and runtime memory must fit within this 2 GB boundary.
The quantization column shows the best compression format for each model. Quantization reduces the precision of model weights to save space. For example a Q4_K_M quantization allows larger models like Allegro 2.8B or Open-Sora Plan 2.7B to fit into 2 GB of video memory. Smaller models like TinyLlama 1.1B can use higher precision Q8_0 quantization because they require only 1.4 GB of space.
When a model exceeds the 2 GB video memory limit you must use CPU offload. This process splits the model between your graphics card and your system RAM. If you have a system with 32 GB of system RAM you can run larger models by offloading the extra weight files. This method allows you to run models that would otherwise fail to load on your hardware.
Offloading comes with a performance cost. System RAM is much slower than GDDR5 video memory. While offloading allows you to run a 3.5B model like SDXL Turbo or SDXL Lightning it will generate outputs much slower than models that fit entirely on the graphics card. You will need 2.6 GB of video memory and 4.6 GB of system RAM for these specific models.
Memory calculations for text models assume a standard 4k context window. Generating longer responses or inputting large documents increases memory usage. If you exceed the context limit the system will run out of memory and crash. You must monitor your context size when running models close to the 2 GB limit.