An official Pro Controller is a lot of money for a second pad, a kid’s pad, or a “let’s see if I even like gyro aiming” experiment. The budget tier exists for exactly those jobs — and it is also the tier where spec sheets lie by omission. This guide is led by the one brand with a licence and a paper trail, PowerA, and is blunt about what the whole tier gives up versus Nintendo’s pad, because a cheap controller that quietly lacks gyro is not a bargain for readers of this site.

The honest headline: what budget money doesn’t buy

PowerA: the defensible budget buy

PowerA is the budget tier’s anchor because it is licensed, widely distributed, and documented: wired models for the lowest spend, wireless models above them, all readable spec sheets. Browse the range via PowerA controllers — and apply the gyro rule model by model: some PowerA pads include motion controls, many of the cheapest wired ones do not, and no product-family reputation substitutes for the line on the specific box. Their charging gear is the same story of licensed-and-fine (PowerA charging docks).

Now the caveat this site is obliged to print, because we wrote the troubleshooting page: PowerA pads and BetterJoy recognition is a long-running mismatch — Windows may see the pad while BetterJoy never lists it, across many models and many years of reports. That doesn’t make a PowerA pad a bad PC controller; most work happily as ordinary wired or Steam controllers. It makes it the wrong purchase specifically for a BetterJoy gyro setup. If your plan is “cheap pad, Steam games, no motion,” buy with confidence. If your plan is “cheap pad feeding BetterJoy’s motion server,” the honest advice is to save toward the real thing instead.

The clone warning

Below the licensed tier sits the clone market: pads sold as “Pro Controller for Switch” with stock photos, invented battery figures and gyro claims that evaporate on arrival. Our tutorial on adding third-party controllers to BetterJoy exists because this can work — v7’s Add Controllers was built for non-original pads, and calibration values in the config file tame odd gyro and stick scaling. “Can work” is doing heavy lifting: Bluetooth IDs vary, gyro quality varies more, and when a clone misbehaves there is no vendor page, no firmware, and no issue thread that ends in a fix. Buy clones as experiments with return policies, not as equipment.

How to read a budget listing

Budget listings are written to be skimmed; read them like contracts instead. The gyro line is the whole game: “motion controls” or “6-axis gyro” named as a feature means the model claims it; silence means absence, however many racing-game photos surround the text. “Supports amiibo” never appears honestly at this tier — if it does, close the tab. Battery figures in milliamp-hours are unverifiable at purchase and wildly optimistic at this price; treat battery as unknown and prefer wired models when the number looks like the headline. Check the connection line too: “wireless” at this tier sometimes means a bundled 2.4 GHz dongle rather than Bluetooth — which may be fine at a desk, matters for BetterJoy (Bluetooth and USB are its native roads), and never appears in the title. Finally, look for a brand page that will still exist next year: firmware, manuals and a support address are the difference between a budget controller and a disposable one, and they cost the maker money — which is exactly why the clones skip them.

Wired versus wireless at this tier

The budget tier splits oddly: its wired models are its most honest products. A wired PowerA-style pad has no battery to degrade, no Bluetooth pairing to fight BetterJoy with, and latency that needs no apology — the cable is the feature. Wireless budget models spend their cost on the radio and battery, and the corners come out of the sticks and gyro instead. For a desk-bound PC player, that trade is usually backwards: take the wired pad and the better sticks. Wireless earns its premium one tier up, where the gyro roundup picks start. The exception is the couch — a cable across a living room is a trip hazard and a cat toy, and a mediocre wireless pad that reaches the sofa beats a good wired one that doesn’t.

The used-Pro alternative

The budget tier’s strongest competitor is not in the tier: a second-hand official Pro Controller, drift-tested, often lands near new-budget money and keeps every feature this site cares about — full gyro, first-class BetterJoy support, real sticks with a known repair path (our Hall-effect upgrade guide applies to it). Shop them via the used Pro Controller listings, and test on arrival: full circles on the calibration screen, centre still at rest, gyro steady in BetterJoy. A used pad that fails those tests goes back; a new clone that fails them just sits in a drawer.

Verdict, by job

• Second pad for guests and kids, Switch-first: a licensed PowerA wired model — cheap, tough, no battery to manage.
• Steam on PC, no gyro ambitions: PowerA wireless or any pad Steam reads natively; spend the saving on games.
• Gyro on PC is the point: skip the tier — new Pro Controller, a tested used one, or the native-gyro options in our gyro roundup.
• Curious and technical: a returnable clone plus the Add Controllers tutorial is a legitimate weekend project — priced as entertainment, not infrastructure.

All six guides in this series live in the buying guides hub, and the comparisons hub covers the software side of the same decisions. Budget money spent with open eyes is good money; budget money spent on a spec sheet’s silence is how drawers fill with almost-controllers.

PC players inherit a Switch controller ecosystem that console players built: docks that keep Joy-Cons alive between sessions, grips that fix small-controller ergonomics, cases that survive the trip between desk and couch. Not all of it matters at a desk — and some of it matters more on PC than it ever did on the console, because a PC setup splits its life between wired desk play and wireless everything else. This guide walks the accessories that earn their place, in the order we’d buy them.

Charging: the dock is a PC accessory too

A Joy-Con pair lives a harder life on PC than on a Switch: there’s no console slot recharging them between sessions, so they die mid-game unless you build the habit for them. A Joy-Con charging dock that holds all four halves — most PC households end up with two pairs — turns charging into parking. PowerA’s licensed docks are the tidy version of the same idea (PowerA charging dock listings), and the Pro Controller needs nothing fancier than its cable and a home; if you want it parked rather than coiled, any stand that fits its shell works — the accessory logic is “a place it always returns to,” not a logo. One PC-specific note: if your controllers start dropping connection as they run low, that’s a symptom we know well — low battery does strange things to Bluetooth behaviour, which is half of what our low battery notification guide is really about.

