Can I edit a SOTA CSV here?

Yes. Click a QSO to change any field, or use Edit fields to change many at once — a summit reference, a callsign, a mode. Then save with the SOTA button: one file per summit and UTC day, and one for chases.

What happens to DATA when I save ADIF?

ADIF has no mode called DATA — SOTA uses it for every data mode. It is kept as written and the page says so; set the real mode (FT8, PSK31) with Edit fields if LoTW needs it.

Is the file uploaded anywhere?

No. It is read by the page itself, in your browser.

plainfolder → Ham radio → SOTA

Open a SOTA CSV file — a Summits on the Air log

Drop the .csv and every V2 line opens as a QSO — date, time, call, band, mode, your summit and theirs — in a table you can sort, filter and edit. Save it as ADIF, or as SOTA CSV again, one file per summit and day.

No server processing No account No daily limits

What a SOTA CSV file is

SOTA CSV is the log format of the Summits on the Air database: one QSO per line, no header, ten fields — V2, your callsign, your summit, date, time, band, mode, the other callsign, their summit, a note. The date is day first (dd/mm/yyyy or dd/mm/yy), the time hhmm or hh:mm, the band a name such as 14MHz or 144MHz, the mode CW, SSB, FM, AM, DATA or DV. Your summit alone makes an activation, theirs alone a chase, both a summit-to-summit; a V2SWL line is a listener’s.

Excel turns 0905 into 905 and 01/11/26 into 11 January, and the database then rejects the file. Here the lines are read the way the database reads them — day first, always — and written back the same way. Lines separated by semicolons or tabs, quoted notes with commas, frequencies such as 14.285MHz instead of a band: all read.

What you can do here

Any logging programEach program writes ADIF its own way — field lengths counted in bytes or in characters, Latin-1 or UTF-8, UTF-16 from Ham Radio Deluxe. All of them open with every accent in its place: São Paulo stays São Paulo.

Nothing is lostEvery field is kept, including the ones a program adds for itself (APP_ fields) and user-defined ones, so saving the log again does not drop anything.

Files for radio programming softwareChannel and DMR contact files are made for the radio maker’s software (CPS), not written to the radio. Tested by importing into AnyTone AT-D878UVII CPS 4.00, AT-D878UV (first model) 4.00, AT-D890UV 1.05, AT-D578UV 1.21, AT-D868UV 1.39, AT-D168UV 1.07, BTECH DMR-6X2 PRO 1.22e, OpenGD77 CPS E2026.05.26, Baofeng DM-32UV V1.60, TYT MD-UV380/UV390 CPS V1.06, Retevis RT3S V2.41, Baofeng DM-1701 V1.05, Radioddity GD-77 V3.1.9 and Ailunce HD1 V3.05.

Messy files tooA field with a wrong length, a log that ends without its last end-of-record, the comments LoTW writes after its values — read the way the program meant them.

Convert SOTA CSV to something else

SOTA CSV→ADIF

Questions

Can I edit a SOTA CSV here?: Yes. Click a QSO to change any field, or use Edit fields to change many at once — a summit reference, a callsign, a mode. Then save with the SOTA button: one file per summit and UTC day, and one for chases.
What happens to DATA when I save ADIF?: ADIF has no mode called DATA — SOTA uses it for every data mode. It is kept as written and the page says so; set the real mode (FT8, PSK31) with Edit fields if LoTW needs it.
Is the file uploaded anywhere?: No. It is read by the page itself, in your browser.