FT8, FT4 & JS8Call: Complete Getting‑Started Guide for Beginners

This guide is written around our popular Digimode‑4 digital‑mode interface, which is used throughout the examples below.
The Digimode‑4 is available via the radio manufacturer shop pages in our main menu. If you’re following along with a different interface, the concepts still apply.

FT8, FT4 and JS8Call are often grouped together, but they are not interchangeable. Each one is designed to solve a slightly different problem on the bands.

FT8 is built for making reliable contacts when signals are weak and conditions are poor. It is fast, structured and highly efficient, which is why it has become so widely used.

FT4 takes the same core idea and pushes it further, trading a little sensitivity for speed.

JS8Call goes in the opposite direction, slowing things down in exchange for real keyboard‑to‑keyboard communication and greater flexibility.

If you are new to digital modes, FT8 is usually the first stop. If you already use FT8, FT4 and JS8Call can open up operating styles that feel very different, even though the station setup is largely the same.

This page explains how each mode works, why people use them, and what you actually need to get on the air. The focus is practical rather than theoretical, with enough background to understand what is happening, without burying you in protocol details.

What FT8 is and how it works

FT8 is a weak‑signal digital mode designed to make contacts when conditions are poor. Instead of sending speech or Morse, it uses short, tightly defined digital messages transmitted as audio tones within a narrow bandwidth.

The efficiency of the mode is what makes it stand out. FT8 signals can be decoded at signal levels well below what you could hear by ear. In practice, this means contacts are possible even when the band sounds dead.

FT8 was developed by Joe Taylor, K1JT, and Steve Franke, K9AN. Since its introduction, it has become one of the most widely used digital modes in amateur radio, largely because it works reliably with modest stations and limited operating time.

How FT8 works in practice

An FT8 signal is only about 50 Hz wide, but the software does not listen to just one signal. Instead, the radio sends a wide slice of audio, typically around 1 to 3 kHz, into the computer via a sound interface or built‑in USB audio device.

The FT8 software processes this audio entirely in the digital domain. Rather than tuning in the traditional sense, it analyses the whole passband, breaking the audio into small time segments, converting them into frequency data, and looking for the exact tone spacing and timing used by FT8. Signals that match are aligned precisely in time, filtered, and passed through error‑correction routines.

Because this processing is mathematical rather than auditory, the software can examine many signals at once and recover information that would be completely inaudible to a human listener. In practice, FT8 routinely decodes signals that are 20 dB or more below the noise floor.

This approach explains both the strength and the limitations of the mode. It is why FT8 works so well under poor conditions, and also why accurate time synchronisation and clean audio levels matter. Small setup issues that might go unnoticed on other modes can prevent successful decoding on FT8.

Introducing the Waterfall Display

When you use FT8, most of what is happening is visible on the waterfall display. This is a scrolling visual representation of the incoming audio, with frequency shown left to right and time flowing downward. Stronger signals appear brighter, while weaker signals blend into the background noise.

FT8 software also overlays horizontal timing markers on the waterfall. These mark the boundaries of the fixed 15‑second transmit and receive cycles used by the mode. Each FT8 transmission begins exactly on one of these boundaries, so signals appear as short horizontal traces that line up neatly across the display as the waterfall scrolls.

Once you have watched a few cycles pass, these timing lines become an easy way to see when a new sequence starts, whether your station is transmitting or receiving, and which signals belong to the same cycle.

This strict timing is also why accurate PC clock synchronisation matters. If your computer clock drifts, your transmissions will no longer line up with everyone else’s, and decoding quickly becomes unreliable.

A Note About FT4

FT4 uses the same style of waterfall display as FT8, but the timing is different. While FT8 operates on 15‑second cycles, FT4 uses 7.5‑second cycles, which makes it effectively twice as fast. On the waterfall, this shows up as a quicker scroll, with shorter signal traces and timing markers that are closer together. The overall visual rhythm feels tighter and more compressed than FT8, which reflects the faster pace of operation.

