Visual Studio Code Extension - Vibrancy ContinuedEnable Acrylic/Glass effect in VS Code.
Links: GitHub | Visual Studio Code Marketplace | Open VSX Registry | issues Maintenance of this project is made possible by all the contributors and sponsors. If you'd like to sponsor this project and have your avatar or company logo appear below, click here. Any support is greatly appreciated 💖 ⚠️ "Your VSCode installation appears to be corrupt"This extension works by editing VS Code's checksum-verified HTML files, which means that a warning prompt will appear after installing and enabling Vibrancy Continued. This warning is safe to disregard, and all changes can be reverted. Click on the cogwheel and select Don't Show Again to hide it.
If you don't have the option to hide the alert, or to fix an Supported Operating Systems✔ macOS (Intel & Apple Silicon) ✔ Windows 10/11 (x64 & ARM64) ✔ Linux (transparency only, blur requires a compositor such as KWin, Hyprland, or Picom) Supported code editors✔ Visual Studio Code (v1.86 and newer) ✔ VSCodium ✔ Code - OSS ✔ Cursor ✔ Antigravity ✔ Devin Some editors may present a persistent warning warning about the installation being corrupted, use this extension to fix it: Fix VSCode Checksums Next. Getting Started
Each time VS Code is updated, please re-enable Vibrancy using the same steps. If you're experiencing issues, please check the FAQs. 🪟 Windows 10/11 notesVibrancy works out of the box on Windows — no extra setup is required. By default the window is borderless and opaque, so Windows Aero Snap, maximize, and resize all keep working. Borderless look vs. window snapping (Windows 10)On Windows there's one unavoidable trade-off, because a transparent window on Windows is a "layered" window that the OS excludes from Aero Snap and maximize:
Windows 11 materials: Acrylic vs MicaOn Windows 11 you can choose the backdrop material via
Legacy / troubleshooting: window can't be resized, or text looks distortedSome VSCode/Electron versions (and certain GPUs) had a hardware-acceleration bug where enabling Vibrancy made windows non-resizable/snappable/maximizable, or produced distorted, blurry text. If you don't experience this, you can ignore this section. If you do, apply the following mitigation:
For more information, see issues #140 and #122. OptionsType (
|
| Value | Frame | Window | Notes |
|---|---|---|---|
auto |
platform default | platform default | Recommended. macOS & Linux → borderless + transparent (on macOS this fixes the file-browser hover flash, #207); Windows → borderless + opaque on current VSCode (Aero Snap works; thin border on Win10), borderless + transparent on older VSCode (no snap). |
framed |
OS title bar/frame | opaque | Most compatible. Use if a borderless window misbehaves for you. |
frameless |
borderless | opaque | Keeps Windows Aero Snap / maximize / resize, at the cost of a thin window border on Windows 10 (Windows 11 has none). On macOS an opaque window can leave "ghost" artifacts in the file tree on some layouts, so prefer auto / frameless-transparent there. |
frameless-transparent |
borderless | transparent | The macOS & Linux default. Fully borderless, and on macOS fixes the file-browser hover flash (#207). On Windows, Aero Snap / maximize won't work (see the Windows note below). Also required for the transparent vibrancy type. |
The window's transparency is not the same as the vibrancy effect: vibrancy shows fine on an opaque window too (macOS via the native effect view, Windows via the DWM material / accent on the window). On Windows we use an opaque window so Aero Snap keeps working (a transparent window there is a layered window, which the OS excludes from snapping). On macOS we use a transparent window because an opaque one leaves stale "ghost" pixels in the file tree on some layouts — and its power cost is negligible (the GPU difference is a matter of utilization %, not actual battery draw).
Deprecated settings:
vscode_vibrancy.forceFramelessWindowandvscode_vibrancy.disableFramelessWindoware replaced bywindowMode. If still set (andwindowModeis left atauto) they are migrated automatically:disableFramelessWindow→framed, andforceFramelessWindow→ the frameless mode appropriate for your platform —frameless-transparenton macOS and Linux,frameless(opaque) on Windows and with Windows 11 Mica/Acrylic materials. You don't need to do anything, but you can switch towindowModedirectly to silence the deprecation warning.
Disable Theme Fixes (vscode_vibrancy.disableThemeFixes)
Disable fixes to Default Dark and Default Light themes for non-VSCode editors like Cursor.
Disable Color Customizations (vscode_vibrancy.disableColorCustomizations)
Prevent Vibrancy from modifying workbench.colorCustomizations which is used to make some elements like the terminal vibrant. Enable this if you want to manage color customizations yourself, or if you use a custom CSS theme that handles its own background colors and transparency. When enabled mid-session, any previously written vibrancy colors will be restored to their original values.
boolean, default is false
Refresh interval (vscode_vibrancy.refreshInterval)
Refresh interval (in milliseconds) for making the background transparent after window resizing. Lower values make the update less visible at the cost of increased CPU utilization. Ignored when using "Prevent Flash" method.
value: 1 ~ 1000, default is 10
Automatic theme switching (vscode_vibrancy.enableAutoTheme)
Enable automatic dark/light mode switching based on OS mode. Requires window.autoDetectColorScheme VSCode setting to also be enabled.
boolean, default is false
Preferred dark/light theme (vscode_vibrancy.preferredDarkTheme / vscode_vibrancy.preferredLightTheme)
Select which themes to use for light and dark modes, they will be used instead of the main Vibrancy Continued theme selected.
The previous misspelled keys
vscode_vibrancy.preferedDarkTheme/vscode_vibrancy.preferedLightThemeare deprecated but still honored — if you have them set, your value is used automatically. Move it to the corrected key to silence the deprecation warning.
theme (vscode_vibrancy.theme)
Select Vibrancy theme:
- Default Dark
- Dark (Only Subbar)
- Default Light
- Light (Only Subbar)
- Noir et blanc
- Tokyo Night Storm
- Tokyo Night Storm (Outer)
- Catppuccin Mocha
- Solarized Dark+
- GitHub Dark Default
| Theme | Screenshot |
|---|---|
| Default Dark | ![]() |
| Dark (Only Subbar) | ![]() |
| Noir et blanc | ![]() |
| Tokyo Night Storm | ![]() |
| Tokyo Night Storm (Only Subbar) | ![]() |
| Solarized Dark+ (with theme: Solarized) | ![]() |
| Catppuccin Mocha | ![]() |
| GitHub Dark Default | ![]() |
| Paradise Smoked Glass | ![]() |
| Paradise Frosted Glass | ![]() |
You can contribute more themes! see here.
FAQs
How to uninstall Vibrancy?
Press F1 or ⌘+Shift+P and activate command "Disable Vibrancy", then restart Visual Studio Code.
You can also just uninstall the extension and restart VSCode, which will automatically remove Vibrancy.
Effect doesn't work correctly in VSCode terminal?
Check your settings. You should change the renderer type of the terminal to dom.
"terminal.integrated.gpuAcceleration": "off"
EROFS: read-only file system when enabling Vibrancy on macOS?
Your installation of VSCode is affected by App Translocation.
To fix this, either use the Finder and move VSCode to /Applications (or move it out of /Applications and then back in), or run the following terminal command:
sudo xattr -dr com.apple.quarantine "/Applications/Visual Studio Code.app"
I'm on Windows 10 and I'm experiencing lag when dragging the window
VSCode window cannot be resized/moved/maximized after enabling Vibrancy
Please see Important notice for Windows users at the top of the description.
Effect doesn't work, but there are no errors
Ensure that you don't have transparency effects disabled globally through your OS settings.
This can usually be found under Accessibility settings, and it may be called "Transparency effects" or "Reduce transparency." If that didn't help, you can also check the Console section in VSCode's Developer Tools, which can be accessed through the command palette.
If nothing else worked, try reinstalling VSCode, you won't lose any settings and this will ensure that your VSCode installation is consistent.
Linux: Why is the background transparent but not blurred?
Currently, we do not support native blur effects on Linux. While transparency can work on its own, blur usually depends on additional support from the system compositor. To achieve a blur effect, use transparent mode together with a compositor such as KWin, Hyprland, or Picom.
Contributing
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Vibrancy relies on user contributions, and as such, any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement".
Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
When creating a PR, please target the development branch.
License
Distributed under the MIT License. See LICENSE.txt for more information.
Thanks ⭐
EYHN : for making the original Vibrancy that this is a fork of
be5invis/vscode-custom-css : The basis of this extension program
DIYgod : Fix issues with VSCode 1.36















