I get asked this constantly, usually by someone new to HF who just worked their first FT8 contact and wants to know if they even need to learn the other modes. The honest answer is that FT8, SSB, and CW aren’t competing for the same job. Each one solves a different problem, and once you understand what each mode is actually good at, the choice usually makes itself. I’ve made this argument before when it comes to how these three modes get lumped together in award categories, and it applies just as much to picking a mode for a given night on the air.
What Each Mode Is Built For
FT8 is a weak signal digital mode. It’s built to pull a decodable signal out of noise that would bury voice or even CW. The tradeoff is speed and depth of conversation. You’re not going to ragchew on FT8. You’re going to exchange a callsign, a grid or signal report, and a 73. That’s the whole QSO, and it happens in a rigid 15 second timing structure whether you like it or not. I’ve written before about how FT8 changed weak signal HF when it was released back in 2017, and it’s hard to overstate how much it reshaped what’s possible on a bad night.
SSB is the mode most people picture when they think of ham radio. It’s a real conversation, in real time, with all the personality and nuance that comes with an actual human voice. You can ragchew for an hour, run a pileup, work a net, or just shoot the breeze with someone across the country. There are some genuinely great HF nets worth checking into if you want to see SSB at its best. The cost is that SSB needs a stronger signal to be understood than FT8 or CW do.
CW sits in an interesting middle ground. It’s not as forgiving of a weak signal as FT8, but it punches well above SSB in terms of how little signal you need to complete a solid contact. A skilled CW operator can work through conditions that would make an SSB contact impossible, and can do it with far less power and a much simpler antenna than either of the other two modes typically require.
Noise Floor Changes Everything
This is where the real differences show up, and it’s the part beginners usually underestimate.
SSB needs a clean, strong signal relative to the noise floor to be intelligible. If your noise floor is elevated, whether from power line noise, solar panel inverters, plasma TVs, or just a noisy urban RF environment, SSB is often the first mode to fall apart. You’ll hear a signal is there, but you can’t pull the words out of the hash. Dialing in the right receive bandwidth helps more than people expect, and I’ve covered good filter width starting points for SSB and digital modes if you want to squeeze out a little more copy in a noisy environment.
CW holds up noticeably better than SSB in a noisy environment. A trained ear can copy a CW signal that’s well below what you’d need to understand a voice signal at the same noise floor, because you’re listening for a distinct tone pattern rather than trying to parse speech.
FT8 is built for exactly this problem. The protocol can decode signals that sound like nothing but noise to the human ear, often down around negative 20 dB signal to noise ratio or worse. If you’re operating from a noisy suburban lot with a compromise antenna, FT8 is going to get you QSOs that SSB and CW simply can’t touch.
Solar Conditions and Propagation
Solar conditions affect all three modes the same way in terms of what propagation is physically available. If the bands are dead, no mode is going to manufacture a path that isn’t there. But how usable a marginal path is differs a lot by mode. A lot of this comes down to how the ionosphere is behaving at the moment, which I get into in more detail in gray line propagation and the layers of the ionosphere.
During poor solar conditions (low solar flux, high absorption, a disturbed geomagnetic field) signals that do make it through are often weak and flutter in and out. This is where FT8 shines the most. Its error correction and weak signal decoding can grab a contact out of a band that sounds completely empty on SSB. I’ve made FT8 contacts on bands where I couldn’t hear a single voice signal.
CW again lands in the middle. Marginal propagation that’s too weak for solid SSB copy is often still workable in CW, especially with a skilled operator and good filtering on the receive side.
During strong solar conditions with high solar flux and open bands, all three modes benefit, but this is really where SSB gets to shine. Strong, stable signals mean you can actually have the ragchew, run the pileup, or work that rare DX station with a real conversation instead of a four-exchange digital handshake.
FT8 Isn’t the Only Digital Mode, and It’s Not Built for Conversation
It’s worth being clear that “digital mode” doesn’t mean “FT8.” FT8’s whole design point is speed and weak signal performance, and it does that by throwing out anything resembling a real conversation. If you want the noise immunity of digital without giving up the ability to actually talk to someone, there are other options worth knowing about.
PSK31 was the original keyboard-to-keyboard ragchew mode and it’s still out there. It’s narrow bandwidth, reasonably weak signal capable, and unlike FT8 it’s free-form. You type, they type back, and you can have a real back-and-forth conversation about the weather, your station, or anything else, just like a live voice QSO except typed instead of spoken.
JS8Call is one I actually use. It takes the FT8 protocol’s weak signal engine and repurposes it for actual messaging. It supports free-text conversation, store-and-forward relay, and even basic network-style features, while keeping a lot of the weak signal decode advantage that makes FT8 useful in bad conditions. If you want FT8-like performance but an actual conversation, JS8Call is the closer match, and it’s my go-to when I want to chat on a band that’s too marginal for SSB. If you’re getting started, I’ve got a full walkthrough on setting up JS8Call and making your first contacts.
VarAC is a newer option built on the VARA modem that combines chat-style ragchewing with file transfer and a built-in contact list, and it’s become popular in emcomm circles for exactly that reason. It’s less about squeezing out marginal contacts and more about reliable, flexible digital communication once you already have a viable path.
RTTY is the old-school option, mechanically simple and still active on the bands, especially during contests. It doesn’t have the weak signal performance of FT8 or JS8Call, but it’s a mode with real history and it still gets used for both quick exchanges and longer chats. If you’re curious whether it’s still worth learning, I’ve laid out what RTTY is and where it still fits today.
None of these replace FT8 for pulling a contact out of the noise floor, and none of them replace SSB for the ease and speed of just talking. But if you want a middle ground where you get some digital noise immunity without losing the ability to have a real conversation, that’s where PSK31, JS8Call, and VarAC live.
Why I Use FT8, SSB, and JS8Call
I don’t treat this as a “best mode” argument because there isn’t one. It depends on what I’m trying to do.
If I want to work weak signal DX or squeeze contacts out of a noisy location and marginal conditions, FT8 is the tool. If I want an actual conversation, want to run a pileup with some personality, or I’m doing emcomm traffic where clarity and speed of a live voice exchange matters, SSB is the tool. And if I want to ragchew on a band that’s too marginal for SSB to hold up, JS8Call is what I reach for. Between the three of them there aren’t many situations I can’t handle.
I don’t operate CW myself, but I’d be doing the mode a disservice not to cover what it brings to the table. If low power, simple antennas, and working through noisy or marginal conditions with minimal infrastructure appeals to you, it’s worth learning even though I haven’t gotten there yet.