Best Programming Cable for Baofeng

Quick answer

The best Baofeng programming cable uses a genuine FTDI chip, like the BTECH PC03-FTDI. Cheap two-pin cables often ship a counterfeit Prolific PL2303 that Windows 10 and 11 refuse to load a driver for, so they never connect. Buy an FTDI cable, install its driver, then pick the right COM port in CHIRP and you will program on the first try.

Almost every "my Baofeng won't program" post comes down to one thing: the cable. Baofeng ships no cable in most kits, and the cheapest USB cables on the market use counterfeit Prolific chips that modern Windows deliberately breaks. The radio is fine and CHIRP is fine, but the cable can never open a COM port, so nothing works.

This page explains why cheap cables fail on Windows 10 and 11, how a genuine FTDI cable fixes it, how to find the right COM port, and the driver steps that get you connected. If you only remember one thing: buy an FTDI cable.

Top picks for 2026

Independently chosen for beginners. We never show live prices — tap through to check the current price.

Reliable CHIRP programming on any OS

BTECH PC03 FTDI Programming Cable

  • Type: programming cable
  • Range: na MHz

Genuine FTDI chip that Windows 10/11, macOS, and Linux support out of the box, with the correct two-pin plug for Baofeng and BTECH handhelds. Ends the counterfeit-Prolific failures that plague cheap cables.

Laptops with only USB-C ports

TIDRADIO USB-C Programming Cable

  • Type: programming cable
  • Range: na MHz

Supported chipset and correct Baofeng-style plug in a native USB-C cable, so you skip the dongle. A dependable wired path to CHIRP for modern laptops.

What to avoid

Baofeng USB Prolific Programming Cable

  • Type: programming cable
  • Range: na MHz

Represents the ultra-cheap generic cable that ships a counterfeit Prolific PL2303. Enumerates with Code 10 on Windows 10/11 and never opens a COM port, the top cause of failed first-time programming. Buy FTDI instead.

Why cheap Baofeng cables fail on Windows 10 and 11

The two-pin plug on a Baofeng (a stacked 3.5 mm plus 2.5 mm connector) is dumb wiring. All the intelligence lives in a USB-to-serial chip inside the cable's USB shell. That chip is where cheap cables go wrong.

Most bargain cables use a counterfeit Prolific PL2303 chip. Genuine Prolific and Microsoft blacklisted these clones years ago. On Windows 10 and 11 the counterfeit chip enumerates but shows Code 10 ("This device cannot start") in Device Manager, and no amount of clicking will make it open a COM port. You did nothing wrong; the driver is refusing the fake chip on purpose.

Symptoms of a counterfeit-Prolific cable:

  • Device Manager shows a yellow warning triangle with Code 10 or Code 43.
  • CHIRP or the Baofeng software reports "radio did not respond" or shows no COM port to select.
  • It once worked, then broke after a Windows update that pushed a newer driver.

The fix is not more drivers. The reliable fix is a different cable with a genuine FTDI chip, which Windows, macOS, and Linux all support out of the box. For the full programming walkthrough once your cable works, see our program a Baofeng with CHIRP guide.

FTDI vs Prolific: what the chip actually changes

Both FTDI and Prolific make USB-to-serial chips that do the same job. The difference for a beginner is not performance, it is whether the cable connects at all on a modern computer. The market is flooded with counterfeit Prolific chips, so a "Prolific" cable is a coin flip; genuine FTDI cables are rarely faked and are supported everywhere.

Genuine FTDI (FT232)Counterfeit Prolific PL2303
Windows 10 / 11Works, driver built inOften Code 10, blocked
macOSWorks, nativeUnreliable
LinuxWorks, native (ftdi_sio)Hit or miss
Driver hunting neededRarelyConstant, and may still fail
Typical costA few dollars moreCheapest, false economy

Genuine Prolific chips do exist and work, but you cannot tell a real one from a fake by the listing photo or price. FTDI takes that gamble off the table. That is why our top pick is FTDI-based, and why we warn against generic "Prolific" cables below.

One more note: CHIRP does not care which chip you use. It only needs a working COM port. The chip choice is purely about getting Windows to give you that port.

Our Baofeng programming cable picks

Match the cable to your computer's ports. Both picks below use supported chipsets, so they connect without a driver fight.

  • BTECH PC03-FTDI (btech-pc03-ftdi): our top pick. Genuine FTDI chip, USB-A, and the correct two-pin Kenwood-style plug for UV-5R, BF-F8HP, UV-82, and most Baofeng and BTECH handhelds. Works with CHIRP on Windows, macOS, and Linux with minimal setup.
  • TIDRADIO USB-C cable (tidradio-usb-c): a good choice if your laptop only has USB-C ports, avoiding a dongle. Supported chipset and correct plug for Baofeng-style radios. TIDRADIO also sells radios with wireless programming, but for CHIRP a wired cable is still the most reliable path.

