# Kirby 6 for a new project?

**URL:** <https://forum.getkirby.com/t/kirby-6-for-a-new-project/35684>\
**Category:** Questions\
**Tags:** v5, v6\
**Created:** [October 28, 2026, 2:24pm UTC](https://forum.getkirby.com/t/kirby-6-for-a-new-project/35684 "2026-10-28T14:24:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![fvsch](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/fvsch/32/15908_2.png) [@fvsch](https://forum.getkirby.com/u/fvsch)\
**Post date:** [October 29, 2026, 7:31am UTC](https://forum.getkirby.com/t/kirby-6-for-a-new-project/35684/2 "2026-10-29T07:31:02Z")

</div>

I think Bastian said in the recently published KirbyConf 2026 keynote that they want to ship v6 this year, so before the end of the year. So technically it could work out.

But it’s a gamble. Maybe the stable v6 will ship in February or March next year because of some big bugs found in v6 betas or big security issues to address in v5/v6. Which _could_ be okay still if you ship something like a `v6.0.0-beta.6` to prod and it’s stable enough, but it’s a risk.

Usually the official advice is: never use pre-releases in prod. Not alphas, not betas.

Another thing to consider is that most plugins will not be updated for v6, and there are breaking changes that will require many plugins to upgrade (especially all panel plugins). So if you use v6 now, I hope you don’t rely on plugins or just one or two that you are willing to fork and update yourself.

Keynote: [Kirby Konf 2026: Keynote](https://forum.getkirby.com/t/kirby-konf-2026-keynote/35633)  
v6 beta announcement: [Kirby 6.0.0-beta.1 is here!](https://forum.getkirby.com/t/kirby-6-0-0-beta-1-is-here/35656)

---

_[View the full topic](https://forum.getkirby.com/t/kirby-6-for-a-new-project/35684)._