Best local AI models for AMD Pro 5600M

8 GB HBM2. At a 4k context, 123 of the 233 models in our catalog with verified parameter counts fit fully, up to Mochi 1 at 10B parameters.

Check your own machine against every model →

The largest models that fit fully

The 30 largest of the 123 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
Mochi 110BQ4_K_M7.3 GB
Gemma 2 9B9BQ4_K_M8 GB
Nemotron Nano 4B / 9B9BQ5_K_M7.7 GB
GLM-4 9B / GLM-4.5-Air9BQ5_K_M7.7 GB
Yi-Coder 1.5B / 9B9BQ5_K_M7.7 GB
GLM-4-9B-Chat / CodeGeeX49BQ5_K_M7.7 GB
GLM-4V-9B / GLM-4.1V-Thinking9BQ5_K_M7.7 GB
Chroma8.9BQ5_K_M7.6 GB
Llama 3.1 8B8BQ5_K_M7.4 GB
Granite 3.3 2B / 8B8BQ6_K7.9 GB
Ministral 3B / 8B8BQ6_K7.9 GB
InternLM 3 8B8BQ6_K7.9 GB
OpenCoder 1.5B / 8B8BQ6_K7.9 GB
Seed-Coder 8B8BQ6_K7.9 GB
MiniCPM-V 2.6 / MiniCPM-o 2.68BQ6_K7.9 GB
Idefics 3 8B8BQ6_K7.9 GB
Fuyu-8B8BQ6_K7.9 GB
Emu38BQ6_K7.9 GB
Stable Diffusion 3.5 Large / Turbo8BQ6_K7.9 GB
EXAONE 3.5 2.4B / 7.8B7.8BQ6_K7.7 GB
Mistral 7B7BQ6_K7.4 GB
Qwen2.5 0.5B / 1.5B / 3B / 7B7BQ6_K6.9 GB
OLMo 2 1B / 7B7BQ6_K6.9 GB
Falcon 3 1B / 3B / 7B7BQ6_K6.9 GB
Command R7B7BQ6_K6.9 GB
OpenHermes 2.57BQ6_K6.9 GB
Zephyr 7B Beta7BQ6_K6.9 GB
OpenChat 3.57BQ6_K6.9 GB
Starling LM 7B7BQ6_K6.9 GB
Codestral Mamba 7B7BQ6_K6.9 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
Open-Sora 2.011B8.1 GB needed10.1 GB
FLUX.1 dev12B14.4 GB needed16.4 GB
Gemma 3 12B12B8.8 GB needed10.8 GB
Gemma 4 12B12B8.8 GB needed10.8 GB
Mistral NeMo 12B12B8.8 GB needed10.8 GB
Pixtral 12B12B8.8 GB needed10.8 GB
FLUX.1 schnell12B8.8 GB needed10.8 GB
FLUX.1 Kontext dev12B8.8 GB needed10.8 GB
FLUX.1 Krea dev12B8.8 GB needed10.8 GB
Vicuna 13B13B9.5 GB needed11.5 GB

How to read this

The AMD Radeon Pro 5600M graphics card features 8 GB of high bandwidth HBM2 memory. This dedicated video memory determines the size of the artificial intelligence models you can run locally. To run a model entirely on the graphics processor, the model files and its working memory must fit within this 8 GB limit. If a model exceeds this capacity, it cannot run solely on the graphics card.

Quantization is a method that compresses model files to save space. The quant column shows the best compression level for each model on this hardware. For example, Mochi 1 is a 10B model that fits into 7.3 GB of memory using the Q4_K_M quant. Smaller models like Mistral 7B can run at the higher quality Q6_K quant while using 7.4 GB of memory. Higher quants preserve more original model accuracy but require more memory.

When a model is slightly too large for the 8 GB video memory, you can offload parts of it to your system RAM. This process requires a computer with sufficient system memory, such as 32 GB of system RAM. For instance, the Gemma 3 12B model requires 8.8 GB of video memory at the Q4_K_M quant and needs an additional 10.8 GB of system RAM to function. Offloading allows you to run larger models like Vicuna 13B, which needs 9.5 GB at Q4_K_M and 11.5 GB of system RAM.

Using CPU offload comes with a performance cost. Transferring data between the AMD Pro 5600M graphics card and the system RAM is much slower than keeping everything inside the HBM2 memory. Models like FLUX.1 dev require 14.4 GB at FP8 or optimized settings and need 16.4 GB of system RAM. These offloaded models will generate tokens or images at a slower rate than models that fit completely within the 8 GB video memory limit.

You must also consider the memory cost of context length. The memory figures listed are calculated using a standard 4k context window. If you increase the context window to process longer documents or chat histories, the model will require more memory. Running a model close to the 8 GB limit, such as Gemma 2 9B at Q4_K_M using 8 GB, leaves no room for context expansion and may cause out of memory errors.