CHIRP is distributed as a series of automatically-generated builds. Any time we make a change to CHIRP, a build is created for it the next day. Thus, CHIRP is versioned by the date on which it was created, which makes it easy to determine if you have an older build. We don't put experimental things into CHIRP before they are ready, except where specifically called out with a warning. Thus, you do not need to worry about finding a stable version to run. You should always be on the latest build available.
Upgrading: You do NOT need to uninstall an existing version of CHIRP before installing a newer one. Just install the new one and it will replace the existing copy! However, be sure to quit CHIRP before installing the new version!
The CHIRP team recommends CHIRP-next unless you experience problems with your radio. If you do, please see How_To_Report_Issues.
The next-generation version of CHIRP is now available for general use! This has the latest and greatest set of features and fixes, but not all radio drivers have been converted yet. Please see ChirpNextBuild for an overview of what CHIRP-next is, and ChirpNextBuildChanges for an overview of some of the larger changes to the UI. Drivers that have not been validated with CHIRP-next are denoted by an asterisk (*) symbol on the supported model list on the Home page.
System requirements for CHIRP-next:
- Windows 10 and later (64-bit)
- macOS Big Sur and later (universal binary with Intel and Apple Silicon support)
- Linux (all modern distros with python3, details here)
The current "daily" builds of CHIRP are the most stable and have the widest driver support. However, this older version is no longer being developed and does not work well on modern macOS and Linux operating systems. You should only use these legacy builds if your radio is not supported by CHIRP-next.
System requirements for CHIRP-daily:
- Windows 2000, XP, Vista, 7, 8, 10, and 11. Older versions of Windows are not supported
- macOS Intel and Apple Silicon macOS, but requires installation of Python 2.7
- Linux via flatpak
Translators and Developers¶
There is extensive documentation about the development and contribution process located at Developers
You can access older versions of chirp in the Daily build archive