DEV Community

Cover image for I Fixed Blender's Render Output Paths ( Because it SUCKS! )
Shayan
Shayan

Posted on

I Fixed Blender's Render Output Paths ( Because it SUCKS! )

The Problem

Blender's render output? Just a text field. No variables, no organization, no help.

You end up with untitled.png, untitled0001.png, final_final_ACTUAL.png. I searched for a solution. Found nothing. AI suggested some janky script. I wasn't having it.

So I built RenderNames.

RenderNames Cover | Auto Naming output paths in blender

How It Works

Write a template once:

{{blend_file}}/{{date}}/{{scene}}_{{camera}}_
Enter fullscreen mode Exit fullscreen mode

It becomes:

my_project/2025-01-15/Scene_Camera_0001.png
Enter fullscreen mode Exit fullscreen mode

Blender adds frame numbers. You handle the smart naming. Done.


What You Get

Live preview — See your output path as you type

Template variables{{scene}}, {{camera}}, {{date}}, {{time}}, {{resolution}}, {{engine}}, and more

Auto-folders — Organize by date, scene, camera

Presets — Save and share with your team

Native Blender — Lives in Output Properties, no weird UI


RenderNames Plugin Features

Install (Literally 2 Minutes)

  1. Download .zip from Releases
  2. Blender: Edit → Preferences → Extensions → Install from Disk
  3. Enable it, go to Output Properties, start templating

Support RenderNames

If this saves you time, here's how you can help:

Star on GitHubgithub.com/novincode/rendernames

💙 Sponsorgithub.com/sponsors/novincode

🐛 Report bugsIssues


Blender 4.2+ | Open source (GPL-3.0)

Top comments (1)

Collapse
 
codeideal profile image
Shayan

Got anything in mind? I'm all ears :)