Elegant File ExplorerPhone camera roll on your PC, finally in order
You plugged the phone in, or emptied Google Photos, or dragged a folder out of the cloud — and now your PC has a thousand files named IMG_20260716_143022, VID_20260714, PXL_20260712, DSC_0431. They’re your life: the kids, the trip, the whiteboard you photographed at work. But as names, they’re gibberish, and they sit in one giant pile that no amount of scrolling makes navigable. This guide decodes those names — because they do mean something — and shows how to get your whole camera roll onto the PC in order, without copying everything twice.
Why your phone names files that way#
Your phone isn’t being random. It follows a decades-old convention (the same “DCIM” folder every camera and phone uses), where the file name is really a tiny label: a prefix that says what kind of capture it is, then the date it was taken, sometimes down to the second.
| Prefix | What it means |
|---|---|
IMG_ |
A photo — the generic label most Android phones and cameras use |
VID_ |
A video |
PXL_ |
A photo or video from a Google Pixel’s camera |
DSC_ |
“Digital Still Camera” — the default on many cameras and some phones |
MVIMG_ |
A Google “motion photo” (a still with a short clip attached) |
After the prefix comes the date, as year-month-day: IMG_20260716 was taken on 16 July 2026, and the digits after it are usually the time. So PXL_20260712_181455 is a Pixel photo from 12 July 2026 at 18:14:55. Once you can read the name, the pile stops feeling random — every file is quietly telling you its birthday.
One name to hand off elsewhere: if you see a -WA in there, like IMG-20260716-WA0031, that file didn’t come from your camera — it came through WhatsApp, and it follows a different scheme. We decode those in WhatsApp file names, explained.
Import without making duplicates#
The first real hazard of moving a camera roll to a PC isn’t losing files — it’s copying the same ones over and over. You import from the cable this month, from Google Photos next month, from a cloud backup after that, and the same IMG_20260716 lands three times in three folders. The names even help you fool yourself, because a re-download often arrives as IMG_20260716(1).
The only trustworthy way to clear those out is by content, not by name. Elegant File Explorer’s duplicate finder compares files byte for byte, so it groups two photos as copies only when they’re genuinely identical — even if one is IMG_20260716 and the other got renamed beach. A photo that was resized or recompressed is a different file and is never lumped in, so you don’t accidentally delete the good version. The full, careful walkthrough — every safeguard, how it always keeps one copy — is in find and remove duplicate files safely. Run it once after a big import and the redundant gigabytes are gone.
Get the whole roll into date order — automatically#
Here’s the move that turns the pile into an archive. The recipe “Phone photos and videos by month” recognizes exactly those camera-roll prefixes — IMG_, VID_, PXL_, MVIMG_ — wherever they landed (Downloads, the Desktop) and files them into Pictures\Phone by year and month. The dump becomes a shelf you can actually browse.
To set it up, open Auto-organization, start a + New rule, and pick “Phone photos and videos by month” from the Recipe Gallery — it fills in the whole rule. Click “Simulate effect” for the Preview — nothing is actually changed, then “Save rule.” Switch “When to run” to real time and every future phone dump sorts itself.
There’s a subtlety worth knowing, and it’s the reason to go one step further. Sorting by the file date works, but the file date resets every time a photo is copied or synced — so a photo from 2019 pulled off an old backup can land under this month. To file by the real day you took the shot, the app reads the capture date the phone wrote inside the photo. That’s a topic with its own dedicated guide, organize photos by capture date, which covers the capture-date tokens and the traps to avoid — no reason to repeat it here, but for a camera roll spanning years, it’s the version you want.
Rename IMG_20260716 into something you’ll recognize#
Date order is huge, but you may still want names a human can read — 2026-07-16_Lisbon_001 instead of IMG_20260716_143022. There are two ways, depending on whether it’s a backlog or a stream.
For a folder you’re staring at right now, the Batch rename dialog fixes the whole selection at once with a live before/after preview: strip the IMG_ prefix, add a trip name, number them 001, 002, 003. For photos that keep arriving, a rule with a “Rename (pattern)” action does it on autopilot, and it can bake the date straight into the name. Both, with every pattern and safeguard, are in batch rename files with rules. The short version: you never have to press F2 a thousand times again.
Everything here happens on your own PC — no account, no cloud, nothing uploaded. Photos are only moved and renamed, never edited, and every rule run can be undone.