WSJT-X Log File Viewer

27th March 2018



This article has been retained as at least some of the details that apply here also apply to the newer "LogView" software.



Note @ 09 June 2018 :  V1.0.0.15 is available for download below but the screenshots and textual description have not yet been updated.  Some functionality has changed and additional features incorporated in this release : Last 50 QSOs, details of radio and antenna used at the time for export in the ADIF for log updating etc..  This latter detail only appears once a radios.txt and antennas.txt file are created - see the File menu to do so - and restart the software before doing any logging on WSJT-X - then select the radio and antenna in use FIRST. 

New menu item under File is 'Generate local grids.txt file' which scans a copy of the WSJT-X-generated ALL.TXT file and extracts a list of callsigns and grid details, which is subsequently used to fill in missing grids during ADIF export.  If WSJT-X is running at the time, an error message may appear if the Decode button is illuminated at the time - just press the OK button until it disappears. Best practice is to run this 'Generate' function when WSJT-X is not running.

Beware using "Rebuild local CSV log file" function until the description is published.

Most importantly, several bugs in the previous releases (v1.0.0.10 and v1.0.0.13 ) have been resolved.


How I use it in practice.... I can see who I have worked fairly quickly by scrolling up or down the callsign list box - or - do a full callsign or wildcard search :

WSJT-X Log File Viewer at bottom LHS of screen, V1.0.0.13 format, with AutoShow selected and displaying the last QSO.


As a newcomer to FT8 via the WSJT-X software, I was left with a question as to who I had worked already on the FT8 mode. You don’t really know until you import the contacts from the automatically generated (by WSJT-X) ADIF file into your main station log, and then you have to have the Logbook open. I use an older version of HRD software (the last one of the free version) and there are some tools to handle automatic import for the newer versions (HRD 6.x) but not 5.x so the process is slow – and manual. Apart from that, the is just way too much info on screen in a typical log book application.

Actually I added FT8 to the emission mode list in HRD so that it would support my contacts but my ADIF import failed because of the <QSO-Date-Off field contained in the data file output by WSJT-X. There is a work-around for that issue too from Version onwards with the inclusion of an ADIF Export feature, notes futher down.

Back to the ‘who have I already worked’… Well, the WSJT-X software actually creates two log files in a specific folder, the ADIF mentioned above plus a comma separated text file and this latter file is the one that interests me at the moment. I opened it using Notepad and I could see my list of completed contacts easily enough but if I made another contact then I had to close it and re-open it. Not a very efficient process.

A special note : You MUST have the 'Prompt Me To Log QSO' ticked (WSJT-X/File/Settings/Reporting/top box in the Logging panel) and actually log the contacts before this software will work.

I thought a simple Windows application would probably be a better approach, read the plain log file and process it a bit and then display just a list of callsigns. I don’t really have any interest in the date, time or even which band was used so they don’t need to be shown. I wrote this in Delphi7 (a visual Pascal) and it is small, quick and does not actually need any real installation process.

The basic application shows a list of callsigns sorted by prefixes, and each new initial number or letter starts a new line. A count of logged entries completes the display. Now the nice bit: if the software determines that the WSJT-X log file has changed because you have made another QSO, it reloads it and updates the callsign list on the screen then leaves the cursor at the most recent additions place. That means that if you have worked a new callsign in WSJT-X then it automatically appears in the application’s window, fully sorted. The default display is ALL contacts but the other WSJT-X supported modes are also available to display individually eg JT4 JT9 JT65 JTMSK  PSK.. FSK.. MSK.. (and any future modes incorporated into WSJT-X)  all depending on what the log file contains.

It (currently) has a QSO count limit of 10000 inbuilt but most users are unlikely to hit that point very quickly, if ever.

It should run normally on any version of 32 or 64 bit Windows.



Early version : This is a screen grab part way through a FT8 contact with KH6AP... Note that his callsign does NOT appear in the "K" line in the Log Viewer at the LHS :




Early version : This is a screen grab after the FT8 contact with KH6AP... Note that his callsign does NOW appear in the "K" line in the Log Viewer at the LHS :




Resize the Viewer display in width and height to utilise spare space on your monitor's display.


This is the Log Viewer display window. A few bells and whistles have been added since the original release. The  Mode selector allows selection by the various WSJT-x modes with the default view being all modes. If the log file only contains one mode (eg FT8) then the All display will be the same as (eg) the FT8 display when FT8 is selected from the drop-down box.  F.S. = Font Size.

The C/S (callsign) or Prefix Search: box is used internally as well as by the user to initiate searches of the total log data. At least two characters plus the Enter key will do a callsign lookup of the log data plus provide country, continent, latitude, longtitude, approximate bearing details, handy when you see an unusual callsign and want to know which way to point the HF yagi. Clicking on the LAST: data box will open up details of that contact - and if AutoShow is ticked then those details will appear automatically as you log your QSO in WSJTX. Clicking on the CLR (clear) button closes any overlaying search results boxes.

