# ParaView 6.2 release schedule

**URL:** https://discourse.paraview.org/t/paraview-6-2-release-schedule/17526
**Category:** Announcements
**Created:** [April 16, 2026, 9:02pm UTC](https://discourse.paraview.org/t/paraview-6-2-release-schedule/17526 "2026-04-16T21:02:21Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [April 16, 2026, 9:02pm UTC](https://discourse.paraview.org/t/paraview-6-2-release-schedule/17526/1 "2026-04-16T21:02:21Z")

</div>

Continuing with our coordinated releases with VTK, ParaView 6.2 will be released following [VTK’s 9.7 release in June 2026](https://discourse.vtk.org/t/vtk-9-7-0-and-10-0-0-release-planning/16371). Here’s the anticipated schedule:

- **Early June 2026** - feature freeze and ParaView 6.2 release candidate 1 released
- **Early to mid July 2026** - final ParaView 6.2 release.

---

<div class="post-metadata">

### Author: ![GregVernon](https://discourse.paraview.org/user_avatar/discourse.paraview.org/gregvernon/32/1494_2.png) [@GregVernon](https://discourse.paraview.org/u/GregVernon)
#### Post date: [April 20, 2026, 11:00pm UTC](https://discourse.paraview.org/t/paraview-6-2-release-schedule/17526/2 "2026-04-20T23:00:05Z")

</div>

@cory.quammen – from that VTK release summary:

> As detailed in the blog, VTK 10 will contain a major change, the change of the default rendering backend from OpenGL to WebGPU, but it will be possible to opt-out and use OpenGL rendering.
> 
> VTK 9.7.0 will already contain all the WebGPU features required to be able to test this backend, but it will be an opt-in, that we strongly suggest users to test their workflow with.

Will ParaView 6.2 then support the WebGPU backend? Will the ParaView release (6.3?) that coincides with VTK 10 be WebGPU by default? Will these be staggered (e.g., 6.2 no WebGPU support, 6.3 non-default support, 6.4 WebGPU default)? Plead the 5th 😉 ?

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [April 22, 2026, 2:55pm UTC](https://discourse.paraview.org/t/paraview-6-2-release-schedule/17526/3 "2026-04-22T14:55:48Z")

</div>

Good questions, Greg! It’s a bit of an open question at the moment. We’ll be working toward integration of WebGPU rendering in ParaView, but the timeline is murkier.

> [@GregVernon](#):
>
> Will ParaView 6.2 then support the WebGPU backend?

No, that is not planned for 6.2.

> [@GregVernon](#):
>
> Will the ParaView release (6.3?) that coincides with VTK 10 be WebGPU by default?

ParaView 6.3 (winter 2027) will probably start to support WebGPU, but it will not be on by default. ParaView 6.4 (summer 2027) may have sufficient WebGPU support to _consider_ turning it on by default. When we do turn it on by default, we will likely call it ParaView 7 instead of 6.x.

---

<div class="post-metadata">

### Author: ![GregVernon](https://discourse.paraview.org/user_avatar/discourse.paraview.org/gregvernon/32/1494_2.png) [@GregVernon](https://discourse.paraview.org/u/GregVernon)
#### Post date: [April 24, 2026, 2:09am UTC](https://discourse.paraview.org/t/paraview-6-2-release-schedule/17526/4 "2026-04-24T02:09:33Z")

</div>

![mole](https://discourse.paraview.org/uploads/default/original/3X/2/8/2861f3ffb7772501843313a20ff290e82d4ff352.gif)

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 9, 2026, 11:28am UTC](https://discourse.paraview.org/t/paraview-6-2-release-schedule/17526/5 "2026-06-09T11:28:09Z")

</div>

VTK 9.7’s release cycle has been pushed back to later this month: [VTK 9.7.0 and 10.0.0 Release Planning - #2 by mwestphal - Announcements - VTK](https://discourse.vtk.org/t/vtk-9-7-0-and-10-0-0-release-planning/16371/2)

Since ParaView’s release now follows just behind VTK’s release cycle, the ParaView 6.2 release will now follow this schedule:

- **July 3, 2026** - feature freeze and ParaView 6.2 release candidate 1 released
- **July 31, 2026** final ParaView 6.2 release

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [September 3, 2026, 1:38pm UTC](https://discourse.paraview.org/t/paraview-6-2-release-schedule/17526/6 "2026-09-03T13:38:03Z")

</div>

An update: our original schedule has slipped. We are working through a couple last critical issues and expect to have

- ParaView 6.2.0-RC2 out early next week
- ParaView 6.2.0-RC3 a week later
- ParaView final before the end of September

Thanks for your understanding.

---

<div class="post-metadata">

### Author: ![otaolafr](https://discourse.paraview.org/user_avatar/discourse.paraview.org/otaolafr/32/3595_2.png) [@otaolafr](https://discourse.paraview.org/u/otaolafr)
#### Post date: [September 4, 2026, 8:22am UTC](https://discourse.paraview.org/t/paraview-6-2-release-schedule/17526/7 "2026-09-04T08:22:50Z")

</div>

hey cory, i assisted to the webminar of vtk 9.7 and they presented something quite cool (for me at least) where the vtk arrays now are literally numpy arrays (I hope that you understand what i mean by it) is this something that will affect the fetching data of paraview 6.2?

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [September 4, 2026, 1:27pm UTC](https://discourse.paraview.org/t/paraview-6-2-release-schedule/17526/8 "2026-09-04T13:27:16Z")

</div>

> [@otaolafr](#):
>
> vtk arrays now are literally numpy arrays

VTK arrays are still `vtkDataArray`s, but they are (and have been for a while) available as numpy arrays through a wrapping mechanism. There are just more types or arrays wrapped now in VTK 9.7.

> [@otaolafr](#):
>
> is this something that will affect the fetching data of paraview 6.2

I’m not sure what you mean. Do you mean the Python `FetchData` function? If so, that won’t change.