Grips and thumbsticks: feel first, hardware later

The cheapest real upgrade in this entire hub is a cap. Joy-Con and Pro sticks wear smooth, thumbs slip at full tilt, and tall replacement caps add leverage that makes fine gyro corrections easier. Start with ordinary thumb grips; step up to KontrolFreek thumbsticks if you play shooters and want the taller, dished profile — they’re the precision end of a two-minute, fully reversible mod. Hand grips that bulk out a single Joy-Con help the split-hand style from our single Joy-Con guide survive longer sessions. Now the honesty paragraph, because this site runs a ladder: caps fix feel, not drift. A wandering centre is a dying potentiometer, and the rung after caps is the Hall-effect module swap in our GuliKit upgrade guide — caps first because they’re cheap and reversible, sticks later because they’re neither.

Cases and cables: the unglamorous multipliers

A Pro Controller case sounds like a console accessory until your pad starts travelling — to a friend’s PC, a tournament, a laptop bag. On PC the case has a second job: it’s where the cable lives, so the pad and its lead never separate. The cable itself deserves a line: for wired play you need a USB-C cable that carries data, and a surprising number of pretty braided cables in drawers are charge-only. A known-good data cable (USB-C cables) is both the lowest-lag way to play and the diagnostic that settles Bluetooth arguments — if it works wired, the radio is your problem, and our Bluetooth adapter guide is the fix. A spare cable also feeds the placement trick from that guide: dongle on an extension, out from behind the case.

Controller grips: the Joy-Con comfort fix

Bare Joy-Cons are an ergonomic compromise — thin, flat, and tiring over a long session, especially held singly. Grip shells and comfort grips add the palm swell the Joy-Con left out, and for PC players they solve a specific problem: the split-hand style that makes Joy-Cons special on PC (one in each hand, arms wherever you like) only stays comfortable if each half sits securely in the hand rather than being pinched. A grip with a bit of texture also stabilises gyro aiming — small rotational slips read as aim noise. Skull & Co.’s grip-and-case ecosystem is the name most readers will meet first in this category; it reaches this site through ordinary marketplace listings (the brand runs no affiliate programme with us), and the selection logic is the same as everywhere in this guide: fit for your exact controller generation, nothing covering the sticks or the Sync button, and nothing so bulky it defeats the charging dock you just bought. Check grips and shells alongside thumb grips — the two are usually sold in the same aisle and solve adjacent problems.

The PC player’s desk audit

Before buying anything in this guide, audit what your setup already does. Is there a place controllers return to, or do they migrate? Is the cable in the drawer data-capable — test it by wiring the pad and seeing whether Windows lists the controller, not just a charging light. When a Joy-Con dies, do you notice in the menu or mid-boss? The accessories that matter are the ones that close the gaps your audit actually finds: dock for the migration problem, cable for the data problem, caps for the slipping-thumb problem. PC players, unlike console players, also have a software witness for most of these — BetterJoy’s controller icons change colour with battery state, so a week of watching them tells you whether charging discipline or charging hardware is your real gap.

What to skip

Skip decorative shells and skins for controllers you use with gyro — anything that adds thickness over the shell does nothing for motion and can interfere with grip comfort. Skip “charging grips” that promise to extend Joy-Con battery with mystery cells; a dock and a rotation habit solve the problem with branded lithium. And skip buying accessories for a controller whose sticks already drift: sequence matters — diagnose on the test screen, climb the ladder (caps, then Hall kit, then replacement in the buying guides hub), and accessorise the controller you’re keeping.

A sensible basket, by player

Everything above assumes the controller itself was the right buy — if you’re still deciding that, start with the gyro controllers roundup and the budget controllers guide, then come back and accessorise.

Stick drift is the tax every Joy-Con and Pro Controller owner eventually pays: the camera creeps, menus scroll themselves, and BetterJoy faithfully reports a stick that is lying to it. Software can hide mild drift — recalibration and a wider deadzone in the BetterJoy config file — but it cannot un-wear a worn stick. GuliKit’s Hall-effect replacement kits are the fix that addresses the mechanism itself. This guide explains what they change, what the install honestly involves, and when you should not do it.

Why sticks drift, and what Hall effect changes

A stock Nintendo stick is a potentiometer: a contact wiper slides across a resistive track thousands of times a session, and the track wears unevenly. The worn centre stops reporting a clean zero — that is drift. A Hall-effect stick replaces the wiper with a magnet and a magnetic sensor: position is read without contact, so the specific wear that causes classic drift is engineered away. It does not make a stick immortal — springs tire, dust exists, and a kit can be faulty — but it removes the #1 failure mode. GuliKit built its name on exactly these kits, sold for Joy-Con and for the Pro Controller as replacement modules.

Before you open anything: the ladder

Work the cheap rungs first, because some “drift” isn’t wear. One: recalibrate the stick in Windows’ game controller panel and in the Switch’s own settings if you use both. Two: clean around the stick base — grit under the cap mimics drift. Three: set a modest deadzone; our config guide covers BetterJoy’s side of it. Four: if the feel is the problem rather than the centre — worn smooth caps, slippery thumbs — a set of thumb grips or KontrolFreek thumbsticks is a two-minute, reversible change. Only when a cleaned, recalibrated stick still wanders on the test screen is the module itself the diagnosis — that’s when this kit earns its money. The whole ladder is organised in the buying guides hub.

The kits and the install, honestly

Kits: GuliKit Hall-effect kit for Joy-Con and GuliKit Hall-effect kit for Pro Controller. You will also want a small electronics screwdriver set with a tri-wing bit for Joy-Con — using the wrong bit on those screws is how a repair becomes a replacement.

