What makes a Wi-Fi adapter good? If your answer was "the speed rating," you're answering the wrong question, and it's the answer almost everyone gives.
Almost everybody.
Daniel wrote in with a whole thing about this. He's got a Raspberry Pi and SBC use case, the IoT end of the house, where the goal isn't throughput at all, it's a connection that just stays up. And he says the radios built into these boards are weak enough that in his experience the link becomes unusable. So he wants thoughts for the buyer picking up a USB Wi-Fi dongle for one purpose only. Stable, reliable connectivity.
One purpose.
Which he points out really makes it a question about antennas and antenna placement relative to the device. Then the specific asks. Why do the built-in radios on Pis and SBCs perform so poorly despite what the specs suggest. What actually matters when stability is the only criterion. How much do antennas and their placement really affect things. What do claims like "high gain antenna" actually mean. How do the form factors stack up, the tiny stub, the six-inch antenna, the cabled external one. And what would a winning spec sheet look like for an adapter optimized purely for stability over the LAN.
He's got a suspicion underneath it, too. He thinks this is really a question about antennas and antenna placement, and he wants to know what differentiates these products. So let's start with why the radio that's already on the board is so often the problem.
Here's the reframe, and it's going to sound wrong for a minute. The three things that decide whether this works, throughput, standard version, stream count, none of them are on your side. The metric that matters is link stability, and stability is an RF problem and a systems problem. It is not a radio-spec problem.
Say more, because "buy the newer standard" is what everybody does.
Newer standards are about moving more bits when everything is already good. Wi-Fi 7 is a throughput story. But a dongle that negotiates 802.11ac and holds minus forty-five dBm for six months is more useful to you than one that negotiates the latest thing and drops every time the fridge compressor kicks on. Stability comes from three variables that don't appear on any spec sheet. Antenna placement and physical separation. USB 3.0 interference. And driver quality.
Those are three sentences that a marketing department would rather you never read.
Right, and there's a resource problem here that's worth naming. The closest thing to a real buying guide for this, anywhere, is a GitHub project. It's morrownr slash USB Wi-Fi, it's got about four and a half thousand stars, roughly forty-seven thousand views a month as of last month. It maintains tested adapter lists, a short list, a long FAQ. That's the reference.
A hobbyist repo as the de facto standard.
There is no published spec sheet for a stability-optimized USB Wi-Fi adapter. Not from the vendors, not from the community. What we're going to build today is synthesized from physics and field data, it isn't quoted from one document. And that absence is itself the story.
To understand why the dongle matters, you first have to understand why the radio already on the Pi is so disappointing. And the answer starts with a surprise.
Start with what the antenna actually is, because the assumption is that it's cheap garbage. Since roughly the Pi 3 era, Raspberry Pi boards use a PCB trace antenna. Not a chip antenna. That's a cost decision on the bill of materials, a printed copper trace instead of a component.
A trace.
And there's a teardown analysis of the Pi Zero W and the Pi 4 antenna that's worth reading. It's a wideband dipole, heavily shorted with inductance, rematched to center with series and shunt capacitors. Cser1 at one point two picofarads, Cser2 at two picofarads, Cshunt at two point six picofarads. Those are the actual matching values.
So somebody sat down and did the math.
And here's the part people get wrong. In an anechoic chamber, peak efficiency measures above minus two dB. That's roughly seventy percent. The analyst's own words, "a pretty good antenna."
So the design isn't the problem.
But efficiency falls off rapidly. Because of that heavily shorted nature, it's a narrowband design, and the impedance moves fast across the band. It's tuned beautifully at the center and it degrades as you leave it. And Raspberry Pi's own whitepaper, RP dash nine seven six three, acknowledges it. Board computers include only an on-board PCB antenna. External whip antennas are only offered on the Compute Module range.
Which is the admission that the on-board one is a compromise.
A cost compromise, not an engineering failure. The failure is environmental. There's a post on the Core Electronics forum from December twenty twenty-two that says it about as plainly as it can be said. The antenna is embedded in the PCB, the design is clever, but overall performance is constrained by the location of the device and the surrounding materials that absorb and reflect signal.
So the antenna's fine. Where it lives is not.
And there's an anecdotal layer on top. Pi 5 users on the Raspberry Pi forums reporting onboard Wi-Fi performing worse than Pi 4 in some setups. One user ordered a second Pi 5 thinking the first was defective. Both exhibited the same poor performance. Fair warning, that's forum-reported, not confirmed by a primary source, but the report is specific enough to take seriously.
Two boards, same behavior, and the user's conclusion was that the hardware was broken twice. That's what bad placement does to you. It makes you blame the wrong object.
Now the hidden killer. USB 3.0 interference. This is where it stops being about the antenna entirely.
This is the one that made me sit up.
Intel published a white paper in twenty twelve on USB 3.0 radio frequency interference with 2.4 gigahertz devices. Document three two seven two one six. And the core fact is that USB 3.0's five gigabit data spectrum is broadband. It ranges from DC to five gigahertz. There's high noise right in the two point four to two point five gigahertz range, which is exactly where most IoT Wi-Fi lives.
That's not a coincidence, that's an overlap.
It's the worst possible overlap. And the measured numbers are dramatic. An external USB 3.0 hard drive raised the 2.4 gigahertz noise floor by nearly twenty dB. The noise from a notebook's USB 3.0 receptacle connector raised it by about twenty-five dB.
Twenty-five dB. That's not interference, that's a jammer.
Effectively, yes. Shield a USB 3.0 peripheral fully and you reduce radiated noise by about twelve dB. Improve the connector shielding and you drop it by at least ten. So the fix exists, but it has to be designed in.
Which most cheap hubs and cables don't do.
And here's the test from that paper that should be framed and hung on a wall. A wireless dongle placed on the opposite side of the laptop, connected via a USB 2 extension cable, worked fine at two feet, three feet, and five feet. A dongle stacked vertically above the USB 3.0 port got "No Response" at every distance.
At every distance.
Every single one. Same radio, same laptop, same room. The only variable was where the antenna physically sat relative to the USB 3.0 connector. Intel's own conclusion is in the paper. Placement of the wireless antenna should be located as far away as possible from a USB 3.0 connector and or device.
So to bring it back to Daniel's Pi. The board's antenna is fine, it measures at roughly seventy percent efficiency, and it's sitting millimeters from the PCB, usually inside a metal or absorbing case, and frequently right next to the USB 3.0 ports and whatever cable is plugged into them.
Which means the failure is environmental. And that has a real consequence for how you spend money. The fix may not be a new adapter at all. The fix may be separation.
That's the kind of conclusion that ruins a shopping trip.
So if the onboard radio's failure is environmental, what actually determines whether an external adapter succeeds? That's where the buying criteria get counterintuitive. Number one is not the radio.
Say it.
It's the driver. morrownr's golden rules read like a set of commandments. Prefer in-kernel drivers, plug and play, standards compliant, maintained upstream. Avoid multi-state adapters, the ones that present themselves as a CD-ROM or a flash drive first so they can load a Windows driver. And avoid multi-function adapters that combine Wi-Fi and Bluetooth.
Why the Bluetooth one? That sounds convenient.
His line is that Bluetooth will likely limit the Wi-Fi to USB 2 speeds. If you need Bluetooth capability, go get a separate Bluetooth adapter. Combining them sounds like a win and isn't.
The convenience tax.
And the chipset landscape is much narrower than buyers assume. Only three companies still supply USB Wi-Fi chipsets. MediaTek, AIC Semiconductor, and Realtek. Intel and Qualcomm-Atheros no longer supply modern USB-capable chipsets.
Intel, who wrote the white paper about the interference.
Intel, who left the USB dongle business. And for Linux, morrownr's recommendation is MediaTek. His assessment of Realtek is blunt enough to quote. "Am I a fan of how the Realtek USB team supports the Linux community? No."
That's a man choosing his words carefully by not choosing them.
The implication is what matters for a stability buyer. A worse radio with a good in-kernel driver can be the more reliable choice than a higher-spec adapter running an out-of-kernel driver. You are not buying the best radio, you are buying the best-supported one.
Second criterion. Power.
This almost never appears in marketing. On an SBC, the USB bus has a budget. morrownr's performance comparison lists heavy-load power draw. Alfa AWUS036ACS at two hundred seventy milliamps. The AWUS036ACHM and AWUS036ACM at three hundred eighty. The EDUP EP dash AC1605GS at five hundred twenty. And the Alfa AWUS036ACH at eight hundred milliamps.
Eight hundred milliamps on a Pi's USB bus.
Can cause brownouts and drops, especially with anything else drawing off the same bus. He uses the AWUS036ACM with a Pi 4B as an access point specifically because of this. His words, "the low power requirement makes it a very good match for Raspberry Pi hardware." That's a stability decision disguised as a spec choice.
What's the actual power budget on something like a Pi 4?
It's tight. The total across all USB ports is well under what a desktop provides, so a single adapter pulling eight hundred milliamps can be most of what you have before anything else is plugged in. Solder a keyboard or a bus-powered drive alongside it and you're asking for drops that look exactly like Wi-Fi problems. Which is how people end up replacing a perfectly good adapter.
Now the antenna physics, because this is where Daniel's suspicion about "high gain" claims gets answered.
It gets answered hard. Dan's Data, which is a long-running Australian tech site, put it this way about add-on Wi-Fi antennas. "Most add-on WiFi antennas are impossible. They can't exist. What's written on the box is contrary to physical laws."
That's not a hedge.
A three dBi antenna has a three dB, or twofold, gain advantage over a theoretical perfect isotropic radiator. And that theoretical radiator would need to emit twice the energy you put in. So a "gain" of three dBi is already at the edge of what physics allows without directing the energy somewhere.
So where does the gain come from?
From not radiating in all directions. That's the trick. The higher the gain of an omnidirectional add-on antenna, the wider the cones above and below the axis where it doesn't work well, or even at all.
The doughnut.
Core Electronics puts it well. As antenna gain increases, the doughnut flattens out. More signal pushed horizontally, less vertically. Which is great if your access point is on the same floor and terrible if it's upstairs. The gain you bought is signal you removed from somewhere else.
And the "high gain" buyer is usually putting the access point upstairs.
Usually, yes. RFI in the antenna business has a line about this. The laws of physics cannot be defeated, and without capture area there is simply no way to increase antenna gain. IoT UK goes further and calls antenna gain "one of the most abused marketing terms in the industry."
So what's a real number?
A standard dipole, the rubber duck on the side of most routers, is the two point one four dBi reference. And there's a common confusion between dBi and dBd, two different references, which lets manufacturers inflate numbers. For a fixed indoor LAN link, a modest two to five dBi antenna may serve you better than a nine dBi one, because the nine dBi one is carving nulls above and below it.
That's the exact opposite of what the packaging implies.
Completely opposite. Because the correct answer for your room depends on where the access point is, and the box doesn't know where your access point is.
Now the form factors, because Daniel asked specifically.
And here's the insight that reframes the whole purchase. Core Electronics makes the decisive RF point. With a USB extension cable, you can use several meters of cable to locate the antenna in the best possible position without incurring any RF signal loss, as you would with an antenna connected by RF coax cable.
Why is that true?
Because the signal is still digital in that cable. You're extending the USB bus, not the RF path. Once it becomes RF, at the antenna, coax losses matter enormously. In the USB domain, you're just moving the radio to a better address.
So the cabled form factor's real advantage is not the antenna. It's the separation.
The fancy-looking antenna on the end of a cabled adapter is almost the least important part of it. What you're buying is a way to put distance between the radio and the Pi's USB 3.0 ports and its metal case. That's the whole game.
Which loops right back to the Intel test.
Straight back to it. And morrownr's practical guidance on this is useful. Extension cables with cradles can be very useful, they let you position the adapter for best performance. But with a warning attached. Some adapters won't work with some extension cables and cradles, and the only way to know is trial and error.
Trial and error. Honest, at least.
He also covers right-angle USB adapters. Those can be very handy, especially on a Raspberry Pi or other small systems with horizontal USB ports, and he's never seen a compatibility problem with them. Which is a cheap way to change where the adapter points.
What does the placement guidance actually say?
Place antennas as high as possible above the ground, at least two to three meters, and try to get clear line of sight, accounting for the Fresnel zone, which is the football-shaped volume around the direct path where the signal wants to spread. And the Core Electronics line that pulls it together. Typical Wi-Fi stick antennas offer gains of a few dB, but the placement of the antenna can easily affect the end to end signal path by several tens of dBs.
Tens.
Tens. You are choosing between a few dB of antenna gain and tens of dB of placement. The antenna is the rounding error.
Let's put real numbers to the form factors, because Daniel asked how they differ in reliability.
There's a test from morrownr dated May thirty-first twenty twenty-one. Forty-five feet, through three walls, channel one forty-nine at eighty megahertz. Link quality out of a hundred, and signal level. The Alfa AWUS036ACHM, mt7610u chipset, single antenna, top of the list at ninety-three out of a hundred at minus forty-five dBm. The Alfa AWUS036ACH, rtl8812au, two antennas, ninety-one at minus forty-six. The EDUP EP-AC1605GS at eighty-four, minus fifty-one. The Alfa AWUS036ACM at seventy-nine, minus fifty-five. And the Netgear A6210 at the bottom, sixty-four out of a hundred at minus sixty-five dBm.
And the Netgear is the portable-looking one.
His note is that it likely appears at the end of the list because of its design. It's designed for portability, not long range. The tiny stub form factor is a portability product. It's not cheating you, it's doing a different job.
So that's the answer to the form-factor question. The stub isn't a worse version of the cabled one. It's optimized for a different thing entirely.
And here's the stability metric that ties all of it together, which is what I'd want Daniel to take away. morrownr's FAQ warns that a signal level weaker than minus fifty-two dBm may be at a level that can adversely affect jitter levels, and jitter disrupts the smooth flow of data.
Minus fifty-two.
He advises checking signal level before anything else. Not throughput, not link speed. Signal level. Because jitter is what makes an IoT link feel broken. The packets still arrive, they just arrive late, and anything that cares about timing falls apart.
So the number to chase is dBm, and the target is better than minus fifty-two.
Better than minus fifty-two with margin, ideally. And notice the test above. Only two of those five adapters cleared that bar in that particular situation. The others didn't, and no amount of throughput would have saved them.
So build the winning spec sheet. Daniel asked for it explicitly.
It doesn't exist as a published document, so here's the synthesized version. One. In-kernel Linux driver, ideally mediaTek chipset, because driver quality determines stability more than radio specs. Two. Single-function. Not Wi-Fi and Bluetooth combined. Three. Not a multi-state adapter that pretends to be a CD-ROM first. Four. Power draw in the two hundred seventy to three hundred eighty milliamp range, for SBC compatibility. Five. A cabled or cradle form factor, so you can physically separate the radio from the Pi's USB 3.0 ports and its case. Six. Modest antenna gain, two to five dBi, matched to where the access point actually sits, not the highest number on the shelf. And seven, a documented community track record.
Which is the morrownr short list criteria.
In-kernel driver, documented track record, currently purchasable. Those are his three tests.
So read your list back to me and notice what it's mostly made of.
It's mostly things the adapter doesn't do. It doesn't combine functions. It doesn't draw too much power. It doesn't depend on an out-of-kernel driver. It doesn't trap the antenna against the Pi's USB 3.0 ports. The antenna is almost the last item.
The best spec sheet for this use case is a list of absences.
And the physical joke underneath it is that 2.4 gigahertz has a half-wavelength of about six centimeters. Which is roughly the length of a Pi Zero. An antenna that size is sitting inside a device that small, next to a USB 3.0 port, inside a case, on a shelf, next to a wall.
Every one of those is doing damage.
Every one of them.
Hilbert: That all tracks. But the cable is what matters.
Go on.
Hilbert: I spent a couple of years doing installs where we were mounting small radios in bad places. Ceiling voids, plant rooms, back of a shop counter. And the thing I learned is that a long USB cable is the cheapest antenna you can buy. I used to keep a roll of the cheapest USB 2 extensions I could find in the van, specifically because they were long and thin and unshielded, which is exactly what you want for this. You tape the dongle to the top of a doorframe or a shelf bracket and run the cable back to the box. I fixed more flaky links that way than with any adapter swap I ever did.
Cheapest possible cable.
Hilbert: It was about the length, not the quality. I was chasing one fault for three weeks. Device in a back office, held a link fine all day, and every time somebody walked past the doorway it dropped. I swapped three different adapters through it. Never the radio. It was the antenna sitting against a steel door frame and a USB 3 port, and once I got it up on the top of the frame on a long cable, it never dropped again.
So you're saying the whole adapter question is downstream of that.
Hilbert: For most people, yes. The cheapest adapter on a long cable in the right place will beat the best adapter jammed into the port every single time. You two spent the episode building a spec sheet. I'd say the first line of the spec sheet should be a longer cable, and the second line should be somewhere better to put it.
And the cradles.
Hilbert: The cradles are the thing. Not the right-angle adapters, those are fine, I never had a problem with them. It's the cradles that fall apart. The plastic ones break at the pivot after a couple of years, and then the dongle hangs off the cable by its own weight. Get a metal one or skip it entirely and use tape, like I said.
Tape.
Hilbert: PVC tape, the good stuff, doesn't go gummy in a hot ceiling void. That's the whole trick. Tape the antenna to the doorframe, run the cable back, done. Then you can stop arguing about which adapter.
The winning spec sheet is a piece of tape and a longer cable.
Hilbert: That's the honest version.
That image of taping a dongle to a doorframe is probably the most honest summary of this whole topic. A cable and a better place to put it.
It makes a point that the research can't. We can establish the physics. Intel's paper tells you why the interference happens. The community tells you which adapters are supported. None of that tells you that the answer is often a roll of cheap cable and some tape.
Before we go. The cutting-room floor. One thing from the research that didn't fit.
The fresnel zone. The football-shaped volume around the direct line between two antennas. And what's striking is how small the practical margin is indoors. You can have clean line of sight, you can see the access point, and still lose signal, because something is intruding into the volume around that line, not the line itself. A door, a person, a filing cabinet. It's the reason a link that looks perfect on a diagram fails in a real room.
The honest open question is why the whole market still sells on speed and gain numbers. If the fix is separation rather than a new adapter, what would it take for a vendor to market a stability-first adapter honestly? "This one is boring and it will not drop." Good luck with that on a box.
The problem gets worse, not better. As SBCs get more capable, USB 3.0 becomes standard on more of them, and the interference problem scales with adoption. Which makes the community's trial-and-error knowledge base more valuable over time, not less.
Leave it here. The best Wi-Fi adapter for a Raspberry Pi may be the one you already own, plus a long cable and a better place to put it.
Thanks as always to Hilbert Flumingtop, our producer.
This has been My Weird Prompts. If you've got a prompt, send it our way. Email us at show at my weird prompts dot com. We'll be back soon.
