SceneRename

stashdb.corrode248 · February 16, 2026, 10:09pm


	Summary	Renames scene files to Studio #Code - Title [Resolution].ext. Studio and title are both required (scenes missing either are skipped). Code and resolution are optional. Colons in titles become commas. Triggers on scene update or via manual task. Enable Dry Run to preview changes in scenerename.log before renaming.
	Repository	https://github.com/stashapp/CommunityScripts/tree/main/plugins/sceneRename
	Source URL	https://stashapp.github.io/CommunityScripts/stable/index.yml
	Install	How to install a plugin?

Scene Rename: File Organizer Plugin

Simple plugin to help organize scene files into a clean, consistent format. It includes debug tracing that integrates with the Logs view, supports dry runs, and provides a clear description in the Plugins UI.

Features

Dry run support
Debug output in the Logs view
Graceful handling of already-renamed files
Does not fail if Code or resolution are missing
Requires a Studio and Title to proceed
Renames through Stash’s moveFiles API, so the database stays in sync without a rescan
Records the pre-rename filename in the scene’s original_filename custom field
Strips illegal and control characters, and truncates to the filesystem’s byte limit

The code is simple and the plugin UI includes clear usage instructions.

Screenshot

What It Does

The Scene Rename plugin renames scene files using the following format:

Studio #Code - Title [Resolution].mp4

For example, a file in my library that still has its default name:

wodhhd_06_1080p.mp4

Is renamed to:

TitanMen #395 - Coyote Point, Dakota Rivers [1080p].mp4

This format keeps filenames consistent and easy to scan. It also makes it simple to group files by studio if desired, or keep everything in a single directory while maintaining a clean, uniform structure.

I’ve found it very effective for keeping my library organized, and others may find it useful as well.

Installation Example (Docker)

I run Stash in Docker. My folder structure looks like this:

docker/
└── docker-compose.yml
└── plugins/
    └── scenerename/
        ├── scenerename.py
        └── scenerename.yml

In docker-compose.yml, add the following under volumes:

- ./plugins/scenerename:/root/.stash/plugins/scenerename

That’s all that’s required. The plugin loads normally, outputs to the Logs window, and supports dry runs.

Releases:

v1.2.0
- Renames through Stash’s moveFiles API instead of os.rename + folder rescan, the database stays in sync, no stale paths, no scan job
- Records the pre-rename filename in the scene’s original_filename custom field, written once so the earliest name survives later renames
- Requires a title as well as a studio; without one the name collapsed to just studio + resolution
- Skip messages now name the missing field
- Strips : from studio names and codes (previously only titles), collapses control characters, trims leading dots and trailing dots/spaces
- Truncates to the filesystem’s 255-byte limit rather than 240 characters, so long non-ASCII titles no longer fail to rename
- Fixed README format and example - resolution follows the title

slinky · February 17, 2026, 7:49pm

I have a script that does something similar, but it uses the following format:

studio_name-yyyymmdd-studio_code-performer_one-performer_two-full_title.ext

Underscores replace spaces and hyphens act as a delimiter. It’s all lowercase and minimizes special character usage to avoid any file system compatibility issues. The script also automatically adds all performers, and will ensure the filename doesn’t exceed 255 characters by first truncating performers and then truncating title if necessary.

I’ve found that this format makes it very easy to search a large filesystem for a specific studio, date, performer, etc. There’s no “right answer” for adult video formatting online, but I gave it my best shot. I’d love to hear other people’s opinions so maybe we can work towards a standardized format for the community.

pervnerd55 · March 7, 2026, 10:59am

Is this script available?

stashdb.corrode248 · August 30, 2026, 6:34pm

Yes. I have an update to it though. Pull request has been opened for the v1.2.0 the update, it contains the source script as well

github.com/stashapp/CommunityScripts

feat(sceneRename): rename via moveFiles and record original filename

main ← stashdbcorrode248:scenerename-movefiles-and-sanitising

opened 06:59PM - 30 Aug 26 UTC

stashdbcorrode248

+97 -17

SceneRename renamed files with `os.rename()` behind Stash's back, then ran `meta…data_scan()` on the parent folder to repair the database afterwards. The file record pointed at a stale path until that scan completed, and a full folder scan is heavy for a single-file change. This switches the rename to the `moveFiles` mutation, so Stash moves the file and updates the file record in one transaction and no rescan is needed. A destination folder is required even for an in-place rename, so the file's current `parent_folder` id is passed, falling back to its path. ### Other changes - **Require a title, not just a studio.** Without one the filename collapsed to the studio plus resolution, which is less useful than the original name. The README already documented this requirement; the code now matches it. The skip message names the missing field rather than listing every field. - **Record the pre-rename basename** in the scene's `original_filename` custom field, written once so the earliest known name survives later renames. A failed write logs a warning and does not fail the rename. - **Harden filename sanitising.** `:` is now stripped from studio names and codes, which never passed through `clean_title()`; control characters are collapsed to spaces; leading dots and trailing dots/spaces are trimmed. - **Truncate to a byte budget rather than a character count.** Filesystem name limits are in bytes (255 on ext4/btrfs), so a 240-character non-ASCII title could produce a name well over the limit and fail to rename. The budget also reserves room for the extension and a duplicate suffix. - **Correct the README** format string and worked example, which showed the resolution before the title while `form_filename()` emits it after. Version bumped to 1.2.0. ### Testing Run against a live Stash 0.31.1 library. Renames land through `moveFiles` with no rescan and no stale paths; `original_filename` is populated; scenes missing a title are skipped with the field named in the log. Sanitising was checked against studio/title combinations containing colons, newlines, tabs, NUL, leading dots and trailing dots/spaces, plus a 300-character CJK title, which previously produced a 706-byte name and now stays within the 255-byte limit.