The warnings, in plain language

Warranty: opening a Joy-Con or a Pro Controller voids Nintendo’s warranty on that controller. If yours is still covered and drifting, the correct first move is Nintendo’s repair channel, not a screwdriver — several regions repair Joy-Con drift out of goodwill policies as well; check before you open. Risk: the ribbon cables and their tiny latches are the fragile part of this job; a torn ribbon turns a stick swap into a dead controller. Work on a clear table, photograph each layer before lifting it, and keep the original modules — if a kit stick misbehaves, the old one can go back. Expectations: a Hall kit fixes centre drift from wear. It does not fix a stick that disconnects (a Bluetooth/board problem — see our lag fix), a damaged stick cap, or drift caused by debris you haven’t cleaned out yet.

After the install: calibration is not optional

A fresh Hall module reports a fresh centre, and neither the Switch nor Windows knows it yet. Run the stick calibration in the Switch’s system settings for console use, and the Game Controllers calibration in Windows for PC use, before you judge the result — an uncalibrated Hall stick can look off-centre in exactly the way that makes people declare a good kit faulty. In BetterJoy, finish the job: if you widened the deadzone to survive the old stick, walk it back down in small steps using the config file or the emulator’s own input settings, testing on a calibration screen between steps. The end state you’re buying with this kit is a stick that sits at a true zero with a minimal deadzone — most of the precision gain is in that pairing, not in the module alone. Then play something with a free camera for ten minutes; slow, constant creep is drift, and if it’s gone, you’re done.

What the box doesn’t include, and sourcing honestly

The kits are stick modules and little else: the tri-wing and Phillips screwdrivers, a spudger for shell clips, and a tray for the nine tiny screws you are about to meet are yours to supply — a generic precision electronics set covers all of it and serves every future repair. Buy kits from listings that name GuliKit as the maker and show the module, not from anonymous “Hall joystick for Switch” listings that borrow the vocabulary; the genuine article’s whole value is in its sensor and its mechanical tolerances, which is precisely what a lookalike saves money on. GuliKit has no direct affiliate programme with this site — the links in this guide route through marketplace listings, and the guidance above about which listing to trust applies to ours too: check the seller, not just the title.

Kit, or a new controller?

Do the rough maths per controller. For Joy-Con, a pair of kits plus tools usually lands well below a new Joy-Con pair, and you keep the shell and buttons you know. For a Pro Controller bought years ago, the kit competes with a drift-checked used Pro Controller and with going Hall-native next time via the pads in our Pro vs 8BitDo Ultimate comparison. If more than the sticks is tired — battery, buttons, shell — replace the controller and keep your time. If the sticks are the only problem, the kit is the honest fix, and it’s the one upgrade in this hub that makes a controller measurably better than the day the drift started.

This is the head-to-head most Switch-owning PC players eventually face. The Switch Pro Controller is the pad BetterJoy was built for — but it was designed for a console, and it shows its age in the sticks. The 8BitDo Ultimate line was designed for exactly this cross-device life — but its gyro story on PC is more conditional than the box suggests. Neither wins everything; the right choice depends on where you play and how much mapper software you’re willing to run.

Side by side

Connection and the gyro path

The Pro Controller’s gyro reaches PC games through software, and the software is mature: BetterJoy exposes the pad as XInput or DS4 and simultaneously serves motion over Cemuhook UDP, which is why emulator players keep choosing it (the setup is our Pro Controller connection guide). Steam Input reads the same pad natively if your library lives in Steam. Either way, the gyro data itself is the full, original stream from Nintendo’s hardware.

The Ultimate’s gyro is real but conditional, and honesty requires the long version: 8BitDo sells several Ultimates, and the gyro is tied to operating mode. In the modes aimed at PC XInput, the guaranteed payload is buttons, sticks and vibration — the same limitation we documented for the 8BitDo adapter. Pair a Bluetooth variant in Switch mode to Steam and gyro aiming works; expect to route emulator motion through Steam or go without. If your buying reason is “gyro in Cemu/Dolphin without fuss,” the Pro Controller plus BetterJoy remains the straighter line — our gyro controllers roundup scores the whole field.

Sticks, drift and the long game

Here the Ultimate strikes back. The Pro Controller’s sticks are potentiometer-based: a wiper rubs a resistive track, the track wears, and the centre starts to wander — the same physics as Joy-Con drift, on a slower clock. When it happens, your options are the repair ladder: recalibrate, widen the deadzone in the BetterJoy config, or fit a Hall-effect replacement as in our GuliKit upgrade guide. Hall-effect sticks read a magnet instead of a rubbing contact, so that specific wear mechanism is designed out. Many Ultimate variants ship with them; that is a genuine, structural advantage — just verify the variant, because the entry models in any family are where features quietly exit.

Feel, layout and the prompt problem

Both are comfortable, conventional pads; the difference that hits daily is letters. The Pro Controller prints Nintendo’s layout, which matches a Switch and most emulator front-ends, but PC games overwhelmingly prompt with Xbox positions — the A/B swap is a setting away in BetterJoy, though the printed letters never change. The Ultimate’s Xbox-style positions end that low-grade confusion in PC games and reintroduce it on the Switch. Pick based on which screen you look at more.

Battery, build and daily life

Daily-life differences are smaller but real. The Pro Controller is the pad your Switch already knows: it wakes the console, pairs back without ceremony, and its battery life is famously long — Nintendo’s own figure is around 40 hours, and in practice it is the controller people forget to charge because they so rarely need to. The Ultimate line answers with convenience features of its own — charging docks bundled with several variants, back buttons on much of the line, and profiles you can tune in 8BitDo’s software rather than in each game. Neither is fragile; both survive bags and drops at hobbyist rates. The deciding daily-life factor is usually the desk: if one pad must serve a Switch on the TV and a PC at the desk, the Pro Controller’s double life is seamless and the Ultimate Bluetooth variants imitate it well; if the Switch belongs to someone else in the house and the PC is yours alone, the Ultimate’s PC-first conveniences stop being imitations and start being the point.

