mrkeyoor.com_
Sat 17 Oct 22:50 UTC
AI Toolsevaluationupdated 17 Oct 2026

Deep-Live-Cam review

Deep-Live-Cam replaces faces in images, recorded video, or a live camera preview using a source portrait. It gives you a local face-swapping workflow, with OBS or similar capture software handling the documented streaming step.

+110stars / 7d
Verdict

Our Deep-Live-Cam run installed 93 packages into 1,888 MB and passed all 13 tests, which earns it a trial for supervised local face-swapping experiments. Rehearse the full camera-to-OBS session before using it live, because the lab result doesn't establish frame rate or preview reliability. I'd pass for unattended CLI work, and commercial users need separate permission for the supplied models.

We ran it

Lab card: what happened when we ran Deep-Live-CamScreenshot of Deep-Live-Cam (deeplivecam.net)
Install✓ · 42s93 packages · 1888 MB
Build✓ · 0s
Tests✓ · 1s13 passed · 0 failed of 13 (pytest)
Known vulns0(pip-audit)
Repo74 files~8,791 lines of source · 67.7 MB · 2 CI workflows · tests dir

Answers from our run

Does Deep-Live-Cam build from source?

Dependencies installed in 42 seconds (93 packages), and the build succeeded in 0s. We cloned commit 24c3223 into a clean Debian container with 3 CPUs and no project-specific setup.

Do Deep-Live-Cam's tests pass?

Yes. The project's own test command finished in 1 seconds and reported 13 passed, 0 failed (pytest).

Does Deep-Live-Cam have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use Deep-Live-Cam?

Commercial teams assuming the code license covers the weights: the README limits the supplied InsightFace models to non-commercial research, and InsightFace lists separate licensing contacts.

What are the alternatives to Deep-Live-Cam?

FaceFusion, DeepFaceLive. Our Deep-Live-Cam run installed 93 packages into 1,888 MB and passed all 13 tests, which earns it a trial for supervised local face-swapping experiments.

Setup2/542-second install, then models, FFmpeg, and hardware-specific setup
Docs3/5Useful platform steps, but an unmaintained CLI and split product labels
Community4/5October push and active PRs alongside unresolved live-mode reports
Maturity3/513 passing tests, with live reliability still requiring hardware checks

Discussed on

  1. hnReal time face swap and one-click video deepfake34 points
  2. hnReal time face swap and one-click video deepfake5 points

Who it’s for

Researchers trying local face swapping within the supplied models' non-commercial terms.
Technical hobbyists comfortable setting up FFmpeg, separate model files, and a hardware-specific runtime.
Creators who have permission to use their source faces and can rehearse a supervised OBS session.

Who it’s NOT for

Commercial teams assuming the code license covers the weights: the README limits the supplied InsightFace models to non-commercial research, and InsightFace lists separate licensing contacts.
Developers building unattended batch pipelines: the README explicitly labels the command-line arguments unmaintained.
Beginners expecting the three-click demo to describe manual setup: the README warns that source installation needs technical skills, FFmpeg, and separate ONNX models.
Performers who cannot rehearse live-mode recovery: open issue 1895 reports an unchanged camera preview despite successful-looking logs, and open PR 1951 describes repeated Live clicks causing a freeze.
Users who cannot obtain consent or label shared deepfakes: the project's use policy requires both for a real person's face.

Setup reality

Our sandbox installed commit 24c3223 in 42 seconds, adding 93 packages and using 1,888 MB on disk. The build succeeded in 0 seconds, and pytest passed all 13 tests in 1 second, with 0 failures. Pip-audit reported 0 known vulnerabilities. The run used Python 3.12 on Debian with 3 CPUs and 8 GB of RAM on October 8, 2026.

Manual use needs FFmpeg and the gfpgan-1024.onnx and inswapper_128_fp16.onnx files in the models directory. The documented local path needs no hosted API credential. The README warns that source setup requires technical skills, despite the short demo showing how to operate a working app.

The README supports Python 3.11 through 3.14 and recommends 3.14. Accelerator instructions differ for CUDA, CoreML, DirectML, and OpenVINO, with specific runtime pairings. The checkout has no Dockerfile, and the CLI is labeled unmaintained. Our measurements don't establish camera reliability, output quality, or frame rate.

Live mode gives you a preview to capture with OBS

Select a source portrait, choose your camera, and press Live: Deep-Live-Cam opens a face-swapped preview that the README tells you to capture with OBS or similar software. That last step matters if you're expecting it to appear directly in a video-call app. Recorded image and video processing is also available. Mouth Mask preserves your original mouth, while Face Mapping assigns different replacement faces to multiple people.

The local approach puts the processing stack on your machine. Our checkout occupied 67.7 MB, but installation expanded the environment to 1,888 MB. That's a reasonable commitment for a computer-vision workstation and a poor fit for someone expecting a lightweight webcam accessory. I'd consider it for consented experiments where you can inspect the result and stop the session when something looks wrong.

What happened when we ran it

Our sandbox installed Deep-Live-Cam commit 24c3223 in 42 seconds, adding 93 packages and occupying 1,888 MB. The build step succeeded with a recorded duration of 0 seconds. Our measurement setup on October 8, 2026, was an unprivileged Debian container using the ghcr.io/astral-sh/uv:python3.12-bookworm image, with 3 CPUs, 8 GB of RAM, and no secrets. These measurements establish that the repository's setup and check commands completed in that environment.

