Start in Settings → Extensions
Use WebAura’s own extension manager to add, disable, inspect or remove compatible scripts. Install only code you understand or trust, and review the sites on which it is allowed to run.
WebAura · Extensions
Extend the browser, carefully.
WebAura supports compatible userscripts and selected browser-extension behaviours. It is not a complete desktop Chrome runtime, so compatibility depends on the APIs an extension uses.
Userscripts
Standard .user.js scripts that inject JavaScript or CSS into a matching page are the most direct fit. Site rules and script dependencies can still affect behaviour.
Content-script extensions
Extensions centred on page-level JavaScript, CSS and DOM changes are more likely to work than extensions that depend on a full desktop browser process.
Common limitations
Background service workers, native desktop messaging, privileged Chrome APIs, complex developer tools and some large rule engines may be unavailable or behave differently.
Built-in alternatives
Before installing anything, check WebAura’s built-in reader, page translation, appearance, media, download, privacy and script controls. A built-in tool is usually easier to support.
Permissions matter
A script can read or change matching pages within the access WebAura grants it. Do not install scripts that request broad access without a clear reason, and never paste unknown code into an extension manager.
If something breaks
Disable the extension, reload the page and test again. Confirm the script’s match rules include the site. If the page works without it, report the extension name, source and WebAura version to support.
Compatibility is not an endorsement
Third-party extension names, stores and scripts belong to their respective owners. CreedStack does not guarantee or audit every third-party package. Their code, data handling and availability are governed by their developers.