The decision in one minute

Ask two questions. Do you feed gyro to an emulator’s motion server — Cemu, Dolphin, a DSU client? If yes, the Pro Controller, because BetterJoy’s path is complete and nothing else in this comparison offers it. Is your PC gaming entirely Steam, and is stick drift your actual pain? Then the Ultimate, in a Hall-effect variant, bought by exact model number. Every other difference — letters, docks, back buttons — is preference, and preferences are allowed to decide once the two structural questions are answered.

Price and verdict

We don’t print prices here because both move with sales and region — check the live listings for the Pro Controller and the 8BitDo Ultimate, and weigh a drift-tested used Pro Controller before paying new money for either. The pattern across our readers: emulator-first and Switch-owning players end on the Pro Controller, because BetterJoy’s DSU path is the deepest gyro integration on PC. Steam-first players who never touch an emulator’s motion settings, and anyone whose Pro Controller has already started to drift, are better served by the Ultimate — with the variant caveat tattooed on the decision. Both answers are in the buying guides hub, alongside the budget tier if both of these are more pad than you need.

Gyro aiming is the reason most readers of this site own a Switch controller in the first place: once you’ve aimed with motion in an emulator or a Steam game, a plain Xbox-style pad feels like it’s missing a sense. But “has gyro” on a product page hides a lot of variation — in how the gyro reaches your PC, in which software can read it, and in what quietly goes missing along the way. This roundup compares the four realistic routes to gyro on PC, with the caveats printed in the same size as the praise.

The contenders, honestly compared

The incumbent: Switch Pro Controller

The Pro Controller remains the reference gyro pad for this site’s readers because it is the one BetterJoy was built around: full gyro through the Cemuhook UDP server for emulators, gyro-to-mouse for desktop games (see using gyro as a mouse), and ordinary XInput everywhere else. If you own a Switch, it is also already in your house. Buying one for PC alone still makes sense — check current pricing on the Pro Controller listing, and consider a checked second-hand unit via our used Pro Controller search if you know how to test for stick drift. What it does not give you on PC: amiibo/NFC (the reader stays silent), the Joy-Con’s IR camera, and true HD Rumble fidelity — you get good rumble, not the Switch’s waveform-level effects.

The PC-native escape: 8BitDo Ultimate

8BitDo’s Ultimate line is the “stop mapping, start playing” option: a PC-shaped controller with its own software, and — on the variants that include it — gyro. It is also the easiest roundup entry to buy wrong. The Ultimate family spans Bluetooth, 2.4 GHz and wired models with different mode switches, and gyro behaviour changes with both model and mode; the adapter lesson from our 8BitDo adapter comparison applies to the pads too — XInput mode is about buttons, sticks and vibration, while gyro generally lives on the Switch-mode side. If your games run through Steam, that can work well; if you need a DSU motion server for an emulator, BetterJoy plus a Nintendo pad is still the straighter road. 8BitDo sells through marketplaces rather than any affiliate programme of ours — the Ultimate listings and the Pro line listings are the places to compare variants side by side.

The licensed budget route: PowerA

PowerA makes officially licensed Switch controllers at friendlier prices, and for Switch-first households they’re a sensible second pad. For gyro-on-PC specifically, treat the brand as a minefield of near-identical models: some include motion controls, many don’t, and the box copy is the only reliable witness. There is a second caveat from our troubleshooting files — BetterJoy’s PowerA recognition checklist exists because many PowerA models never appear in BetterJoy at all, even when Windows sees them. A PowerA pad is a fine purchase for what it is; it is not the pad to buy for BetterJoy gyro. Listings: PowerA controllers.

The PlayStation-side option: DualSense

If your gyro gaming happens in Steam, the DualSense is a first-class citizen: Steam Input reads its gyro natively, and DS4Windows can expose it (including a DSU server) to emulators. It adds a touchpad the Nintendo pads lack. It is here for completeness, with one labelling duty: BetterJoy does not support it, and nothing on this site’s download page will make it work — that job belongs to Steam or DS4Windows, which we compare in BetterJoy vs DS4Windows.

How to verify a gyro claim before you buy

Because “gyro” is the word this whole page turns on, here is the three-minute check we apply to any controller not listed above. First, find the manufacturer’s own spec page — not the marketplace listing — and look for motion controls listed as a feature of the exact model number, not the product family. Second, ask the mode question: in which connection mode does the gyro work, and does that mode work on PC, or only when talking to a Switch? A gyro that only exists in Switch mode can still serve you through Steam, but it will not feed an emulator’s motion server the way BetterJoy’s does. Third, search the model plus “gyro” in the support forums of the software you actually run — Steam, your emulator, this site’s troubleshooting hub — because the gap between a sensor existing and your stack reading it is where purchases go wrong. A controller that survives those three checks is a gyro controller; one that fails the second is a Switch accessory with a PC hobby.

The caveats that apply to every row

No controller in this roundup brings NFC/amiibo reading or the Joy-Con IR camera to PC — those features have no path through BetterJoy, Steam Input or DS4Windows as of writing. Rumble everywhere is a translation, not the original HD Rumble. And every wireless route inherits the Bluetooth rule: your radio and its drivers are part of the controller, whether you paid for them separately or not. Decide by ecosystem first (Nintendo pads for emulator-plus-Switch life, PC-native pads for Steam-only life), then by variant-level specs — and use the buying guides hub and the 2026 decision guide to sanity-check the choice. If you’d rather shop the whole category at once, start from gyro controllers for PC.

