Discofork
Repository brief

hacksider/Deep-Live-Cam

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T12:01:21.750Z
3mo ago

hacksider/Deep-Live-Cam

Deep-Live-Cam is an actively maintained Python project for real-time face swap and one-click video deepfake from a single image. It is very popular (85,887 stars, 12,497 forks) and recently updated, so forks may be active and differentiated. The repo includes a GUI-oriented app and platform-specific launchers for Windows and DirectML/CUDA setups.

GitHub
Loading tags...
Stars85,887
Forks12,497
Default branchmain
Last pushed2026-03-28T20:54:34Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if your goal is Colab or SageMaker execution and you want a notebook-first path. Stick with upstream if you need the full desktop GUI, local GPU workflows, or the latest upstream fixes.

Prefer upstream unless you specifically need a frozen 2024-era baseline or a private fork to build on. For active use, this fork is too stale and adds no visible value over upstream.

Choose this fork if Chinese localization and a modified, less restricted build matter more than staying current with upstream. Avoid it if you need the latest face-swap pipeline, GPU support, or maintenance parity with the main project.

Choose this fork if localization and a more guided UI matter more than staying current with upstream. Choose upstream if you want the latest fixes, broader maintenance, and maximum compatibility.

Choose this fork only if you want a clean, upstream-like base and do not need recent fixes or enhancements yet. If you want the current project state, use upstream instead.

Adopt only if you want a near-upstream snapshot from late 2025; otherwise upstream is the better choice because this fork is 51 commits behind and adds no visible features.

Prefer upstream unless you specifically need this older snapshot; the fork adds no evident features and is significantly behind on maintenance.

Prefer upstream unless you specifically need this exact older snapshot; this fork offers no visible advantages and is materially behind on maintenance.

Choose this fork only if you want its less restricted positioning or its custom Windows-oriented packaging and accept significant staleness. If you want current fixes, better compatibility, or the full upstream feature set, upstream is the safer choice.

Choose this fork only if the uncensored positioning is the point. For most adopters, upstream is the better default because it is actively maintained and keeps the safety, enhancement, and compatibility work this fork appears to drop.