This page will tell you how to use plugins.
Plugins are written in C++ and will run as a part of Hyprland.
Make sure to always read the source code of the plugins you are going to use and to trust the source.
Writing a plugin to wipe your computer is easy.
Never trust random
.sofiles you receive from other people.
Plugins come as shared objects, aka.
Hyprland does not have any “default” plugins, so any plugin you may want to use you will have to find yourself.
It is highly recommended you use the Hyprland Plugin Manager,
hyprpm. For manual instructions, see a bit below.
Make sure you have the required dependencies:
Find a repository you want to install plugins from. As an example, we will use hyprland-plugins.
hyprpm add https://github.com/hyprwm/hyprland-plugins
once it finishes, you can list your installed plugins with
and enable or disable them via
hyprpm enable name and
hyprpm disable name.
In order for the plugins to be loaded into hyprland, run
You can add
exec-once = hyprpm reload -n to your hyprland config to have plugins loaded at startup.
-n will make hyprpm send a notification if anything goes wrong (e.g. update needed)
In order update your plugins, run
For all options of
Different plugins may have different build methods, refer to their instructions.
If you don’t have hyprland headers installed, clone hyprland, checkout to your version,
build hyprland, and run
sudo make installheaders. Then build your plugin(s).
To load plugins manually, use
hyprctl plugin load path !NOTE: Path HAS TO BE ABSOLUTE!
You can unload plugins with
hyprctl plugin unload path.
Oh no. Oopsie. Usually means a plugin is broken.
hyprpm disable it.
hyprctl plugin list
As long as you read the source code of your plugin(s) and can see there’s nothing bad going on, they will be safe.
Hyprland employs a few tactics to unload plugins that crash. However, those tactics may not always work. In general, as long as the plugin is well-designed, it should not affect the stability of Hyprland.