Wireless USB Big Sur Adapter packages Realtek Wi-Fi drivers for Intel Macs
Drivers for Realtek 802.11n and 802.11ac USB Wi-Fi adapters. Packages for macOS
At a glance
- What is it?
- Wireless USB Big Sur Adapter is a community installer for Realtek 802.11n and 802.11ac USB Wi-Fi drivers on macOS, built for older Intel Macs and Hackintosh builds. It is a binary package with no source, it does not support WPA3, and it requires SIP to be disabled.
- Who is it for?
- Adopt this package only if you have an Intel Mac or a Hackintosh build with a Realtek 802.11n or 802.11ac USB adapter and no working alternative, and if you are prepared to disable SIP and Gatekeeper, keep a restore path, and accept that there is no source to audit. Do not adopt it on Apple silicon, where the README says it does not work, and do not adopt it if your network uses WPA3 or if your adapter is a Mediatek based one.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 38 days ago.
- What is it written in?
- Mainly Rich Text Format, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 23, 2026, and from our analysis. They are not legal advice.
Editorial analysis
The package exists because Realtek abandoned macOS drivers
Wireless USB Big Sur Adapter is a set of drivers for Realtek 802.11n and 802.11ac USB Wi-Fi adapters, packaged for macOS. The reason it exists at all is stated in the README: there is no source for this project, and all wifi companies have abandoned it as well as Realtek the main builder.
That sentence is the whole context. A USB Wi-Fi adapter needs a kernel extension or a driver package that matches the macOS release, and the vendor that shipped the chip does not maintain one for current macOS. The result is that a Mac with a Realtek adapter either has no working Wi-Fi or relies on a community built driver that has to be updated whenever Apple changes something.
The target hardware is old. The README notes that it does not work on Mac M1, M2, M3 and M4 Apple chip hardware, and works only for Mac Intel. The supported macOS versions run from Big Sur 11 through Monterey 12, Ventura 13, Sonoma 14 and Sequoia 15, and the README adds macOS Tahoe 26 with a dedicated usage page. Mojave 10.14.6 and Catalina appear in the supported list too, and the README says explicitly, do not use on other operating systems.
The topic tags on the repository line up with that scope: macos, macos12 through macos14, realtek-driver and macos14-wifi. This is a driver package for a shrinking corner of Apple's hardware base, not a general networking tool.
SIP must be fully disabled before any release will install
The security cost of this package is stated without hedging. The README says that to use any release, SIP Security must be disabled, fully disabled, and gives the command:
csrutil disableThere is a linked discussion on SIP security for details, and a second discussion on enabling SIP again afterwards. The README also points to a separate Disable-Gatekeeper page for the Sequoia 15 path, since Gatekeeper blocks the installer package on that release.
This is the crux of the design. macOS System Integrity Protection blocks unsigned kernel extensions and restricted system components from loading, and a community driver package for a chip the vendor no longer supports cannot be signed the way an official driver would be. The usual escape hatch is to turn SIP off, install the driver, and turn SIP back on. Whether that works is exactly the kind of thing the discussions exist to answer.
The README also mentions a Fix_Apple_Services document, which covers Messages and FaceTime problems. That is a distinct failure mode from the driver itself, and it is a good clue about the overall experience: getting a community Realtek driver working on a modern macOS often involves a second problem in the networking stack that the package also tries to address.
The honest framing is that this trades a macOS security boundary for a piece of hardware support. A machine that keeps SIP disabled is a machine where unsigned code can load, and the person who disables it owns that risk. The package does not offer a signed, notarised path.
Known working adapters are listed by model, which is the useful part
The most practically valuable section of the README is the long list of known working and tested adapters, and it is worth reading before downloading anything.
The list covers a wide spread of Realtek-based sticks: Alfa AWUS036AC and AWUS036ACH, TP-Link Archer T2U in several variants including the Plus, NANO, MINI and AC600, the Archer T3U and T3U Plus, the Archer T2U MINI V3, the ArcherT4U V1 to V3, and the Archer T9UH V1 and V2. ASUS entries include the USB AC68, USB-N13 and USB Nano-AC53. D-Link contributes the DWA-121 N150, DWA-131 E, DWA-171 C, DWA-182 D and DWA-192 A. EDIMAX has more than half a dozen entries including the EW-7611UCB, EW-7722UTn V2, EW-7822ULC, EW-7612Uan V2, EW-7833UAC, N300 and EW-7811Un N150. There are also Cudy, COMFAST, BrosTrend, Fenvi, Mercusys, Netgear, Netis, Plexgear, Tenda, TRENDnet, UGreen, Zebronics and Zyxel models.
Reading that list is how you decide whether this is worth the SIP change. The same Realtek chip, RTL8812bu for example, appears across several brands, so the chipset matters more than the brand name. The README credits Realtek for the driver work and OCLP-Mod for the package, and there is a link for reporting an adapter that works but is not listed.
Two exclusions are stated at the top of the README. It does not work on Mediatek adapters, which have their own separate package, and it does not work for WPA3 networks. That second one is a real functional ceiling: a modern home router set to WPA3 will not work with this driver.
Hackintosh users are pointed at three different forks
If you are running a Hackintosh, the main repository is not the place to start. The README steers you to two alternatives, and the split follows the bootloader.
For OpenCore Legacy Patcher users, the recommendation is the Wireless-USB-OC-Big-Sur-Adapter repository, and the same is said for Hackintosh builds using OpenCore in general. For Clover, the pointer is to WirelessAdapterCloverBigSur. The main repository is described as being for packages on a real Mac, and it does say the packages work on a Hackintosh PC or laptop.
The reasoning behind the split is not spelled out, but the shape of it is familiar in the Hackintosh world: OpenCore and Clover differ in how they hand off the bootloader and what the kext loading environment looks like, and community driver packages tend to be built against one of them.
The install path for the newest release lives in a dedicated file rather than in the README. There is a Usage-macOS-Tahoe.md file for macOS Tahoe 26, and the README's support list runs through Sequoia 15, Sonoma 14, Ventura 13, Monterey 12, Big Sur 11, Catalina and Mojave 10.14.6. The newest tagged release is V18, and the README points at the Wireless USB Big Sur Adapter-V18 release page for the download.
The repository itself is mostly documentation and packaging. The top level holds the README, an index.md and support.md and update.md for the GitHub Pages site, the _config.yml for that site, the per-version usage pages, and a Package sources directory. The.github workflow badge at the top of the README is for pages-build-deployment, which deploys the site rather than building the driver.
A binary package with no source and an unknown licence
The licence field for this repository is unknown, and there is no LICENSE file in the top level entries, which hold .gitignore, the documentation files and the Package sources directory. That is a genuine issue for redistribution, and it is different from the MIT or Apache-2.0 position most projects in this space take.
The absence of source is the other half of the picture, and the README is upfront about it. There is no source for this project. For a component that loads into the kernel and operates at the network layer, the ability to read what the code does is a meaningful part of the trust model, and here you are trusting a prebuilt package instead.
The repository is not archived and the last push was on 2026-09-16, so it is receiving changes. The version history is documented in a changelog embedded in the README rather than through GitHub releases, and the only tagged release is V18 from 2024-07-11. The update log runs from 15 September 2021, when V8 adapted for the latest macOS Big Sur 11, through entries about package background changes, icon updates, the status bar app, the removal of agents and a daemon in November 2022, and support for Tahoe added on 05 Jul 2025.
The recent entries are largely cosmetic, which is consistent with what the project is. The 10 January 2026 entry is an update of the program icons, and the 18 Oct 2025 entry updated the Wi-Fi icons. The functional work, adding support for a new macOS release, is what a macOS driver package for unsupported hardware has to keep doing.
The alternative is a different adapter or a different network path
The honest comparison here is not between two driver packages. It is between installing this one and changing the hardware or the network path.
The first alternative is an adapter whose macOS support is still maintained. Apple's own Wi-Fi and Ethernet options cover most use cases, and a Thunderbolt or USB-C Ethernet adapter sidesteps the Wi-Fi driver question entirely if the machine has the port. A Mac with a broken or missing internal Wi-Fi radio and a USB port is the exact situation this package addresses, and in that situation there are only three answers: fix the driver, replace the adapter, or do not use Wi-Fi.
The second alternative is a different distribution path for the same class of driver. There are other community Realtek driver packages, and the README itself points to a MediaTek specific package for adapters with a MediaTek chipset, which is the same idea applied to a different vendor. The difference in approach between such packages is packaging and support matrix rather than technology, which is why the adapter model list and the Tahoe usage page matters more than any feature comparison.
There is also the option of using OpenCore Legacy Patcher or its modifications, which the README credits for the package, on a machine where the bootloader is already in play.
What no alternative changes is the security trade. Every route to running an unsigned Realtek driver on a modern macOS involves loosening a system protection, and the specific question this repository answers is whether that loosening is worth it for your Mac.
Editorial conclusion
Adopt this package only if you have an Intel Mac or a Hackintosh build with a Realtek 802.11n or 802.11ac USB adapter and no working alternative, and if you are prepared to disable SIP and Gatekeeper, keep a restore path, and accept that there is no source to audit. Do not adopt it on Apple silicon, where the README says it does not work, and do not adopt it if your network uses WPA3 or if your adapter is a Mediatek based one. Before you install, confirm your Mac is Intel, read Usage-macOS-Tahoe.md for the version specific steps, and check the known working adapter list for your exact model before downloading the V18 release.
Frequently asked questions
Does the Wireless USB Big Sur Adapter package work on Apple silicon Macs?
No. The README says it does not work on Mac M1, M2, M3 and M4 Apple chip hardware and works only for Mac Intel, and it states the package is for Intel Macs.
Why does installing these Realtek Wi-Fi drivers require disabling SIP?
The README says that to use any release, SIP Security must be fully disabled, and it gives the csrutil disable command, with a linked discussion explaining the SIP situation. There is also a separate page for enabling SIP again afterwards.
Can this driver connect to a WPA3 network?
No. The README lists as a limitation that it does not work for WPA3 networks, alongside the note that it does not work on Mediatek adapters.
Which macOS versions are supported by the Wireless USB Big Sur Adapter package?
The README lists macOS Tahoe 26, Sequoia 15, Sonoma 14, Ventura 13, Monterey 12, Big Sur 11, Catalina and Mojave 10.14.6, with a separate Usage-macOS-Tahoe.md page for Tahoe. It says not to use the package on other operating systems.
How do I check if my USB Wi-Fi adapter is supported?
The README contains a long list of known working and tested adapters by model, from Alfa, TP-Link, ASUS, D-Link, EDIMAX and others, and it asks you to report an adapter that works but is not listed. Realtek-based chips are the ones covered, and Mediatek adapters are not.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/chris1111-wireless-usb-big-sur-adapter)Was this useful?