A Bluetooth adapter is the least glamorous purchase in a Switch-controller-on-PC setup, and the one most likely to decide whether the whole thing feels great or quietly miserable. BetterJoy’s own issue tracker tells the story: Joy-Con lag and dropouts are reported again and again on PCs whose only crime is an ageing internal Bluetooth radio or an outdated Intel Bluetooth driver, while the same controllers behave perfectly through a decent external dongle. This guide explains when an adapter is the actual fix, what to look for, and — just as important — when you don’t need one at all.

Why the adapter matters for Joy-Con and Pro Controller

Switch controllers are chatty Bluetooth devices. A paired set of Joy-Cons is two separate radios streaming sticks, buttons and gyro data, and BetterJoy polls them continuously to feed its XInput/DS4 emulation and the Cemuhook motion server. Weak radios show up as input lag, jitter, one Joy-Con dropping while the other survives, or gyro that feels drunk. In the BetterJoy repository, the maintainer has noted that Joy-Cons “don’t like” some Intel Bluetooth setups, one long thread traced problems to Intel Bluetooth driver versions below 22.180.0, and several users fixed persistent lag by moving to an external USB Bluetooth dongle. Our Joy-Con Bluetooth lag fix walks through the software side of that diagnosis; this page is the hardware side.

Buying criteria that actually matter

The short list, by situation

We route these through one category link because models churn constantly and a named chipset with live driver support matters more than any single SKU: Bluetooth 5.x USB adapters for PC. Choose within it by situation:

• Desktop PC with no Bluetooth, or pre-2018 internal Bluetooth: a current Bluetooth 5.0+ dongle from a recognisable networking brand. This is the default buy and the one that resolves most “Joy-Con lag” reports.
• PC tucked behind a TV or under a desk: a dongle with an external antenna, or any dongle plus a short USB extension cable (a plain USB cable drawer item — the extension trick works with the cable you may already own) so the radio sits in the open.
• Very price-sensitive, or outside Amazon’s easy reach: marketplace dongles via AliExpress accessories can be fine, but apply the criteria table ruthlessly — named chipset, real driver page — because the no-name end of that market is exactly where the bad experiences come from.

A word about the very cheap end

There is a floor below which a dongle stops being a bargain. The ultra-cheap Bluetooth 4.0 sticks that ship with a mini CD and no manufacturer page fail this audience in predictable ways: drivers that predate Windows 11, radios that hold one controller happily and drop the second Joy-Con, and no firmware or support path when an update breaks them. They also predate the connection behaviour modern controllers expect. If a listing cannot name its chipset, it is telling you what it is. Spending slightly more once — on a current, named, driver-supported adapter — is cheaper than buying the cheap one twice, and it keeps the troubleshooting honest: once the radio is above suspicion, any remaining problem is genuinely in software, where our guides can help.

When you do NOT need an adapter

Plenty of readers can skip this purchase entirely. If your laptop or motherboard has a modern Intel or Qualcomm Bluetooth radio and its drivers are current, update the drivers first — the sub-22.180.0 Intel driver issue costs nothing to fix. If you play at a desk, a wired USB connection to the Pro Controller removes Bluetooth from the equation completely and is the lowest-lag option we cover in connecting a Pro Controller to PC. And if only one controller ever connects and it already behaves, an adapter solves a problem you don’t have. Buy one when the symptoms match — lag, drops, one Joy-Con losing sync — not as a ritual upgrade.

Quick questions

Will a Bluetooth 5.x adapter reduce lag versus my motherboard’s Bluetooth? If your current radio is old, badly placed, or running the problematic older Intel drivers, very likely yes — that is the pattern in BetterJoy’s issue reports. If your current setup is modern and already stable, expect no difference.

Can one adapter run a Pro Controller and two Joy-Cons? That is the normal case BetterJoy’s own wiki describes — a decent adapter sustaining three to four connections. Radios that fall over usually fail earlier, with a single Joy-Con dropping first.

Does the adapter replace BetterJoy? No. The adapter is only the radio; BetterJoy still does the translation to XInput/DS4 and the gyro server. Hardware adapters that replace the software layer entirely are a different product class — we compare one in BetterJoy vs MAGIC-NS 2.

Setting a new adapter up with BetterJoy

Install the adapter’s driver, then disable the old internal Bluetooth radio in Device Manager so Windows cannot pair your controllers back onto the weak radio — running two radios is a classic cause of “it still doesn’t work.” Remove the existing controller pairings, re-pair through the new adapter (hold Sync on the controller, pair in Windows settings), then start BetterJoy. If a controller was previously hidden by the old setup, our double input fix and the connection guides in the tutorials hub cover the recovery steps. More buying decisions — controllers, sticks and accessories — live in the buying guides hub.

The real repository, by the numbers

Open the official BetterJoy repository on GitHub

Why the numbers matter: a fake “official” page can copy a logo and a description, but it cannot copy a six-year-old public repository with its issue history, its 596-issue backlog, and its download counters. If the page you’re on can’t take you to this repo, it isn’t a source — it’s a funnel.

Reading the Releases tab like a regular

The Releases tab is the only download shelf. Each release has a version tag, a date, the author’s notes, and one asset: for v7.1, the single file BetterJoy_v7.1.zip. Everything you need follows from that shape:

• One asset per release. If a “release” offers installers, multiple EXEs, or architecture choices for v7.1, you’re not looking at the real thing — v7.1 ships one combined ZIP.
• Trust the notes, all one line of them. v7.1’s entire changelog is the comma-decimal config fix; our version history reproduces the real milestones. Feature lists longer than the author’s own are marketing fiction.
• Dates are load-bearing. A “BetterJoy release” dated after November 2021 cannot be from this repository’s author line. Which brings us to the fork.

