Replace Text in Filenames
Replace Text in Filenames applies a literal, case-sensitive split-and-join replacement to the basename only; the final extension is preserved. Every occurrence is replaced. If Find is left empty, JavaScript splits the basename between characters and can insert the replacement repeatedly, so a non-empty Find value is essential. The result is renamed-files.zip, not an in-place rename.
Runs locally — files stay on your deviceIs filename replacement case-sensitive?
Yes, and it replaces all exact occurrences in the basename.
Literal replacement is not a regular expression
The Find text has no wildcard or regex meaning. Matching is exact and does not inspect the extension.
How it works
Each name is split at its final extension, base.split(find).join(replacement) transforms the basename, and JSZip packages the copies.
Key concepts
All matches
Every exact occurrence in the basename changes.
Extension excluded
A Find value matching pdf will not alter .pdf.
When to use it
- Replace a repeated project token.
- Remove known literal text by using an empty replacement.
- Standardize exact casing when the source pattern is known.
When not to use it
- Do not leave Find empty.
- Do not expect regex, wildcard, or case-insensitive matching.
- Do not use it to alter extensions.
Worked examples
Token update
- Input
draft-draft.txt; Find draft; Replace final- Expected output
final-final.txt
All occurrences change.
Case mismatch
- Input
Report.pdf; Find report- Expected output
Report.pdf
Matching is case-sensitive.
Remove text
- Input
IMG-copy.jpg; Find -copy; replacement empty- Expected output
IMG.jpg
Empty replacement deletes matched text.
Common mistakes
Empty Find
It can insert replacement text between characters. Correction: Always enter a non-empty Find value.
Expecting regex
Special characters are literal. Correction: Use an explicit regex-aware renamer elsewhere.
Trying to change extension
The extension is separated first. Correction: Use a dedicated extension workflow.
Best practices
- Use a non-empty, specific Find token.
- Test on a small batch.
- Review collision and portability risks before extracting.
Related operations and differences
Add Prefix to Filenames
Choose Add Prefix to Filenames when you need to add a prefix to selected filenames.; use Replace Text in Filenames specifically for rename replace.
Add Suffix to Filenames
Choose Add Suffix to Filenames when you need to add a suffix before every extension.; use Replace Text in Filenames specifically for rename replace.
Lowercase Filenames
Choose Lowercase Filenames when you need to convert selected filenames to lowercase.; use Replace Text in Filenames specifically for rename replace.
Uppercase Filenames
Choose Uppercase Filenames when you need to convert selected filenames to uppercase.; use Replace Text in Filenames specifically for rename replace.
Compare Two Files
Choose Compare Two Files when you need to compare two files securely by SHA-256.; use Replace Text in Filenames specifically for rename replace.
File Checksum Comparator
Choose File Checksum Comparator when you need to compare a file digest with an expected checksum.; use Replace Text in Filenames specifically for rename replace.
Limitations and privacy
- No empty-Find validation, regex, case-insensitive mode, preview, collision handling, extension replacement, paths, or in-place rename.
- Uses a simple last-dot extension rule.
- Output is renamed-files.zip.
Processing happens in this browser. Selected file contents are not uploaded by this tool.
Downloads and copied results remain on this device; handle them according to their sensitivity.
Frequently asked questions
Are all matches replaced?
Yes.
Can replacement be empty?
Yes, to remove matched text.
Can Find be empty?
It should not be; current behavior can insert text between characters.
Is .pdf changed by searching pdf?
No, the final extension is preserved.