Platforms & versions
On this page
Scope
XTermPro is designed as a cross-platform desktop operations workspace. Download availability and feature testing are separate: a package existing does not prove every feature has passed native testing on that platform.
Choose a platform
| Platform | Verified v3.2.18 packages | Notes |
|---|---|---|
| macOS | arm64 DMG, amd64 DMG | Match Apple Silicon or Intel hardware. |
| Windows | x64 installer ZIP, x64 portable ZIP | Extract fully before installation or launch. |
| Linux | None in this release | Experimental — awaiting development release. |
| iOS / Android | No mobile app package | The website can be browsed on mobile. |
Feature and component differences
The v3.2.18 release notes announce combined tag filters. The v3.2.17 notes announce the unified script workspace. These are publication evidence, not native functional tests performed for this website.
SSH/SFTP, files, notes and logging workflows in these guides are based on product source documentation where not specifically confirmed by release notes. Check the actual package and controls. Local terminals depend on the OS shell; do not assume POSIX commands work in every Windows shell.
HTML/JS, PDF, Office previews and recording depend on packaged runtime components. Kubernetes requires a reachable API, credentials, RBAC permissions and any relevant cluster components. AI/iChat and cloud sync require services and credentials. RDP remains a development preview.
Check before upgrading
- Record the installed version, OS, architecture and original package source.
- Save files and notes and back up configuration plus independent data.
- Read the target release notes and choose the matching package.
- After installation, verify the displayed version and a small test workflow before normal use.
Common problems
Equal version labels do not guarantee equal package components. Missing controls can depend on platform, permissions, service settings or feature switches. Do not delete configuration to investigate a missing capability. Use Troubleshooting and include the package source when contacting support.