Every logger speaks its own dialect.
N1MM hands you a Cabrillo file. Your handheld logging app spits out ADIF with a slightly different field set. The VHF contest robot wants EDI. POTA wants ADIF with park references in exactly the right place. SOTA wants a CSV, split per summit. And the moment you try to send the same session to two different places, something is missing, mislabelled, or in the wrong column.
I kept running into this while getting my station and my logging habits sorted out, and with my first field day coming up in September it was only going to get worse. So I built a tool that sits in the middle of all of it. One log in, the right format out. I called it QSObridge.
The Idea in One Picture
The whole thing is a bridge. Messy input on one side, a clean validated log in the middle, and whatever format you actually need on the other side.
Read Almost Anything
You drop a file in, paste from the clipboard, or pick several files and merge them. QSObridge reads ADIF (.adi and .adx), Cabrillo, EDI / REG1TEST, SOTA-CSV, FLE, and generic CSV, TSV and XLSX tables with a column mapping step for the odd ones.
It is deliberately forgiving. Encoding is detected automatically, broken records are skipped with a warning instead of crashing the whole import, and every field your logger exported is kept, even the ones a stricter tool would silently throw away. Two ADIF files with different field sets? No problem, everything is preserved.
Edit in a Real Grid
Once the log is in, you get a fast virtualised grid with dynamic columns, so you immediately see every field that was actually present in the file. From there it behaves like the spreadsheet you wish your logger had:
Validate Against What You Are Actually Submitting
This is the part that saves the field day, literally. You pick your target, a contest or an activation, and QSObridge instantly shows the required fields as columns, pushed to the front and flagged in amber, even if your log does not have them yet. Anything missing or invalid gets a red border, plus a plain “still needed” summary so you know exactly what to fix before you hit export.
There is band plan consistency checking, tooltips, and a health panel so you can see at a glance whether the log is ready to go.
Eighteen Profiles Built In
You do not have to configure any of this from scratch. QSObridge ships with 18 ready profiles, selectable in one click, and it can auto-detect the right one from the Cabrillo contest ID.
Profiles are just JSON, so they are easy to import and share. If you need something exotic that is not on the list, you can assemble your own output format instead.
Export, With a Wizard
On the way out you can produce ADIF (with POTA, WWFF, SOTA and LoTW flavors), Cabrillo v3, EDI, SOTA-CSV (split per summit), JSON, or a custom format. You pick exactly which fields to include, see a live preview, and get a warning if the chosen format would drop data, with a sidecar file to keep the rest. An upload wizard points you at the right flavor for LoTW, eQSL, QRZ, Club Log, POTA, WWFF, SOTA or a contest robot.
The v2 Additions
Version 1 was already the full converter. Version 2 added the smart stuff:
There is also ADX output and dBase DBF input, saved views that remember your filters, columns and sorting, and a proper pass over accessibility with ARIA grid roles and live status messages.
Where It Draws the Line
One thing QSObridge deliberately does not do is award and statistics tracking. That job belongs with LoTW, Club Log, QRZ and the D3 logbook map already on this site, not inside a converter. Keeping the tool focused on one thing, moving a log cleanly from one format to another, is what makes it worth reaching for.
The whole thing is client-side, offline installable as a PWA, MIT licensed, and tested with a healthy pile of automated checks so it does not quietly mangle your log. No account, no server, no data leaving your device.
73 de ON3VZ