If you have spent any time on HF digital lately, you have seen it: FT8 is everywhere. It is popular because it works, especially when propagation is ugly and signals are buried. But FT8’s success has a downside too. Crowded band segments, slower exchanges, and a lot of waiting around can make it feel like you are stuck in traffic. That is the gap a new experimental mode called FT2 is trying to fill.
📌 TL;DR - What FT2 is
- Core idea: A WSJT-style mode tuned for speed, not maximum weak-signal sensitivity.
- Cycle time: About 3.8 seconds (about 4x faster than FT8, about 2x faster than FT4).
- Decode floor: Around -12 dB SNR (less sensitive than FT8, but usable when signals are strong).
- Best use: Contests, DXpeditions, pileups, and high-density activity.
- Status: Experimental and typically requires a modified WSJT-X build (often referenced as Decodium).
Why This Matters
FT8 is the king of weak-signal digital for a reason. It can pull useful decodes out of the mud. But if you have ever operated during heavy activity, you also know the cadence can feel slow, especially for contest-style exchanges where every second matters. FT2 leans into a different goal: move contacts quickly when signals are already strong enough to support it.
FT2 is not trying to replace FT8. It is trying to be the speed option you switch to when the band is hot and rate matters.
What Is FT2?
FT2 is an experimental WSJT-style digital mode optimized for ultra-fast QSOs. The headline feature is its transmit/receive cycle. Instead of FT8’s 15-second cadence, FT2 runs at about 3.8 seconds. That speed changes the feel of operating immediately, because a complete exchange can be over before you are used to seeing an FT8 station finish a single cycle.
- T/R cycle: ~3.8 seconds
- Full QSO time: typically ~7 to 11 seconds in quick-exchange flow
- Sensitivity: reported around -12 dB SNR
Where FT2 Came From and Where It Is Now
FT2 is credited to IU8LMC and developed with support from the ARI Caserta Team. The key detail is that it is not just theory. The software has been used on-air, and early operators report verified QSOs in the mode. One widely shared milestone claims that on February 16, 2026, operators completed dozens of real FT2 contacts with a 3.8-second cycle, including QSOs on 40 meters and 80 meters, with decodes reported down to about -12 dB SNR. It is also explicitly described as experimental, which matters because it implies rapid changes, limited adoption (for now), and the need for beta-style expectations.
How FT2 Works (Same DNA, Compressed Time)
One reason FT2 is easy to understand is that it does not throw out the WSJT playbook. Under the hood, it uses the same fundamental building blocks as FT8 and FT4, then compresses time to achieve its speed goal.
- 77-bit payload
- LDPC (174,91) forward error correction
- 8-GFSK modulation
The big change is time compression. Shorter symbols and a much shorter cycle drive the engineering trade-off behind FT2: speed versus bandwidth versus sensitivity. At about 3.8 seconds and roughly 150 Hz bandwidth, FT2 is often described in the -12 to -13 dB sensitivity neighborhood. That is less than FT8, but often enough for strong-signal operating where speed is the priority.
FT2 vs FT8 vs FT4
Think of these three modes as a set of gears. FT8 is the low gear for pulling weak signals through rough conditions. FT4 is the middle ground. FT2 is the high gear you use when conditions are good and you want to go fast. The important takeaway is direction, not perfection. As FT2 evolves, some details may shift, but the general trade remains the same.
| Parameter |
FT8 |
FT4 |
FT2 |
| T/R Cycle |
15 s |
7.5 s |
3.8 s |
| TX Duration |
12.64 s |
4.48 s |
~3.55 s |
| Modulation |
8-GFSK |
4-GFSK |
8-GFSK |
| Bandwidth |
50 Hz |
83 Hz |
~150 Hz |
| Reported Sensitivity (approx.) |
-21 dB |
-17.5 dB |
~ -10.8 to -13 dB |
| Full QSO Time (typical) |
~60 s |
~30 s |
~7 to 11 s |
| Theoretical QSO Rate |
~60/hour |
~120/hour |
~240/hour |
| Clock Accuracy (claimed) |
±200 ms |
±100 ms |
±50 ms |
The important point is that FT2 gets its speed by giving up some decode margin and using more bandwidth. That is why it is not a replacement for FT8, and also why it could be very attractive when conditions support it.
Who FT2 Is For
FT2 makes the most sense when signals are already in good shape and rate is the goal. If you are trying to max out QSOs per hour, shaving seconds off every exchange is a big deal, and that is exactly where FT2 shines.
- Contesting: Fast exchanges and higher potential QSO rate per hour.
- DXpeditions: Move stations quickly when the rare one is strong and demand is high.
- Pileups and high-density activity: Throughput wins when the band is packed.
Maybe not: FT2 is not a weak-signal miracle machine. If your favorite part of FT8 is squeezing contacts out of marginal openings, FT2 probably will not feel like an upgrade.
- Marginal propagation: The reported -12 dB neighborhood means it will not dig as deep as FT8 in poor conditions.
- Early adoption reality: Fewer decoders and listeners worldwide right now can mean less spotting and fewer easy pickups compared to FT8.
- Tighter timing: Faster cycles make clock sync and a clean station setup more important than they might feel in casual FT8 use.
How to Get on the Air with FT2
FT2 is still experimental, so you typically will not find it in a stock WSJT-X install. Right now, there are two common ways people are getting on the air with FT2: a modified WSJT-X build often referenced as Decodium, and WSJT-X Improved 3.1.0 260226 (beta), which is being shared as a test release that includes new open-source FT2 code. The exact details can change quickly, but the setup process is straightforward if you already run FT8 or FT4.
✅ HOW TO - FT2 setup in plain steps
- Pick an FT2 build: Decodium or WSJT-X Improved 3.1.0 260226 (beta).
- Install the build: follow that project’s instructions and keep changes minimal until RX and TX are confirmed.
- Configure and confirm your station basics: set audio levels, verify PTT works, and confirm CAT or rig control connects cleanly.
- Import the FT2 frequency file (QRG) if required: some builds need it so FT2 appears correctly in band and mode menus.
- Sync your clock: FT2’s short cycles make time accuracy more important than casual FT8 use.
- Start where signals are strong: FT2 is happiest when decoding is not the limiting factor.
- Verify with PSK Reporter: confirm you are being decoded and look for where activity is showing up.
Tip: If your first FT2 attempts feel quiet, that can be normal. Early adoption means fewer monitors worldwide, so spots and decodes may look sparse compared to FT8.
Frequently Asked Questions
Is FT2 meant to replace FT8?
No. FT2 is a specialized mode for situations where speed matters more than weak-signal sensitivity, such as contests, pileups, and high-density band activity. FT8 remains the better choice when propagation is marginal and you need maximum decode margin.
How fast is FT2 compared to FT8 and FT4?
FT2 uses a 3.8-second transmit/receive cycle. That is about four times faster than FT8's 15-second cycle and roughly twice as fast as FT4's 7.5-second cycle. A complete FT2 exchange typically wraps up in about 7 to 11 seconds.
What software do I need to try FT2?
FT2 is currently experimental and not included in a stock WSJT-X install. Your two main options are Decodium or WSJT-X Improved 3.1.0 260226 (beta). Some builds also require importing a frequency QRG file so FT2 band selections appear correctly.
Bottom line
FT2 is a purpose-built speed mode. It keeps the familiar WSJT-style structure, but compresses the cycle to about 3.8 seconds, trading some sensitivity for the ability to complete QSOs in seconds instead of a minute. Use FT2 when signals are strong and rate matters. Use FT8 when propagation is marginal and you need maximum decode margin. Also expect experimentation, because software builds and operating practices may change quickly while FT2 is still in its early stages.
Downloads