Stop exporting ADIF files. Stop uploading to QSL World by hand. Install the QSL World bridge once, and every FT8 and FT4 contact you make in WSJT-X flows straight into your QSL World logbook in real time — with the right callsign, grid, frequency, mode, RST, and timestamp, exactly as WSJT-X recorded it.
Free for all QSL World operators. Works alongside WSJT-X without changing how you operate.
The bridge runs quietly in the background while you operate. The moment you click Log QSO in WSJT-X, your contact is on QSL World — usually before you finish reaching for the mouse. No clicks, no exports, no copy-paste, no end-of-session ADIF cleanup.
It works whether you make one QSO an evening or two hundred during a contest.
Real-time logging. Every contact WSJT-X logs is sent directly to QSL World over your normal internet connection. Your logbook stays current to the second.
Full contact data. The bridge captures everything WSJT-X already knows about the QSO — DX callsign, grid square, frequency, band, mode, RST sent, RST received, transmit power, comments, and exact UTC timestamp. Nothing is guessed, nothing is lost.
No double-logging. Hands off your local WSJT-X log file. The bridge listens to WSJT-X’s standard UDP reporting (the same channel JTAlert and GridTracker use), so it coexists peacefully with everything else in your shack software stack.
Built for automation. Coming soon: enable automatic forwarding to QRZ.com Logbook through your QSL World account, so a single QSO ends up in three places — WSJT-X, QSL World, and QRZ — with one click.
Cross-platform. Native installers for Windows 10/11 and macOS. No Python, no command line, no dependencies to install yourself.
1. Install the bridge. Download the installer for your platform and run it. Takes about thirty seconds. No configuration screens, no API keys to copy and paste.
2. Tell WSJT-X to share its data. Open WSJT-X → File → Settings → Reporting tab. Tick Enable UDP Server and set it to 127.0.0.1 port 2237. (If you already use JTAlert or GridTracker, you’re done — they use the same port.)
3. Operate normally. Make contacts the way you always do. When you click Log QSO, the bridge picks up the contact and submits it to QSL World instantly. Watch your logbook update on qslworld.com in real time.
That’s the entire setup.
Because manual logging is a tax on the fun part. You came on the air to make contacts, not to fight with file exports at the end of the night. The bridge removes the chore.
Because contests are brutal. Two hundred QSOs in an evening means two hundred opportunities to lose track. Real-time logging means your QSL World logbook is contest-ready — not contest-cleanup waiting to happen.
Because your data should travel with you. QSL World gives you a confirmed, public, browsable record of every contact, anywhere you are. The bridge makes sure that record is always current.
Because you already have a WSJT-X workflow that works. The bridge doesn’t ask you to change a single thing about how you operate. It just listens.
Does it interfere with WSJT-X? No. The bridge is a passive UDP listener — exactly the same kind of program as JTAlert, GridTracker, or N1MM Logger+. WSJT-X doesn’t even know it’s there. You can run all of them at the same time on the same port.
Does it work with JTDX? Yes. JTDX uses the same UDP reporting protocol as WSJT-X, so the bridge picks up JTDX contacts the same way.
Do I need a QSL World account? Yes — the bridge submits contacts to your operator profile on qslworld.com. If you don’t have an account yet, sign up here (it’s free).
What if I lose internet during a session? WSJT-X still logs the contact locally to its own ADIF file as always. The bridge will retry submission once connectivity comes back. You won’t lose anything.
Does it modify my WSJT-X log file? No. The bridge is read-only with respect to WSJT-X. Your wsjtx_log.adi is untouched. If you ever uninstall the bridge, your local log is exactly as WSJT-X left it.
Can I disable it temporarily? Yes. Quit the bridge from your system tray and your WSJT-X contacts stop being submitted until you start it again. WSJT-X keeps logging locally either way.
What about privacy? The bridge only sends the contact data WSJT-X publishes on its UDP port — the same data JTAlert and GridTracker see. It doesn’t read your hard drive, doesn’t watch your keyboard, doesn’t talk to anyone except qslworld.com.
Will it submit to QRZ.com too? Soon. The next release adds optional one-click QRZ Logbook forwarding through your QSL World account, so every contact lands in WSJT-X → QSL World → QRZ automatically.
What does it cost? Nothing. The bridge is free for all QSL World operators.
[ Download for Windows ] · [ Download for macOS ]
Tested with WSJT-X 2.6 and 2.7, JTDX 2.2, Windows 10/11, and macOS 12+. Reports a problem or request a feature: qsl@qslworld.com
73 — and good DX.