“But there’s no hash on the release page” — correct, and here’s the workaround

GitHub displays a SHA-256 digest next to release assets, but Davidobot’s older releases predate that being filled in — the v7.1 page shows no digest. Absence of a published hash is not a reason to skip verification; it’s a reason to use a measured one. We downloaded the asset from the official release and hashed it: BetterJoy_v7.1.zip, 4,438,028 bytes, SHA-256 a9ffe5bb14b05e775f34f9eeff41fca89a350d49252eedae1e330e88952e7f36. Our safety guide has the two-minute PowerShell check. Alternatively, skip third-party files entirely and pull the asset through our direct link to the official v7.1 release file — the bytes come from GitHub itself.

The v8 puzzle: the fork is real, the label is what lies

Here’s the confusing part, stated plainly: a genuine, maintained community fork — d3xMachina/BetterJoy — legitimately uses v8.x version numbers (currently v8.5.0a). It is a real open-source project, on GitHub, under a different owner’s name. So “BetterJoy v8” is not automatically a scam — but any page that attributes v8.x to Davidobot, or presents it as the official continuation without naming the fork’s owner, is lying about provenance, and a site careless with provenance is careless with files. The tell is always the repository owner in the URL: Davidobot = original (ends at v7.1); d3xMachina = the community fork (v8.x). Anyone else’s name = neither.

Using Issues and the Wiki without drowning

Two parts of the real repository are worth knowing beyond Releases. The Wiki carries the project’s own FAQ and Problems page, its settings descriptions, and its notes on coexisting with Steam — written for the v7 era, and still the first place our troubleshooting guides check against. The Issues tab holds the project’s full support history: 596 open issues as of October 2026, including the famous ones (the Duplicate timestamp enqueued flood, controllers not detected, PowerA recognition threads running from 2019 to 2025). A dormant repo’s issue tracker is read-only in practice — new reports rarely get maintainer replies — but as an archive of real error strings and real fixes it is unmatched, and its age is itself a provenance signal no fake site can reproduce.

Red flags of fake BetterJoy sites

• An installer. Real BetterJoy is a ZIP with an EXE inside. “Setup wizards,” downloader stubs, and browser extensions are wrappers monetising your click.
• “Official v8/v9 by the original author.” Disproven above — check the repo owner, always.
• Invented changelogs and ratings: feature bullets for v7.1 beyond the comma fix, star ratings with no source, “VirusTotal 0/70” badges that link nowhere.
• Requests to disable antivirus, pay, or “unlock.” The real software is free, MIT-licensed, and its occasional antivirus warnings are a known category effect (explained in the safety guide) — nobody legitimate asks you to switch protection off.
• Switch 2 editions. No BetterJoy, from either line, supports Switch 2 controllers; see the honest answer before downloading anything with that label.

Frequently asked questions

Is this site the official BetterJoy page?

No — and we say so on our About page. We are an unofficial resource that links to the official repository and measures its files; the only official presence is Davidobot’s GitHub. A site claiming to be official while not being that repo is the reddest flag on this page.

Why does GitHub show the license as “Other”?

The repository’s LICENSE file bundles the MIT text with third-party license sections (HIDAPI and others), which GitHub’s automatic classifier labels “Other.” The license text itself is MIT; read the file, not the classifier.

Where should I actually download from?

The repo’s Releases tab — or, identically, our download page, whose primary button is the official GitHub asset and whose mirror is labelled as a mirror. Verify with the hash, and you’re done.

More in the Versions & Trust hub.

Step 1: release your controllers before touching anything

While BetterJoy is running, it adds connected controllers to HIDGuardian’s list of affected devices — which is precisely why they “disappear” for other software. Release them first, while the machinery is still intact:

1. Open BetterJoy one last time, with your controllers connected.
2. In your browser, go to http://localhost:26762/ — the HidCerberus page served locally by the HIDGuardian setup.
3. Under Currently affected devices, remove every entry.
4. Close BetterJoy completely (check the system tray; it may be minimised there rather than closed).

Skipping this step is the number-one cause of “I uninstalled BetterJoy and now nothing sees my Pro Controller.” (Newer BetterJoy versions offer an option to remove affected devices at shutdown, which does this for you — but verify on the localhost page anyway.)

Step 2: uninstall the HIDGuardian layer (if you installed it)

If you ran the driver installers from the v7.1 package, you have HIDGuardian and its HidCerberus service. Inside your extracted BetterJoy folder, open Drivers\HIDGuardian\ and run “HIDGuardian Uninstall (Run as Admin).bat” — right-click, Run as administrator. Use the bundled uninstaller rather than deleting driver files by hand: filter drivers removed out of order can take other input devices with them, which is a much worse afternoon. If you later plan to install the community fork, this step is doubly important — its HidHide must never coexist with HIDGuardian.

Step 3: uninstall ViGEmBus from Windows Apps

ViGEmBus was installed by MSI, so it removes like a normal program:

1. Open Settings → Apps → Installed apps (or the classic Control Panel → Programs and Features).
2. Find ViGEmBus (listed as the Nefarius Virtual Gamepad Emulation Bus driver), choose Uninstall, and complete the wizard.
3. If you later installed the standalone ViGEmBus 1.22.0 from its author’s GitHub, the same entry removes it.

Note what this does not affect: other programs that use ViGEmBus (DS4Windows and friends) depend on it too. If you keep those, keep the driver — removing BetterJoy does not require removing ViGEmBus, and our ViGEmBus repair guide covers reinstalling it if something else breaks.

Step 4: restart, then clean the leftovers

