ProPresenter 6 vs ProPresenter 7: what changed, and what should you do now?

ProPresenter 7 was a major redesign compared with ProPresenter 6, but in 2026 both are legacy releases relative to the current ProPresenter line. This comparison is still useful for understanding an older installation or migration history; it should not be read as a recommendation to install version 7 on a new production computer.

The short answer

Version 7 brought a rebuilt interface, much closer Mac/Windows parity and substantially reworked media and output workflows. If you are still running version 6 or 7 today, the practical question is usually whether to keep a stable legacy machine temporarily or move to the current ProPresenter release—not whether to move from 6 to 7.

What changed when version 7 replaced version 6

A rebuilt interface

Version 7 reorganized libraries, playlists and the live workspace. Long-time version 6 operators had to relearn where common controls lived, while new volunteers generally benefited from the more modern workflow.

Cross-platform parity

The macOS and Windows editions became much more alike. That reduced friction for teams preparing content on one platform and presenting it on another.

Media and output handling

Screen configuration, multiple outputs and production-oriented media workflows were reworked substantially in version 7. Those changes were especially important for teams running separate audience, stage and stream feeds.

Operating-system support at the time

Version 7 replaced version 6 as the actively developed generation in 2020. That historical advantage no longer makes version 7 a current release today; newer ProPresenter generations have since replaced it.

Migrating a legacy production setup

1. Back up first. Preserve libraries, playlists, themes, media and any licence information before changing the working machine.
2. Build the replacement alongside the old system. Keep the proven production computer available until the new one has passed rehearsal.
3. Move a small sample first. Check fonts, media paths, themes and screen layouts before importing everything.
4. Verify licensing early. Current subscriptions use account sign-in and seats; legacy versions may use keys or unlock codes.
5. Run full rehearsals. Test the complete signal path, not just the operator screen.

Licensing is different now

Legacy ProPresenter 6 and 7 installations came from an older perpetual-licence era. Renewed Vision now sells new ProPresenter purchases as monthly or annual subscriptions, and the subscription documentation describes access to releases beginning with version 17. An old version 6 or 7 key does not by itself represent a current subscription.

Recommendation

If a legacy machine is stable and an important event is days away, leave it alone until you have a maintenance window. For planned upgrades, test the current release on supported hardware, confirm the subscription/seat plan, migrate content deliberately and keep the old system as rollback until the new workflow has survived real rehearsals.