Get in touch

Webaura · Extensions & userscripts

Extensions that
actually work in Webaura.

Webaura is a mobile WebView browser, not desktop Chrome — so we're upfront about what we run and what we don't. The short version: userscripts (Greasy Fork / .user.js) and content-script-based Chrome Web Store extensions work; userscript managers and network-level ad blockers don't, because Webaura already does those jobs natively.

Last updated: 2026-05-04 App version: v1.5.0+ Manage in: Settings → Extensions
5
Install sources
12+
Built-in tools
100k+
Compatible scripts
0
Hidden permissions

Where you install from · 01

Three big script libraries —
tap to open.

These are the same three sources Webaura's built-in Add Extension sheet links to. Open any of them in your browser, find a script you like, and Webaura's install banner will appear automatically.

Userscript directory
Greasy Fork

The biggest open userscript library on the web — 100,000+ free .user.js scripts you can install with a single tap. Tap install on any script and Webaura will pick it up automatically.

Open Greasy Fork greasyfork.org/en/scripts Web extension store
Chrome Web Store

Browse Google's full Chrome extension catalogue. Webaura installs the content-script-based ones automatically and shows an honest "Not supported" dialog for the service-worker ones.

Open Chrome Web Store chromewebstore.google.com Userscript hub & docs
Tampermonkey

Tampermonkey's homepage is the best on-ramp for new users — read the docs, browse popular scripts and copy any .user.js URL straight into Webaura's built-in script manager.

Open Tampermonkey tampermonkey.net
Heads up: the Tampermonkey extension itself doesn't run inside Webaura — Webaura already includes its own built-in script manager, so you don't need it. The Tampermonkey website is still useful for browsing scripts and copying their .user.js URLs, which Webaura accepts directly.

Other supported sources

OpenUserJS Direct .user.js URL Local file import Paste script source

Honest compatibility · 02

What works, what doesn't.

Android WebView shares the same Chromium rendering engine as Chrome, but it doesn't ship the full set of Chrome browser APIs. That makes some extension classes possible and others structurally impossible — here's the line.

✓ Supported

Userscripts & content-script extensions

  • Greasy Fork userscripts (most popular site)
  • OpenUserJS-style .user.js scripts
  • Direct .user.js URLs from any site
  • Pasted script source or imported local file
  • CRX extensions that mainly inject JavaScript or CSS into the page
  • Page customisers, dark-mode/theme scripts
  • YouTube / X / Twitter / Reddit / Instagram helpers
  • Image, link & copy-helper scripts
  • Reader, cookie-banner and shortcut utilities
  • Site-specific UI enhancers
× Not supported

Manager & request-blocker extensions

  • Tampermonkey (and Beta / Dev / Next variants)
  • Violentmonkey
  • Greasemonkey
  • uBlock Origin
  • AdBlock & AdBlock Plus
  • Ghostery
  • Anything that needs a Manifest V3 background service worker
  • Extensions that rely on chrome.declarativeNetRequest or native messaging
  • Extensions that need persistent browser-action popups outside the page

Why some can't run

  • Userscript managers like Tampermonkey and Violentmonkey are themselves "managers" — Webaura already includes its own built-in script manager, so installing a second one would create an empty shell.
  • Network-level blockers (uBlock Origin, AdBlock, Ghostery) work by intercepting Chrome's network requests through APIs that simply aren't exposed inside Android WebView. Webaura's built-in ad blocker fills that role at the page level instead.
  • Manifest V3 service-worker extensions depend on Chrome browser APIs that don't exist in WebView. We honestly redirect those installs rather than silently failing.

Already inside · 03

Built-in extension-style tools.

Before you go hunting for an extension, check the toolbox — many of the things people add Chrome extensions for are already in Webaura, sandboxed and on by default.

🚫Built-in ad blocker
🧩Built-in script manager
📖Reader mode
🌐Page translation
🔍Find in page
💾Save page offline
🖥️Desktop mode / UA spoof
🖼️Long-press image tools
🎬Media detection
⬇️Quick downloader bridge
🍪Cookie / session aware extraction
🔧Page compatibility scripts
🛒Chrome Web Store install bridge

Try these · 04

Extensions you can install today.

A starter pack of popular, content-script-based userscripts and extensions that work well inside Webaura. Tap any card to open the source — then hit Install from the install banner Webaura shows over compatible pages.

Userscript · Greasy Fork

Return YouTube Dislike

Brings the YouTube dislike count back. Pulls archived counts from the public Return-YouTube-Dislike API and overlays the number under the like button.

YouTube UI tweak Free
Open on Greasy Fork
Userscript · Greasy Fork

Bypass All Shortlinks Debloated

Skips the wait timers and ad gates on most URL shorteners (linkvertise, adfly clones, ouo.io, exe.io and many more). Saves clicks, saves seconds.

Productivity All sites
Open on Greasy Fork
Userscript · Greasy Fork

Auto Redirect to Old Reddit

Forces every reddit.com link straight to old.reddit.com — faster, lighter, more readable. Works automatically the moment a page loads.

Reddit Redirect
Open on Greasy Fork
Userscript · Greasy Fork

Set Video Speed

Adds custom speed buttons (0.25× → 4×) to any HTML5 video player on the web — YouTube, Vimeo, Dailymotion, embedded learning videos, the lot.

Video All sites
Open on Greasy Fork
Userscript · Greasy Fork

YouTube Anti-Translate

Stops YouTube from auto-translating titles, channel names and descriptions to your locale. Keeps the original creator language intact.

YouTube Locale
Open on Greasy Fork
Userscript · Greasy Fork

