Mac Ham Radio Logging Software: MacLoggerDX vs RUMlogNG

For years the standard advice to a Mac owner who wanted to keep a ham radio log was to buy a cheap Windows laptop. That advice is out of date. Mac ham radio logging is now served by two mature native applications, MacLoggerDX and RUMlogNG, both written by active DXers, both with rig control, DX cluster integration and direct uploads to Logbook of The World, and WSJT-X itself ships a macOS build for FT8 and the other weak-signal modes. This guide compares the two main loggers, explains what each does well, walks through the parts that are different on a Mac, such as serial ports and audio routing, and says honestly where a Windows program in a virtual machine is still the better tool.

The Two Native Loggers

MacLoggerDX

MacLoggerDX from Dog Park Software is the best-known Mac logger and, by the developer’s own count on the MacLoggerDX product page, is used in well over a hundred countries. It is a fully native macOS application built on a fast SQLite database. Its strengths are in everyday DXing: it organises and filters spots from your chosen DX cluster, tunes the radio to a spot with a click, can swing a rotator toward it, and raises alerts for rare contacts or band openings, including by text message or email. It supports more than a hundred radios for CAT control, logs contacts directly from WSJT-X, JTDX and JS8Call, and uploads automatically to Club Log, QRZ Logbook, LoTW, HRDLOG and eQSL. There are 2D and 3D maps, a DXpedition tracker with band and mode alarms, NCDXF beacon tracking, award tracking, label printing and support for the K1EL WinKeyer. The page offers a demo to try before purchasing.

RUMlogNG

RUMlogNG, by DL2RUM, describes itself on the RUMlogNG page as a logging, QSL handling and printing tool made especially for the short wave DXer, by a DXer. It handles an unlimited number of logs and QSOs, uses Club Log data for automatic DXCC recognition, includes a contest module, and can run RTTY directly through Fldigi or an Elecraft transceiver. QSL management is a particular strength: it prints QSL labels, tracks incoming paper cards, fully supports LoTW and eQSL with one-click upload and download, and can prepare files for a global QSL printing service. It connects to a DX cluster or a local skimmer, queries QRZ.com or HamQTH for callsign details, and keeps worked, confirmed and missing DXCC statistics in view.

MacLoggerDX Versus RUMlogNG at a Glance

The two programs overlap heavily, so the choice usually comes down to style and to a few specific features. The table summarises the main points from the developers’ own descriptions.

If you want the richest DX cluster and alerting experience with maps and rotator control, MacLoggerDX is the natural choice. If your life revolves around DXCC bookkeeping, paper QSL cards and the bureau, RUMlogNG was built for exactly that. Both import and export ADIF, so switching later is not a disaster; our guide to ADIF and moving your log between programs explains how to do it cleanly.

Rig Control on a Mac

CAT control works the same way on a Mac as anywhere else: the radio presents a serial port, usually over USB, and the logger talks to it. The Mac-specific details are the drivers and the port names. Most modern transceivers use a Silicon Labs or FTDI USB-to-serial chip; recent macOS versions include drivers for the common ones, and the port appears in /dev with a name beginning with “cu.” or “tty.” followed by the chip or device name. Both loggers list the available ports in their preferences, so you rarely need to type the path. If a radio does not appear, check whether the manufacturer offers a macOS driver, and check the System Settings privacy pane if the application has not been allowed to use the port.

Only one program can own a serial port at a time, which matters when you want a logger and WSJT-X running together. MacLoggerDX solves this by acting as a CAT server using the DX Lab Commander protocol, so WSJT-X talks to the logger and the logger talks to the radio. RUMlogNG and WSJT-X can be linked in a similar spirit, and the general technique is described in our article on rig control with Hamlib, which also runs natively on macOS. For Icom radios with network connectivity, wfview is an open-source Mac option that MacLoggerDX can interface with.

Audio, Sound Cards and Digital Modes

WSJT-X for macOS is a first-class build, and a Mac with a USB audio interface or a radio with a built-in USB sound card is a perfectly good FT8 station. The audio devices appear in the WSJT-X settings by name; choose the radio’s USB codec for both input and output, and make sure macOS is not using the same device for system sounds, or your next notification chime will go out on the air. Our WSJT-X FT8 setup walkthrough covers the settings in order, and the only Mac-specific step is granting microphone permission to the application the first time it asks. Both loggers then receive each decoded contact as it is logged and upload it to LoTW or Club Log in the background, so a Mac FT8 station needs no manual log transfer at all.

Fldigi is also available for macOS and gives you RTTY, PSK31 and the other sound card modes; RUMlogNG integrates with it directly. For CW, MacLoggerDX supports the WinKeyer, which keeps the keying timing in hardware where it belongs rather than at the mercy of the operating system’s scheduler.

Contesting on a Mac

