Rename Multiple Files at Once on Android
You have 200 photos called IMG_4471 and a folder that sorts in the wrong order. Here's the naming scheme that fixes it, and why zero-padding matters.
If a folder of files sorts in the wrong order, the cause is almost always that
computers sort filenames lexicographically, character by character — so photo2
comes after photo10, because 1 sorts before 2. The fix is zero-padding:
photo002 and photo010 sort correctly everywhere, forever, with no special software
needed. That single convention solves most of what people are trying to fix when they
go looking for a bulk renamer.
On Android, Convertlix's Batch File Renamer renames files on the handset, so nothing leaves the device — no upload, no server-side copy, nothing to retain. The scope, up front: Android 8.0 or later, sign-in required (there is no guest mode), and on the free tier a batch holds 5 items with a 25 MB per-file ceiling, against a server-set monthly allowance of conversions shown in the app. Premium raises batches to 200 items — stated as a limit, because a 500-file shoot is beyond both and belongs on a computer.
Why your files sort in the wrong order
Sorting compares strings position by position, not the numbers inside them. So the
comparison of IMG_2.jpg and IMG_10.jpg reaches the character after IMG_, sees 2
against 1, and stops: 1 is lower, so IMG_10 comes first. The file manager isn't
broken; it's doing exactly what string comparison does.
Some software papers over this with "natural sort", which detects digit runs and compares them numerically. macOS Finder and Windows Explorer both do it, which is why this problem seems to vanish on a desktop and reappear the moment the files go somewhere else — a web upload form, a ZIP archive listing, a PDF assembled from images, a script, another operating system.
Zero-padding removes the dependency entirely. Pad to the width of your largest number, plus a digit of headroom:
- Up to 99 files → two digits:
01,02, …99 - Up to 999 files → three digits:
001,002, …999 - Uncertain → use three. The cost is one character.
The same logic applies to dates, and it is why ISO order (YYYY-MM-DD) is the one
date format worth putting in a filename. 2026-09-13 sorts chronologically as a
string; 13-09-2026 sorts by day-of-month across every year, and Sept 13 2026 sorts
alphabetically by month name, putting April first. This is not a stylistic preference —
it is the difference between a folder that sorts itself and one that never will.
| Naming scheme | Sorts correctly? | What goes wrong |
|---|---|---|
IMG_1, IMG_2 … IMG_10 | No | 10 sorts before 2 outside "natural sort" software |
IMG_001, IMG_002 … IMG_010 | Yes, everywhere | Nothing; needs the width chosen up front |
2026-09-13_invoice | Yes, chronologically | Nothing |
13-09-2026_invoice | No | Sorts by day, mixing years together |
Invoice for Smith & Co (final).pdf | Yes, but fragile | Spaces, & and ( break scripts, URLs and some upload paths |
scan 1.jpg, scan 1 (1).jpg | No, and ambiguous | Duplicate-suffix names tell you nothing about order |
Characters to keep out of filenames
Renaming in bulk is the moment to fix this, because you are touching every name anyway.
Safe everywhere: letters, digits, hyphen, underscore, and a single dot before the extension.
Causes problems: spaces (need quoting in every command line, become %20 in URLs),
&, #, %, ?, ! (special in shells and URLs), / and \ (path separators —
usually impossible anyway), : * ? " < > | (illegal on Windows, so a ZIP
made on Android may fail to extract there), leading or trailing spaces and dots, and
emoji (fine on your phone, unpredictable in archives and older systems).
Length. Keep the whole path under about 255 characters. Deeply nested folders with long descriptive names hit that limit on Windows in particular, and the error message when they do is rarely helpful.
What renaming does not change
Worth knowing, because people expect more from it than it does:
- It doesn't change any metadata. The EXIF capture date, camera model and GPS
coordinates inside a photo are inside the file, not in its name. Renaming
IMG_4471.jpgto2026-09-13_wedding_012.jpgleaves all of it untouched — which matters if the reason you were renaming was privacy. Stripping that data is a separate job, covered in Remove GPS and EXIF Data From Photos (Android). - It doesn't change the file's content or size. A rename is a directory operation. Nothing is re-encoded, so there is no quality cost of any kind.
- It doesn't fix an order already baked into something. If you have already built a PDF from images in the wrong sequence, renaming the images changes nothing about the PDF — that needs Remove, Reorder or Rotate PDF Pages (Android).
The order in which to do things, then: rename first, then assemble. Get the filenames sorting correctly, then build the PDF or the archive, because both Turn Photos Into One PDF for an Upload (Android) and a ZIP take the files in the order the picker hands them over.
How to rename a set of files cleanly
- Decide the scheme before you touch anything. Something like
YYYY-MM-DD_subject_NNN.ext. Write it down. Renaming twice because you changed your mind halfway is the main way this goes wrong. - Count the files and pick your padding width. Two digits up to 99, three up to 999. Choose for the final count, not today's count, if more are coming.
- Work on copies the first time. Renaming is a directory change, so there is no undo unless your tool provides one. Duplicate the folder until you trust your pattern.
- Rename the batch. In Convertlix, open Batch File Renamer, pick the files through Android's file picker and apply the pattern. Free batches hold 5 items, so a large set goes in groups — mind the numbering continuing correctly across them, which is the practical annoyance of a small batch cap.
- Sort the folder by name and read the list. This is the check. You are looking for anything out of sequence, any gap in the numbering, and any duplicate.
- Then assemble. Build the PDF, the ZIP or the upload once the names sort right.
When this doesn't work
- Large sets. Free batches hold 5 items and Premium 200. Several hundred files is beyond both, and a desktop tool or a one-line command will do it in seconds without a cap. That is the honest answer for a photographer with a card full of images.
- Renaming based on file contents or metadata. Naming photos from their EXIF capture date, or documents from a value inside them, needs a tool that reads the file. That is a different class of software — Adobe Bridge, ExifTool, digiKam and Advanced Renamer all do it and a phone utility does not.
- Files you don't have write access to. Anything inside another app's private storage, on a read-only share, or on a memory card mounted read-only.
- Files in use. A file open in another app may refuse to be renamed, or be renamed and then rewritten under the old name.
- Breaking existing references. Renaming files that something else points at — a web page, a spreadsheet, a project file, a playlist — breaks those links silently. Rename before you reference, not after.
FAQ
Why does file 10 come before file 2 in my folder?
Because filenames are compared as text, character by character, rather than as numbers.
At the position where 2 meets 1, the comparison ends and 1 wins, so file10 sorts
before file2. Some file managers apply a "natural sort" that special-cases digit runs,
which is why the problem seems to disappear on a desktop and returns in a ZIP listing,
an upload form or a script — zero-padding to file02 and file10 fixes it everywhere.
How should I number files so they always sort correctly?
Pad the numbers with leading zeros to a fixed width covering your largest number: two
digits up to 99, three up to 999. Put dates in YYYY-MM-DD order, which sorts
chronologically as plain text, and stick to letters, digits, hyphens and underscores.
A name like 2026-09-13_contract_003.pdf will sort correctly on every system and inside
every archive without any special handling.
Does renaming a file change its content or metadata?
No. A rename is an operation on the directory entry, not on the file, so the bytes are untouched — nothing is re-encoded and there is no quality cost. Metadata inside the file is also untouched, which means a photo's EXIF capture date, camera model and GPS coordinates all survive the rename. Removing those requires a separate metadata tool.
Does Convertlix upload my files to rename them?
No. The files are opened through Android's own file picker and renamed on the phone; nothing is sent anywhere, and the app has no storage permission, so it cannot see anything you did not select. Its network calls carry identity, licence, quota, configuration and payment data, never a file. Sign in once, switch on airplane mode, and it still works.
Is there a free way to rename lots of files at once?
Yes, and for large sets it is the better answer. Windows Explorer renames a selection
with numbered suffixes for free (though it uses (1)-style numbering, which doesn't
zero-pad), and Advanced Renamer and Bulk Rename Utility are free, Windows-based
and enormously more capable, including renaming from EXIF data. On macOS and Linux,
Finder's batch rename and a one-line shell loop
(i=1; for f in *.jpg; do mv "$f" "$(printf '%03d' $i).jpg"; i=$((i+1)); done) handle
thousands of files instantly. ExifTool renames photos from their capture date, which
is the thing most people actually want for a camera roll. The reason to use a phone tool
is that the files are on the phone and the computer is elsewhere.
If the files are on your phone and something is taking them in the wrong order, pad the numbers and get the names sorting correctly before you assemble anything.