Upgrading Broadcaster from legacy versions
Broadcaster Upgrade Preparation Reference
Use this checklist before upgrading your Broadcaster from a legacy version.
Before You Begin
- Back up your configuration file. In the Broadcaster UI, go to Settings > Export and save the configuration before starting the upgrade.
- Confirm your license. Depending on your upgrade path, the license may need to be reloaded or reactivated after the upgrade completes.
- Whitelist the license server. V16 uses license2.zixi.com as its license server which needs to be whitelisted on your network before upgrading.
Upgrade Paths by Platform
Current Version | Target | Path |
|---|---|---|
v13/v14 | v16 | Upgrade in two steps: v13/v14 → v15, then v15 → v16. This helps prevent potential issues during the jump. |
v15.3.44122+ (Linux x86) | v17 | Direct upgrade supported. |
Linux ARM | v17 | Upgrade to v16.12.45243 first, then to v17. |
AWS Graviton (ARM) | v17 | Requires Amazon Linux 2023. Amazon Linux 2 is not supported. |
Windows/Mac | All Versions | No in-place UI upgrade. Run the installer directly to upgrade. |
For full OS compatibility details, refer to the System Requirements document.
Network & Licensing Configuration
Before configuring v16.x Broadcasters, make sure your port settings and licensing URL match the current requirements:
After Upgrading: Migrating the Files Directory
The upgrade installer does not automatically move files between the old and new install directories. Deleting the old directory without migrating it first can break existing workflows.
Once upgraded to v16, before you delete the old v15 directory:
- Locate the files directory under the old install path, e.g.: zixi_broadcaster-centos7/files
- Move its contents into the corresponding directory in the new install path: zixi_broadcaster-linux64/files
- Confirm dependent workflows still function correctly.
- Only then delete the old v15 directory to reclaim disk space.