Despite these differences, the waterfall itself is only a visual aid. All decoding, whether for FT8 or FT4, happens inside the software’s digital signal processing engine. The display helps you see timing, signal placement, and activity, but it plays no role in the actual decoding of signals.

Why FT8 Works So Well

FT8 works because everything about it is optimised for weak‑signal conditions. Each transmission occupies very little bandwidth, is precisely timed, and is decoded entirely in software using strong error correction.

Instead of trying to follow one signal at a time, the decoder analyses the whole audio passband and attempts to recover many signals in parallel. This digital processing allows FT8 to extract usable information even when signals are buried deep in noise.

The result is a mode that remains reliable when propagation is marginal, noise levels are high, or signal strength would make voice or faster digital modes impractical.

Why FT8 is so widely used?

FT8 is widely used because it works in situations where many other modes struggle. It can decode signals well below the noise floor, which makes it possible to work DX with low power, indoor or compromised antennas, and during periods of poor propagation. For many operators, this alone is enough to justify its popularity.

The contacts themselves are quick and highly structured. FT8 exchanges only the information needed to complete a valid QSO, callsigns, signal reports, grid information, and a final acknowledgement. Because transmissions are tightly timed and automated, a complete contact typically takes little more than a minute. This suits operators with limited time and makes the mode practical on busy or noisy bands.

FT8 is also efficient in terms of spectrum use. Each signal occupies only a small amount of bandwidth, which allows many stations to operate side by side without causing mutual interference. Even on crowded bands, large numbers of contacts can take place within a relatively small slice of spectrum.

From a practical point of view, FT8 is easy to get started with. It does not require expensive radios or complex audio hardware, but it does rely on accurate computer timing and sensible audio levels. Once those basics are in place, the mode is generally very forgiving.

Finally, FT8 provides immediate feedback. Reporting networks such as PSK Reporter make it easy to see where your signal is being heard and how conditions are changing. This makes the mode particularly useful for testing antennas, comparing setups, and understanding propagation in real time.

Where FT4 and JS8Call fit in, and what they offer that FT8 does not

FT4 and JS8Call are often mentioned alongside FT8 because they share similar technical foundations, but they are designed for different operating styles.

FT4 is best thought of as FT8 made faster. It uses the same general approach to weak‑signal digital communication, but with much shorter transmit and receive cycles. Instead of 15‑second slots, FT4 runs on cycles of around 7.5 seconds. The result is quicker exchanges and a noticeably faster pace on the bands.

This makes FT4 well suited to contesting, rapid DX hunting, and busy band conditions where speed matters. The trade‑off is sensitivity. FT4 does not dig quite as deeply into the noise as FT8, so extremely weak signals that decode on FT8 may not decode reliably on FT4. In practice, many operators switch between the two depending on conditions, using FT8 when signals are marginal and FT4 when they are stronger.

JS8Call takes a different path entirely. While it is built on the same underlying weak‑signal technology, it is designed for real keyboard‑to‑keyboard communication rather than short, automated exchanges. Instead of fixed messages, JS8Call allows free‑text communication, along with features such as directed calling, relaying, and store‑and‑forward messaging.

This flexibility makes JS8Call useful for longer conversations, experimentation, and situations where infrastructure is limited or unreliable. It is often used for portable operation, back‑country communication, and emergency or off‑grid scenarios.

JS8Call QSOs take longer, and the mode is not intended for rapid contacts, but it offers a level of control and interaction that FT8 and FT4 deliberately avoid.

Taken together, the three modes cover a wide range of operating styles. FT8 prioritises reliability under poor conditions, FT4 prioritises speed when conditions allow, and JS8Call prioritises communication when messaging matters more than efficiency.

Choosing between FT8, FT4 and JS8Call

By this point, it should be clear that FT8, FT4 and JS8Call are not competing versions of the same thing. They are different tools, built on similar technology, but aimed at different operating styles.

FT8 prioritises reliability. FT4 prioritises speed. JS8Call prioritises communication. None of them is universally better than the others, and most operators who spend time with digital modes end up using more than one, depending on conditions, available time, and what they want to achieve on the air.

