Prepared based on the documentation for the open-source Aura Camera project, published by user lamooof. Facts and links were checked on September 24, 2026.
Disclosure: the creator of Aura Camera commissioned this material about their project. Links go to the public repository; there are no affiliate links.
Aura Camera is a free open-source extension that replaces your webcam background with an image, blurs it, or fills it with a solid color on Chrome pages. Frame processing happens locally, and the video call site keeps receiving a stream from your regular camera. You do not need to select a separate "virtual camera." The latest reviewed version is 0.4.2, test build. Aura Camera source code and instructions.
If you need to quickly clean up your video before a web meeting, this is a practical option without OBS or a system virtual camera driver. But there is an important limit: the extension works in the browser on HTTP/HTTPS pages, including Google Meet, not in separate desktop apps. Compatibility with a specific site and performance depend on the user's environment. Below: installation, settings, processing architecture, and a clear look at the limitations.
Contents
- What Aura Camera can do
- How it differs from Google Meet's built-in background effects and OBS
- What you need before installation
- How to install Aura Camera
- How to set the background before a call
- Segmentation algorithms and edge quality
- What happens to the video and data
- Limitations and common issues
- Frequently asked questions
- Conclusion
What Aura Camera can do
The extension has three main ways to change the background: image, blur and color. In image mode, there are eight built-in images; you can also upload your own in JPG, PNG, WebP, or AVIF format up to 20 MB. The background is selected in the extension interface, and you can preview the result in a separate preview window before joining a meeting. Project documentation.
By default, processing for regular sites and Google Meet is enabled, with a separate toggle for Meet. The default settings in version 0.4.2 are SelfieMulticlass + RGB, the "Light Studio" background, "Balanced" quality, and "For call" load mode. Users can change the algorithm, quality, and load level, and if performance slows down, they can switch to the fast profile "Accelerate · Selfie + Balanced." Saved settings are not reset during updates. README, version history.
What makes Aura Camera different is that it works inside the browser video pipeline. The page still sees the regular camera; the extension replaces the video frames the site receives with processed ones. For the person on the call, it looks like a changed background, but no new device appears in the system video device list. This setup means you do not need to configure a separate video source in the web service, but it also limits the extension to pages where its browser code runs. README, technical breakdown.
How it differs from Google Meet's built-in background effects and OBS
In Google Meet there are already built-in background effects: blur, static images, and custom images. Availability depends on the client, account, and organization settings; Meet can use on-device or cloud processing. If you only use Meet and the native effects are enough, check those first. Aura Camera makes sense if you want one set of custom extension settings for supported web pages or want open-source code. It is better not to run two background-removal tools at the same time: Aura Camera's author instructions explicitly recommend disabling the site’s own effect when using the extension. Google Meet help, Aura Camera README.
OBS with a virtual camera solves a different problem: it provides a separate system video device that can be selected in different apps. Aura Camera does not create such a device and does not process video in a separate desktop client. So the simple rule is: for a call in a supported Chrome tab, you can start with Aura Camera; for sending a composed scene to standalone apps, you need another solution. This is a comparison of architecture, not a promise that Aura Camera works with every calling platform.
| Situation | What to try |
|---|---|
| Call only in Google Meet; the built-in backgrounds are enough | Meet's built-in "Backgrounds and effects" |
| You need your own background, blur, or color on a Chrome page | Aura Camera, after checking the specific site first |
| You need a processed stream as a separate camera for a desktop app | A system virtual camera, for example in OBS |
| Access to source code and local processing logic matters | The Aura Camera repository and its data policy |
What you need before installation
To install, you need desktop Chrome 119 or newer, Python 3.10 or newer and internet access for the initial model preparation. Node.js, a separate pip installation, WASM build tools, and sudo privileges are not required. After preparation, the models and library files are stored in the extension folder. The installation process is manual: the project is distributed as source code that you prepare with a script and load through Chrome Developer Mode. Aura Camera instructions.
This is an important trade-off. A free open-source extension can be reviewed and built from the repository, but installation takes more steps than clicking a button in the extension store. Install code only from the project's official repository and verify the folder you give to Chrome.
How to install Aura Camera
- Open the Aura Camera repository and download the source files via Code → Download ZIP, then unzip the archive. If you use Git, you can run
git clone https://github.com/lamooof/aura-camera.git. - Open a terminal in the folder that contains
prepare.pyand theextensionsubfolder. Run the setup and verification:
python3 prepare.py
python3 prepare.py --checkOn Windows, if the command python3 is not available, use py -3. The setup downloads two Selfie models and the required libraries. If the connection drops, run the first command again: files that have already been downloaded are saved in the local cache.
- In Chrome, open
chrome://extensions, turn on Developer mode and click Load unpackedextension. Select theextensionsubfolder, not the project root. This matches Chrome’s general instructions for loading unpacked extensions as well. Chrome documentation. - Pin the Aura Camera icon. Open Camera and model check, click Enable preview and allow the browser to access the camera. Check the outline and background before the call. The Check all models button tests launching the downloaded models on synthetic frames; it does not replace checking your camera in a real meeting.
- Open or refresh the call page, and choose the standard camera in the site settings. If it was already working, turn it off and back on again. Disable the site’s built-in background replacement if you plan to use the Aura Camera effect.
All of these steps are covered in the project README. If you have a new version of the extension, finish the call first: the update instructions for 0.4.0 or 0.4.1 include a local update.py, a backup, and keeping already downloaded models. You do not need it for the initial install.
How to set up the background before a call
Start with the default settings and turn on the main switch. For the image, choose one of the built-in backgrounds or upload your own; for a more neutral result, try blur. A solid color is useful when you need a plain background with no details. Then open the preview and check not only the face, but also the hair, shoulders, hands, clothing edges, and objects near the person. Interface guide.
If the laptop is under noticeable load or the motion looks choppy, first switch to the “For calls”mode, quality “Economy” or the fast Selfie algorithm. Additional models and more detailed modes can increase the computing load. Do not rely on a single FPS number from someone else’s test: the repository explicitly says speed depends on the browser and the computer, and the published measurement of a separate filter did not measure a real video call. README, test report.
Mask anti-flicker smooths small changes in the object edge from frame to frame. With strong stabilization, the edge may lag behind motion and leave a semi-transparent trail; the developer recommends lowering it to about 25–30% or turning it off. This feature does not remove light flicker inside the image. It is a setting for balancing edge stability and response speed, not a universal quality improvement. README, CHANGELOG.
Segmentation algorithms and outline quality
The extension’s job is to separate the person from the surroundings, build a mask, and apply the selected background. In the basic setup, Selfie and SelfieMulticlassare available. The command python3 prepare.py --all adds RVM, MODNet and the experimental MiDaSdepth mode; it also increases the volume of downloaded dependencies. After that, you need to repeat python3 prepare.py --check and reload the existing extension in chrome://extensions. You do not need to install a second copy. project README.
The model names should not be read as a simple “worse to better” scale. Selfie is geared toward fast startup, SelfieMulticlass separates multiple image classes, RVM and MODNet offer different matting approaches, and MiDaS adds relative, not absolute, depth. In Aura Camera, depth is used as an experimental correction for uncertain areas of the mask; it does not turn an ordinary webcam into a distance sensor. The author’s technical analysis describes the limitations of each adapter and notes the lack of a comparative study on user RGB video clips. Aura Camera technical analysis.
Practical takeaway: compare settings in your own lighting and on your own device. Check whether strands of hair and hands remain visible, whether clothing close to the background color gets “lost,” and whether a trail appears when you turn your head. The built-in model test confirms that the models launch and return a valid result; the visual quality of a specific scene is evaluated through the preview and a trial call.
What happens to video and data
According to Aura Camera data processing policy, the source code does not record calls, collect analytics, or send frames to a separate extension server. Frames, masks, and the temporary anti-flicker history are processed in browser memory. Settings and one user-uploaded image are saved in chrome.storage.local. During the initial setup, the script downloads models and libraries from external sources; these are network requests for files, not an upload of camera video.
At the same time the video call site receives the final video and operates under its own transmission and recording rules. Local processing in Aura Camera does not make the call itself local. In addition, the extension requests broad permissions for HTTP/HTTPS pages, and its code interacts with the page context. The project policy explicitly warns that this is not a security boundary against a malicious site, which may obtain the source video by other means. Therefore, the phrase “background hidden” should be understood as a visual effect in the standard video stream, not as a guarantee of privacy for the surrounding environment. Aura Camera policy, extension manifest.
The project source code is open under the MIT License; third-party components retain their own licenses. This gives you the ability to review and modify the original Aura Camera code within the license terms. Before distributing your own build, check the LICENSE and third-party notices.
Limitations and common issues
Version 0.4.2 is labeled as a test release. The published project report says 227 automated checks passed, including logic, interface, and browser video pipeline tests, but it also clearly notes that no new real calls were run in the user’s Chrome during that run, and the neural network models in browser tests were replaced with controlled mocks. The test count should not be turned into a promise of error-free performance on every site. Aura Camera report.
| Issue | What to check |
|---|---|
| The extension says the models are not prepared | Repeat python3 prepare.py and python3 prepare.py --check, then reload the extension. |
| The normal background stayed in the call | Check the main toggle, whether the regular site or Google Meet is allowed, refresh the tab, and restart the camera on the site. |
| Preview will not open | Check camera permission in Chrome and close the app that has taken over the device. |
| Video slows down | Turn on “For Call,” “Economy,” or Selfie; turn off the second background effect on the site. |
| The outline leaves a trail | Reduce stabilization or turn off anti-flicker. |
| Diagnostics needed | Save the report from the “Outline, depth, and diagnostics” section and review it before publishing. |
These steps follow the troubleshooting guide. If the problem occurs on only one site, it may be a compatibility limitation of that specific page; having permission for HTTP/HTTPS does not mean all sites handle the camera the same way.
Frequently asked questions
Is Aura Camera really free?
Yes. The repository is published openly, and the original code, documentation, backgrounds, and icons are distributed under the MIT License. Third-party dependencies have their own terms. Download the project from the official repository and review its license files.
Do I need to choose “Aura Camera” instead of the webcam in Google Meet?
No. In Meet settings, choose the regular physical camera. Aura Camera changes video frames inside the browser; it does not create a separate device with that name. If the page was already open before the extension was turned on, refresh it and restart the camera. Project guide.
Does the extension work in desktop Zoom or Teams?
The extension is designed for HTTP/HTTPS pages in Chrome, not for standalone apps. Support for a specific web version of a service should be checked in practice; the official Aura Camera documentation does not promise compatibility with every site. README.
Is internet required during every call for background processing?
The models and compute libraries are prepared in advance and then read locally. Internet is needed for the initial download of dependencies, while the video meeting service itself normally needs internet for the call. These are separate network processes. README, data policy.
Can a replaced background be considered privacy protection?
No. It changes the visible final stream in the normal scenario, but the project policy explicitly excludes using the extension as protection against a malicious page. Even with the effect working correctly, the call site receives the resulting video, and participants may record the meeting. Aura Camera policy.
Conclusion
Aura Camera is a fit for users who want to replace or blur a webcam background for free directly in Chrome, review open-source code, and fine-tune the result before a web call. Start with the two basic models and the preview, then check the effect on the site you need. For desktop apps, you need a separate solution with a virtual camera; for use in a single Google Meet, you can first evaluate its built-in background effects. Download the source code and read the Aura Camera guide.