Vibrancy Continued installs statistics

Visual Studio Code Extension - Vibrancy Continued

Enable Acrylic/Glass effect in VS Code.

[!TIP] Solutions for common issues can be found in the FAQ and Known Errors

See also: Windows 10/11 notes and Linux notes

       

 

Links: GitHub | Visual Studio Code Marketplace | Open VSX Registry | issues

Maintenance of this project is made possible by all the <a href="https://github.com/illixion/vscode-vibrancy-continued/graphs/contributors">contributors</a> and <a href="https://github.com/sponsors/illixion">sponsors</a>. If you'd like to sponsor this project and have your avatar or company logo appear below, <a href="https://github.com/sponsors/illixion">click here</a>. Any support is greatly appreciated 💖

<p align="center"> <a href="https://github.com/doughayden"><img src="https://avatars.githubusercontent.com/u/110487462?s=120&v=4" width="64px" alt="User avatar of user doughayden" /></a> <a href="https://github.com/hjnnjh"><img src="https://avatars.githubusercontent.com/u/37699150?s=64&v=4" width="32px" alt="User avatar of user hjnnjh" /></a> </p>

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)

✔ NixOS (via an automatic writable copy — see NixOS notes)

Supported code editors

✔ Visual Studio Code (v1.95 and newer)

✔ VSCodium

✔ Code - OSS

✔ Cursor

✔ Antigravity

✔ Devin

✔ Kiro

Other editors built on VSCode may work too. Vibrancy changes their window only when it can tell exactly where the change goes, and warns that the result is untested. If it can't tell, it refuses with "Your code editor is not supported". If an editor won't start afterwards, see Restoring an editor that won't start.

Vibrancy keeps the editor's integrity check quiet in these editors too, including those that don't let you dismiss its warning.

Getting Started

1. Install the extension from Visual Studio Code Marketplace.

2. Press F1 and activate command "Reload Vibrancy."

1. Restart VSCode when prompted.

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 notes

Vibrancy 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:

• Default (windowMode: auto / frameless) — opaque window. Snap, maximize, and resize work, but Windows 10 draws a thin 1px border around the window (Windows 11 doesn't show it at all). This is a cosmetic limitation of opaque resizable windows on Win10 that can't be removed without breaking snapping. (On older VSCode builds, where opaque vibrancy rendered incorrectly, auto instead uses a transparent window — no border, but no snapping; this matches frameless-transparent below.)
• Pixel-perfect (windowMode: frameless-transparent) — fully transparent window. No border at all, the cleanest possible look — but Aero Snap / maximize stop working.…