# 🎉 Node-RED 5 beta.0 released

**URL:** <https://discourse.nodered.org/t/node-red-5-beta-0-released/99870>\
**Category:** News\
**Tags:** docker\
**Created:** [5 December 2025 14:19 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870 "2025-12-05T14:19:39Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [5 December 2025 14:19 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/1 "2025-12-05T14:19:39Z")

</div>

🎉 The first **beta** release of Node-RED 5 is now available!

As promised in our recent [blog post](https://nodered.org/blog/2025/12/03/node-red-roadmap-to-5), we're starting the beta releases for Node-RED 5 today.

This is the first step on the path to an updated Node-RED user experience.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/7/3765311bc650099bf6b1495fcd742ff5f3d78b08.png)

### New Sidebar Design

The sidebars have been updated to make them more accessible. Rather than hide available sidebars in a hard to discover drop-down menu, we now show a bar of buttons down the side.

We've also reworked the left-hand side to have the same sidebar behaviour - and in doing so, we've moved the Info sidebar over to the left. This is a more natural place for it to live as a way to navigate your workspace.

I really want to stress, this is an iteration; we already have a number of follow up tasks planned to further improve aspects of this new approach. Check the sub-issue list [here](https://github.com/node-red/node-red/issues/5291) if you want to see what's coming.

### Updated pan/zoom behaviour

We've updated how you navigate around the workspace to align better with standard behaviours seen elsewhere.

As before, you can pan around the workspace with the middle-mouse button. If you don't have a middle-mouse button, you can now achieve the same result by holding the spacebar whilst dragging around with the left-mouse button.

There's also a new 'zoom to fit' button in the status bar; this will zoom your view to ensure all of your nodes are visible.

The pinch-zoom behaviour on touch screens is also better behaved.

* * *

## Installing the beta

If you want to try out the beta, you will need specify node-red@next when you use npm to update. Without the `@next` you'll still get 4.1.x

So on a Pi you'd do:

```auto
sudo npm install -g --unsafe-perm node-red@next

```

## Docker images

The beta images are available under `nodered/node-red-dev:v5.0.0-beta.0` - with the default image being based on **Node 24**.

## Reporting problems

If you hit any problems, please report them either as a reply on this topic, or in the #core-dev slack channel. Please do not post new topics to the forum regarding the beta as that could confuse users who are not using the beta.

## What's Next

The Node-RED 5.0 work is being tracked in [this issue](https://github.com/node-red/node-red/issues/5362). From there you'll find sub-issues for the various strands of activity going into Node-RED 5.

For the UX updates, you can follow [this issue](https://github.com/node-red/node-red/issues/5291) - with a number of sub-issues already raised for the next betas to address.

There's also a healthy backlog of issues and PRs from the community we'll be working through, so expect other exciting updates to come.

---

<div class="post-metadata">

**Author:** ![mbonani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mbonani/32/10631_2.png) [@mbonani](https://discourse.nodered.org/u/mbonani)\
**Post date:** [5 December 2025 14:20 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/2 "2025-12-05T14:20:41Z")

</div>

I'm probably doing something wrong. When I run a container using any of the `ghcr.io/node-red/node-red-dev:5.0.0-beta.0` images, I get Node-RED 4.1.2.

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [5 December 2025 14:24 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/3 "2025-12-05T14:24:58Z")

</div>

I'll have a look, but they should have been built from the same images as the ones on docker hub

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [5 December 2025 14:31 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/4 "2025-12-05T14:31:16Z")

</div>

I know what the problem is.

New builds running, will replace existing tagged images. Will post when finished.

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [5 December 2025 14:40 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/5 "2025-12-05T14:40:19Z")

</div>

Running this on desktop PC (Linux Mint)

Should I update my node.js from v20 and if so to what - v22 or v24? and how do I do that?

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [5 December 2025 14:46 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/6 "2025-12-05T14:46:37Z")

</div>

New builds done, and have the right versions now

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [5 December 2025 14:50 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/7 "2025-12-05T14:50:08Z")

</div>

> Should I update my node.js from v20 and if so to what - v22 or v24? and how do I do that?

Node 20 is fine for now.

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [5 December 2025 14:57 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/8 "2025-12-05T14:57:18Z")

</div>

Loving the easy hiding palette to get more real estate

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [5 December 2025 15:31 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/9 "2025-12-05T15:31:39Z")

</div>

Please note, that ONLY NodeJS 24 docker builds are available for this beta release and NodeJS have dropped 32bit ARM support for the Alpine docker builds, so the default containers will NOT run on a Pi Zero any more.

The debian based containers still have ARMv7 support, so should work on Pi Zero 2 W and Pi 3

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [5 December 2025 15:34 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/10 "2025-12-05T15:34:11Z")

</div>

This is true of "bare-metal" installs also... not just containers... there is no Nodejs v24 for Armv6 - so not for Pi0 or Pi1. As Nick noted v5 "may" work on nodev20 or 22 but won't be officially supported. (IE it may stop working at any point when a v24 only feature is incorporated)

---

<div class="post-metadata">

**Author:** ![RvG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rvg/32/96613_2.png) [@RvG](https://discourse.nodered.org/u/RvG)\
**Post date:** [5 December 2025 16:23 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/11 "2025-12-05T16:23:17Z")

</div>

The permanent vertical button bars take some horizontal space, but clicking the buttons to hide/show the sidebars helps in managing your screen real estate. Probably a bit easier than activating the dynamic toggle chevrons.

I was initially confused why my Info button was on the right hand sidebar unlike in Nick's screenshot, but that must be because I've customized the button order before upgrading.

On my browser here (Edge on Windows) the Ctrl+Space shortcut doesn't work anymore to toggle the right-hand sidebar as it does on 4.1.1. Maybe the new panning shortcut gets in the way?  
Ctrl+P still toggles the left hand sidebar.

The 'P' in that shortcut makes less sense now that you can move the Palette to the right-hand sidebar if you want 🙂 . The descriptions for these Toggle actions in the Keyboard Shortcuts editor should also be updated at some point to 'Toggle left sidebar' and 'Toggle right sidebar'. But lets wait until more sidebar work is done before nitpicking.

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [5 December 2025 16:50 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/12 "2025-12-05T16:50:25Z")

</div>

Updated on Pi using the script Nick posted and when I look at version it still says 4.1.1? Is that right?

---

<div class="post-metadata">

**Author:** ![dimitrieh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dimitrieh/32/101708_2.png) [@dimitrieh](https://discourse.nodered.org/u/dimitrieh)\
**Post date:** [5 December 2025 17:02 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/13 "2025-12-05T17:02:24Z")

</div>

Live demo version of Node-RED 5.0 beta running on the Node-RED experiment framework (no edits possible): [https://nr-node-red-dev.tailbfedba.ts.net/](https://nr-node-red-dev.tailbfedba.ts.net/)

Note: link might change in the future

Feel free to try it out directly and leave your feedback here!

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [5 December 2025 17:04 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/14 "2025-12-05T17:04:32Z")

</div>

> [@gerry](#):
>
> it still says 4.1.1

Did you restart node red?  
If so then how did you install node red initially, and how do you start it.

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [5 December 2025 17:05 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/15 "2025-12-05T17:05:02Z")

</div>

First update didn't work for some reason, now says 5 beta in palette.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [5 December 2025 17:10 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/16 "2025-12-05T17:10:45Z")

</div>

Cue the peak downloads from Node Developers.

Im at the The works xmas party tonight.  
But will be testing over the weekend - mainly anything breaking in the Nodes I develop - and indirectly Node RED of course

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [5 December 2025 17:16 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/17 "2025-12-05T17:16:43Z")

</div>

Initial reaction - the tab being to the far right - Nice! - often I have to scroll the tabs, so Nice work!!

my only criticism on that change, is the layout tab has been moved to the left.  
Feels like a disconnected UX (IMO)

The far left, should only contain Nodes available to deploy IMO, it feels like double standards

 ![Screenshot 2025-12-05 at 17.16.26](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/b/ab3a870bbe6516ff8b98c5adc719c307aad458e3.png)  
 ![Screenshot 2025-12-05 at 17.23.42](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/4/a47c8f8263c52dfbfef17bf1b4557ac32e13f334.png)

---

<div class="post-metadata">

**Author:** ![AllanOricil](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/allanoricil/32/106911_2.png) [@AllanOricil](https://discourse.nodered.org/u/AllanOricil)\
**Post date:** [5 December 2025 18:37 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/18 "2025-12-05T18:37:59Z")

</div>

> [@marcus-j-davies](#):
>
> my only criticism on that change, is the layout tab has been moved to the left.  
> Feels like a disconnected UX (IMO)
> 
> The far left, should only contain Nodes available to deploy IMO, it feels like double standards

I disagree. The flows list tab is like a file explorer. All file explorers I know are placed on the left. This new UI seems weird for "experienced" users, but it is closer to current UIUX standards. You guys have to start throwing away your biases. Go in a trip for 1 year without touching NR and come back 🤭

However, because the flows "explorer" and nodes are on the same side bar, I understand that Users that are used to drag and drop nodes will have a hard time swtiching between the file explorer and then back to the nodes list, and therefore I agree that there is still some UX pain with the new UI. So, my proposal is to make the Nodes list a sidebar on its own that renders on top of the canvas a little bit to the right of the currently selected left sidebar menu. This means that it can be open with what is currently selected in the left sidebar. Below is what I meant @dimitrieh @knolleary

 ![IMG-20251205-WA0010](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/b/fb4798cd64d19c2095d1db2cd3ab9de358a40854.jpeg)  
 ![IMG-20251205-WA0011](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/3/8399ea3dd5700121b1ce2f4cb0978742dd0456ca.jpeg)  
 ![IMG-20251205-WA0012](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/9/0919036eb89cd67db4aadf0abf07e7e64a566345.jpeg)

The "Flow Explorer" should be renamed to just "Explorer", and inside of it there should exist 2 vertical collapsable tabs, one for flows and the other for files/assets, named flows explorer and assets explorer, respectively.

Im available for consulting services by the way. But really you just need to copy what has been accepted in the industry. Just look at other editors

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [5 December 2025 18:40 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/19 "2025-12-05T18:40:43Z")

</div>

I view the Node-red editor with Firefox on a laptop screen resolution 1920 x 1080.  
This is full width of the editor with v4.1

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/1/3122cfb3d663310c82a487e4932d66afe2c44477.png)  
I often wish for more desktop and less sidebar.

And this is v5.0.0-beta.0. Disappointingly, there is less desktop visible.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/d/cd2d960dda94c9ead8dad55b44bb6e3438017226.png)

Why all the empty space in the sidebars? Changing the settings:

```auto
Left tab bar 44.6667px ==> 10px
Palette 210.667px ==> 150px
Right sidebar 300.6667px ==> 200px
Right tab bar 44.6667px ==> 10px

```

Gives a useful increase in editor space.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/a/aaf57f77b302a3b5606a8718d4d17c90183ee2a0.png)

Why do we need both tab bars (far left & far right)? The button to show/hide the left column can go perfectly happily in the right hand tab column with all the other buttons.

I am forever dragging the right bar wider and narrower to accommodate debug messages.  
**But when I am debugging, I don't need the palette column at all** It is now easier to hide it by clicking the button, but I fail to see the value of two sidebars simultaneously.  
When I am dragging nodes into the flow, I don't generally need the right hand column.

There could be a button (in the right hand tab bar) to toggle between having right or left column expanded (or of course, both)

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [5 December 2025 19:11 UTC](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870/20 "2025-12-05T19:11:48Z")

</div>

> [@jbudd](#):
>
> The button to show/hide the left column can go perfectly happily in the right hand tab column with all the other buttons

Just drag it across to the right hand button column

Only just realised that this drags the nodes tab bar across as well!!

[Next page](https://discourse.nodered.org/t/node-red-5-beta-0-released/99870.md?page=2)