If you enjoy making contacts under marginal conditions, FT8 will usually be your default choice. If the bands are open and busy and you want faster exchanges, FT4 often makes more sense. If you want to send real messages, experiment, or operate without relying on external infrastructure, JS8Call offers capabilities that the other two deliberately avoid.

Looking at the three side by side in the table below helps clarify these differences, not to rank them, but to show where each one fits best.

Operating frequencies and where these modes sit on the bands

Once you understand what FT8, FT4 and JS8Call are, the next practical question is where to find them on the air. Each mode has well‑established operating frequencies on every band, and most activity naturally gathers around these spots.

Choosing the right frequency matters. It determines whether your software is decoding real signals, whether you are joining active QSOs, and whether you are operating within the correct part of the band.

Transmitting even a little outside the usual centres can mean calling into empty spectrum, or worse, into the wrong segment altogether.

The table below shows the most commonly used FT8, FT4 and JS8Call frequencies across the HF and VHF bands, along with a small number of widely used alternatives. These are not arbitrary choices.

They are the places operators return to because they work, whether you are chasing DX on FT8, moving quickly on FT4, or using JS8Call for messaging.

What you need to get started, software and hardware

Once you understand how these modes work, the next step is getting on the air. The requirements are straightforward, and in most cases you already have much of what you need.

FT8, FT4 and JS8Call all use the same basic station setup. The software is free, the hardware requirements are modest, and there is very little difference between modes from a connection point of view. If your station can run one of them, it can run all three.

What matters most is having a clean audio path between your radio and computer, reliable PTT control, and accurate time synchronisation. With those basics in place, digital modes tend to work consistently and predictably.

Software You’ll Need

For FT8 and FT4, most operators use either WSJT‑X or JTDX. Both are purpose‑built for weak‑signal digital modes and are widely used across the amateur radio community. From an operating point of view, they do the same job, and the station setup is identical regardless of which one you choose.

JS8Call requires its own dedicated application. It uses the same general modulation approach as FT8, but adds real keyboard‑to‑keyboard messaging and more flexible communication features. If you want to use JS8Call, you run it instead of WSJT‑X or JTDX, not alongside them.

All of these programs are free, open‑source, and relatively lightweight. They run well on modest hardware and are actively maintained, which makes them suitable whether you are just getting started or have been using digital modes for years.

Hardware You’ll Need

The hardware requirements for FT8, FT4 and JS8Call are straightforward. At a minimum, you need an HF transceiver capable of SSB operation, an antenna suitable for the band you want to use, and a computer running Windows, macOS, or Linux.

The critical link between the radio and the computer is the audio interface. This may be an external sound‑card interface, or a radio with a built‑in USB audio codec. It carries receive and transmit audio in both directions and, in many cases, also provides push‑to‑talk control and CAT connectivity.

CAT control, short for Computer Aided Transceiver control, allows the software to communicate directly with the radio. With CAT enabled, the software can read and set frequency, select the correct mode or data setting, trigger transmit without additional control lines, and log QSOs with accurate band and frequency information. In normal use, everything is controlled from the computer screen rather than the radio’s front panel.

Using a proper digital‑mode interface, or a radio with integrated USB audio and CAT support, greatly simplifies operation. It reduces cabling, avoids manual configuration errors, and ensures reliable communication between the radio and the software.

Recommended Digital Mode Interfaces for a Smooth Start

While some modern transceivers include built‑in USB audio and CAT control, many radios still do not provide a clean or well‑isolated way to interface with a computer. In those cases, a dedicated digital‑mode interface is the simplest and most reliable way to connect your station to WSJT‑X, JTDX, or JS8Call.

A good interface provides clean, isolated audio in both directions and dependable control of transmit and frequency. This reduces setup issues, avoids ground loops and RF feedback, and makes day‑to‑day operation far more predictable.

That is where our Digimode interfaces are designed to help.

