qutebrowser's primary maintainer, The-Compiler, is currently workingpart-time on qutebrowser, funded by donations.

To sustain this for a longtime, your help is needed! See theGitHub Sponsors page oralternativedonation methods for more information. Depending on your sign-up date andhow long you keep a certain level, you can get qutebrowser t-shirts, stickersand more!

# apt install --no-install-recommends git ca-certificates python3 python3-venv libgl1 libxkbcommon-x11-0 libegl1 libfontconfig1 libglib2.0-0 libdbus-1-3 libxcb-cursor0 libxcb-icccm4 libxcb-keysyms1 libxcb-shape0 libnss3 libxcomposite1 libxdamage1 libxrender1 libxrandr2 libxtst6 libxi6 libasound2

• On Ubuntu 20.04 / Linux Mint 20 / Debian Bullseye, no OpenSSL 3 is available. However, Qt 6.5moved to OpenSSL 3 for its binary builds. Thus, you will either need to live with:adblock-update and:download being broken, or use--pyqt-version 6.4 for thescripts/mkvenv.py script to get an older Qt.

• If running from git, run the following to generate the documentation for the:help command (thescripts/mkvenv.py script used with a virtualenv install already does this for you):

  $ pip install -r misc/requirements/requirements-docs.txt  # or install asciidoc manually$ python3 scripts/asciidoc2html.py

• If you prefer using QtWebKit, there’s QtWebKit 5.212 available in those distributions. Note however that it is based on an upstream WebKit from September 2016 with known security issues and no sandboxing or process isolation.

• If video or sound don’t work with QtWebKit, try installing the gstreamer plugins:

  # apt install gstreamer1.0-plugins-{bad,base,good,ugly}

  Note those are only needed with QtWebKit, not with the (default) QtWebEngine backend.

# dnf install qutebrowser

Fedora only ships free software in the repositories.To be able to play videos with proprietary codecs with QtWebEngine, you willneed to install an additional package from the RPM Fusion Free repository.For more information seehttps://rpmfusion.org/Configuration.

With Qt 6 (recommended):

With Qt 5:

# pacman -S qutebrowser

$ git clone https://aur.archlinux.org/qutebrowser-git.git$ cd qutebrowser-git$ makepkg -si$ cd ..$ rm -r qutebrowser-git

# pacman -S gst-plugins-{base,good,bad,ugly} gst-libav

# emerge -av qutebrowser

# emerge -av gst-plugins-{base,good,bad,ugly,libav}

# xbps-install qutebrowser

$ nix-env -i qutebrowser

sbopkg -V 14.2sbopkg -r

sqg -p qutebrowser

PYTHON3=yes sbopkg -i qutebrowser

# cd /usr/ports/www/qutebrowser# make install clean

Prebuilt standalone packages and installersare built for everyrelease.

Note that you’ll need to upgrade to new versions manually (subscribe to thequtebrowser-announcemailinglist to get notified on new releases). You can install a newer versionwithout uninstalling the older one.

The binary release ships with a QtWebEngine built without proprietary codecsupport. To get support for e.g. h264/mp4 videos, you’ll need to buildQtWebEngine from source yourself with support for that enabled.

If you want to test out new features before an official qutebrowser release, automatednightlybuilds are available. To download them, open the latest run (usually the first one),then download the archive at the bottom of the page.

Those builds also include variants with debug logging enabled, which can be useful totrack down issues.

• PackageManagement PowerShell module

• Chocolatey package withchoco:

• Scoop’s client

Use the installer frompython.org to getPython 3 (be sure to install pip).

Theninstall qutebrowser via virtualenv.

The easiest way to install qutebrowser on macOS is to use the prebuilt.appfiles from therelease page.

Note that you’ll need to upgrade to new versions manually (subscribe to thequtebrowser-announcemailinglist to get notified on new releases).

The binary release ships with a QtWebEngine built without proprietary codecsupport. To get support for e.g. h264/mp4 videos, you’ll need to buildQtWebEngine from source yourself with support for that enabled.

This binary is also available through theHomebrew packagemanager as acask:

If you want to test out new features before an official qutebrowser release, automatednightlybuilds are available. To download them, open the latest run (usually the first one),then download the archive at the bottom of the page.

Those builds also include variants with debug logging enabled, which can be useful totrack down issues.

Alternatively, you can install the dependencies via a package manager (likeHomebrew orMacPorts) and runqutebrowser from source.

Homebrew

$ brew install pyqt@6$ pip3 install qutebrowser

First of all, clone the repository usinggit and switchinto the repository folder:

Using a Qt installed via virtualenv needs a couple of system-wide libraries.See theDebian-based distributions section for details about which librariesare required.

Then run the install script:

This installs all needed Python dependencies in a.venv subfolder(which subdirectory the environment is created in is configurable via the--venv-dir flag).

This comes with an up-to-date Qt/PyQt including a pre-compiled QtWebEnginebinary, but has a few caveats:

• Make sure yourpython3 is Python 3.9 or newer, otherwise you’ll get a "No matching distribution found" error and/or qutebrowser will not run.

• It only works on 64-bit x86 systems, with other architectures you’ll get the same error.

• It comes with a QtWebEngine compiled without proprietary codec support (such as h.264).

See the next section for an alternative install method which might help withthose issues but result in an older Qt version.

You can specify a Qt/PyQt version with the--pyqt-version flag, seescripts/mkvenv.py --help for a list of available versions. By default, thelatest version which plays well with qutebrowser is used.

Alternatively, you can usescripts/mkvenv.py --pyqt-type link to symlinkyour local PyQt/Qt install instead of installing PyQt in the virtualenv.However, unless you have a new QtWebKit or QtWebEngine available, qutebrowserwill not work. It also typically means you’ll be using an older release ofQtWebEngine.

On Windows, runset PYTHON=C:\path\to\python.exe (CMD) or$Env:PYTHON ="..." (Powershell) first.

There is a third mode,scripts/mkvenv.py --pyqt-type source which uses asystem-wide Qt but builds PyQt from source. In most scenarios, this shouldn’tbe needed.

Runningscripts/mkvenv.py does not install a system-widequtebrowserscript. You can launch qutebrowser by doing:

You can create a simple wrapper script to start qutebrowser somewhere in your$PATH (e.g./usr/local/bin/qutebrowser or~/bin/qutebrowser):

If you cloned the git repository, runscripts/mkvenv.py --update which willtake care of updating the code (viagit pull) and recreating the environmentwith the newest dependencies.

Alternatively, you can update your local copy of the code (e.g. by pulling thegit repo, or extracting a new version) and the virtualenv should automaticallyuse the updated versions. However, dependencies won’t be updated that way.