plainfolder → Ham radio → Check and fix an ADIF log

Check and fix an ADIF log

Drop the log and every QSO is checked field by field against the ADIF specification. What has a single right answer is fixed with one click; everything else opens in a card where you edit the QSO yourself.

No server processing No account No daily limits

What is checked

The fields every logger and LoTW need — call, date, time, band or frequency, mode — and then each field by its ADIF type: dates and times that exist, numbers that are numbers, grid squares, latitude and longitude, Y or N where ADIF wants Y or N, values from the ADIF lists (QSL_RCVD, QSL_SENT, PROP_MODE, continent and the rest), DXCC codes, CQ and ITU zones. A band that does not match the frequency is found, and so is a mode that ADIF keeps as a submode.

What is fixed with one click

Only what has one right answer: the band taken from the frequency when it is missing or wrong; FT4, USB or JS8 moved from MODE to SUBMODE under MFSK, SSB or MFSK; old mode names such as PSK31 written the current way; spaces around a callsign; latitude and longitude in decimal degrees (40.749971) written as ADIF wants them (N040 44.998), and a longitude written with N or S, as one logger does, put back as E or W; 160.0 in a whole-number field as 160. Nothing else is touched.

What you fix yourself

A date that does not exist, a mode ADIF does not know, a value outside its list. Click the QSO: every field opens for editing, with its name and description from the specification; remove a field, add one, or delete the whole QSO. To set one field in many QSOs at once — your grid square, your callsign, a POTA reference — use “Edit fields”: in every QSO the filters show, or only in the ones you tick.

Questions

Why does LoTW or Club Log reject my file?
Most often a QSO without a band or mode, a mode name it does not know, or FT4 written as a mode on its own. Those are exactly what this check looks for first — fix them here, save, and upload the new file.
Are fields my logger added flagged as errors?
No. Fields that are not in ADIF, like the ones some loggers add without the APP_ prefix, are listed as worth a look, not as errors, and kept as they are.
Is the log uploaded?
No. The file is checked and fixed in your browser; nothing is sent anywhere.

Other fixes

ADIF viewerMap of QSOs from ADIFMerge ADIF filesView the WSJT-X logLoTW ADIF downloadeQSL ADIF downloadClub Log ADIF downloadQRZ Logbook ADIF exportGridTracker log fileLog4OM ADIFLogbook Excel templateBlank ham radio log sheetPrint an ADIF logCheck a Cabrillo logRemove duplicate QSOsLoTW confirmations to your logPrint QSL cardsPrint QSL labelsPOTA log filesSOTA CSV from ADIFDMR contact listRadioID to AnyToneRadioID to OpenGD77RadioID to DM-32UVRadioID to MD-UV380RadioID to GD-77RadioID to Ailunce HD1Brandmeister talk groups