Loading Now

WebFT8: Running FT8 Straight From Your Browser

FT8 changed weak-signal ham radio more than almost any mode before it. Now a new question is showing up on forums and Discord servers: what if you didn’t need WSJT-X at all? What if FT8 just ran in your browser?

That’s the idea behind WebFT8, one of a small but growing group of browser-native FT8 tools. Instead of installing software, configuring audio drivers, and wiring up CAT control, you open a web page. The decoding, the waterfall, the QSO logic, and the logbook all live there.

webft8

What FT8 Actually Does

FT8 stands for Franke-Taylor 8-FSK, built by Joe Taylor (K1JT) and Steve Franke (K9AN) for making contacts under weak-signal conditions. Rather than voice, it trades short, structured text messages back and forth:

CQ CALLSIGN GRID CALLSIGN CALLSIGN -10 CALLSIGN CALLSIGN R-08 CALLSIGN CALLSIGN RR73

Each cycle runs exactly 15 seconds, and both stations need to be synchronized to UTC within a second or two. Miss that window and you miss the transmission. This timing requirement doesn’t go away just because the software runs in a browser. WebFT8 has to track UTC as carefully as any desktop app.

ft8 architecture

How WebFT8 Works

The official Web-FT8 Client calls itself an early beta, built to decode and encode FT8 in standard browsers using Web Audio for input, WebAssembly for the signal processing, and the Web Serial API for radio control. Put simply, the browser stops being a display and starts being the whole computer.

A traditional FT8 setup looks like this: radio, USB audio interface, computer, WSJT-X, CAT control back to the radio, then separate logging software. WebFT8 collapses most of that chain into one page. The browser handles audio, decoding, radio control, and the log.

webft8 architecture

The current feature set includes:

  • Real-time waterfall covering 0 to 3 kHz, with adjustable contrast, brightness, and noise floor
  • Automatic QSO sequencing that tracks where a contact stands and what comes next
  • Web Serial CAT control for reading and setting radio frequency
  • Band selection across HF and VHF, from 160 through 6 meters
  • Built-in logbook with ADIF export
  • QRZ.com logging integration

WebAssembly Made This Possible

FT8 decoding takes real computing power. A decoder has to sample audio, run an FFT, spot candidate signals, sync them, pull symbols back out, and run error correction, all before the next 15-second window closes. That’s a heavy job for JavaScript alone.

WebAssembly changes the equation by letting code written in C or C++ run inside the browser at near-native speed. A few projects have already proven this works. ft8_lib offers a lightweight C implementation built with constrained hardware in mind. ft8js compiled that kind of processing into WebAssembly for browser and Node.js use. ft8ts took a different route, writing the whole FT8/FT4 codec in TypeScript. Between them, these projects show that FT8 no longer needs a desktop app to run well.

Why Portable Operators Should Care

The strongest case for WebFT8 isn’t the home shack. It’s the field.

A SOTA, POTA, or Field Day station usually means a laptop, FT8 software, CAT software, audio drivers, a logging program, and enough patience to get them all talking to each other. WebFT8’s whole pitch is cutting that down to a browser tab, which matters a lot more when you’re setting up on a hilltop with cold hands than it does at a desk.

Browsers run on Windows, Linux, macOS, Android, and iOS, which opens up an interesting possibility: a phone or tablet as the entire operating console. That said, don’t expect every phone to talk to every radio tomorrow. Direct CAT control from a mobile device still depends on USB OTG support, Web Serial availability, and how the operating system handles device permissions. The browser side is ready before the hardware side fully catches up.

Local Processing, Not a Cloud Dependency

One question worth asking upfront: does WebFT8 need an internet connection to work?

The decoding itself doesn’t. Because the FT8 engine runs locally through WebAssembly, your receiver audio never has to leave your machine to get decoded. The internet only becomes necessary for optional extras, like loading the app the first time, looking up a callsign, or syncing a QSO to QRZ.com.

That local-first approach has a privacy upside too. Audio stays on your device instead of streaming to a remote server for processing, which cuts down on both bandwidth and any concern about who else might see your receive audio.

The Hard Part Nobody Sees

Displaying a decoded FT8 message on a web page is the easy part. Building a decoder that actually performs well under real conditions is a different problem entirely.

A serious decoder has to handle weak signals, frequency drift, timing offsets, noise, and several overlapping stations all transmitting in the same window, while running LDPC error correction and avoiding false decodes. Some browser projects are already tackling this seriously. The Signal Decoder project, for example, runs a WebAssembly engine with LDPC decoding, OSD fallback, and multiple passes of interference subtraction to pull weak signals out of a crowded band. This is genuine digital signal processing, not a JavaScript animation drawing text on a waterfall.

Where This Could Go Next

WebFT8 sits inside a wider wave of browser-based ham radio experimentation. FT8 Player breaks down the structure of an FT8 message for educational use. WebSocket FT4/8 connects browser decoding to SDRplay’s SDRconnect over a WebSocket link, complete with a waterfall and a map of decoded stations. Projects like wfweb go further still, offering full remote transceiver control with multiple digital modes through a browser.

Line those up and a pattern appears: full CAT control from the browser, support for FT4, JS8, WSPR, and other modes side by side, and eventually a complete remote-station console you can reach from anywhere with a browser and a connection. None of that is finished yet, but the pieces are being built in parallel by different teams.

Should You Ditch WSJT-X?

Not yet, and probably not soon. WSJT-X is mature, stable, and trusted by a huge share of the FT8 community for good reason.

WebFT8’s strengths are real: no installation, easy portable setup, a single integrated interface, and the possibility of running from a phone or tablet in the field. Its limits are just as real: browser compatibility varies, Web Serial support isn’t universal across radios, decoder performance is still catching up, and mobile operating systems impose their own restrictions on hardware access. The developers themselves label the current client an early beta, which is an honest description.

One safety note worth keeping in mind with any browser-based radio tool: transmission should always require a deliberate action from the operator unless you’ve knowingly turned on an automated mode. Good radio software makes it hard to key up by accident on the wrong frequency.

The Bigger Shift

What matters most about WebFT8 isn’t that it decodes FT8. It’s the proof that a modern browser can genuinely function as a radio computing platform, handling high-performance audio, FFT processing, hardware communication, and graphics, tasks that used to belong strictly to native desktop applications.

The radio engineering underneath hasn’t changed. Good timing, good antennas, and careful operating still matter as much as ever. What’s changing is the interface between the operator and the radio, and that shift from desktop software to browser tab is worth watching closely over the next few years.

Related Posts

 

Prof. D. Prabakaran (VU3DXR) is the founder and driving force behind DXR Electronics Bits. With over 28 years of academic and technical education experience, he currently serves as Principal of PSV Polytechnic College, Krishnagiri and has dedicated his career to empowering students and radio enthusiasts with clear, practical electronics knowledge

Post Comment