Transfer Photos from Your Phone to a Laptop Without a Cable
Moving photos off a phone sounds solved, yet most people do it in a way that quietly throws information away. This guide covers how to get the actual photo (full resolution, original format, metadata intact) onto a laptop without a cable, and is candid about the one case where a cable is still the right tool.
What “send it to myself” usually does to a photo
The reflex is to message the photo to yourself or email it. Both work, and both change the file:
- Chat apps re-encode. A 12-megapixel, 4 MB photo typically arrives as a 1–2 megapixel, 100–300 KB JPEG unless you explicitly choose “send as document” or a “HD” option, and even then some apps strip metadata.
- Email keeps the pixels but not the batch. Twenty photos hit the message size ceiling fast (why the limit is what it is), and some phone mail clients offer “small / medium / large” sizes that resample.
- Metadata is the silent casualty. Capture time, camera, lens, GPS position and orientation live in EXIF fields inside the file. Re-encoding often drops them; that is why photos sometimes arrive rotated or land in the wrong place in a timeline.
A file transfer, as opposed to a share, moves the bytes unchanged. Whether the pixels and metadata survive is then decided by the receiving software, not the network.
Cable-free, original quality: the direct link
- On the laptop, open
app.sharedrop.orgin any browser and click Receive. - On the phone, open the ShareDrop.org app or the same address, tap Send, and choose Photos. Select as many as you like — the picker shows the total size.
- Scan the laptop's QR code with the phone, or type the short code.
- Approve on both ends. Compare the safety codes once; then let it run. Each file is verified with SHA-256 before it counts as done.
What you receive is the file the phone holds: HEIC stays HEIC, RAW stays RAW, EXIF stays inside. On the same Wi-Fi expect the transfer to move at your router's speed; on a Wi-Fi 5 or 6 network a hundred 4 MB photos is a matter of seconds, not minutes.
Format questions people hit next
“My laptop cannot open .HEIC”
iPhones default to HEIC, which stores the same picture in roughly half the space of JPEG. Windows 10/11 opens it after installing the free HEIF Image Extensions from the Microsoft Store; macOS and modern Linux image viewers handle it natively. If you need JPEG for an older tool, the cleanest fix is on the phone before sending: Settings → Camera → Formats → Most Compatible makes new photos JPEG. Existing HEIC files can be converted by any image viewer; do that after the transfer so the original is preserved.
Live Photos and motion photos
A Live Photo is two files: a still and a short video. Picking it in a photo picker sends the still; the motion part is a separate item on the phone and a separate file if you want it. Android motion photos are one file with the video embedded, and arrive as such.
“Do I lose the album structure?”
Albums are database entries in the phone's photo library, not folders on disk, so no transfer method carries them over as-is. Sort on the laptop by the capture date in EXIF, which survived precisely because the bytes were not re-encoded.
What survives each method
| Method | Full resolution | Original format (HEIC, RAW) | EXIF (date, camera, location) | Live Photo motion |
|---|---|---|---|---|
| Chat app, as a photo | No: resampled | No: converted to JPEG | Mostly stripped | No |
| Chat app, as a document | Yes | Yes | Usually kept | No: still only |
| Email attachment | Yes, unless the mail app offers a smaller size and you pick it | Yes | Kept | No: still only |
| Cloud photo service (Google Photos, iCloud) | Depends on the quality setting | Depends on setting; RAW often kept | Kept | Yes, within the service |
| Direct transfer | Yes | Yes, byte for byte | Kept | Still, plus the video as a second file if you pick it |
| Cable import | Yes | Yes | Kept | Yes, with the platform's import tool |
RAW, ProRAW and 48-megapixel files
A ProRAW or DNG file from a recent phone is 25–75 MB, and a 48-megapixel HEIC is several times a normal photo. These are exactly the files chat apps mangle worst and email refuses soonest. A direct transfer or a cable are the only two paths that deliver them untouched; a cloud photo service will keep them only if its quality setting is “original,” which on free tiers eats the quota quickly.
The third way: a photo sync service
Google Photos and iCloud Photos are not transfer tools, but they solve the same problem for people who want every photo on every device continuously. The trade-offs are an account on the laptop, a copy in the cloud for as long as you keep the service, and, the one that bites, the quality setting: “storage saver” modes recompress, and only “original quality” keeps what the camera captured. For a one-off move of a few hundred photos, the sync is slower than a direct transfer and leaves more behind; for a library you want mirrored, it is the right tool.
Import tools, by laptop
| Laptop | Built-in import from a cable | Where photos land |
|---|---|---|
| Windows 10/11 | Photos app → Import → From a connected device | Pictures, in dated folders if you choose |
| macOS | Photos app, or Image Capture for plain folders | The Photos library, or any folder you pick |
| Linux | File manager once the phone is in file-transfer mode; Shotwell or digiKam for libraries | Any folder |
After they arrive: putting them in order
Because the EXIF capture date survived, the laptop can sort by it. Windows Photos and macOS Photos both read it on import and group by day; for a plain folder, most file managers can sort by “date taken” rather than “date modified,” which is what you want — the modified date is the moment of transfer, the same for every file. If you moved photos from two phones, expect duplicates only where a photo was shared between them earlier; a transfer does not create duplicates by itself.
Frequently asked
The photos arrive rotated
The file is fine. Phones store the image as the sensor captured it and note the orientation in EXIF; a viewer that ignores that field shows it sideways. Modern viewers honour it; an old one, or a web tool that strips EXIF on upload, does not. Re-saving from a good viewer bakes the rotation in if you need it permanent.
The dates are all today
You are sorting by modified date, which is the moment the file was written on the laptop. Sort by date taken, which came through in EXIF, and the timeline is correct.
Screenshots have no location or camera
Screenshots are PNGs with almost no metadata; that is normal, not a stripping problem. Only camera photos carry EXIF.
Sending photos to someone else's laptop
The steps are identical; the consideration that changes is metadata. An original photo carries the exact location it was taken, to a few metres, and the time to the second. Sending originals to a friend is fine; sending them to a marketplace buyer, a landlord or a stranger from a forum is a reason to strip location first. On iOS, the share sheet's Options let you turn off Location for that share; on Android, Google Photos offers “remove location” when sharing. A direct transfer sends exactly what you picked, so do the stripping before you pick.
When a cable really is the better tool
Wireless shines for tens to hundreds of photos. For a full library migration (many thousands of files, tens of gigabytes), plug the phone into the laptop. USB 3 moves data at several hundred megabytes per second, sustained, and the phone's own import tools (Windows Photos, macOS Image Capture, or Android's file mode) are built for the long haul. Wireless would work, but you would be waiting for the radio when the wire is sitting in a drawer.
A note on receiving in different browsers
Chrome and Edge on a laptop write each photo to disk as it arrives, so batch size is limited only by free space. Safari and Firefox assemble each file in memory and are capped at 512 MB per file, which is no constraint for photos, but matters if the same batch contains long 4K videos (why the limit exists).
