NoWait
Automatically skips link shorteners and waiting pages
Before
linkvertise.com/1234/abc?r=…
↓
After
destino-final.com/pagina-real
NoWait
How it works
NoWait automatically bypasses link shorteners, "link-lockers" and artificial waiting pages — Linkvertise, ouo.io, adf.ly and 90+ other sites — so you land directly on the final destination, with no captchas, timers or interstitial ads. It is a maintained fork of FastForward (public domain), with one key difference: the content script only runs on domains with a registered bypass, not on every page you visit.
- 1
Detects the link
The content script checks whether the domain has a registered bypass before doing anything.
- 2
Resolves the bypass
It runs that shortener’s dedicated module, without ever loading its intermediate page.
- 3
You land on the destination
You get redirected straight to the final URL — no captchas, ads or timers.
NoWait
What it includes
-
90+ site-specific bypasses
Each shortener has its own waiting or captcha mechanism, resolved with a dedicated bypass: Linkvertise, ouo.io, adf.ly, sh.st, work.ink and many more.
-
IP logger blocking
If a link cannot be bypassed and also logs your IP address, NoWait blocks it instead of letting you navigate there.
-
Link tracker evasion
bit.ly, t.co, goo.gl and similar are resolved without ever loading the intermediate page.
-
Crowd bypass (optional, off by default)
For shorteners without an automatic bypass yet, it looks up and shares destinations already discovered by the FastForward community.
-
Configurable whitelist
Exclude your own domains by wildcard so NoWait never acts on them.
-
Native Manifest V3 on both browsers
Independent build for Chrome/Chromium and Firefox, each with its own manifest — not a generic package retrofitted after the fact.
Privacy and security
Privacy and security
NoWait does not collect personally identifiable information. All processing of the URL being bypassed happens locally in your browser.
-
The destination URL never leaves your device through the main bypass mechanism.
-
The only telemetry sent (to a first-party server) is the domain of the bypassed shortener and which bypass module ran — never the full destination URL, its path or its parameters.
-
Crowd bypass is optional and off by default; when enabled, it uses the FastForward community service under its own privacy policy.
-
Bypass definitions are bundled at extension build time: there is no live definitions download.
Permissions and why they are requested
| storage | Stores your preferences locally (whitelist, crowd bypass toggle) — never synced to third parties. |
| tabs | Detects and redirects the active tab to the final destination once the bypass is resolved. |
| declarativeNetRequestWithHostAccess | Applies IP logger blocking and tracker evasion rules without manually intercepting every request. |
| host_permissions: <all_urls> | IP logger and tracker blocking must be able to apply on any site; the content script that runs bypasses only injects on domains with a registered bypass. |
FAQ
Frequently asked questions
Is it paid? + −
No. NoWait is completely free, with no paid plan or PRO tier.
Does it work on Firefox? + −
Yes, it works on Chrome, Chromium and Firefox.
What data does it collect? + −
No personal data. Only minimal, anonymous telemetry (shortener domain and bypass module used), never the full destination URL.
Can I exclude my own links? + −
Yes, using the configurable wildcard whitelist in the extension options.