# Qt 5 support to end starting in ParaView 6.2
**URL:** https://discourse.paraview.org/t/qt-5-support-to-end-starting-in-paraview-6-2/17365
**Category:** Development
**Tags:** qt
**Created:** [December 11, 2025, 10:56am UTC](https://discourse.paraview.org/t/qt-5-support-to-end-starting-in-paraview-6-2/17365 "2025-12-11T10:56:13Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [December 11, 2025, 10:56am UTC](https://discourse.paraview.org/t/qt-5-support-to-end-starting-in-paraview-6-2/17365/1 "2025-12-11T10:56:13Z")
To finalize ParaView’s transition to Qt 6, the ParaView team is planning to stop supporting Qt 5 in ParaView starting with ParaView 6.2. Qt 6 will be the only major version of Qt supported by ParaView going forward. ParaView 6.2 is scheduled for release mid-2026.
Qt 5.15 was end-of-lifed earlier [this year](https://endoflife.date/qt). Supporting only Qt 6 will reduce ParaView source code maintenance involved in supporting two Qt major versions.
Please let us know if this end of support for Qt 6 will cause problems for your use of ParaView.
---
### Author:  [@CsatiZoltan](https://discourse.paraview.org/u/CsatiZoltan)
#### Post date: [December 11, 2025, 6:04pm UTC](https://discourse.paraview.org/t/qt-5-support-to-end-starting-in-paraview-6-2/17365/2 "2025-12-11T18:04:54Z")
In terms of licensing, how does the existing and the potential future license changes in Qt 6 affect the use of ParaView in commercial applications (I mean a ParaView branded application)?
In terms of toolchain, did you face any issues compiling the Qt 6 based ParaView on older machines? We plan to target HPC clusters.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [December 12, 2025, 12:06pm UTC](https://discourse.paraview.org/t/qt-5-support-to-end-starting-in-paraview-6-2/17365/3 "2025-12-12T12:06:34Z")
> [@CsatiZoltan](#):
>
> In terms of licensing, how does the existing and the potential future license changes in Qt 6 affect the use of ParaView in commercial applications (I mean a ParaView branded application)?
Which license change are you refering to ? I dont see anything.
> did you face any issues compiling the Qt 6 based ParaView on older machines?
We usually do not compile Qt6 ourselves and rely on binaries provided by the Qt company
> We plan to target HPC clusters.
I would not expect Qt to be enabled in a ParaView deplayed on an HPC cluster.
---
### Author:  [@CsatiZoltan](https://discourse.paraview.org/u/CsatiZoltan)
#### Post date: [December 12, 2025, 12:48pm UTC](https://discourse.paraview.org/t/qt-5-support-to-end-starting-in-paraview-6-2/17365/4 "2025-12-12T12:48:44Z")
> [@mwestphal](#):
>
> Which license change are you refering to ? I dont see anything.
You are right, I mixed it up.
> We usually do not compile Qt6 ourselves and rely on binaries provided by the Qt company
I had in mind the case when you let the ParaView superbuild build Qt from sources.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [December 12, 2025, 12:52pm UTC](https://discourse.paraview.org/t/qt-5-support-to-end-starting-in-paraview-6-2/17365/5 "2025-12-12T12:52:44Z")
> [@CsatiZoltan](#):
>
> I had in mind the case when you let the ParaView superbuild build Qt from sources.
With Qt6, we do not support building Qt from sources in the paraview superbuild, instead the system Qt is being packaged.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [April 16, 2026, 8:57pm UTC](https://discourse.paraview.org/t/qt-5-support-to-end-starting-in-paraview-6-2/17365/6 "2026-04-16T20:57:05Z")
Having heard no objections, we will proceed with removing Qt 5 support in ParaView 6.2.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 1, 2026, 2:50pm UTC](https://discourse.paraview.org/t/qt-5-support-to-end-starting-in-paraview-6-2/17365/7 "2026-10-01T14:50:25Z")
ParaView 6.2 still supports Qt5. ParaView 6.3 will remove support for it.