AutoShow now has a slider control included that allows the user to select how many characters of the last QSO callsign will be used in the AutoShow results. The minimum is 2, the maximum is 6, the default is 3, the value selected is just to the left of the slider (eg 3ch means a '3 character' match). That means that the listed callsigns might be all for that call area (ie the basic prefix) or just the station actually worked, and the value of the setting is retained for the next time the software is executed. Changing the slider value automatically updates the displayed results.


For example, clicking on 7K2XRZ in the basic viewer list brings up the low level overlay and fills 7K2XRZ into the search box (intentionally shortened by one character) :

V10010 7K2XRZ 1


Then clicking on the 7K2XRZ in the BOLD PRINT in that first overlaying window produces more detail :


V10010 7K2XRZ qso detail

Note the My Call/Grid detail at the bottom of the listing.



This is a much-magnified view of the "search box" in an early version.  If "Wild" is ticked, just a prefix or suffix to see any matching results where it occurs in any part of a callsign.  With it unticked, it must start the callsign i.e. the prefix.   AutoPrefix has been implemented as AutoShow, details above.


Log exporting in ADIF format:  it now has an ADIF export facility that actually works with LOTW's TQSL and also imports into eQSL without problems. It would probably import directly into many other logging applications that currently show up errors when attempting a direct import from the WSJT-X log adi file. It also imports into HRD 5.x provided you have added the WSJT-X modes into HRD's emission mode list. Some backups are created for ADI files so that critical log data is not overwritten.

There is an option that allows 'New only' so that new contacts since the last export are the only ones processed thus avoiding the dreaded "dupe" message on imports. Of course, full log exports are still available.  

The Create/edit radios.txt and Create/edit antennas.txt menu options are optional. If utilised, this provides selectable lists of radios (example above)  and antennas that are when exporting ADIF data. It is important to change antenna selection when changing bands as the accuracy of the final log data depends on these settings.  

The 'Rebuild local CSV log file' function must be used only as a last resort as it simply takes the main WSJT-X log file, adds the extra fields used to enhance the ADIF output and replaces the previous log file - after first backing up the original !  Any callsign changes (eg /P or /VK2...) or grid square details eg (QG62LG, QG55IU,...), rig names and antenna selections in the previous local log file are all lost when using this rebuild option. 


The modes currently supported by WSJT-X 1.8 have been hard-coded at the moment. By default the software always starts with ALL selected.


The default font size is 10 but 11pt works well for me. Set it to any of the available values and all callsign-based segments will show the new sizing.


The View menu provides easy access to a number of files used by either WSJT-X or the Viewer. Note that the top listing for WSJTX.LOG is a local copy and not the original. The one at the bottom is the actual main log file and should not be kept open while making QSOs with the WSJT-X software.


The 'Last 50 QSOs' is available from this menu item as well as from a button on the main screen. Selecting any of the listed callsigns brings up data about that QSO.


The blue text on the About box is a hyperlink back to the VK4ADC.COM web site, but not directly to this web page.


New menu item under File from V1.0.0.15 onwards is 'Generate local grids.txt file' which scans a copy of the WSJT-X-generated ALL.TXT file and extracts a list of callsigns and grid details, which is subsequently used to fill in missing grids during ADIF export.  If WSJT-X is running at the time, an error message may appear if the Decode button is illuminated at the time - just press the error message's OK button until it disappears. Best practice is to run this 'Generate' function when WSJT-X is not running.


Error displayed... Just press the OK button until it disapears....


 The best suggestion is that you just play with the software and find out what it can do for you. You can't hurt the original WSJTX data as any operations are made on copies of the data files, not the originals.


The log file location is determined from the Windows logged-on user ID automatically.

The display window's position on-screen plus other working values are saved to the Windows Registry when the Exit button is pressed to terminate the software. 

The ZIP of this Viewer application IS NO LONGER AVAILABLE FOR DOWNLOAD.
Currently V1.0.0.13, zip file contains WSJTLogViewer.exe and CTY.DAT.

(Please do not copy this file and make available from other websites - the latest version will only be available via this link,)

Just extract it into any folder (preferably a new/empty one) OVERWRITING ANY PREVIOUS VERSION, it will make a Desktop shortcut to the executable the first time it is run. No other things to do to install it.

Please note that it is early in development so may have some issues to be resolved as yet.

Please notify of any bugs found direct to 'doug at vk4adc dot com' with subject 'WSJTXViewer Bug'.


WSJTX Log Viewer Registry Entries Removal Tool :   If you have tried out the software and it doesn't do anything for you, you can manually delete any Desktop shortcut and delete the folder where the application resides (and thus removing any working data files) but the Log Viewer also stores some settings info in the Windows Registry. To remove those entries, download the Viewer Removal Tool (ZIP Format file here), extract and run it.   It will delete any registry entries used for versions up to any including V1.0.0.10.




Not all images on this web page are updated with software version changes. 

File versions:

