Best local AI models for AMD R7 360

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.

ModelParametersBest quant that fitsMemory used at 4k
Allegro2.8BQ4_K_M2 GB
Open-Sora Plan2.7BQ4_K_M2 GB
LFM2 1.2B / 2.6B2.6BQ4_K_M1.9 GB
Playground v2.52.6BQ4_K_M1.9 GB
Stable Diffusion 3.5 Medium2.5BQ4_K_M1.8 GB
Canary 1B / Qwen-2.5B2.5BQ4_K_M1.8 GB
SeamlessM4T v22.3BQ5_K_M2 GB
Parler-TTS2.2BQ5_K_M1.9 GB
Kimi K3 DSpark2.2BQ5_K_M2 GB
SmolVLM 256M / 500M / 2B2BQ6_K2 GB
Stable Diffusion 3 Medium2BQ6_K2 GB
Pyramid Flow2BQ6_K2 GB
Wav2Vec2 / XLS-R2BQ6_K2 GB
Moondream 21.9BQ6_K1.9 GB
Qwen3 1.7B1.7BQ6_K1.7 GB
SmolLM2 135M / 360M / 1.7B1.7BQ6_K1.7 GB
StableLM 2 1.6B1.6BQ8_02 GB
Sana 0.6B / 1.6B1.6BQ8_02 GB
Zonos 0.11.6BQ8_02 GB
Dia 1.6B1.6BQ8_02 GB
Whisper Large v31.55BQ8_02 GB
ControlNet / T2I-Adapter / IP-Adapter1.5BQ8_01.9 GB
Hunyuan-DiT1.5BQ8_01.9 GB
Stable Video Diffusion1.5BQ8_01.9 GB
Whisper Large v2 / turbo1.5BQ8_01.9 GB
AudioGen1.5BQ8_01.9 GB
AudioLDM 21.5BQ8_01.9 GB
Tango 21.4BQ8_01.8 GB
TinyLlama 1.1B1.1BQ8_01.4 GB
SantaCoder 1.1B1.1BQ8_01.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.

ModelParametersMemory at Q4_K_MSystem RAM at 4k
SmolLM3 3B3B2.2 GB needed4.2 GB
Replit Code v1.5 3B3B2.2 GB needed4.2 GB
Kandinsky 3.13B2.2 GB needed4.2 GB
Voxtral Mini / Small3B2.2 GB needed4.2 GB
Orpheus TTS3B2.2 GB needed4.2 GB
Higgs Audio v23B2.2 GB needed4.2 GB
MusicGen small/medium/large3.3B2.4 GB needed4.4 GB
Stable Diffusion XL3.417B4.1 GB needed6.1 GB
SDXL Turbo3.5B2.6 GB needed4.6 GB
SDXL Lightning3.5B2.6 GB needed4.6 GB

How to read this

The AMD Radeon R7 360 graphics card features 2 GB of GDDR5 memory. This dedicated video memory determines the maximum size of the artificial intelligence models you can run directly on the hardware. Because 2 GB is a highly constrained memory limit for modern AI tasks, selecting the correct quantization level is critical to prevent out of memory errors.

Quantization is a compression method that reduces the size of model weights. The quant column indicates the optimal format for balancing model accuracy and memory consumption. For this graphics card, models like Allegro 2.8B and Open-Sora Plan 2.7B require a Q4_K_M quantization to fit within 2 GB of video memory. Smaller models such as SmolLM2 1.7B and Moondream 2 can use a higher quality Q6_K quantization while staying within 1.7 GB and 1.9 GB of memory respectively. The smallest models like TinyLlama 1.1B can run at Q8_0 quantization using only 1.4 GB of video memory.

When a model exceeds the 2 GB physical limit of your graphics card, you must use CPU offload. This technique splits the model layers between your graphics card and your system RAM. For example, running the 3B parameter SmolLM3 or Replit Code v1.5 3B requires 2.2 GB of video memory at Q4_K_M quantization plus an additional 4.2 GB of system RAM. Larger models like SDXL Turbo 3.5B require 2.6 GB of video memory at Q4_K_M and 4.6 GB of system RAM.

CPU offload allows you to run larger architectures but it comes with a severe performance cost. Transferring data between your system RAM and the graphics card over the system bus is much slower than using the dedicated GDDR5 memory directly. This transfer bottleneck significantly reduces the generation speed of models like Stable Diffusion XL which requires 4.1 GB of video memory at FP8 and 6.1 GB of system RAM.

You must also consider the memory cost of context length. Running a text model with a standard 4k context window requires additional video memory to store the active conversation history. If your model already consumes the entire 2 GB of video memory, any active context will spill over into your system RAM. This spillover slows down processing speeds during longer chat sessions.