If you have been watching the HF waterfall in early 2026, you have probably noticed something has changed. The familiar 15-second cadence of FT8 is still there, still dominant, still logging contacts across continents on signals you cannot hear with your ears. But alongside it, something faster and wider has appeared — a frantic little pulse that comes and goes before you have had time to think.
That is the FT2 digital mode. And depending on who you ask, it is either the most exciting development in amateur radio since FT8 itself, or the clearest sign that we have completely lost the plot.
FT2 Digital Mode
FT2 digital mode was developed by Martino, IU8LMC, and the ARI Caserta Team as a radical compression of the existing FT4 protocol. The idea is straightforward enough: take FT4, halve the transmit/receive period, and see what happens. What happens is a 3.75 to 3.8 second cycle that can complete a full QSO — callsigns, signal report, RR73 — in somewhere between 15 and 20 seconds.
The technical specifications are worth knowing before you form an opinion:
Cycle duration: 3.75 to 3.8 seconds
Full QSO time: 15 to 20 seconds
SNR floor: approximately -12 to -14 dB
Bandwidth: around 150 Hz
Modulation: 8-GFSK with the standard 77-bit payload.
That last point is important. FT2 uses the same message structure as FT8 and FT4 — it is not reinventing the encoding, just compressing the timeline dramatically. And that compression is what creates every single trade-off the community has been arguing about since the mode showed up on the bands.
This brings us to the software situation, which matters more than it might first appear. FT2 digital mode is not part of the official WSJT-X release from Joe Taylor’s Princeton group. It runs through WSJT-X Improved — a community-maintained fork of the original software — along with a handful of other experimental clients. If you want to get on the air with FT2, WSJT-X Improved is your primary route in. That distinction has real consequences for compatibility and logging, and we will get to both.
The First Few Weeks: Pure Dopamine
Honest accounts from the first operators to try FT2 digital mode in late 2025 are almost uniformly enthusiastic. When a mode lets you log 40 stations in the time it usually takes to finish a cup of coffee, the initial reaction is going to be excitement. Early adopters on 20m and 10m described the experience of watching contacts stack up at that speed as genuinely addictive.
For POTA activators and contest operators especially, the attraction was immediate and practical. One Canadian operator shared on a popular forum that FT2 had saved an activation outright — the band was closing, five contacts were still needed, and in FT8 there simply was not enough time left. FT2 finished the job with minutes to spare.
There was also the satisfaction of getting the setup right. FT2’s timing requirements are tight enough that tuning your station to handle it properly feels like a real technical achievement. That sense of being on the leading edge of something new drew in a wave of experimenters who had been feeling a little restless since FT8 became routine.
Where the Problems Start
The enthusiasm did not last long for a significant portion of the community. Once operators moved beyond the initial novelty, three recurring complaints started dominating every forum thread, mailing list, and subreddit discussion touching FT2 digital mode.
Time synchronisation is ruthless. FT8 is forgiving of a small timing error. FT2 is not. With a 3.8-second window, a delta time drift of even 0.1 seconds can be enough to kill a decode entirely. The standard Windows time service — what most operators have been running without a second thought for years — is simply not adequate. Community threads quickly filled up with guides to installing Meinberg NTP, Dimension 4, or GPS-disciplined clocking solutions. “If your clock drifts while you sneeze, you’re off the air” is an actual quote from the r/amateurradio subreddit, and it is not really a joke.
This has created a genuine barrier to entry. Depending on your perspective, that is either a reasonable technical standard for a mode with these demands, or an unnecessary complication that locks out the average hobbyist who just wants to operate.
Equipment stress is not trivial either. FT8 at 100% duty cycle is already harder on finals than SSB phone. FT2 makes FT8 look gentle by comparison. The gaps between transmissions in FT4 and FT8 offer at least some thermal relief. In FT2, those gaps are so short they barely register. Multiple operators have reported watching heatsink temperatures climb sharply in just a few minutes of continuous operation. The community has settled on a practical workaround — run no more than 25% of rated power — but that creates a circular problem. The mode already has a weaker sensitivity floor than FT8. Dropping power compounds that further.
The logging situation is a third headache entirely. Because FT2 digital mode is not an official ADIF mode, most logging software does not know what to do with it. Users are currently logging FT2 contacts as MFSK or DATA and hoping that LoTW will eventually sort it out. For anyone who cares about award credits or accurate records, this is a real problem rather than a minor inconvenience.
The software fragmentation adds another layer of frustration. WSJT-X Improved and some of the other clients that support FT2 have not always been compatible with each other, which means you can sometimes see signals on the waterfall that your software simply cannot decode. You know there is activity there. You just cannot reach it.
The Technical Criticism That Matters Most
Strip away the forum arguments and the shack anecdotes, and the single most important fact about FT2 digital mode is this: it is not a weak-signal mode.
FT8 built its entire reputation on pulling contacts out of noise that your ears cannot detect — down to -24 dB SNR. That capability is genuinely useful, and it is what lets a modest station with a compromise antenna work DX it has no business working. It is the reason FT8 spread across the globe as fast as it did.
FT2’s sensitivity floor sits at approximately -12 to -14 dB, which is roughly 10 to 12 dB worse than FT8. In practical terms, that gap is the equivalent of the difference between a 100-watt station and needing 1,500 watts to cover the same path. FT2 digital mode does not dig into the noise — it clears a pile-up when the band is already wide open and signals are running strong. That is a legitimate use case, but a far narrower one than FT8 serves. Early descriptions of FT2 as a weak-signal mode were simply inaccurate.
There is also the automation question, which gets under the skin of many operators regardless of how they feel about speed in general. At 3.8 seconds per cycle, there is no realistic way to run FT2 without Auto-Seq enabled. The software is making every decision. The operator is watching the screen. Some find that liberating — the station is working as efficiently as the physics allow. Others find it uncomfortable, because the question of what skill is actually being exercised becomes difficult to answer. The observation that FT2 is “robots talking to robots” is a bit uncharitable, but it points at something real.
The spectrum footprint is a practical irritant too. At roughly 150 Hz per signal — approximately three times the width of an FT8 signal — FT2 takes up meaningful real estate on already crowded digital segments. Complaints about FT2 signals sitting on top of existing FT8 activity appeared early and have not gone away. Wider and faster does not automatically make you a good neighbour on a shared band.
Will FT2 Digital Mode Last?
FT2 digital mode is unlikely to replace FT8. The sensitivity gap is simply too large. The average operator with a modest antenna and 100 watts gets too much value from FT8’s ability to work the world on a difficult day to trade that away for faster contacts when conditions are already good.
Whether FT2 threatens FT4 is a more interesting question. Contesters already accept FT4’s reduced sensitivity in exchange for speed. FT2 is the logical continuation of that trade-off pushed to its current limit. If the software situation stabilises — official ADIF support, reliable logging, and a stable widely-adopted version of WSJT-X Improved or a successor — FT2 could establish a real niche in contest and activation operations where band conditions are strong and throughput is the priority.
For now it sits in an awkward middle ground. The operators who love it are using it regularly and getting genuine value from the pace. The operators who bounced off it — usually after timing problems or thermal concerns — have returned to FT8 and FT4 and have no strong reason to try again.
The initial excitement around FT2 digital mode has already peaked. What comes next is the slower, less dramatic process of finding out whether the mode has enough real-world utility to survive once the novelty has fully worn off. Amateur radio has seen plenty of modes arrive with a bang and quietly disappear. It has also seen modes that seemed niche become permanent fixtures. Which way FT2 goes depends mostly on whether the software ecosystem catches up to the enthusiasm of its early adopters.
If you want to try it, sort out your time synchronisation before anything else, pull your power down to 25% or below, and keep a close eye on your temperatures throughout. Get WSJT-X Improved installed and spend some time understanding how the timing works before you call CQ. Do all that, and FT2 is genuinely interesting to operate — fast in a way that feels almost surreal after years of FT8’s patient 15-second rhythm.
Just go in with clear expectations about what the mode can and cannot do, and you will not be disappointed.
Related Posts
- FT2 Digital Mode: Latest News, Software Updates, and Ham Radio Adoption
- The FT2 Schism: When a New Digital Mode Split in Two
- FT2: The Fastest Digital Mode in Amateur Radio