RenForge — Preview. Decide. Rename.

Built for cautious power users

RenForge keeps renaming predictable: no “magic ai” — just clear steps, full previews, and loud warnings when something’s off.

Preview-first pipeline

Chain rename steps and see the final result before touching disk. If it looks wrong, nothing is applied.

Filters that make sense

Contains / starts / ends / extension with Match ALL (AND) / ANY (OR), plus a case-sensitive toggle.

Safety checks

Invalid names, duplicates, and “target exists” issues are highlighted before you hit Apply.

Wrapped full names + pagination

Long filenames are shown clearly, with paging (10 per page) so you can actually review things calmly.

Undo CSV export

Optionally write an undo log (CSV) so you can revert if needed.

Deterministic behavior

Same inputs → same outputs. RenForge won’t invent creativity when you just want consistency.

Screenshots

Screenshot 1
Main screen preview pipeline
(set data-src)

Preview pipeline

Screenshot 2
Filters with AND/OR
(set data-src)

Filters

Screenshot 3
Conflicts + warnings
(set data-src)

Safety checks

Screenshot 4
Apply options + undo CSV
(set data-src)

Apply workflow

User manual

RenForge follows one simple philosophy: Preview first. Rename second.

1 Select a folder

Choose your target directory (non-recursive)

RenForge loads files from one folder (v1 keeps it intentionally simple and safe).

2 Add filters

Narrow down files before you touch names

Use contains / starts / ends / extension. Combine them with Match ALL or Match ANY and toggle case sensitivity.

3 Build your rename pipeline

Stack steps like LEGO… for filenames

Remove text, replace text, insert before extension, append/prepend, or change extension — all in preview.

4 Review conflicts

RenForge flags trouble before Apply

Duplicate targets, invalid characters, and “target already exists” are highlighted so you can adjust safely.

5 Dry run or apply

Pick your safety mode

Stay in Dry Run to validate changes. Switch to Apply only when the preview looks perfect.

6 Export undo CSV

Optional — but recommended

Create an undo log CSV so you can revert via the revert tool if you ever need to roll back.

Pro tip: If your gut says “hmm…”, that’s your inner monk protecting your filesystem. Stay in Dry Run until the preview is boringly correct.

FAQ

Quick answers for common questions (and existential dread).

What makes RenForge “safe”?

It’s preview-first, deterministic, and runs checks (invalid names, duplicates, existing targets) before applying changes. You decide — RenForge just makes the consequences obvious.

Does it rename files recursively?

Not in v1. Non-recursive scanning is intentional to reduce “oops I renamed my entire life” moments.

Can I undo changes?

Yes — export the undo CSV at apply time, then use the revert tool to roll back. Think of it as a paper trail for your future self.

Where do I get binaries?

Use the Download button above to jump to GitHub Releases (configure the repo URL in the script below).