FT8 for Beginners: What It Is and How to Make Your First Contact

FT8 is the reason a lot of hams who'd never touch Morse code are suddenly working stations on six continents before breakfast. It's a weak-signal digital mode built into the free program WSJT-X, and per PSK Reporter's Wikipedia summary, it now makes up the vast majority of digital reports that service records — but the same things that make it easy (automated messages, forgiving sensitivity) also make it easy to set up wrong. This walkthrough covers what FT8 actually does under the hood, what gear and software you need, where to find it on the dial, how a first contact actually unfolds, and — because this regularly trips up new Technicians — exactly which HF privileges your license class does and doesn't give you for working it.

What FT8 Actually Is

FT8 is one of several weak-signal protocols built into WSJT-X, the free program originated by Joseph Taylor, K1JT (the "WSJT" in the name stands for "Weak Signal communication by K1JT"). According to ARRL's coverage of the mode's introduction, FT8 is named after its two developers, Steve Franke, K9AN, and Joe Taylor, K1JT, and it first appeared in a beta release of WSJT-X in mid-2017. The name itself describes the modulation: ARRL notes the "8" designates an eight-tone frequency-shift keying format, with tones spaced at 6.25 Hz.

The defining trait of FT8 is speed relative to its older siblings. ARRL's article on the mode states plainly that transmit and receive cycles in FT8 each last about 15 seconds — and an entire FT8 contact can take about 1 minute, per ARRL, versus four to six minutes for a minimal QSO in one-minute modes like JT65, per the WSJT-X user guide. WSJT-X's own user guide frames it the same way, describing FT8 as "four times faster (15-second T/R sequences) and less sensitive by a few dB" than the older one-minute modes. That speed-for-sensitivity trade is deliberate: the current WSJT-X user guide puts FT8's decoding threshold at about -21 dB signal-to-noise (2,500 Hz reference bandwidth), well below what you could hear by ear, but it doesn't reach quite as deep into the noise floor as a slower mode would.

The other defining trait is how narrow the signal is. ARRL's piece puts it simply: "an FT8 signal occupies just 50 Hz." The WSJT-X user guide's protocol specification spells out the math: FT8 uses 8-tone frequency-shift keying at a 6.25-baud keying rate, and "the total occupied bandwidth is 8 × 6.25 = 50 Hz." Fifty hertz is almost nothing, which is why dozens of simultaneous FT8 conversations can stack up, tone by tone, inside a single SSB-width receive passband without stepping on each other.

What You Need to Get on the Air

FT8 doesn't require exotic equipment, but every piece of the chain matters:

• An HF-capable transceiver that can run USB (upper sideband) mode and either accept audio in/out over a sound-card-style interface or, better, support CAT (computer-aided transceiver) control so WSJT-X can read your dial frequency and key the radio directly.
• A computer to run the software — WSJT-X's minimum spec, per its own user guide, calls for at least a 1.5 GHz CPU and 200 MB of available memory, though faster hardware is always better.
• WSJT-X itself, free from the WSJT project's own site — the reference program for FT8, FT4, and the older JT-series weak-signal modes.
• A rig interface or audio cable connecting your transceiver's audio and PTT (push-to-talk) lines to your computer, whether that's a dedicated USB sound-card interface or your radio's built-in USB audio/CAT port.
• An accurate computer clock. This one is non-negotiable. WSJT-X's own system requirements list "a means for synchronizing the computer clock to UTC within ±1 second", not as a nice-to-have. Every station starts its 15-second transmit window at the same instant; drift by more than a second or two and your transmissions land outside everyone else's receive window, so you simply won't get decoded. Free NTP sync utilities handle this automatically — check it before you blame your radio or antenna.

Finding FT8 on the Dial

