Safety guides

Prevent collisions, permission errors and irreversible bulk rename mistakes.

Quick answer: Preview, unique target names, backup and permission checks are essential for high-volume rename tasks.

Task-by-task guides

Safety

The New Name column is a safety check showing expected changes before any filesystem operation.

Safety

BRU offers mechanisms for reverting some recent renames, but recovery should be tested before a large or critical batch.

Safety

A batch must produce unique target names in the same directory to avoid conflicts.

Safety

Keep a verified copy or versioned backup before a batch that affects many files or nested directories.

Safety

A small rehearsal exposes unexpected case changes, extension modifications and duplicate results early.

Safety

Most BRU name transformations change the filename stem; leave Extension rules inactive to preserve the recognized type.

Safety

Access Denied may arise from permissions, open handles or protected locations rather than a broken renaming rule.

Safety

Windows can block a rename while a file is open; close the application holding it rather than forcing an operation.

Safety

Windows forbids characters such as colon, question mark and backslash in ordinary filenames.

Safety

Deep directory paths may exceed limits for some applications even when the naming rule itself works.

Safety

Renaming on a shared drive can disrupt other users and requires permission and conflict checks.

Safety

Renaming a synced folder can trigger large sync updates and break shared links or references.

Safety

Changing .jpg to .png in a filename does not transform the actual image data.

Safety

Read-only attributes and parent-folder permissions can affect whether a batch rename succeeds.