1. Restart Windows. Driver and service removals only fully land after a reboot, and several “still broken” stories are just this step skipped.
2. Delete the extracted BetterJoy folder and its BetterJoyForCemu.exe.config — that file holds all your settings, so if you might return, copy it somewhere first; deleting it is what makes the removal “clean.”
3. Check for remnants: in Device Manager, enable View → Show hidden devices and look under Human Interface Devices and Game controllers for greyed-out BetterJoy-era entries you no longer use; remove only entries you recognise as the virtual devices.
4. If a HidCerberus service entry somehow survived the batch file, the recovery guide’s steps clear it — don’t go deleting service entries from the registry by hand.

Step 5: re-pair your controllers fresh

Windows remembers pairings that were made under the old hiding layer, so give it a clean start: in Settings → Bluetooth & devices, remove the Pro Controller / Joy-Cons, then pair again (hold the sync button on top of the controller until the lights run). From here the controller belongs to Windows and whichever tool you use next — Steam Input, another mapper, or a fresh BetterJoy install from the download page — with no ghost of the old setup.

Verify the cleanup

Before you call it done, run three quick checks. First, connect your controller and open the Windows game controller panel (joy.cpl): you should see only the physical controller (and any virtual devices belonging to tools you kept) — no BetterJoy-era Xbox 360/DS4 entries lingering from the old setup. Second, restart once more and confirm nothing reappears; a virtual controller that resurrects itself means a driver package is still installed and Step 3 needs a second look. Third, open whichever program you actually use the controller with and confirm buttons register — the entire point of the careful order above is that this check passes the first time. If it doesn’t, the failure is almost always a controller still on the affected-devices list, and the recovery guide, not a reinstall, is the fix.

Checklist

Frequently asked questions

There is no BetterJoy entry in Installed apps. Is that normal?

Yes. BetterJoy is a portable program — you extracted a ZIP, so there is nothing to “uninstall” for the app itself. The Installed apps entries belong to its drivers (ViGEmBus), which is why this guide is mostly about them.

My controller vanished from everything after I uninstalled. What now?

That’s the skipped Step 1: the controller is still on HIDGuardian’s affected-devices list. Follow the localhost:26762 recovery guide — the fix is releasing it there, not reinstalling drivers at random.

I’m switching to the fork. Is this guide still the right prep?

Yes — run Steps 1–2 and 4–6 (you can keep ViGEmBus, since the fork bundles the same final version), then install the fork per the fork guide.

More in the Versions & Trust hub and the troubleshooting hub.

Why it can’t work: a different protocol, not a new model number

The original Joy-Cons and Pro Controller present themselves to Windows as standard Bluetooth HID gamepads — unusual in places, but readable, which is the entire foundation BetterJoy (and Steam Input, and every other mapper) is built on. The Switch 2 controllers are not standard HID devices. Reporting from the driver-development community has established that they use a custom BLE (Bluetooth Low Energy) GATT protocol, and the Switch 2 Pro Controller stays silent until it receives a proprietary activation sequence from the host. A PC that doesn’t send that sequence gets nothing — no buttons, no sticks, no gyro.

Even the identifiers are all new: Joy-Con 2 (R) is 057e:2066, Joy-Con 2 (L) is 057e:2067, and the Switch 2 Pro Controller is 057e:2069 — none of which appear in BetterJoy’s device handling, because none of them existed when it was written. There is no “add the PID and it works” fix; the gap is the protocol underneath.

The symptom everyone Googles

If you’ve tried, you already know the pattern: Windows Bluetooth settings may discover the controller, pairing may even appear to succeed — and then nothing. No input anywhere, BetterJoy shows no device, games see nothing. That is the activation problem above, not a broken controller and not a BetterJoy bug. One more warning from the community guides: repeatedly forcing pairing attempts can trigger a cooldown in which the controller refuses connections for several minutes. If yours went quiet after many retries, leave it alone for a while rather than concluding it’s bricked.

What Switch 2 owners can actually do on PC today

Steam, wired, in beta

The one relatively official path: Valve added Switch 2 Pro Controller support over USB to the Steam Client Beta (late November 2025). The feature was at one point disabled and, per Steam’s January 2026 update notes, re-enabled — beta-channel software behaving like beta-channel software. Two limits to keep in view: it is wired only (Bluetooth is still not an official path for these controllers on PC), and Valve’s wording covers “Switch 2 controllers” without itemising Joy-Con 2 support — Pro Controller over USB is the verified case, Joy-Con 2’s full status in Steam is not officially confirmed feature by feature. If you go this route, our guide to BetterJoy and Steam coexisting explains the one-translator-per-game rule that keeps Steam Input setups clean.

Community projects: experimental, labelled as such

Developers are reverse-engineering the protocol in the open. Names you will encounter include connectyourpro (a Windows community tool focused on the Pro controllers, with Bluetooth support its own author describes as experimental) and Procon2Tool (a web-based workaround discussed in the Steam community). A Valve-commissioned driver has also landed in the Linux kernel line — USB only, no Bluetooth yet. All of this is promising, none of it is BetterJoy, and none of it comes with guarantees: no promise of gyro, rumble, or stability, and quality will vary month to month. We label these experimental deliberately, and we don’t offer downloads for them.

The option nobody likes: wait

Protocol reverse-engineering takes time, and official wireless support may or may not arrive. Anyone selling you a “BetterJoy Switch 2 Edition” download today is selling a fiction — see the red flags in our safety guide.

A note on the Switch 2 GameCube controller

The same November 2025 Steam beta that added wired Pro 2 support also improved the GameCube side of the family — Valve’s notes covered the GameCube adapter in Wii U mode with rumble on Windows — and the Switch 2 GameCube controller carries its own new device ID (057e:2073). We flag it separately because its PC status is even less itemised than the Pro 2’s: treat it as “mentioned in the same beta wave, not individually verified here,” and don’t buy one for PC use on the strength of a headline. The pattern of this whole page applies: with Switch 2 hardware, only believe a PC feature when a primary source names the exact controller and the exact connection.

