WSJT-X is the software running FT8 on my IC-7300 Mark II, and it’s the default recommendation for anyone getting started with weak-signal digital modes. JTDX is a fork of that same codebase, and it’s been around long enough that people regularly ask whether it’s actually worth switching to.
Where JTDX came from
JTDX started as a fork of the WSJT-X codebase, maintained separately by a different development team with a specific focus on squeezing more decodes out of marginal signals. Both programs support the same core protocols, FT8, FT4, and the older JT modes, and both connect to the same logging tools like GridTracker, so switching between them doesn’t mean rebuilding your whole digital station.
What’s actually different
JTDX’s main claimed advantage is decoder sensitivity, its development has historically prioritized pulling extra decodes out of crowded or weak band conditions compared to stock WSJT-X. In practice, the gap between the two has narrowed considerably as WSJT-X has continued its own development, and most casual operators won’t notice a dramatic difference in day-to-day use. JTDX’s interface is also slightly more configurable in places, appealing to operators who like to tune decoder settings manually.
My take
I run WSJT-X because it’s the reference implementation, has the widest compatibility with other software in the ecosystem, and gets the most active ongoing development from the original K1JT team. If you’re a serious weak-signal DXer chasing every last decode in a crowded pileup, it’s worth trying JTDX side by side to see if it makes a real difference on your station. For everyone else, I wouldn’t bother switching just for the sake of it.
Related reading: What Is PSK31? · What Is RTTY? · ARDOP vs VARA