Not sure which handheld you are programming, or comparing models before you buy accessories? Use the HT comparison tool to line up connector types and features across popular radios.

Avoid the fake-Prolific trap

The cable to avoid is the ultra-cheap generic listed simply as a "Baofeng USB programming cable" with a bare two-pin plug and no chip named (baofeng-usb-prolific in our catalog represents this category). These almost always carry a counterfeit Prolific PL2303 and are the single biggest cause of failed first-time programming.

How to spot one before you buy:

  • The listing does not say "FTDI" anywhere.
  • It is the cheapest option by a wide margin.
  • Reviews mention "Code 10", "won't install", or "stopped working after update".
  • The seller links you to an old third-party Prolific driver to "fix" it.

If you already own one of these, don't fight it. Rolling back to an ancient driver sometimes works for a session but breaks again on the next Windows update. A genuine FTDI cable costs only a few dollars more and ends the problem for good.

Finding the right COM port

Once you plug in a working cable, your computer assigns it a serial (COM) port. CHIRP needs you to pick that exact port. Here is how to find it.

Windows: Open Device Manager and expand Ports (COM & LPT). With the cable plugged in you should see an entry like "USB Serial Port (COM5)" for FTDI. Note the number. If you see a yellow triangle instead, the driver failed, usually the counterfeit-Prolific problem above. A quick trick: unplug the cable and watch which entry disappears, then plug it back in to confirm the COM number.

macOS: The port shows up as a device like /dev/tty.usbserial-XXXX. In CHIRP's port dropdown pick the usbserial entry.

Linux: The FTDI cable appears as /dev/ttyUSB0 (or a higher number). Add your user to the dialout group if you get a permission error, then log out and back in.

In CHIRP, choose Radio, then Download From Radio, select that port, set vendor Baofeng and the correct model, and read the radio. The full step-by-step is in our CHIRP programming guide.

Driver tips and quick troubleshooting

A supported cable usually needs no manual driver on a current OS. When something still won't connect, work through this list in order:

SymptomLikely causeFix
No COM port appears at allCounterfeit Prolific chip blocked, or dead cableTry another USB port; if still nothing, replace with an FTDI cable
Code 10 / yellow triangleCounterfeit Prolific on Windows 10/11Use an FTDI cable; driver rollbacks are temporary
Port shows but "radio did not respond"Radio off, volume too low, or plug not fully seatedTurn radio on, set volume to about half, press the plug firmly all the way in
Wrong COM port selectedMultiple ports listedUnplug to see which port disappears, select that one
Works then drops mid-readLoose two-pin plug or USB extensionPlug directly into the computer, hold the connector steady

Two easy wins people miss: the radio must be powered on before you read it, and the stacked two-pin plug must be seated fully, it often needs firm pressure to make both contacts. If your OS truly needs a driver for an FTDI cable, get it from FTDI's official VCP driver page, never a random third-party download.

Frequently asked questions

Why won't my Baofeng cable connect?
Almost always because it uses a counterfeit Prolific PL2303 chip that Windows 10 and 11 block, showing Code 10 in Device Manager with no usable COM port. The radio and CHIRP are fine. Replace it with a genuine FTDI cable, which every modern OS supports, and it will connect without a driver fight.
What cable do I need for CHIRP?
Any cable that opens a working COM port, since CHIRP only needs the serial port, not a specific chip. In practice that means a genuine FTDI cable with the correct two-pin Kenwood-style plug for Baofeng, such as the BTECH PC03-FTDI. Avoid unlabeled cheap cables that hide a counterfeit Prolific chip.
FTDI or Prolific, which is better for Baofeng?
FTDI, for one reason: reliability. Both chips can do the job, but the market is flooded with counterfeit Prolific PL2303 chips that Windows blocks, and you cannot tell a fake from a photo. Genuine FTDI cables are rarely faked and work on Windows, macOS, and Linux with no driver hunting.
How do I find the COM port for my cable?
On Windows, open Device Manager and expand Ports (COM & LPT); a working FTDI cable shows as "USB Serial Port (COMx)". Unplug the cable and see which entry disappears to confirm the number. On macOS look for a /dev/tty.usbserial device, and on Linux for /dev/ttyUSB0. Select that port in CHIRP.
Can I fix a counterfeit Prolific cable with an old driver?
Sometimes for one session, but it is not a real fix. Rolling back to a legacy PL2303 driver may connect once, then break again after the next Windows update replaces it. A genuine FTDI cable costs only a little more and permanently ends the problem, so replacing the cable is the better use of your time.
Do I need a driver for an FTDI Baofeng cable?
Usually not. Windows 10/11, macOS, and current Linux include FTDI drivers, so the cable appears as a COM port automatically. If yours does not, install the official VCP driver from FTDI's website, never a random third-party download, then re-check Device Manager for the assigned port.

Sources & references

Last verified: