# When will 3D Slicer support Qt 6?

**URL:** <https://discourse.slicer.org/t/when-will-3d-slicer-support-qt-6/44319>\
**Category:** Development\
**Created:** [September 2, 2025, 4:24pm UTC](https://discourse.slicer.org/t/when-will-3d-slicer-support-qt-6/44319 "2025-09-02T16:24:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vincent](https://avatars.discourse-cdn.com/v4/letter/v/e9bcb4/32.png) [@Vincent](https://discourse.slicer.org/u/Vincent)\
**Post date:** [September 2, 2025, 4:24pm UTC](https://discourse.slicer.org/t/when-will-3d-slicer-support-qt-6/44319/1 "2025-09-02T16:24:37Z")

</div>

First of all, thank 3D Slicer developers so much for working on supporting Qt 6.  
When will 3D Slicer support Qt 6? Will 3D Slicer support Qt 6 in 2025 ?

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [September 2, 2025, 4:52pm UTC](https://discourse.slicer.org/t/when-will-3d-slicer-support-qt-6/44319/2 "2025-09-02T16:52:59Z")

</div>

3D Slicer is actively being worked on (by @jcfr) to support Qt 6. See the work being tracked at the below GitHub issue. As of today there has been some work to backport some fixes to the PythonQt upstream. Then with an updated PythonQt, we can update CTK and then finally Slicer to support Qt 6. Expect at least a build option that is using Qt6 in the next few weeks.

> <https://github.com/Slicer/Slicer/issues/6388>
>
> Users are running into issues that are not going to be fixed on Qt5, therefore, …we need to switch to Qt6.
> 
> Issues reported by users that would be likely fixed by moving to Qt6:
> \- Proxy issues on mac (https://discourse.slicer.org/t/proxy-issue-in-extensions-manager/23467)
> \- Layout selector toolbutton menu appears on primary screen (https://discourse.slicer.org/t/dropdown-menus-spawn-on-other-monitor/13003/14)
> \- https://github.com/Slicer/Slicer/issues/7206
> 
> Unfortunately, Qt6 considerably raises minimum software and hardware requirements - see https://github.com/Slicer/Slicer/pull/6108

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [September 2, 2025, 4:53pm UTC](https://discourse.slicer.org/t/when-will-3d-slicer-support-qt-6/44319/3 "2025-09-02T16:53:49Z")

</div>

The general plan is to issue one more Qt5 release (5.10) and then switch the preview builds to Qt6 for testing.

---

<div class="post-metadata">

**Author:** ![Vincent](https://avatars.discourse-cdn.com/v4/letter/v/e9bcb4/32.png) [@Vincent](https://discourse.slicer.org/u/Vincent)\
**Post date:** [September 3, 2025, 11:45am UTC](https://discourse.slicer.org/t/when-will-3d-slicer-support-qt-6/44319/4 "2025-09-03T11:45:52Z")

</div>

Will 5.10 support both of Qt 5 and Qt 6 ?

---

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [September 3, 2025, 12:31pm UTC](https://discourse.slicer.org/t/when-will-3d-slicer-support-qt-6/44319/5 "2025-09-03T12:31:16Z")

</div>

To my understanding 5.10 will be Qt 5 only, and then eventually there will be a 5.11 with Qt 6, and then the next stable Qt 6.

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [September 3, 2025, 12:42pm UTC](https://discourse.slicer.org/t/when-will-3d-slicer-support-qt-6/44319/6 "2025-09-03T12:42:22Z")

</div>

There is a possibility the 5.10 tag has a build option to choose building with Qt5 or Qt6, but the default build option and what the final Slicer 5.10 stable release installer will use is Qt5.

---

<div class="post-metadata">

**Author:** ![ssv](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ssv/32/15085_2.png) [@ssv](https://discourse.slicer.org/u/ssv)\
**Post date:** [November 5, 2025, 3:45am UTC](https://discourse.slicer.org/t/when-will-3d-slicer-support-qt-6/44319/7 "2025-11-05T03:45:56Z")

</div>

When to expect slicer support with qt6?

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [November 5, 2025, 4:21am UTC](https://discourse.slicer.org/t/when-will-3d-slicer-support-qt-6/44319/8 "2025-11-05T04:21:03Z")

</div>

Development is actively in progress. See recent work prepping for Qt6. It will be a build option first. Slicer Stable release 5.10.0 is expected to be released this week using Qt5 and Slicer Preview will switch to Qt6 likely soon after that.

> <https://github.com/Slicer/Slicer/commit/8a44717a61b16fa43c3616722375a0eb30950c3a>
>
> Adopt target-level AUTOUIC and remove legacy UI wiring to reduce boilerplate
> and… align CTK with Qt6-ready CMake practices.
> 
> \- Replace all \`qt5\_wrap\_ui()\` usage.
> \- Enable \`AUTOUIC\` on all Slicer libraries and tests.
> \- Set \`AUTOUIC\_SEARCH\_PATHS\` from declared UI forms (or \`Resources/UI\`).
> \- Set global \`AUTOGEN\_SOURCE\_GROUP\` to "Generated" for consistent IDE layout.
> \- Add AUTOGEN include dir so generated \`ui\_\*.h\` headers resolve reliably.
> \- Clean up: remove unused UI wrapping in \`Modules/Loadable/Markups/Widgets/Testing/Cxx/CMakeLists.txt\`
> 
> Co-authored-by: Hans Johnson \<hans-johnson@uiowa.edu\>