The Digimode‑3 is a high‑performance, isolated USB sound card interface. It is a good choice if you prefer to control your radio manually, or if you already use a separate CAT control solution.

The Digimode‑4 combines USB audio and CAT control in a single compact unit. It provides clean audio, precise frequency control, and full software integration, making it a straightforward option for FT8, FT4, and JS8Call operation, particularly for operators who want a tidy and fully automated setup.

Our great value and high performance interfaces are available for Alinco, Icom, Kenwood, Ten‑Tec, Xiegu, and Yaesu radios. Selecting a model matched to your transceiver helps ensure reliable operation with minimal configuration.

Digimode‑4 Interface (Compact USB CAT + Sound Card interface)

The Digimode‑4 is a compact USB interface for Icom radios, giving you both CAT control and a built‑in USB sound card for digital modes such as WSJT‑X, FLDigi, Ham Radio Deluxe, EchoLink, PSK31, DM780, N1MM, MixW, and more.

Clean Tx/Rx audio via Bourns 600:600 Ω isolation transformers
Opto‑isolated PTT for safe, reliable keying
One simple USB cable to your PC — no extra adapters needed
Works with any digital mode that needs audio + CAT control (FT8, PSK31, SSTV, Packet, Pactor, EchoLink, etc.)
Icom version shown in image

WSJT‑X

WSJT‑X is the most widely used software for weak‑signal digital modes. It was developed by Joe Taylor, K1JT, and is designed specifically for making contacts under difficult propagation conditions.

In addition to FT8 and FT4, WSJT‑X supports a range of other weak‑signal modes used across HF, VHF, and higher bands, including JT65, JT9, Q65, MSK144, and WSPR. Its decoding engine is capable of recovering signals well below the audible noise level, which is what makes these modes practical with modest stations.

WSJT‑X also includes integrated rig control, basic logging, and automatic sequencing for supported modes. Once configured, most operation is handled directly from the software, with minimal interaction required at the radio.

WSJT-X can be downloaded from here

JTDX

JTDX is a fork of WSJT‑X that focuses specifically on extracting the best possible performance from FT8 and JT65, particularly in crowded or noisy band conditions. It is aimed at operators who spend a lot of time chasing DX or operating in pileups and want every possible decoding advantage.

Compared to WSJT‑X, JTDX places more emphasis on decoding weak and overlapping signals. Many users find it will successfully decode stations that other software misses, especially when the band is busy or signals are closely spaced. It also includes logic to highlight rarer callsigns and tools that suit DX‑focused operating.

JTDX is deliberately narrow in scope. It does not support FT4 or JS8Call, and it is not intended as a general‑purpose digital modes package. Instead, it is optimised for operators who primarily run FT8 or JT65 and want maximum performance in those modes.

You can download JTDX from SourceForge here.

JS8Call

JS8Call is built on the same weak‑signal foundations as FT8, but it removes the rigid timing and fixed message structure. Instead of short, automated exchanges, it allows free‑text keyboard‑to‑keyboard communication, making it a messaging‑oriented digital mode rather than a rapid QSO protocol.

While it retains the narrow bandwidth and weak‑signal performance associated with FT8‑style modulation, JS8Call adds flexibility. Operators can send typed messages, call specific stations, relay traffic through others, and use store‑and‑forward techniques when direct communication is not possible. The software also supports beaconing and simple status queries, which can be useful for monitoring band conditions or station availability.

Because of this, JS8Call is often used where communication matters more than speed. It lends itself well to longer QSOs, portable and back‑country operation, and situations where internet connectivity is unavailable or unreliable. Contacts take longer than FT8 or FT4, but the trade‑off is control and the ability to communicate beyond basic signal reports.

JS8Call is free to download and runs on the same platforms as other digital‑mode software.

JS8Call can be downloaded from here

Setting up your station for FT8, FT4 and JS8Call

Once you understand how FT8, FT4 and JS8Call differ, the next step is turning that knowledge into on‑air operation. In practice, all three modes use the same basic station setup. What matters is clean audio between the radio and computer, correct software configuration, and accurate time synchronisation.