Twitter / X Image Downloader

Adds a download button to every image and video on X (formerly Twitter) — saves the original full-resolution file rather than the compressed preview.

X / Twitter Download
Browse on Greasy Fork
Userscript · Greasy Fork

Cookie Banner Cleaner

Auto-dismisses GDPR / cookie-consent overlays on the sites that ship them. Reads cleaner, no scroll-blocking modals, no extra taps.

All sites Reader
Browse on Greasy Fork
Userscript · Greasy Fork

Image Hover Preview

Hover (or long-press on mobile) any thumbnail and instantly see the full-size image without clicking through. Works across most image-heavy sites.

Images All sites
Browse on Greasy Fork
Chrome Web Store · Content scripts

Refined GitHub

Tons of small UI improvements on github.com — collapse PR diffs, copy file paths, mark old comments and more. Almost entirely content-script driven, so the page-side parts work in Webaura.

GitHub Developer
Open on Chrome Web Store
Chrome Web Store · Content scripts

Stylus

Restyle any website with custom CSS themes. Browse community styles for Twitter, YouTube, GitHub, Reddit and thousands more — Webaura runs the injected styles, you skip the dark-mode subscription.

Theme All sites
Open on Chrome Web Store
Chrome Web Store · Content scripts

WhatFont

Tap any text on a page to identify the font, size, weight, line-height and colour. Tiny script, no background worker — runs cleanly inside Webaura.

Designer Inspector
Open on Chrome Web Store
Built-in · No install

Webaura Reader Mode

Strips ads, sidebars and clutter from articles automatically. Adjustable font, line-height and theme. No extension needed — open any article and tap the reader icon.

Built-in Reader
See in Webaura

Install · 05

From browse to installed
in three steps.

01

Open the extension page in Webaura

Browse to a Greasy Fork script, an OpenUserJS page, or any Chrome Web Store extension detail URL. Webaura detects the install context automatically.

02

Tap "Install"

For userscripts, tap the green Install button on Greasy Fork — Webaura intercepts the .user.js file and adds it to your script manager. For Chrome Web Store extensions, the install banner appears at the top of the page; tap it and Webaura fetches and parses the CRX.

03

Manage from Settings → Extensions

Toggle each script on or off, view its source code, edit the @match patterns, or remove it entirely. Filter by source type (CRX / userscript / built-in) and search by name.

At a glance · 06

Compatibility matrix.

What runs where, by extension class. If a class isn't listed here, treat it as "not officially supported" until proven otherwise.

Extension type Webaura Desktop Chrome Notes
Greasy Fork userscripts (.user.js) ✓ Yes ✓ via Tampermonkey Native script manager, no extra install
OpenUserJS userscripts ✓ Yes ✓ via Tampermonkey Same install path as Greasy Fork
Direct .user.js URL or paste ✓ Yes ✓ Yes Webaura validates & sandboxes on add
CRX, content-script driven ✓ Yes ✓ Yes Page customisers, themes, helpers
CRX, MV3 service worker ✗ No ✓ Yes WebView lacks the worker runtime
Userscript managers (Tampermonkey, etc.) ✗ Not needed ✓ Yes Webaura already includes one
Network blockers (uBlock Origin, AdBlock, Ghostery) ✗ No ✓ Yes Use Webaura's built-in ad blocker instead
Native messaging hosts ✗ No ✓ Yes Not exposed on Android

FAQ · 07

Frequently asked.

Is it safe to install random userscripts?
Userscripts run with full access to the pages they target, so only install from sources you trust. Greasy Fork and OpenUserJS show the script source code right on the page — give it a quick look, especially for any script that touches login pages, banking sites or anything financial. Webaura sandboxes each script per-site, but it can't read intent.
Why doesn't Tampermonkey work? It's listed everywhere.
Tampermonkey is itself a userscript manager — it provides the runtime that runs your scripts. Webaura already provides that runtime built-in, so installing Tampermonkey on top would create an empty shell with no engine behind it. Use Webaura's Settings → Extensions page directly to manage your scripts.
Can I bring my Tampermonkey scripts over from desktop?
Yes. In Tampermonkey on desktop, export each script to a .user.js file (or just copy the source). In Webaura, open Settings → Extensions → Add Script and either paste the source, point to the .user.js URL, or import the file from your phone's storage.
What about uBlock Origin or AdBlock?
These work by hooking Chrome's network-request APIs, which aren't available inside Android WebView. Webaura includes its own page-level ad blocker that does most of the same job — toggle it from the browser menu. Independent reviews still place WebView-based ad blocking behind desktop uBlock for edge cases, but it covers the common ones.
Does every Chrome Web Store extension work?
No — only the ones that mainly use content scripts. When you tap install on a CRX from chromewebstore.google.com inside Webaura, the app fetches and parses the manifest, then either installs the compatible parts or shows a "Not Supported" dialog explaining why. We err on the side of being honest rather than installing something that won't work.
Where do I report a script that's broken or malicious?
Report scripts on the source site (Greasy Fork has a "Report" tab on every script page; the Chrome Web Store has a flag option). For Webaura-side issues — install failing, script not running, ad blocker missing a domain — email us at info.creedmotions@gmail.com.
Are extensions covered by Webaura's privacy policy?
The userscripts and CRX extensions you install are third-party code — Webaura sandboxes and runs them, but doesn't author them. Your installed list, on/off state and per-site permission grants are part of the on-device browsing data described in our Privacy Policy → Extensions & userscripts section.

Quick references

Privacy Policy Terms of Service Delete data Back to Webaura