age-verification-bypass: a Firefox extension that rewrites age gates instead of faking an ID
Extension to bypass age verification on some websites
At a glance
- What is it?
- helloyanis/age-verification-bypass is an MIT-licensed WebExtension for Firefox and Firefox-based browsers that answers age-verification popups on the page itself. It is a proof of concept about the fragility of online age checks, not a general-purpose unlock for every gate on the web.
- Who is it for?
- Adopt it if you use Firefox or a Firefox-based browser, you want to read a specific gated page without handing over an ID, and you accept that it is a proof of concept whose per-site behaviour is documented in the project wiki rather than guaranteed.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 4 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 17, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What age-verification-bypass actually solves, and for whom
The extension exists to answer one narrow question: what happens to a page when the age gate in front of it simply disappears? Its author frames the project as a proof of concept showing that age verification online is not a good idea, and the argument in the README is about data exposure rather than convenience. Every ID uploaded to a verification vendor is a record that can leak, and the README points readers to breach statistics rather than making its own claims. The stated audience is people who want to avoid that exposure, plus, in the author's own words, children who would otherwise move to less moderated sites or borrow a parent's ID.
That framing matters when judging the tool. It is not a commercial product with a support contract. It is a small WebExtension whose supported-service list is a snapshot of what currently works, and the README sends readers to the project wiki for the details. If you want a permanent, site-independent bypass, this is the wrong shape of project.
Two mechanisms: reply rewriting and element removal
The README describes two methods, chosen per site. The first is rewriting the server response. On any website, the extension looks for the calls that create the age-verification popup, and instead of letting that request through it substitutes its own popup code, which then sends the callback telling the site the verification succeeded. Bluesky is the example the README gives for this path. The second method is hide and remove: the extension injects a script into the page that strips the popup elements and the image blurs applied to NSFW content. AliExpress and Reddit are named as users of this approach.
This is why the extension requests access to all URLs. It cannot know in advance which request on which origin builds the gate, so it watches broadly and decides at runtime. The README states plainly that no data is collected and that neither the author nor the verification platforms can check whether you visited a given site. The trade-off is the permission itself: a broadly scoped content script is a large trust surface for a tool this small, and the README does not document an audit.
Installing age-verification-bypass and testing it on the demo page
The README gives two install routes: the Mozilla Add-ons listing, or the latest release from the GitHub releases page. It also states the platform constraint without hedging: the extension works on Firefox and Firefox-based browsers such as Tor or Librewolf, and will not work on Chrome even if you sideload it. There is no npm package and no build step described for end users, so installation is the normal add-on flow.
After installing, the README instructs you to allow the extension to run on all websites, or at least on the site you are trying to use, and in private browsing mode if you use it. Those switches live in the extension settings. The manifest at the repository root is where the declared permissions live if you want to read them before granting anything.
# No build step is documented for users; install from the listing
# https://addons.mozilla.org/addon/age-verification-bypass
# or from the releases page:
# https://github.com/helloyanis/agechecker.net-bypass/releases/latestTo confirm it is working, the README points at a specific test target. Open the AgeChecker demo page and you should be let through directly instead of seeing the gate.
Where the bypass stops: server-side double checks
The supported-services list is honest about failure, which is unusual and useful. AgeChecker.net is described as fully bypassed unless the site's server does a double check with the AgeChecker server. AgeGO has three tiers in the README: basic integration bypassed, advanced integration partially bypassed, and server-to-server mode, where you are redirected to an AgeGO page instead of getting a popup, bypassed at the page level but usually defeated by additional checks on the server. The README says it is unlikely to work in that last case.
Veriff is listed with an explicit warning: only a few sites using it are supported, and you should try but not expect it to work. X.com appears as a beta that is not released yet and requires being logged in. So the pattern is clear. If the gate is decided in the browser, the extension can answer it. If the site's backend independently asks the vendor whether verification happened, rewriting the page response changes nothing, because the browser was never the authority. That is the boundary of this design, and no amount of per-site patching removes it.
Reddit, Bluesky and the side effects the README admits
Two of the supported sites come with caveats worth reading before you install. For Reddit, the extension lets you view NSFW subreddits and posts, but the README notes those subreddits cannot be found through Reddit search and you need a direct link, and that you have to be logged out. The author calls it a clunky solution and recommends redlib, a private Reddit front-end, instead. For Bluesky, sensitive posts become visible without logging in, and media is revealed by clicking Show in the Sensitive Media banner. The README also flags a side effect: posts carrying labels from their author will appear as posts labelled by Bluesky's automoderation.
That last point is the kind of detail that decides adoption. If you rely on Bluesky's labelling to tell you why a post is hidden, the extension blurs that distinction. The extension does not remove the label, it changes which label appears to apply.
Alternatives, and why a VPN is not one of them
The closest alternative named in the README is redlib, a private Reddit front-end, which the author suggests for viewing NSFW posts with more privacy than logging out of Reddit and using this extension. The difference in approach is architectural. redlib fetches Reddit content through its own front-end, so the gate is never rendered in your browser at all. This extension leaves you on the real site and edits what the page does. redlib therefore covers one site and does it thoroughly; the extension covers a list of sites and depends on each site's integration style.
A VPN is a different kind of tool entirely and does not substitute for either. It changes the network path your requests take. Age verification gates are usually tied to a logged-in account, a cookie or a server-side session, not to your IP address, so routing traffic through another country does not answer a popup. The related searches that pair VPNs with age verification are answering a question about jurisdiction, and this project does not address jurisdiction at all.
Maintenance, licence and the cost of a moving target
The repository is not archived, and the last push was on 2026-09-14. Releases are frequent: v1.2.1 on 2026-08-31, v1.2.2 on 2026-09-03, and v1.2.3 on 2026-09-13. That cadence is consistent with the design, because every supported site can change its popup markup or its callback shape at any time and break one of the two mechanisms. The upgrade cost is therefore not a version bump you schedule; it is the risk that a site you depend on stops being covered between releases, with the wiki as the only place that tracks which services currently work.
The licence is MIT, declared in LICENCE.md at the repository root. MIT permits reuse and modification with the copyright notice retained, and it comes with no warranty, which matches how the README presents the project. Nothing here is legal advice, and the README itself raises the legal framing as an argument rather than a compliance statement. If you are deploying this inside an organisation, the permission scope and the licence text are the two things to read first.
Editorial conclusion
Adopt it if you use Firefox or a Firefox-based browser, you want to read a specific gated page without handing over an ID, and you accept that it is a proof of concept whose per-site behaviour is documented in the project wiki rather than guaranteed. Do not adopt it if you need Chrome support, if the site you care about validates the check on its own server (AgeChecker.net and AgeGO both have that failure mode), or if you are looking for a tool that fabricates an identity document or a selfie, which this extension does not do. Before relying on it, install it from the Mozilla Add-ons listing or the releases page, grant it access to all sites or to the one site you need, then open agechecker.net/demo to confirm the extension is actually intercepting requests on your browser build; if the demo still shows a gate, the problem is your permissions, not the site.
Frequently asked questions
Is there a way to verify age without an ID in age-verification-bypass?
The extension does not verify anything. It rewrites the page's age-verification popup so the callback reports success, or removes the popup and blur elements entirely, so no identity document is involved.
Can a VPN get around age verification instead of age-verification-bypass?
The README does not present a VPN as a substitute. It describes the extension as rewriting popup code or removing gated elements on the page, and notes that sites doing server-side double checks still block it regardless of how the request arrived.
How do I remove the 18+ restriction on Google with age-verification-bypass?
Google is not in the supported-services list. The README covers AgeChecker.net, AgeGO, AgeVerif.com, AliExpress, Bluesky, Reddit, Spankbang and Veriff, plus an unreleased beta for X.com.
Community notes