V1.0.0.0 Initial release 27Mar2018

V1.0.0.1 28Mar2018 Fixed last line of callsigns not showing, changed results font to Times New Roman (Blue for main list, Red for individual callsign details box) & added font size thumbwheel, made window width resizeable and vertical size partially resizeable. 

V1.0.0.3 29Mar2018 Released version that includes an ADIF export function via a small button above the one marked Exit. The resulting ADIF file does not contain the <QSO-Date-Off field. 
The application also creates a shortcut on the Windows desktop only on the very first time it is run. If you subsequently delete it, it does not make another.
The WSJTX log file is automatically copied and updated  across to a file in the executable's folder, the same folder that contains the ADI export file, so that the original file remains untouched.

V1.0.0.4 30Mar2018 Callsign results set with varying colours so that different leading letters or numbers have a pattern of changing colours.

V1.0.0.5 4Apr2018 Added a callsign search box with a Wild option.  With Wild ticked, any callsign with matching any letters anywhere will be displayed - can even be a single letter or number. When not ticked, the letters must match from the beginning of the callsign i.e the prefix component. The CLR (Clear) button clears the callsign search text box and the search results table. Fixed ADI export structure for dates and times so HRD accepts (done 10/4/2018).

V1.0.0.6 15Apr2018: Revised the search results arrangements. Any callsign in full log list can be simply clicked and all results (QSOs) matching that callsign are shown in an overlaying window. Any result in this second window can have the callsign line clicked to reveal the full details saved in the WSJTX log file - eg confirming sent and received reports for a contact - in a new overlapping window. A single click closes the overlap window (aqua background) and a double-click closes the initial search results window (yellow background).  A press of the CLR button (Clear) closes both results windows.  The cursor on startup and after any new log addition is placed on the most recent callsign and a click on that will provide the details - the cursor is now a hand symbol over the search results boxes to show an altered use mode.  The "wild search" has been improved and the duplicate callsign entries bug has been solved. The WSJTX log file location detail box has been removed as it is set by WSJTX and is not under user control.

V1.0.0.7 16Apr2018: Screen layout revised slightly to allow a format control to be added for the ADIF export feature. The export can be 'Unsorted' (preferred), 'Sorted' into callsign order, or 'New only' which exports only those QSOs not previously exported.  The exported data automatically opens in Windows Notepad if the AutoView is ticked.  The search results overlay background colours were also altered to yellow and aqua respectively to aid reading easily.

V1.0.0.8 25Apr 2018:  Major changes to the file system arrangements in this releease so that the WSJTX.LOG file details are only added to a main local log file ( Viewer_local_log.csv ) if the software senses that the source data file changes.  Two additional fields are added into the local log file, your callsign and your grid square info as retrieved from WSJT_X.INI as set at the time WSJTX is configured. This means that you can maintain one continuing log for all contacts made using WSJTX even when portable (eg VK4ADC/3 or even KH6/VK4ADC) or in a different grid square (eg QF22 instead of QG62). The country, continent, Latitude and Longtitude details are also displayed along with an approximate bearing and distance (in KMs) upon a callsign or prefix search (2 chars + Enter is the minimum required in the search box) with DX info sourced from a CTY.DAT file in the application's folder. CTY.DAT will update from the WSJTX log folder if one is present there and is newer. The current callsign and grid settings are displayed in the "Logged with:" panel. The AutoShow box can be ticked to automatically display callsign and contact details for any new QSOs, noting that the search callsign is intentionally shortened by one character (eg VK4AD instead of VK4ADC) to ensure search outcomes are complete. The callsign and grid have been added to the log detail summary as different values may have been used thoughout the log, and these details are also in the ADIF export data. A comand line /CTYDEBUG generates a CTYBASIC.DAT file which contains a variant of the CTY.DAT source information, and it is this revised data which the country lookup utilises. 

V1.0.0.9  27Apr2018 Reinstated a couple of sections of code that caused the WSJTX.LOG file not to be updated to the current application folder.

V1.0.0.9  29Apr2018 A file menu system was incorporated to reduce working screen space and now allows quite a narrow Viewer window. Note vertical and horizontal sizes are variable to a point so width can be set to utilise spare space on screen. All ADIF Export operations have been moved to the File Menu along with the Exit function (or the user can use the X function at top RHS of the application to exit), displayed mode selection is now on Mode Selection with the default being All every time the software is started. Font sizes from 8 to 16 point can be selected from the Font Size menu.  A new series of options is on the View menu and it allows quick and easy viewing of a number of files used in the Viewer operation - special warning about the active WSJTX log file included. The main function of the About menu item is to provide a quick hyperlink back to the VK4ADC.COM web site.  An exra function has been added to the View menu to display the paths of the various files against a green background and is for diagnostic purposes if the data file is not updated after each QSO.


30 April 2018 : Registry removal tool created and added to the web page. It removes any entries in the Windows Registry that the Log Viewer creates and uses. Download link above.