Plugins
Hayase supports Chrome extensions as plugins, allowing you to extend the app's functionality using the vast ecosystem of existing Chrome extensions.
Unlike content source extensions (torrent, NZB, subtitle, HTTP), plugins are standard Chrome extensions that can modify or enhance Hayase's behavior in various ways.
Installing Plugins
From a .crx File
- Download the
.crxfile from a trusted source - Settings → Plugins → Install Plugin → Select .crx file
- Confirm installation
From a .zip File
- Download or package the extension as
.zip - Settings → Plugins → Install Plugin → Select .zip file
- Confirm installation
From an Unpacked Directory
- Have the extension's folder containing
manifest.jsonready - Settings → Plugins → Install Plugin → Select manifest.json
- Confirm installation
Downloading .crx Files from the Chrome Web Store
To install a Chrome extension as a plugin, you first need to obtain its .crx file:
Go to the Chrome Web Store
Find the extension you want
Copy the extension's ID from the URL (e.g.,
coolextensionid123inhttps://chromewebstore.google.com/detail/name/coolextensionid123)Download the
.crxdirectly using the following URL pattern:https://clients2.google.com/service/update2/crx?response=redirect&prodversion=150&acceptformat=crx2,crx3&x=id%3D{extension_id}%26ucFor example:
https://clients2.google.com/service/update2/crx?response=redirect&prodversion=150&acceptformat=crx2,crx3&x=id%3Dcoolextensionid123%26ucYou may need to update
prodversionto the latest Chrome version if the download fails - check Wikipedia for the current release number.The extension will show up in your Downloads directory, without a download popup.
Install the downloaded
.crxfile in Hayase
Managing Plugins
Enabling/Disabling
Settings → Extensions → Plugins → Toggle ON/OFF
Uninstalling
Settings → Extensions → Plugins → Uninstall
Notes
- Not all Chrome extensions are compatible - plugins must work within Hayase's sandboxed environment.
- Extensions that require full browser APIs (e.g.,
tabs,windows,bookmarks) may not function as expected. - Content scripts and page-modifying extensions may require additional compatibility.