WSJT-X ships with a built-in table of conventional working frequencies for each mode and band, and you select a band from that table rather than hunting for FT8 activity by ear. The FT8 dial frequencies in WSJT-X's own default frequency table (checked October 2026) are 7.074 MHz on 40 meters, 14.074 MHz on 20 meters, 10.136 MHz on 30 meters, 18.100 MHz on 17 meters, 21.074 MHz on 15 meters, 24.915 MHz on 12 meters, and 28.074 MHz on 10 meters, with additional conventional spots on 160, 80, and 6 meters. These are "dial" frequencies — the actual audio tones carrying traffic sit a few hundred to a couple thousand hertz above the dial frequency inside your receiver's passband, which is what the waterfall display in WSJT-X shows you.

Your radio needs to be in USB mode at the listed dial frequency with the mode's sub-band selected in WSJT-X. From there, the software reads incoming audio, decodes any FT8 signals in your passband, and lists them, each with its signal-to-noise reading in dB, in its Band Activity window.

Your First FT8 QSO, Step by Step

A full FT8 exchange is scripted, which is exactly what makes it approachable for a first digital-mode contact. A standard FT8 QSO runs through this sequence of transmissions:

1. CQ call. You (or someone else) transmits "CQ [callsign] [grid square]" — for example, "CQ W1ABC FN42" — announcing you're listening for a contact.
2. Reply. A station answers with both callsigns and their grid square.
3. Report. You send both callsigns and your signal report of them, in dB signal-to-noise.
4. Roger plus report. They answer with "R" plus their report of you.
5. RRR and 73. You send "RRR" (or "RR73"), and they close with "73" — the recommended basic QSO in the WSJT-X user guide.

WSJT-X automates almost all of this. Double-clicking a decoded CQ in the Band Activity window fills in the other station's callsign and grid, and the program's auto-sequencer generates the correct next message for each stage of the exchange — you mostly just watch the clock and click "Enable Tx" at the right moments rather than typing anything by hand. Because every transmission is a short, structured burst inside a 15-second window, there's little room for ad-libbing; FT8 is built for efficient contact exchange, not conversation, which is a different experience than voice or even CW ragchewing.

Power and ALC: Keep It Clean

FT8's constant-duty, narrow-bandwidth signal is unforgiving of a dirty transmitter in a way voice operation often isn't, because distortion products spread energy sideways into neighboring FT8 conversations instead of just roughening up your own audio. The control that matters most here is ALC — Automatic Level Control, the feedback circuit built into most transceivers that reins in drive power before the power amplifier saturates. Overdrive the radio from the sound card and ALC action compresses the signal, which is exactly the kind of distortion that splatters into neighboring FT8 signals.

For digital modes specifically, the fix is to control drive from the audio side, not the RF side. The WSJT-X user guide's setup procedure is to transmit a test tone and "adjust the Pwr slider (at right edge of main window) downward from its maximum until the RF output from your transmitter falls slightly," which it calls generally a good level for audio drive. In practice: set RF power to your intended output and let the audio level, not the RF control, set the drive, rather than leaving audio drive high and using RF power alone to "turn it down." On raw power, FCC rule 47 CFR 97.313(a) already sets the standard: a station "must use the minimum transmitter power necessary to carry out the desired communications." FT8 doesn't need much power to be decoded on the other end, and running more than you need mostly just adds to interference on an already busy sub-band.

License Privileges: What Technician vs. General Can Work

This is the part that genuinely trips up new operators, and getting it wrong is a rule violation, not a style choice. Per 47 CFR 97.301 (checked October 2026 on the eCFR), Technician HF privileges are 80 m 3.525-3.600, 40 m 7.025-7.125, 15 m 21.025-21.200 and 10 m 28.0-28.5 MHz — but 47 CFR 97.307(f)(9) limits Technicians to CW only on the 80, 40 and 15 meter segments, and 97.313 caps them at 200 W PEP. General privileges under 97.301(d) are far broader: segments of 160, 80, 40 (7.025-7.125 and 7.175-7.300 MHz), 30, 20, 17, 15 and 12 meters, plus all of 10 meters, 28.000-29.700 MHz, covering every HF FT8 frequency in the WSJT-X default table.

