Intel Arc for Stable Diffusion: ComfyUI + A1111 setup (2026)

You can run Stable Diffusion on Intel Arc through three backends: Intel's IPEX (PyTorch extension), OpenVINO, or Microsoft DirectML. Per Intel's Arc + SD guide, the IPEX path in ComfyUI is the current reference for maximum throughput. Community benchmarks put the Arc A770 16GB roughly on par with a MSI RTX 3060 12GB for SDXL 1024×1024, and the Arc B580 slightly behind — competitive but not a clear win.

The non-CUDA image-gen path

Every AUTOMATIC1111 tutorial written before 2024 assumed CUDA. Every "why is my Arc slow?" thread since then has resolved to some variant of "you're on the wrong backend, install IPEX." Stable Diffusion on Intel Arc is doable, actively supported in ComfyUI, and reasonably fast — but the install path is unfamiliar if your last SD box was NVIDIA.

The buyer this piece is for: you're considering Arc for local LLMs, image gen, or both, and want to know whether the image side is a first-class citizen or a "sort of works" checkbox. Short answer: it works well enough to make Arc a defensible buy on VRAM per dollar; not yet well enough to skip CUDA if you're day-jobbing SD workflows and the price delta is small.

Key takeaways

• Three backends run SD on Arc: IPEX (PyTorch fork), OpenVINO (Intel inference runtime), DirectML (Microsoft's Windows abstraction). IPEX is fastest today.
• On SDXL 1024×1024, community benchmarks put the Arc A770 16GB and MSI RTX 3060 12GB within ~10% of each other; Arc B580 is 15–20% slower.
• SD 1.5 512×512 favors CUDA — xformers memory-attention is more mature than the IPEX equivalent — but the gap is 10–15%, not "unusable."
• VRAM matters more for SDXL than raw speed. The A770 16GB fits SDXL + refiner + a control net comfortably; 12GB cards run tight.
• ComfyUI is the front-end community mindshare has landed on for Arc; A1111 works but needs more manual wrangling for the same throughput.
• Driver resets on Windows during long batches are the single most common failure mode reported on r/IntelArc. Update Arc drivers first.

What backends make Stable Diffusion run on Arc?

IPEX (PyTorch extension). Intel's fork of PyTorch that adds XPU (Intel GPU) device support. ComfyUI has first-class IPEX support today; A1111 requires a patched fork. This is where the fastest steady-state throughput lives.

OpenVINO. Intel's inference runtime. Excellent for shipping trained models with minimum overhead — you'll see it in Intel demos and product integrations. For interactive image gen with frequent model swaps, IPEX is more ergonomic.

DirectML. Microsoft's abstraction that lets any DirectX 12–compatible GPU run PyTorch/ONNX workloads. Universal, but slowest of the three on Arc. Useful only if you're stuck on Windows and can't get IPEX working.

Community consensus per r/IntelArc and r/StableDiffusion threads through 2026: use IPEX with ComfyUI unless you have a specific reason otherwise.

How to install ComfyUI + A1111 on Arc

ComfyUI on Windows. Install the current Intel Arc driver and the Intel oneAPI base toolkit. Clone ComfyUI, create a Python 3.11 venv, install PyTorch with the Intel XPU wheel (Intel publishes install commands under intel-extension-for-pytorch), then python main.py --directml NO — instead use python main.py with the XPU device auto-detected. Confirm the launch log shows "Using xpu" not "Using cpu."

ComfyUI on Linux. Kernel 6.5+, install intel-compute-runtime, activate the oneAPI environment (source /opt/intel/oneapi/setvars.sh), install ComfyUI in a venv with the IPEX wheels, run. The Linux path is the smoother of the two once you clear the runtime install.

A1111 on Arc. Use the openvino-fork or the ipex-branch community forks. Neither is upstream. Expect more manual environment fiddling than ComfyUI. On Windows, the openvino fork tends to work with the fewest surprises; on Linux, the IPEX branch.

Spec-delta table

Spec sources: TechPowerUp Arc B580 page, Intel Arc product pages, NVIDIA's public RTX 3060 datasheet. The A770 leans on more raw bandwidth than the B580, which shows up in SDXL numbers.

Benchmark table: it/s across the cards

Numbers pulled from community reports on r/IntelArc, r/StableDiffusion, and Intel's own developer blog through 2026-Q2. All values are approximate — image-gen throughput varies with sampler, step count, VAE, and driver build.

The pattern: SD 1.5 favors CUDA. SDXL narrows the gap, and at 1024×1024 the Arc A770 16GB matches or beats the MSI RTX 3060 12GB. That's not a coincidence — SDXL's memory-bandwidth-heavy attention layers reward the A770's 560 GB/s.

VRAM vs resolution

If your workflow is SDXL + refiner + ControlNet + a couple of LoRAs, 16GB is the difference between "works" and "keep restarting."

Common Arc gotchas for image gen

• Windows driver resets on long batches. Community threads on r/IntelArc trace this to power/thermal transients during idle-to-full-load swings. Update to the current WHQL Arc driver, and if it still trips, cap frequency 10% lower in Intel Graphics Command Center.
• xformers alternatives. xformers is CUDA-only. On Arc use SDPA (scaled dot-product attention) built into recent PyTorch. Set the flag --use-pytorch-cross-attention in ComfyUI.
• Precision flags. BF16 is fast on Arc. FP16 works. FP32 fallback happens silently on some ops and tanks throughput. Watch the log for "downgraded to fp32" messages.
• Model format. Some Hugging Face models ship in FP32 safetensors. Convert to FP16 or BF16 before use — smaller footprint, faster load, no visible quality loss for SD.
• VAE encoding. Some VAE variants have Intel-specific bugs. If images come out with strange color casts, swap to the sdxl-vae-fp16-fix variant.

Perf-per-dollar + perf-per-watt

At SDXL 1024×1024, roughly:

The MSI RTX 3060 12GB is still the perf-per-watt leader. Arc A770 is dollar-competitive with the 3060 and beats it on VRAM. Arc B580 is the cheapest way onto Intel's stack if you're okay with slightly less throughput. Pair either with a Ryzen 7 5800X and a fast NVMe like the Samsung 970 EVO Plus — model loading is a big sequential read, and slow storage stretches every context swap.

Verdict matrix

Use Intel Arc if: you want 16GB (A770) for SDXL headroom near the 3060's price; you already own or plan to own an Arc card for other workloads; you're on Linux and comfortable with the oneAPI toolchain.

Use an RTX 3060 12GB if: SD 1.5 is your main workflow (10–15% CUDA advantage); you rely on xformers-based nodes/extensions; you want the largest community-support base for troubleshooting; you also run CUDA image or video workflows (Stable Video Diffusion, AnimateDiff — CUDA maturity matters).

Worked example: SDXL portrait workflow

A common workflow: SDXL base + refiner, 1024×1024, one ControlNet (canny or depth), two style LoRAs, batch of 4 images per prompt. On an Arc A770 16GB running IPEX under ComfyUI: model load ~35 s, 25 steps at ~3 it/s = 8 s per image base, 3 s per image refiner, plus VAE and cross-attention overhead. Total ~50 s per 4-image batch after models are hot. Peak VRAM ~13.5 GB. Comfortable.

The same workflow on a MSI RTX 3060 12GB: 25 steps at ~2.8 it/s = similar per-image time, but peak VRAM sits at ~11.6 GB with the ControlNet + LoRA stack — tight enough that adding a second ControlNet triggers --medvram behavior and cuts throughput materially. This is where the A770's 16GB earns its price.

When NOT to buy Arc for image gen

Three situations where CUDA is still the right call:

1. Stable Video Diffusion / AnimateDiff / video-oriented pipelines. Community mindshare is CUDA-first and remains so through 2026. Arc support is coming but lags.
2. Training / fine-tuning. DreamBooth, LoRA training, textual inversion — CUDA path is well-trodden. IPEX path exists but has more edges.
3. Windows-only shops with no oneAPI comfort. DirectML on Arc is functional but slow, and IPEX on Windows needs the exact right driver + runtime + wheel combination. If your team can't spare a day for the setup, buy CUDA.

Real-world numbers for a 100-image session

If you're generating an evening's worth of prompts — say 100 SDXL 1024×1024 images with base+refiner at 25/25 steps — approximate wall-clock on each card:

The energy delta is real but small — pick on VRAM headroom and price, not power bill. If your rig runs overnight batches, keep a spinning-disk archive for finished images so your NVMe stays working set.

Storage and CPU pairing

A Samsung 970 EVO Plus 250GB is enough for OS + ComfyUI + a starter SDXL model set (~30 GB used). If you're rotating LoRAs, ControlNets, and IPAdapters, add a Crucial BX500 1TB SATA as bulk storage. CPU-side, a Ryzen 7 5800X handles the tokenizer, prompt scheduler, and VAE decode without becoming the bottleneck; anything less than 6 cores starts to show up in prompt-to-first-image latency.

Bottom line

Stable Diffusion on Intel Arc is real in 2026. It's not the CUDA experience — you'll spend an evening on the install path, learn the SDPA flags, and put up with occasional driver resets. In exchange you get 16GB VRAM at $329 (A770) or 12GB at $249 (B580) — pricing NVIDIA hasn't matched at those tiers. If image gen is your one workload and you want it "just work" today, buy the MSI RTX 3060 12GB. If SDXL is your headline workflow and VRAM headroom matters, the A770 16GB is a legitimate pick. Pair either with a Ryzen 7 5800X, a Samsung 970 EVO Plus 250GB system drive, and a Crucial BX500 1TB for model storage.

Related guides

• IPEX-LLM + Ollama on Intel Arc vs RTX 3060 12GB (2026)
• Intel Arc Pro B60 24GB vs RTX 3060 12GB: the VRAM math
• RTX 3060 12GB vs Intel Arc B580 for 1080p gaming: FPS per dollar (2026)

Citations and sources

• ComfyUI — GitHub repository and install docs
• Intel — Stable Diffusion with Intel Arc GPUs technical guide
• TechPowerUp — Intel Arc B580 GPU specs

This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.