In our run, pytest passed all 13 tests in 1 second, with 0 failures, and pip-audit reported 0 known vulnerabilities. The checkout contained 74 files and about 8,791 source lines, with 2 CI workflow files, a tests directory, and no Dockerfile. The supplied measurements contain no camera, output-quality, or frame-rate result. A passing suite is useful evidence about the checked code paths, but it doesn't establish how a live performance will behave.

Manual setup still needs FFmpeg and separate face models

The README explicitly warns beginners away from manual installation. You need FFmpeg and a Python environment, plus gfpgan-1024.onnx and inswapper_128_fp16.onnx placed in the models directory. Windows instructions also call for Visual Studio runtimes. The documented local workflow doesn't ask for a hosted API credential. You still need to obtain the model assets before a successful package installation becomes a working media application.

Python 3.12 worked in our sandbox, while the current instructions recommend Python 3.14 and support 3.11 through 3.14. Acceleration adds platform choices: CUDA on Nvidia, CoreML on Apple hardware, DirectML on Windows, or OpenVINO on Intel. The OpenVINO section even supplies a version-pairing table. Follow the route for your actual hardware and preserve that environment. Our 42-second install supplies no evidence about GPU compatibility or acceleration speed.

The latest Ultimate release is a separate website download

The September 7 release, 2.7.5-Ultimate, advertises Face Fader, Favorites, a Library, and a Face Picker, then directs readers to the project's website. Its release notes say it is available exclusively there. Meanwhile, the repository README still heads the source project as 2.1.6. Those labels make it especially easy to mistake a prebuilt-product announcement for a description of the checkout.

Our 93-package installation belongs to commit 24c3223, so it cannot validate the separately distributed Ultimate build. Treat the website's convenience claims and exclusive features as a separate purchase decision. The three-click demonstration describes operating an already working application. It doesn't describe the source installation, and our successful package run doesn't show that every feature advertised for Ultimate exists in the open checkout.

The CLI is unmaintained, and live-mode failures have open reports

The source README explicitly labels its command-line arguments unmaintained. That's enough for me to pass if unattended batch processing is the main requirement. Live users have another concrete concern: issue 1895 reports a camera preview showing the original face despite apparently successful logs. It remained open after a September update. That report describes a user's experience, not a failure reproduced by our lab.

An open Windows live-mode pull request describes a deadlock when Live is clicked again during model loading and proposes disabling repeated activation. A proposed fix is not a shipped guarantee. Our 13 passing tests don't resolve that report. Before depending on this app for a show, try the actual camera and accelerator, change source portraits, and verify that stopping and restarting the preview works.

Model terms can stop a commercial deployment

The repository uses AGPL-3.0, while its credits warn that the supplied InsightFace models are for non-commercial research. InsightFace's model policy separately distinguishes code permission from model permission and provides licensing contacts. A business should settle permission for its chosen weights before building a client-facing workflow around them. Downloadable source alone doesn't answer whether those models fit the intended commercial use.

Pip-audit's 0 known vulnerabilities in our installed environment says nothing about model permissions. Nor does it certify the output as safe to share. The project's own policy asks users to obtain consent for a real person's face and label shared results as deepfakes. Those conditions are part of adopting this particular app. A performer who needs an undisclosed substitution should walk away before spending time on drivers.

October changes show maintenance alongside unresolved reports

GitHub recorded a push on October 10, 2026, with 97,091 stars and 45 open issues and PRs when checked. The open list split into 19 issues and 26 PRs. October contributions address live-preview shutdown and CoreML caching, while the unchanged-preview report remains open. This is ongoing maintenance with unresolved user problems. The September Ultimate release date alone would tell you much less about source health.

Our 13-test result makes Deep-Live-Cam worth trying for supervised experiments, with hardware rehearsal still required. For automation, I'd start by comparing FaceFusion's batch and job commands. DeepFaceLive is another Windows-focused live option, though its repository is archived. If you choose Deep-Live-Cam, make your first rehearsal a complete session through OBS, including shutdown, using the same camera and models you'll use in front of an audience.

Alternatives

ProjectWhat it isPick it when
FaceFusion gh↗A face-manipulation application with headless, batch, and queued-job commands.pick this instead when scripted processing and explicit job management matter more than Deep-Live-Cam's live-preview workflow.
DeepFaceLiveA Windows-focused live face-swap app supporting trained models and single-photo swaps.pick this instead when you need its trained-model live workflow and can accept maintaining an archived project.

Sources

  1. Deep-Live-Cam source README and platform instructions
  2. Deep-Live-Cam 2.7.5-Ultimate release
  3. Issue 1895: unchanged live preview despite successful-looking logs
  4. PR 1951: repeated Live-click deadlock and Windows launcher fixes
  5. InsightFace code and model licensing policy
  6. FaceFusion commands and job management
  7. DeepFaceLive README and archived repository
  8. Deep-Live-Cam repository activity and open queue

More ai tools reviews

BeefTV · OpenDots · reelmimic · easyread · motion-video-kit · livecanvas · the whole board →