# Editor: Save tabs display and order between web page loads

**URL:** <https://discourse.nodered.org/t/editor-save-tabs-display-and-order-between-web-page-loads/99486>\
**Category:** Feature Requests\
**Created:** [22 October 2025 21:03 UTC](https://discourse.nodered.org/t/editor-save-tabs-display-and-order-between-web-page-loads/99486 "2025-10-22T21:03:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gdvine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gdvine/32/101799_2.png) [@gdvine](https://discourse.nodered.org/u/gdvine)\
**Post date:** [22 October 2025 21:03 UTC](https://discourse.nodered.org/t/editor-save-tabs-display-and-order-between-web-page-loads/99486/1 "2025-10-22T21:03:29Z")

</div>

It's quite inconvenient to lose all open subflow tabs but the currently active one on web page reload. In my opinion, the full set of what tabs in what order ought to be saved in browser storage to be loaded up any time the Editor page is loaded, if that data is present.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [23 October 2025 10:35 UTC](https://discourse.nodered.org/t/editor-save-tabs-display-and-order-between-web-page-loads/99486/2 "2025-10-23T10:35:15Z")

</div>

What is possible is to open and maintain the order of subflows.  
However, it's not possible to maintain the order of all tabs; if subflows are distributed among flows, this order will be lost.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [23 October 2025 11:24 UTC](https://discourse.nodered.org/t/editor-save-tabs-display-and-order-between-web-page-loads/99486/3 "2025-10-23T11:24:46Z")

</div>

> [@GogoVega](#):
>
> it's not possible to maintain the order of all tabs

Forget it 😉

It's alive 🤪

> <https://github.com/node-red/node-red/pull/5322>
>
> \## Types of changes
> 
> \- \[\] Bugfix (non-breaking change which fixes an issue)
> …- \[x\] New feature (non-breaking change which adds functionality)
> 
> \## Proposed changes
> 
> Ref: https://discourse.nodered.org/t/editor-save-tabs-display-and-order-between-web-page-loads/99486
> 
> Restore tab order from last session. This also includes subflows, they will be opened and ordered.
> 
> The local storage name is \`tabOrder\` and it's an array.
> 
> Notes:
> \- There is no filter mechanism every time the editor is loaded because the reorder overwrites the array.
> \- The order of the last session will not be applied if a current tab is not there; to avoid a session that is too old.
> 
> \## Checklist
> 
> \- \[x\] I have read the \[contribution guidelines\](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md)
> \- \[x\] For non-bugfix PRs, I have discussed this change on the forum/slack team.
> \- \[x\] I have run \`npm run test\` to verify the unit tests pass
> \- \[\] I have added suitable unit tests to cover the new/changed functionality

---

<div class="post-metadata">

**Author:** ![gdvine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gdvine/32/101799_2.png) [@gdvine](https://discourse.nodered.org/u/gdvine)\
**Post date:** [23 October 2025 16:17 UTC](https://discourse.nodered.org/t/editor-save-tabs-display-and-order-between-web-page-loads/99486/4 "2025-10-23T16:17:03Z")

</div>

Great work! 🫡

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [22 December 2025 16:17 UTC](https://discourse.nodered.org/t/editor-save-tabs-display-and-order-between-web-page-loads/99486/5 "2025-12-22T16:17:29Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.