VLearnVibium

How to Install Vibium on Windows

Install Vibium on Windows with pip or npm, activate a virtual environment, pre-fetch Chrome for Testing, and run your first browser automation script.

By Pramod Dutta··3 min read·Verified with Vibium 26.2
▶ Animated overview · made with Remotion

To install Vibium on Windows, install Python 3.9+ from python.org (check "Add Python to PATH"), create a virtual environment, and run pip install vibium. Vibium ships as a single binary and auto-downloads its own Chrome for Testing on first run, so there's no ChromeDriver to install, no PATH editing for the browser, and no version matching by hand. The pip install vibium command pulls the correct Windows x64 package automatically. Prefer Node? npm install vibium works the same way. Vibium 26.2 also fixed Windows-specific issues such as zombie Chrome and chromedriver processes lingering after a run, so cleanup is reliable on Windows now. Below is the full setup: install Python, create and activate a virtualenv (with the PowerShell execution-policy fix if needed), install Vibium, optionally pre-fetch Chrome, and run your first script. See what is Vibium for the full background.

What do I need before installing Vibium on Windows?

You need Python 3.9 or higher (Python client) or Node.js (JavaScript/TypeScript client). Download Python from python.org and, in the installer, check "Add Python to PATH" — this is the single most common Windows setup mistake. Verify it in a new terminal:

python --version

You do not need to install Chrome yourself. Vibium downloads its own Chrome for Testing, which means it's independent of whatever Chrome (if any) is on the machine — ideal on locked-down corporate Windows.

How do I create and activate a virtual environment?

A virtual environment keeps Vibium isolated from system Python. In Command Prompt or PowerShell:

mkdir my-vibium-project
cd my-vibium-project
 
python -m venv .venv
.venv\Scripts\activate

If PowerShell blocks activation with a script-execution error, allow signed scripts for your user, then activate again:

Set-ExecutionPolicy -Scope CurrentUser RemoteSigned
.venv\Scripts\activate

Once activated, your prompt shows (.venv) and you're ready to install.

How do I install Vibium with pip?

With the virtual environment active:

pip install vibium

pip install vibium automatically resolves the Windows x64 platform package, so you don't choose a build manually. Everything installs into .venv, keeping your system Python clean.

Should I pre-download Chrome for Testing?

Optional, but recommended on Windows — especially behind a corporate proxy or on CI agents where the first run shouldn't stall on a download:

vibium install

This fetches the Chrome for Testing build matching your Vibium version up front. Otherwise Vibium downloads it automatically the first time you call launch().

How do I run my first script on Windows?

Create hello.py:

from vibium import browser_sync as browser
 
vibe = browser.launch()
vibe.go("https://example.com")
 
print(vibe.find("h1").text())
 
png = vibe.screenshot()
with open("screenshot.png", "wb") as f:
    f.write(png)
 
vibe.quit()

Run it:

python hello.py

Chrome opens, loads the page, prints the heading, saves screenshot.png, and closes. Vibium auto-waits for actionability, so find("h1") blocks until the element is ready — no manual sleeps needed. See find element and take a screenshot for more.

Does Vibium clean up Chrome processes on Windows?

Yes — and reliably as of 26.2. Earlier builds could leave zombie Chrome and chromedriver processes after a run on Windows; that's fixed, and process exit handlers now clean up on close and on Ctrl+C. Still, for long-running scripts, always quit in a finally block so a crash can't leak a browser:

from vibium import browser_sync as browser
 
vibe = browser.launch()
try:
    vibe.go("https://example.com")
    print(vibe.find("h1").text())
finally:
    vibe.quit()

If you ever see a stale Chrome after an upgrade, check Vibium version mismatch errors to confirm the client and cached browser are aligned.

Prefer Node? Install the JavaScript client

The TypeScript/JavaScript client installs identically on Windows:

npm install vibium

Same single binary, same auto-downloaded Chrome for Testing. Pick Python or Node to match your stack.

Next steps

Frequently asked questions

How do I install Vibium on Windows?

Install Python 3.9+ from python.org with Add to PATH checked, create a virtual environment, then run pip install vibium. Vibium ships as a single binary and auto-downloads Chrome for Testing on first run, so there is no ChromeDriver to install or match by hand.

Do I need to install Chrome before using Vibium on Windows?

No. Vibium downloads its own Chrome for Testing automatically on first launch, independent of any system Chrome. You can optionally pre-fetch it with vibium install so the first run is faster, which is useful on CI agents and locked-down corporate machines.

How do I activate the Vibium virtual environment on Windows?

After python -m venv .venv, run .venv\Scripts\activate in Command Prompt or PowerShell. If PowerShell blocks the script, set the execution policy for your user with Set-ExecutionPolicy -Scope CurrentUser RemoteSigned, then activate again and run pip install vibium.

Vibium is created by Jason Huggins. This is an independent tutorial — see the official Vibium site and GitHub repo for canonical docs.

Related guides