Comparison
Cross Platform Terminal vs Windows Terminal
Microsoft's tabbed terminal host for Windows, connecting to command-line apps through ConPTY. Windows Terminal’s own site →
| Feature | Cross Platform Terminal | Windows Terminal |
|---|---|---|
| Platforms | Linux, Windows (macOS in progress) | Windows 10 build 19041+ and Windows 11 |
| Windows | Native, identical to the Linux build | Native — it ships with the OS |
| Licence | Proprietary | MIT, open source |
| Price | €7.49/month or €67.41/year, no free tier | Free |
| Rendering | GPU, whole grid in one draw call | DirectWrite-based text layout and rendering, 24-bit colour |
| Configuration | In-app settings, per-profile | A JSON settings file |
| Session persistence | Opt-in detachable sessions, no multiplexer needed | None built in |
| Agent awareness | Detects 8 agent CLIs and reports five states per pane | None |
Where Windows Terminal is the better choice
- Free, already installed, and the best possible WSL and PowerShell integration — it is Microsoft's own console host.
- Tabs, panes, themes and profiles, maintained by the platform vendor.
- If Windows is your only machine, there is very little reason to pay for anything.
Where CPT is the better choice
- It only runs on Windows. Your Linux box gets something else, with different shortcuts and a different layout — which is the specific problem CPT is built to remove.
- Detachable sessions, dockable panels, edge rails and pinned panes.
- Agent detection with real per-pane states.
The short version
Windows-only developers should use Windows Terminal; it is free and it is very good. CPT earns its price the moment you have a Linux machine as well and are tired of maintaining two different muscle memories.
Windows Terminal details checked against Repository on 10 September 2026. Projects move; if something here is out of date or wrong, tell us and it gets fixed.