Copy photos from your phone to a PC by cable, safely

Two scenes, and you’ve lived at least one of them.

Scene 1: you plug the phone into the PC. It buzzes, says it’s charging, and… nothing. No window opens. No device appears under This PC. You switch USB ports, switch cables, start blaming the cable (it’s almost never the cable).

Scene 2: the device does appear. You open the photos folder, select nine hundred files, hit copy — and the progress bar climbs to 340, stalls, and vanishes with a message saying “a device attached to the system is not functioning”. The whole copy died over one file. You don’t know which of the 900 made it. You start again from zero.

Both scenes have an explanation, and neither of them is the cable.

The step everyone forgets#

A modern phone arrives on the cable in charge only mode. It opens up to the computer only after you do two things — in this order:

1. Unlock the screen. With the phone locked, its contents stay closed. That’s protection, and it’s permanent: waiting won’t help.
2. Choose “File transfer” on the prompt that appears on the phone’s screen (on some devices the prompt sits in the notification shade and you have to pull it down to see it).

If you plugged it in, stared at the PC and never looked at the phone, that prompt is probably still there waiting. That’s the forgotten step in nine out of ten “my phone doesn’t show up on my PC” cases.

There’s a second, sneakier reason: many phones accept one connection at a time. If a File Explorer window is already browsing the device, the next program that tries to get in may simply fail. Closing that window and unplugging/replugging the cable fixes it.

Why the big copy dies halfway#

Scene 2 has a structural cause: a phone is not a hard drive. It doesn’t expose a real disk to Windows — it talks over a device protocol, slower and more fragile, answering one question at a time. Every file is a negotiation.

In that setup, one corrupted video, one photo the camera app is still writing, or a folder the phone refuses to list is enough to take down the entire copy. And when it falls over, you get the worst possible outcome: some of it came across, and you don’t know which part.

The right way to handle this isn’t to insist; it’s to import in a way that survives the error — skipping the problem file, counting how many it skipped, and carrying the batch through to the end.

Importing in a queue, with progress, without freezing#

In Elegant File Explorer, with the phone connected and unlocked, open Go ▸ Portable devices….

The window lists the devices it found — phone, camera, tablet. If yours isn’t there, it doesn’t leave you in the dark: it shows exactly the reminder about unlocking and choosing “File transfer”, plus a Refresh button to try again once you’ve fixed it.

Pick the device and browse its folders like any other folder — the list shows Name, Size and Modified. Camera photos and videos almost always live in a folder called DCIM (the convention every camera and phone has followed for decades).

Select what you want to bring over and set up the import at the bottom:

• Import to — the destination folder on the PC. It defaults to an “Imported” folder inside your Pictures; change it to wherever you prefer.
• How to organise — and here’s the detail that changes your next day:
  • No subfolders (everything together in the destination),
  • Subfolders by date (YYYY-MM) — photos land already split by month: 2026-07, 2026-06, 2026-05…,
  • Subfolders by type — images, videos, audio and documents each in their own.

Choosing “by date” at import time saves you the whole afternoon of tidying afterwards. It’s the same number of clicks with a completely different result on this side.

Click Import selection and the queue starts. While it runs you see the current file, how many of how many are done, the bytes and the speed — and the app stays responsive: reading the device happens in the background, so the window never freezes or goes white with “not responding”.

Three behaviours matter more than they sound:

• An error doesn’t kill the batch. If a file fails, it’s skipped and counted. At the end the summary is honest: “Imported 887 · 13 with errors (skipped, the batch went on)” — you know exactly what came over and what didn’t.
• Cancelling undoes nothing. Hit Cancel? The files already imported stay where they are. You pick up later without starting over.
• When it’s done, you’re already there. The Open destination in the app button takes you straight to the folder with what just arrived.

Need to send something the other way — a PDF, some music, a document for the trip? Send to device… does the return leg.

An honest warning about deleting from the phone#

There is a Delete from device action, and it comes with a confirmation that tells the truth rather than softening it: there is no Recycle Bin on the device — deletion is permanent.

That’s not the program being dramatic; it’s how phones work. When you delete a file over the cable, it doesn’t land anywhere recoverable on the PC side. Which is why the healthy order is always the same: import first, confirm it arrived, and only then free up space on the phone.

Once the photos land: the two steps worth taking#

Bringing them over is half the job. The other half is not rebuilding the mess on the PC.

First, sort by capture date, not file date. Copying files tends to rewrite the modified date, so a photo from 2019 shows up as if it were taken today. The date that matters is stored inside the photo itself, and you can organise photos by capture date automatically — including the ones already lost in old folders.

Second, deal with the repeats. Anyone who imports the same phone two or three times a year inevitably duplicates photos. It’s worth a duplicate pass that checks content, comparing the actual file instead of trusting the name — IMG_2043.jpg and IMG_2043 (1).jpg may be the same photo, or may not.

And if those prefixed names (IMG_, VID_, PXL_, DSC_) bother you, they do mean something — we decoded them in your phone’s camera roll on the PC, finally in order.