Stable Diffusion Not Using AMD GPU (Slow, CPU Only)

Share
Workaround available Windows, Linux (AMD GPUs) Updated November 14, 2026Based on 4 user reportsHow we research

Quick answer

The original web UI targets NVIDIA CUDA. On AMD use the DirectML fork on Windows (--use-directml) or ROCm on Linux, otherwise generation runs on the CPU.

Most likely fix: Windows: DirectML fork

How to fix it

Try these in order — the most common fix is first.

  1. 1. Windows: DirectML fork

    1. Install the community DirectML fork of the web UI (lshqqytiger/stable-diffusion-webui-directml)
    2. Add --use-directml to COMMANDLINE_ARGS
    3. Update the AMD driver
    Did this fix it?
  2. 2. Linux: ROCm

    1. Check that your card is on AMD's ROCm support list
    2. Install the ROCm build of PyTorch in a fresh venv
    Did this fix it?
  3. 3. If it stays slow

    1. Use --medvram on 8 GB cards
    2. Expect the first image to be slower while shaders compile
    3. Consider a cloud GPU or an NVIDIA card
    Did this fix it?

Symptoms

'Torch is not able to use GPU', GPU usage near 0% while the CPU is busy, or images take minutes.

Why it happens

  • CUDA build of PyTorch installed on an AMD card
  • Stock A1111 does not support AMD on Windows
  • ROCm is Linux-oriented and supports only some cards
  • Shader compilation makes first generations slow

This guide also covers

  • stable diffusion amd gpu
  • stable diffusion amd slow
  • stable diffusion directml not using gpu

Still not working?

If Stable Diffusion keeps failing, you're not alone. See every Stable Diffusion problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us
Fixed it? Share this guide

The same problem in other apps

All slow, laggy or resource-hungry guides →

Other Stable Diffusion errors

All 10 Stable Diffusion errors and fixes →