If you want to run FT8 from a park, summit, campsite, or other portable location, carrying a laptop can seem like overkill. qFT8 takes a different approach, putting FT8 and FT4 operation directly on an Android phone.
This free, ad-free Android FT8 app supports more than 50 transceivers, automatic time synchronization, ADIF logging, QRZ and LoTW integration, POTA and SOTA features, and a built-in web server for remote operation.
So, is qFT8 actually good enough to replace a laptop for portable FT8? I looked at its features, supported radios, setup requirements, logging capabilities and limitations to find out—and there are some compelling reasons portable operators should take a close look.
Table of Contents
My verdict: qFT8 is one of the most interesting pieces of portable ham-radio software I’ve seen, particularly for POTA and SOTA operators. It doesn’t make WSJT-X obsolete, but for an Android-equipped portable station, it can eliminate the need for a computer altogether.
qFT8 at a Glance
Feature | qFT8 |
|---|---|
Platform | Android |
Cost | Free |
Advertising | None |
FT8 | Yes |
FT4 | Yes |
FT2 | Yes |
JS8 | Yes |
Supported radios | 50+ |
USB CAT/audio | Yes |
VOX/audio operation | Yes |
ADIF import/export | Yes |
QRZ integration | Yes |
LoTW integration | Yes |
POTA support | Yes |
SOTA support | Yes |
AUTO operating mode | Yes |
Manual CALL mode | Yes |
Remote web control | Yes |
Screen-off operation | Yes |
Time synchronization | NTP/GPS |
Current version reviewed | 2.20 |
The qFT8 website lists version 2.20, dated August 6, 2026, with a download size of about 6 MB. It is available through Google Play and as a downloadable APK.
What Is qFT8?
qFT8 is an Android amateur-radio application developed by Luis Quesada Torres, HB9IPH.
Its primary purpose is straightforward: run digital-mode operation directly from an Android phone instead of requiring a traditional computer.
The official documentation describes qFT8 as an Android application capable of decoding and transmitting FT8, FT4, FT2, and JS8 messages using a transceiver. It can connect directly to supported radios through USB, communicate with other equipment through audio/VOX, and can even be used without a radio for experimentation between phones.
The application is free, contains no advertising, and is source-available. The developer also identifies the open-source components incorporated into the project, including FT8CN, ft8_lib, KISS FFT, and usb-serial-for-android.
That doesn’t automatically make qFT8 better than established desktop software.
What it does give you is something desktop FT8 software cannot easily provide:
A complete digital-mode station that fits in your Android phone and can travel with your portable radio.
Why qFT8 Is Interesting for Portable Radio
The biggest advantage becomes obvious when you think about a typical POTA or SOTA activation.
You may already be carrying:
- A lightweight transceiver
- Battery
- Antenna
- Coax
- Key or microphone
- Phone
Adding a laptop makes the station considerably larger and more complicated.
With qFT8, the Android phone can handle:
- FT8 decoding
- FT8 transmission
- CAT control
- Audio
- Time synchronization
- Logging
- QSO management
- POTA/SOTA information
- QRZ/LoTW synchronization
- Station selection
- Remote control
That makes qFT8 particularly interesting for operators who want to keep their portable station small and battery-efficient.
The application also includes a battery-saving mode that allows it to continue operating with the phone screen off.
Supported Radios
One of qFT8’s strongest features is its radio compatibility.
The current documentation lists direct USB CAT/audio support for more than 50 radios and radio families, including equipment from QRP Labs, Icom, Yaesu, Elecraft, Xiegu, Kenwood and several smaller manufacturers.
Some of the supported radios include:
Manufacturer | Examples |
|---|---|
QRP Labs | QMX, QMX+, QDX, QDX-M |
Icom | IC-7300, IC-7300 MK2, IC-705, IC-7610, IC-7100, IC-9700 and others |
Yaesu | FT-891, FT-710, FTX-1, FT-991/991A, FT-DX10, FTDX101 |
Elecraft | K4/K4D/K4HD, K3/K3S, KX3, KX2, KH1, K2 |
Xiegu | X6100, X6200 |
Kenwood | TS-480, TS-590, TS-2000 series |
Other | FX-4CR, QuantumSDR, (tr)uSDX, uSDX+, usdr |
The official list is considerably longer, so if you’re considering qFT8, check the current supported-device list rather than assuming your particular radio will work because another model from the same manufacturer does.
What if your radio isn’t directly supported?
You may still be able to use qFT8.
The application supports operation through the radio’s speaker and microphone using VOX, as well as generic audio connections. That is more limited than direct CAT/audio integration, but it considerably expands the range of radios that can potentially be used.
There is an important catch with external interfaces such as Digirig.
qFT8’s automatic device detection is designed around radios with native USB controllers or model-specific cables. A generic USB-serial interface can be detected only as a generic interface, causing qFT8 to default to VOX mode. If your radio is connected through something like a Digirig and you want CAT control, the manual says you may need to select the transceiver model manually in the settings.
That’s an important distinction if you’re planning a portable station around an external interface.
What You Need to Get Started
For a directly supported radio, the hardware requirements are surprisingly modest.
You need:
- An Android phone
- A compatible transceiver
- A USB data cable or appropriate OTG adapter
- An antenna suitable for the band you’re operating
- A valid amateur-radio license for transmitting
The USB cable matters.
A charge-only USB cable won’t provide the data connection required for qFT8 to communicate with the transceiver. The developer specifically warns that incompatible cables and adapters are among the most common reasons the phone fails to recognize the radio.
For portable operation, I’d make a known-good USB data cable and appropriate OTG adapter part of the station kit, rather than discovering at the summit that the cable in your bag only charges the phone.
Setting Up qFT8
The basic setup is considerably easier than a conventional computer-based FT8 installation.
When you first launch qFT8, it requests the permissions it needs to operate.
You’ll need to provide:
- Microphone/audio permission
- Your callsign
- USB connection permission when the radio is attached
Location permission is optional but recommended because qFT8 can use approximate location information to obtain your Maidenhead grid locator. The developer states that the application does not access or share precise location data.
You should also allow qFT8 to operate in the background if you want screen-off operation.
Once the radio is connected, qFT8 can automatically configure supported transceivers.
For QMX users, the manual includes a dedicated audio-check procedure that uses indicators on the QMX display to confirm that the phone’s transmit audio is reaching the radio correctly.
Time synchronization
Time is critical for FT8.
qFT8 supports automatic NTP synchronization and GPS-based synchronization, which is particularly useful when operating away from an internet connection.
This is one of the reasons a phone is such a good platform for portable digital modes: you don’t have to manually solve the computer-clock problem every time you set up in the field.
The qFT8 Interface
The application is organized around several main areas:
- Bottom operating bar
- Spectrogram
- Stations
- Log
- Settings
The spectrogram provides the familiar visual representation of activity across the FT8 passband and allows you to select the transmit offset.
The Stations tab is where qFT8 becomes considerably more interesting than a simple mobile FT8 decoder.
AUTO Mode: qFT8’s Most Interesting Feature
qFT8 has two primary operating approaches:
AUTO and CALL.
In AUTO mode, qFT8 analyzes decoded stations and chooses an eligible contact according to the criteria you’ve configured.
The target-selection system can be used to pursue objectives such as:
- Any new station
- Nearby stations
- Distant stations
- Strongest signals
- DXCC entities
- Grids
- CQ zones
- ITU zones
- POTA stations
- SOTA stations
You can also define how frequently a station or entity can be contacted and whether the objective is based on callsign, band, mode, or confirmation status.
That means AUTO isn’t simply:
“Find a strong signal and call it.”
It can instead be configured around a particular operating objective.
For example, you could configure qFT8 to maximize unique DXCC contacts or work stations across different bands.
CALL mode
CALL mode provides manual control.
You select a station and tell qFT8 to call it. The application will continue trying to work that station until the QSO is completed, after which it can return to AUTO operation.
This gives you a useful combination of automation and operator control.
Spy and Busy modes
qFT8 also provides Spy and Busy modes.
Spy mode allows the application to attempt to contact stations that haven’t necessarily called CQ to you yet.
Busy mode can allow it to attempt contacts with stations that are already engaged in another QSO.
These are advanced operating features, and they are particularly interesting for operators trying to maximize the number of contacts made during a limited portable operating session.
qFT8 for POTA
This is where I think qFT8 really starts to separate itself from a basic Android FT8 application.
The software has dedicated POTA support for both hunters and activators.
As a POTA hunter, qFT8 can identify POTA activity and prioritize those stations in AUTO mode.
As an activator, you can configure the CQ modifier as POTA, allowing the software to transmit the appropriate POTA-oriented CQ message. qFT8 can then continue calling CQ and process incoming contacts automatically.
The logging side is even more useful.
When you export your POTA activation log, qFT8 can populate the relevant ADIF fields, including:
- MY_SIG
- MY_SIG_INFO
- MY_POTA_REF
That means the resulting ADIF file contains the information required for the POTA activation rather than forcing you to manually edit every contact afterward.
For a portable operator, that’s a meaningful reduction in post-activation work.
qFT8 for SOTA
SOTA receives similar treatment.
qFT8 can identify SOTA activity from CQ modifiers and summit references, prioritize SOTA stations, and provide SOTA-specific ADIF export functionality.
For an activator, the workflow is straightforward:
- Synchronize the phone’s time.
- Set the CQ modifier to SOTA.
- Configure AUTO mode.
- Enable transmission.
- Let qFT8 call CQ and process chasers.
If a particular chaser needs to be worked manually, you can select that station and use CALL mode before returning to automatic operation.
Again, the important part isn’t simply detecting SOTA contacts.
It’s the combination of operating + automation + logging in the same application.
Logging, ADIF, QRZ and LoTW
qFT8 includes standard ADIF import and export, allowing you to move QSOs into or out of the application.
That makes it much easier to incorporate qFT8 into an existing station rather than treating it as a completely isolated logbook.
QRZ
qFT8 provides direct QRZ integration.
A completed QSO can be uploaded automatically, and failed uploads can be retried in the background. The developer notes that QRZ integration requires an appropriate paid QRZ subscription.
LoTW
LoTW integration is also built in.
The setup requires your LoTW credentials and the appropriate TQSL certificate, but once configured, qFT8 can upload QSOs and check confirmations automatically.
You can also configure how qFT8 determines whether a QSO has been successfully uploaded—for example, requiring it to reach either QRZ or LoTW, or requiring both services.
That’s unusually sophisticated logging functionality for an Android application.
JS8 Support
qFT8 isn’t limited to conventional FT8-style exchanges.
The current application also includes a JS8 chat interface.
JS8 mode provides keyboard-to-keyboard messaging, with multiple operating speeds. qFT8 organizes traffic into global, broadcast, group and individual station channels, while also supporting longer messages through automatic multi-chunk transmission.
One important point is that these messages are not private or encrypted. They are transmitted over amateur radio in the clear and can be received by other stations monitoring the frequency.
Remote Web Server
Another unusually advanced feature is qFT8’s built-in web server.
The phone can host a web interface that lets another device on the same network monitor and control qFT8.
Depending on the configured security level, the web interface can provide:
- Spectrogram viewing
- Station monitoring
- Log viewing
- AUTO control
- Manual CALL control
- Frequency selection
- Band changes
- TX control
The default TCP port is 13497.
This can be useful in two very different situations.
At home, you could use a laptop or tablet as a larger secondary display while the Android phone remains connected to the radio.
In the field, you could potentially use another device as a control/display terminal.
There is an important security warning here.
The remote interface has three security levels:
Level | Capability |
|---|---|
Read only | View station activity and logs |
Read + Stop TX | View information and stop transmission |
Full control | Full remote operation |
Full control should obviously be treated carefully. Anyone who gains access to the configured network endpoint could potentially control the station, including starting transmission.
I would use the least powerful access level that meets your needs.
The Limitations You Need to Know
qFT8 is impressive, but this isn’t a mature desktop application with years of development behind it.
There are practical limitations, and the developer’s troubleshooting documentation is unusually candid about them.
USB connectivity can be finicky
A poor-quality cable, incompatible OTG adapter, loose connection, or charge-only cable can prevent the phone from communicating properly with the radio.
Carry a spare cable if you’re taking qFT8 into the field.
RF interference can affect the phone
The developer specifically warns that RF from the transmitter can interfere with the phone’s touchscreen.
A poorly shielded USB cable or an antenna positioned too close to the phone can result in an unresponsive screen during transmission. Ferrites or chokes may help.
This isn’t unique to qFT8, but it is particularly relevant when your entire station is concentrated around a phone.
Android battery management can interfere
Some Android manufacturers are aggressive about shutting down background applications.
If qFT8 stops working when the screen is turned off, the developer recommends checking the phone’s battery settings and allowing qFT8 to run without optimization.
This is something I would test before relying on qFT8 during an important activation.
You cannot change transmitter power from qFT8
For safety reasons, qFT8 does not provide software control of transmitter power.
Power must be adjusted on the radio itself.
That’s actually a sensible limitation for a portable application, but it’s worth knowing.
QMX and QDX power readings have limitations
The documentation identifies several situations where power readings can be misleading.
For example, QDX equipment does not provide the power/SWR information qFT8 would normally expect.
There is also a known QMX firmware issue in which power readings above 9.9 W can wrap around—for example, a reported 10.1 W can appear as 0.1 W.
That’s a radio firmware issue rather than evidence that qFT8 is actually transmitting at the displayed power.
Phone processing power matters
If messages are visible on the waterfall but arrive too late to be decoded, the phone may simply not have enough processing headroom for the selected decoding configuration.
The manual recommends adjusting decoding speed and timing, and warns that deep decoding requires additional processing power.
So don’t assume every inexpensive Android phone will perform identically.
qFT8 vs. WSJT-X
This is probably the most important comparison.
WSJT-X remains the reference application for FT8 operation. The current official release is available for Windows, macOS and Linux and supports FT8, FT4 and numerous other weak-signal modes.
So is qFT8 a replacement for WSJT-X?
Not really.
It’s better understood as a different operating platform.
qFT8 | WSJT-X | |
|---|---|---|
Primary platform | Android | Windows/macOS/Linux |
FT8 | Yes | Yes |
FT4 | Yes | Yes |
Portable phone operation | Excellent | No |
Laptop required | No | Yes |
Direct radio integration | Extensive | Extensive |
POTA/SOTA features | Excellent | Requires additional workflow |
ADIF | Yes | Yes |
QRZ integration | Built in | External workflow |
LoTW integration | Built in | External workflow |
Remote web interface | Built in | Different ecosystem |
Best environment | Portable operation | Shack/desktop operation |
Software maturity | Newer | Extremely mature |
WSJT-X has a huge advantage in maturity, documentation, ecosystem and long-term acceptance.
qFT8’s advantage is portability.
If I’m sitting at a desk with a large monitor, a full-size radio and a reliable computer, I see little reason to abandon WSJT-X simply because qFT8 exists.
If I’m standing on a summit with a QRP transceiver and want to leave the laptop at home, the calculation changes completely.
qFT8 vs. FT8CN
FT8CN is another Android FT8 project and is therefore a much more direct comparison.
FT8CN describes itself as an application for running FT8 natively on Android and has been available for several years.
qFT8 builds on some of the same technical ecosystem, including components from FT8CN and ft8_lib.
The distinction is that qFT8 has developed a particularly broad feature set around portable operation, including its current radio-support list, AUTO/CALL operation, QRZ/LoTW integration, POTA/SOTA workflows, JS8 support and remote web control.
FT8CN remains an important Android FT8 project, but qFT8 is particularly compelling if your goal is an integrated portable station rather than simply decoding FT8 on a phone.
Can qFT8 Replace a Laptop?
For some operators, yes.
For everyone, no.
I’d divide the answer this way:
qFT8 can replace the laptop if:
- You primarily operate FT8/FT4/JS8.
- You have a supported radio.
- Your Android phone is capable enough.
- You’re primarily interested in portable operation.
- You want to minimize station weight.
- You operate POTA or SOTA.
- You don’t need the broader desktop software ecosystem.
Keep the laptop if:
- You operate many digital modes.
- You want the full WSJT-X ecosystem.
- You need a large display.
- You perform extensive logging or data analysis.
- You run multiple radio applications simultaneously.
- You prefer a traditional shack environment.
The important distinction is that qFT8 isn’t trying to win a desktop-versus-desktop software battle.
It’s attacking the portable-radio problem.
And at that job, it makes a lot of sense.
Who Should Use qFT8?
I’d particularly recommend looking at qFT8 if you’re:
- A POTA activator
- A SOTA activator
- A portable QRP operator
- An operator using a QMX/QMX+, QDX/QDX-M, IC-705 or another supported radio
- Someone who wants FT8 without carrying a laptop
- An Android user who already carries a capable phone
- An operator who wants integrated QRZ/LoTW logging
The POTA/SOTA integration alone makes this considerably more interesting than a basic Android FT8 decoder.
Who Should Probably Stick With WSJT-X?
If your station is primarily home-based and you already have a computer dedicated to digital modes, there’s no compelling reason to switch simply because qFT8 exists.
WSJT-X is mature, extensively documented, cross-platform and designed specifically for weak-signal digital communication. The current project supports Windows, macOS and Linux.
qFT8 isn’t better because it’s newer.
It’s better when portability is the problem you’re trying to solve.
Is qFT8 Worth Using?
Yes—with one important qualification.
Treat it as software that you should test with your particular Android phone, radio and cable before depending on it for an important activation.
That’s especially important because Android hardware varies considerably, USB connectivity can be temperamental, battery-management behavior differs between manufacturers, and the developer’s documentation identifies several radio-specific quirks.
The good news is that qFT8 is free, contains no advertising, supports a very broad range of radios, and doesn’t require you to purchase anything simply to experiment with it.
That makes the barrier to entry extremely low.
Final Verdict
qFT8 is one of the most compelling Android applications for portable digital-mode amateur radio.
It isn’t merely a phone-based FT8 decoder.
The combination of native radio control, FT8/FT4/FT2/JS8 support, automatic time synchronization, ADIF logging, QRZ and LoTW integration, POTA/SOTA support, AUTO operation and remote web control makes it a surprisingly complete portable operating environment.
The most impressive aspect isn’t any single feature.
It’s the fact that so many of them work together.
A POTA activator can take a compatible transceiver, Android phone, battery and antenna into the field and potentially leave the laptop at home. qFT8 can handle the digital-mode operation, help identify the contacts worth working, maintain the log and prepare the activation records for later submission.
That’s a meaningful change to the portable operating experience.
I wouldn’t replace WSJT-X on my home station simply because qFT8 exists.
But if I were building a lightweight portable FT8 station today, qFT8 would absolutely be on my shortlist.
Best for: POTA and SOTA operators, QRP enthusiasts, portable ham-radio operators, and anyone who wants FT8 without carrying a laptop.
Not ideal for: Operators who need the broader capabilities and mature desktop ecosystem of WSJT-X.
Overall verdict: Highly recommended for Android-based portable FT8 operation.
Before You Go Portable
If you’re planning to use qFT8 away from home, test the complete station first.
- Confirm that your radio is directly supported or that your interface works.
- Use a known-good USB data cable.
- Test transmit and receive audio.
- Verify that the phone maintains accurate time.
- Test screen-off operation.
- Check Android battery-optimization settings.
- Test your antenna and SWR.
- Confirm that QSOs are being logged correctly.
- Test your QRZ/LoTW configuration if you’re using it.
- Export a sample ADIF file.
- Keep a backup logging method available for your first few activations.
That last point is especially important.
The best portable setup isn’t the one with the fewest components. It’s the one you’ve already tested.
Where to Get qFT8
The safest place to obtain qFT8 is the developer’s official distribution.
The official site currently lists version 2.20, provides a Google Play option and also offers the APK for manual installation.
The complete operating documentation is available in the:
Because qFT8 is actively evolving, I’d check the official manual and supported-radio list before every major station change rather than relying on an old compatibility list.
Frequently Asked Questions
Is qFT8 free?
Yes. The developer describes qFT8 as free and ad-free.
Does qFT8 work without a radio?
Yes. The documentation says you can experiment with qFT8 using the phone’s own speaker and microphone, and multiple phones can communicate with each other through audio when close enough.
Does qFT8 support the Icom IC-705?
Yes. The IC-705 is included in the current direct CAT/audio support list.
Does qFT8 support the QRP Labs QMX?
Yes. QMX and QMX+ are directly supported, with a dedicated setup and audio-check procedure.
Does qFT8 support POTA?
Yes. qFT8 has dedicated POTA hunter and activator functionality and can export POTA-specific ADIF fields.
Does qFT8 support SOTA?
Yes. It supports both SOTA hunting and activation workflows, including SOTA-specific ADIF export.
Does qFT8 support LoTW?
Yes. LoTW integration supports uploads, confirmations and log importing, although the required TQSL certificate must be configured.
Does qFT8 support QRZ?
Yes. QRZ integration can automatically upload completed QSOs and retry failed uploads, but QRZ’s relevant logbook API service requires a paid subscription.
Can qFT8 replace WSJT-X?
For portable Android operation, potentially. As a general replacement for the mature desktop WSJT-X ecosystem, no. WSJT-X remains a much broader desktop weak-signal platform for Windows, macOS and Linux.
Does qFT8 work with a Digirig?
It can work with external interfaces such as Digirig, but automatic detection may default to VOX because the interface appears as a generic USB-serial device. The qFT8 manual says to manually select the transceiver model if you want CAT control through such an interface.
Does qFT8 work when the phone screen is off?
Yes. qFT8 has a battery-saving/background operating mode, although Android battery-management settings may need adjustment on some phones.
Can qFT8 control transmitter power?
No. For safety reasons, transmitter power must be adjusted directly on the radio.
Is qFT8 suitable for POTA and SOTA?
Yes—that is arguably its strongest use case. The combination of portable Android operation, AUTO mode, activity detection and dedicated ADIF export makes qFT8 particularly well suited to field operation.
- Download: Google Play or sideload the APK from the developer’s site
- Manual: qft8.com/manual
- Source: GitHub
