Productivity

File Renamer

Pick many files, preview new names from a template ({name}, {ext}, {n}, {n3} …), optionally do literal find & replace on each basename, then download one ZIP — all in your browser like APK Analyzer reading archives locally. Your originals on disk are never modified; APK String Extractor follows the same “no upload” idea for packaging.

Ad placement — top banner

No files selected

Drop files here or click to browse — renaming runs on your device only

Placeholders: {name} basename (after find/replace), {ext} extension with dot, {n} counter, {n2} / {n3} / {n4} padded.

Original New name Change
Choose files to see the preview.
Ad placement — mid rectangle

What this tool does

File Renamer targets the common “I have a folder of exports / screenshots / assets and I need consistent names” workflow. You select files in the browser, tune a naming pattern, preview every row, and take home a single ZIP archive with the new names — without installing a desktop batch tool and without sending bytes to DroidXP, similar in spirit to how APK Analyzer inspects packages locally.

What it does not do

It does not change files where they already live. It does not run regex find/replace (only literal text). It does not recurse folders — select the files you need (or zip a tree first, then work inside the archive elsewhere). Browsers cannot safely “rewrite in place” across your filesystem; the ZIP download is deliberate.

Workflow tips

  • Always keep originals until you have extracted the ZIP and spot-checked a few entries.
  • Include {ext} in your template when you want to preserve each file’s suffix.
  • Large batches: watch your machine’s RAM; split into chunks if the tab becomes sluggish.

How to use File Renamer

  1. Step 1: Drop or browse to choose files — order follows selection; numbering follows that order.
  2. Step 2: Optionally fill find/replace, then set the template and Start at; read the preview for collisions.
  3. Step 3: Click Download ZIP, extract on disk, verify, then remove or archive originals on your own terms.

Frequently Asked Questions

Does DroidXP upload my files to a server?

No. Files are read in your browser only — the same local-only stance as APK Analyzer and APK String Extractor. The ZIP is generated with JSZip on your device; DroidXP never receives file contents.

Are my original files on disk modified?

No. This tool does not write back to your folders. You get a new ZIP download with renamed entries; keep both until you verify the archive.

What placeholders can I use in the template?

{name} is the filename without extension (after optional find/replace), {ext} is the extension including the dot (or empty), {n} is the counter starting at your Start at value, and {n2} / {n3} / {n4} are zero-padded widths.

Does find-and-replace use regular expressions?

No — it is literal substring replacement. For complex patterns, rename in two passes or use a developer-focused tool.

What if two files end up with the same new name?

The tool detects collisions and appends a numeric suffix like “ (2)” before the extension so ZIP entries stay unique.

Are path characters or reserved Windows names handled?

Illegal filename characters are replaced with underscores and leading dots are trimmed. Very unusual names may fall back to a safe default.

Is there a limit on file count or size?

Only your browser’s memory and time. Huge folders can slow the tab or fail — work in batches for massive archives.

Why ZIP instead of individual downloads?

Browsers cannot silently rewrite arbitrary paths on your computer. A single ZIP is the reliable way to return many renamed files at once.

Will extensions or MIME types change?

Only the filename string changes — file bytes are copied as-is. Keep {ext} if you want the same suffix as the source.

Same privacy idea as APK String Extractor?

Yes: processing happens locally. Only the JSZip CDN script (if cached) and static DroidXP assets load like other tools.

Ad placement — sidebar 300×600