This is the honest limitation. Serious contest logging is dominated by Windows programs, and the big names in our contest logger comparison are Windows-only. Both Mac loggers can log a contest and RUMlogNG has a dedicated contest module, which is fine for a casual single-operator entry. For a full-weekend effort with SO2R, a multi-operator network, voice and CW message keying tied to the exchange, and Cabrillo output for every contest sponsor, most Mac-based contesters run a Windows contest logger in a virtual machine. On Apple silicon that means an ARM build of Windows under a virtualisation product, with USB serial devices passed through to the guest. It works well, though it adds a layer to troubleshoot. An alternative that avoids virtualisation on contest weekends is a small dedicated Windows machine for contesting, with the ADIF exported afterwards into the Mac logger that holds your lifetime log.

Setting Up a Mac Logger Step by Step

The first evening with either program follows the same path, and doing the steps in order avoids most of the questions that fill the support forums.

1. Enter your station details first. Callsign, locator, DXCC entity, CQ and ITU zones and the station’s default power. Everything downstream, from distance and bearing to award tracking, depends on these fields being right, and a wrong locator entered on day one produces wrong headings for every contact until it is noticed.
2. Connect the radio before importing anything. Plug in the USB lead, wait for macOS to enumerate the port, then choose it in the logger’s radio preferences along with the baud rate the radio is set to. Confirm that the frequency and mode in the logger follow the radio’s dial. If they do not, the usual suspects are a baud rate mismatch or the CI-V address on an Icom.
3. Import your existing log as ADIF. Export from your previous program, import into the Mac logger, and compare the contact count before and after. A mismatch almost always means a few records with unusual band or mode names that the importer rejected; the import report lists them.
4. Configure LoTW and the other services. Install TQSL, load your certificate, point the logger at it, and run a test upload of a handful of recent contacts. Then download confirmations so that your DXCC counts reflect reality.
5. Connect the DX cluster and set your filters. Choose a cluster node, log in with your callsign, and filter by the bands and modes you actually operate. An unfiltered cluster window on a contest weekend is unreadable; a filtered one is a working tool.
6. Link WSJT-X last. With the radio already under the logger’s control, set WSJT-X to use the logger’s CAT server, confirm that frequency changes in WSJT-X reach the radio, and make one FT8 contact to confirm that it appears in the log and uploads.

Once these six steps are done, daily use is mostly automatic: the radio sets band and mode, the cluster window fills with filtered spots, and each contact is logged and uploaded without a keystroke beyond the log entry itself.

Keeping the Log Safe and Confirmed

Whichever logger you choose, the workflow after each contact is the same: upload to LoTW and whichever other services you use, then back up the database. Both programs can upload automatically. The Logbook of The World system requires the TQSL application for signing, which has a macOS version, and the loggers call it for you once it is configured with your certificate. Our guide to LoTW, eQSL and paper confirmations covers the certificate setup. For backups, Time Machine will capture the logger’s database automatically; it is still wise to export an ADIF file now and then to a cloud folder, because a plain text ADIF can be read by any logger on any platform if the worst happens.

Other Mac Options Worth Knowing

• Browser-based logbooks. A self-hosted or hosted web logbook runs in any browser and sidesteps the operating system entirely. They are weaker at rig control but excellent for a multi-computer household.
• QRZ Logbook and Club Log as online primary logs, with a Mac logger only as the entry tool. Both Mac loggers can upload to them.
• Linux-style tools. Several open-source Linux loggers can be compiled or installed on macOS through package managers, though the native options above are more polished.
• Portable and POTA logging apps on an iPad or iPhone, exporting ADIF to the main Mac log at home.
• DX alerts. A monitoring application such as LY4A DX Reminder runs on macOS alongside your logger and alarms when a chosen callsign is spotted on your bands and modes, which complements the loggers’ own cluster windows when you are away from the desk.

The Bottom Line

A Mac is a fully capable logging and digital-mode platform. MacLoggerDX gives the most complete DX cluster, mapping and alerting package with broad rig support and direct links to WSJT-X; RUMlogNG gives a DXer’s bookkeeping tool with first-rate QSL and DXCC management and a built-in contest module. Both upload to LoTW and eQSL and both speak ADIF, so you can start with one and move later. The one area where Windows still rules is heavyweight contesting, and a virtual machine or a small spare PC fills that gap without giving up the Mac for everything else.

Frequently Asked Questions

What is the best ham radio logging software for Mac?

MacLoggerDX and RUMlogNG are the two mature native choices. MacLoggerDX leads on DX cluster, maps and alerts; RUMlogNG leads on QSL and DXCC bookkeeping. Both support LoTW, eQSL and ADIF.

Does WSJT-X run on a Mac?

Yes. WSJT-X has an official macOS build, and both Mac loggers can receive contacts from it automatically.

Can MacLoggerDX control my radio?

It supports more than a hundred radios over a USB or serial connection and can also act as a CAT server so WSJT-X shares the radio with it.

Can I run N1MM Logger on a Mac?

Not natively. Windows contest loggers run on a Mac only inside a virtual machine with the serial devices passed through, which is how many Mac-based contesters operate.

Does RUMlogNG upload to LoTW?

Yes. It fully supports LoTW and eQSL, including one-click upload and download of confirmations, using the TQSL application for signing.

Is there a free Mac logging program?

MacLoggerDX is a paid application with a demo to try first; check the RUMlogNG page for its current terms. Open-source Linux loggers can sometimes be built on macOS, and browser-based logbooks work on any platform.