Choose the value you can support.

When both records contain a field with different values or type indicators, the bench asks you to keep Log A's field or Log B's field. It does not choose the newest, longest or most complete-looking value.

A worked synthetic conflict

The sample W1AW pair differs in TIME_ON, RST_SENT and COMMENT. Log A reports 14:30:00, 599 and Park activation. Log B reports 14:30:30, 579 and Club log. Select a source for each conflict. If you choose B's time, A's signal report and B's comment, those exact values appear in the merged record. The discarded values remain in the manifest's original input records.

Check your station identity

The matching key identifies the station worked, not your own operating location. Inspect STATION_CALLSIGN, OPERATOR and MY_* location fields before deciding that a pair represents one contact. A conflict in STATION_CALLSIGN or MY_* also shows a reminder in the comparison. ARRL documents why callsign and station-location context matter for LoTW. This bench neither signs nor submits logs.

For a synthetic example, suppose A records STATION_CALLSIGN as K1TEST with MY_GRIDSQUARE FN31, while B records K1TEST/P with MY_GRIDSQUARE FN32. Even if CALL, band and time agree, one may describe a portable contact and the other a home-station contact. Check the original operating notes. Do not select a station value simply to make the rows agree; keep both records when you cannot establish that they describe the same QSO.

One-sided and empty fields

A field present in only one contact is copied into the merged contact automatically. An explicit empty field is still a value, not the same as an absent field. If A has an empty COMMENT and B has text, choose deliberately rather than assuming the text is more accurate. Unknown and application-defined fields follow the same rules.

Field type differences matter

If values agree but optional type indicators differ, the field is still a conflict. Choosing a source keeps its value and its type indicator together. This tool preserves indicators but does not certify all type/value combinations. The ADIF specification remains the format authority.

Keep uncertainty visible

If the records may describe separate contacts, choose Keep both contacts. Leaving the candidate unreviewed also keeps both. A selected merge can be undone using Keep both contacts. Review choices stay in browser memory only; refreshing the page loses them.

Header conflicts

Conflicting custom header fields need explicit choices before either download is available. Incompatible USERDEF definitions cannot be resolved in this tool because a choice could change the meaning of retained fields. Align those definitions in the source loggers first. Read what the exported copy preserves.