What still works perfectly

Everything BetterJoy ever supported still works: the original Switch Pro Controller, Joy-Cons and Switch SNES controller pair with a PC and map through BetterJoy exactly as documented in our tutorials, and the community fork covers the same original family (plus NES/N64 pads). If you own both console generations, your Switch 1 pads remain your PC pads; the Switch 2 pads are, for now, console-only except for the wired Steam beta above. And if you’re deciding what your setup actually needs in 2026, the decision guide walks the scenarios without the nostalgia.

Frequently asked questions

Will a future BetterJoy update add Switch 2 support?

The official line has been dormant since 2021 and shows no sign of a Switch 2 release; the community fork hasn’t announced one either, and the protocol work is being done by separate projects. Treat any date or promise you read elsewhere as speculation.

Can Joy-Con 2 work over USB instead?

Joy-Con 2 has no wired data mode for PC play in the verified sources — the wired Steam path applies to the Switch 2 Pro Controller. Don’t buy cables expecting otherwise.

My Switch 2 Pro Controller pairs but sends no input. Is it faulty?

Almost certainly not: pairing without the proprietary activation sequence produces exactly that symptom. Test the controller on the Switch 2 itself; if it works there, it’s the PC protocol gap described above.

More version and trust answers live in the Versions & Trust hub.

What we verified (October 2026)

Two of these rows matter more than the rest. The original v7.1 ZIP bundles a 1.16.x-era ViGEmBus MSI and HIDGuardian, a hiding layer its own author discontinued years ago; the fork brings both components to their final, modern forms. And unlike Davidobot’s older releases, GitHub publishes a SHA-256 digest for the fork’s asset, so the file is checkable against the value above — the same verification habit we recommend in Is BetterJoy Safe?

What the fork actually changed

Beyond swapping the bundled drivers, the fork’s own changelog describes a maintenance pass over the original code: a long list of crash and disconnect fixes, stick calibration controls, and deadzone/range adjustments that can be set per stick — things v7.1 users otherwise handle inside each emulator. The runtime move matters for longevity as much as features: v7.1 is a .NET Framework-era binary from 2021, while the fork builds on .NET 10, which is the generation Microsoft currently services. None of this makes the fork “BetterJoy 2” — it is the same mapper idea, carried forward by a different maintainer with a modern toolchain — but it explains why the fork exists at all: the original’s components (HIDGuardian discontinued, ViGEmBus retired at 1.22.0, .NET Framework frozen) each reached end-of-life while the controllers people use did not.

One boundary is worth repeating in this section because fork coverage elsewhere blurs it: the fork’s controller support is the original Switch family plus the retro pads. Its README’s testing notes centre on official Pro Controllers and Joy-Cons. It does not add Switch 2 support, and it does not promise broader third-party pad support than the original — by the maintainer’s own account, less testing has happened there, not more.

Download the fork

Download the community fork on GitHub (d3xMachina, v8.5.0a)

The button goes to the fork’s own GitHub release asset — no mirror, no wrapper. Prefer the known quantity instead? The conservative choice remains the official v7.1 download, Davidobot’s own release, and nothing on this page should be read as talking you out of it.

Who should try the fork

• You hit the original’s age. If v7.1’s legacy driver stack gives you trouble — especially anything involving HIDGuardian, which also conflicts with HidHide if both end up installed — the fork starts from the modern components (our double-input guide explains the HidHide approach).
• You want the extra controllers. NES and N64 pad support exists only in the fork line.
• You value current maintenance. The fork shipped releases in mid-2026; the original’s last push was July 2024. If a Windows update breaks something tomorrow, the fork is the line that can plausibly answer.
• You’re willing to test newer builds. The “a” in v8.5.0a is a fix-up release four days after v8.5.0 — normal for an active project, and a reminder that this line moves.

Who should stay on v7.1

• Your setup already works. v7.1 has been the stable reference for five years and about 1.75 million downloads of its ZIP. Don’t migrate a working rig on curiosity alone.
• You follow guides literally. Most tutorials, forum answers and our own tutorials hub describe v7.1’s menus and config file; the fork’s newer build may differ in details.
• You use third-party controllers. The fork’s maintainer notes testing focused on official Pro Controllers and Joy-Cons; third-party pads are the original line’s documented feature (v7’s Add Controllers), and even there, results vary by model.
• You don’t want a moving target. A dormant program never surprises you; an LTS fork occasionally will.

Before you switch

Don’t run both lines into the same driver stack. If you move to the fork, first remove the original cleanly — our uninstall guide covers the ViGEmBus MSI and the HIDGuardian remnants — then install the fork’s bundled components. Above all, never leave HIDGuardian and HidHide on the same system: Nefarius’ own guidance says the two must not coexist, and the fork shipping HidHide is a reason to make sure the old layer is really gone. And keep the fork’s identity straight when you read about it elsewhere: v8.x = d3xMachina’s community fork; v7.1 and below = Davidobot. The version history keeps the two lines visually separate for exactly this reason.

Frequently asked questions

Is the fork official?

No. It is an independent community fork by d3xMachina, built from Davidobot’s MIT-licensed source. It is legitimate to use and link — MIT allows forking — but it is not endorsed by, or a release of, the original author.

Does the fork support Switch 2 controllers?

No. Its controller list is the original Switch family plus NES/N64 pads. Switch 2 controllers use a different protocol entirely — see the Switch 2 answer.

Can I keep v7.1 and the fork side by side?

The programs themselves are just folders, but their driver and hiding layers overlap (ViGEmBus, HIDGuardian vs HidHide). Treat it as one installation or the other, and uninstall cleanly when switching.

More context in the Versions & Trust hub.