Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/hacksider/Deep-Live-Cam/llms.txt

Use this file to discover all available pages before exploring further.

By default, Deep-Live-Cam runs inference on the CPU, which is reliable but slow for real-time use. Enabling a GPU execution provider offloads the ONNX model inference to your hardware accelerator, significantly improving frame rates. The provider you use depends on your GPU: NVIDIA cards use CUDA, Apple Silicon uses CoreML, and AMD/Intel GPUs on Windows can use DirectML or OpenVINO.
Deep-Live-Cam auto-detects the best available provider at startup in this order: cuda → rocm → coreml → dml → cpu. You can override this with the --execution-provider flag.

Choosing a provider

CUDA is the recommended provider for NVIDIA GPUs (Turing architecture or newer for best performance). It requires installing the CUDA Toolkit and cuDNN before updating the Python packages.1. Install system dependencies2. Install Python packagesWith your virtual environment active, install PyTorch with CUDA 12.8 support and the GPU-enabled ONNX Runtime:
pip install -U torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu128
pip uninstall onnxruntime onnxruntime-gpu
pip install onnxruntime-gpu==1.21.0
3. Run with CUDA
python run.py --execution-provider cuda
When CUDA is active, Deep-Live-Cam automatically selects the FP16 inswapper model (inswapper_128_fp16.onnx) when it is present, falling back to the FP32 variant (inswapper_128.onnx) on older GPUs. It also promotes libx264 to h264_nvenc for hardware-accelerated video encoding.

Performance notes

ProviderHardwareReal-time capable
CUDANVIDIA GTX 10xx+Yes
CoreML (Silicon)Apple M1–M4Yes
CoreML (Legacy)Intel MacLimited
DirectMLAMD/Intel (Windows)Varies
OpenVINOIntelVaries
CPUAnyNo
For the fastest inference on NVIDIA hardware, use CUDA with onnxruntime-gpu==1.21.0. When CUDA is active, Deep-Live-Cam automatically selects the FP16 inswapper model when available (reducing memory bandwidth) and promotes video encoding to h264_nvenc or hevc_nvenc, keeping encoding off the CPU.

Build docs developers (and LLMs) love