Mode matters as much as the band segment. Per 47 CFR 97.305's table of emission types by frequency, the 10-meter band's 28.0-28.3 MHz segment is authorized for RTTY and data modes, while 28.3-29.7 MHz is the phone and image segment (CW is permitted anywhere a licensee has privileges). That 28.0-28.3 MHz data segment is exactly where the conventional FT8 dial frequency of 28.074 MHz sits — which means a Technician-class license is enough to legally run FT8 on 10 meters, but nowhere else on HF (Technicians also hold all of 6 meters, a VHF band, where WSJT-X's default FT8 frequency is 50.313 MHz). A Technician who keys up FT8 on 14.074 MHz, even accidentally, is outside their privileges entirely; 7.074 MHz sits in a Technician segment, but one that is CW-only. If you're studying toward General specifically to unlock more FT8 bands, that upgrade — not new gear — is what actually opens up 20, 40, and 80 meter FT8 activity; our guide to reading a band plan and knowing where to operate walks through how to check a segment before you transmit on it, and our Technician exam study-plan guide is the right starting point if you're not licensed yet. Rules change, and license class privileges are exactly the kind of detail worth re-checking against the current FCC rule before you transmit, rather than trusting memory of an old band chart.

Logging and Confirmations: LoTW and PSK Reporter

Two free tools round out an FT8 setup. Logbook of The World (LoTW), ARRL's service, is — per its own help page — a way to "electronically submit contacts (QSOs) for confirmation"; when both operators in a QSO upload matching log entries, LoTW marks the contact confirmed, which counts toward awards like DXCC without exchanging paper QSL cards. PSK Reporter serves a different purpose: according to its Wikipedia summary, "the platform works by collecting digital signal reports from software clients such as WSJT and FLDIGI, then mapping them to show which stations are being heard by other clients." Plug your callsign into PSK Reporter's web map after a session and see, station by station, where your FT8 signal actually landed — a confidence check and a rough, crowd-sourced propagation indicator in one.

Getting Started This Week

If you're licensed and already have an HF rig, the fastest path in is: confirm your license class's legal band segment first, download WSJT-X, sync your computer clock, wire up a basic audio interface, and tune to the dial frequency your license actually covers. You don't need a tower or an amplifier — FT8's sensitivity is the whole point, and the WSJT-X home page itself talks about working the world with a few watts and a simple antenna. For a lower-power angle on the same idea, our guide to QRP operating and working big distance on low power covers the broader philosophy FT8 fits into. And if radio apparel is more your thing while you wait for propagation to improve, Sidetone's own shop designs lean on the hobby's inside jokes rather than generic callsign clipart — worth a look between band openings.

FAQ

Can a Technician-class license legally run FT8 on 20 meters? No. Per 47 CFR 97.301(e) (checked October 2026), Technicians have no 20-meter privileges, and their 80, 40 and 15 meter segments are CW-only under 97.307(f)(9) — 10 meters is the only HF band where a Technician can run FT8. Running FT8 on 14.074 MHz requires at least a General class license.

Where on 10 meters can a Technician run FT8? Specifically 28.0-28.3 MHz, the segment 47 CFR 97.305 authorizes for RTTY and data modes on that band. The conventional FT8 dial frequency of 28.074 MHz falls inside that segment, which is why 10-meter FT8 is open to Technicians when propagation supports it.

Why does my computer clock matter so much for FT8? Because every station's 15-second transmit/receive cycle has to line up with everyone else's. WSJT-X's own system requirements call for synchronizing your computer clock to UTC within about one second; drift beyond that and your transmissions fall outside other stations' receive windows, so you simply won't get decoded even with a strong signal.

Do I need to set ALC to a specific number for FT8? No single number fits every radio. Set drive from the audio side, as the WSJT-X user guide describes — lower the Pwr slider from maximum until RF output just starts to fall — rather than by riding the RF power control. Letting ALC compress the signal spreads distortion into neighboring FT8 conversations on an already crowded sub-band.

Is LoTW required to make FT8 contacts? No — LoTW only confirms contacts for award credit after the fact. You can make and log FT8 QSOs without ever touching it; it's a confirmation and awards-tracking layer, not something that affects whether a contact completes over the air.