# .red as file extension for Node-RED flows

**URL:** <https://discourse.nodered.org/t/red-as-file-extension-for-node-red-flows/79511>\
**Category:** Core Development\
**Tags:** editor, feature-request\
**Created:** [30 June 2023 17:53 UTC](https://discourse.nodered.org/t/red-as-file-extension-for-node-red-flows/79511 "2023-06-30T17:53:49Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![rko](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rko/32/45807_2.png) [@rko](https://discourse.nodered.org/u/rko)\
**Post date:** [30 June 2023 23:30 UTC](https://discourse.nodered.org/t/red-as-file-extension-for-node-red-flows/79511/5 "2023-06-30T23:30:17Z")

</div>

> [@jbudd](#):
>
> but it is smart enough not to classify the contents based on the file name.

Well I think it's efficient as a first guess of the format. Whether or not it is really what it "pretends" to be should be handled by the linked application.

The fact that you used `.cpp` makes it quite clear how important extensions are. You immediately assume that it is C++, because we are so used to it. Plus filtering is fast and easy (cause you don't have to check the content in the first step).

Anyway, this is not a feature I need desperately, but it would help to identify Node-RED flows in our cloud system and link them to a [flow viewer](https://discourse.nodered.org/t/standalone-flow-viewer-plugin/79388/55) application. And instead of using a special file extension internally only, I thought others could benefit from this, maybe.

---

_[View the full topic](https://discourse.nodered.org/t/red-as-file-extension-for-node-red-flows/79511)._