At its simplest, a digital‑mode station follows a straightforward signal path. The computer generates and receives digital audio and, if supported, sends rig‑control commands such as PTT and frequency changes. That data passes through a USB interface before reaching the radio.

The interface sits between the PC and the transceiver and handles audio in both directions. In the case of a Digimode‑3, this means an isolated USB sound card that provides clean transmit and receive audio, with PTT handled via VOX or the radio’s internal audio‑trigger options.

If you use a Digimode‑4, audio and CAT control are combined in a single unit, allowing the software to control transmit, frequency, and operating mode directly.

At the radio end, audio is connected through the ACC or DATA port, while CAT control uses the radio’s dedicated control interface where available.

With this arrangement in place, the software can manage frequency changes, transmit control, and logging without constant interaction with the radio’s front panel.

This PC‑to‑interface‑to‑radio chain is the backbone of FT8, FT4 and JS8Call operation. A properly isolated interface reduces RF feedback, avoids ground‑loop issues, and ensures that transmitted audio remains clean and consistent. Once set up correctly, the station behaves predictably, allowing you to focus on operating rather than troubleshooting.

Software configuration basics

Because JTDX and JS8Call are built on the same foundations as WSJT‑X, the basic configuration process is very similar across all three applications. Once you understand how one of them is set up, the others will feel familiar.

The key areas that matter are selecting the correct audio devices, confirming CAT or PTT control, setting sensible transmit levels, and ensuring your computer clock is accurately synchronised. Most decoding and transmit issues can be traced back to one of these basics rather than the software itself.

To avoid common setup problems, it is worth following a structured approach rather than guessing settings.

Our WSJT‑X setup guide walks through the core configuration step by step. Accurate time synchronisation is covered separately in our PC time‑sync guide, and clean transmit audio, which is essential for reliable decoding and good on‑air behaviour, is addressed in our clean‑signal optimisation guide.

Once these fundamentals are in place, FT8, FT4, and JS8Call tend to work consistently, allowing you to focus on operating rather than troubleshooting.

Welcome to ham-interfaces.com

FT8, FT4 & JS8Call: Complete Getting‑Started Guide for Beginners

On This Page

What FT8 is and how it works

Why FT8 is so widely used

Where FT4 and JS8Call fit in, and what they offer that FT8 does not

Choosing between FT8, FT4 and JS8Call

Operating frequencies and where these modes sit on the bands

What you need to get started, software and hardware

WSJT‑X

JTDX

JS8Call

Setting up your station for FT8, FT4 and JS8Call

Software configuration basics

Further reading and useful resources

What FT8 is and how it works

How FT8 works in practice

Introducing the Waterfall Display

A Note About FT4

Why FT8 Works So Well

Why FT8 is so widely used?

Where FT4 and JS8Call fit in, and what they offer that FT8 does not

Choosing between FT8, FT4 and JS8Call

Operating frequencies and where these modes sit on the bands

What you need to get started, software and hardware

Software You’ll Need

Recommended Digital Mode Interfaces for a Smooth Start

WSJT‑X

JTDX

JS8Call

Setting up your station for FT8, FT4 and JS8Call

Software configuration basics

Further reading and useful resources

www.ham-interfaces.com

Welcome to ham-interfaces.com

FT8, FT4 & JS8Call: Complete Getting‑Started Guide for Beginners

On This Page

​​

What FT8 is and how it works

How FT8 works in practice

Introducing the Waterfall Display

A Note About FT4

Why FT8 Works So Well

Why FT8 is so widely used?

Where FT4 and JS8Call fit in, and what they offer that FT8 does not

Operating frequencies and where these modes sit on the bands

What you need to get started, software and hardware

Software You’ll Need

Recommended Digital Mode Interfaces for a Smooth Start

​​WSJT‑X

JTDX

JS8Call

Setting up your station for FT8, FT4 and JS8Call

Software configuration basics

Further reading and useful resources

WSJT‑X