For years, getting photos off an iPhone meant finding a computer. You plugged the phone into a Mac or a PC, waited for the right app to notice it, and dragged files across. If you did not own a computer, or the one you owned had no space left, your only real option was to pay for more cloud storage.
That has not been true since iOS 13. The Files app can read and write external drives directly, which means an iPhone can copy its own photo library onto a USB stick or a portable SSD with nothing else in the room.
This is a practical guide to doing that properly: the hardware that actually works, how the drive needs to be formatted, both methods for the transfer, how to confirm the copy is real, and what to do when something does not behave.
If your reason for doing this is that your phone has run out of room, the companion piece on what to do when iPhone storage is full covers the wider problem, including the Recently Deleted trap that makes deleting photos appear to free nothing.
Can you back up an iPhone to a USB drive without a computer?
Yes, and it is a supported, first-party capability rather than a workaround.
Apple added external drive support to the Files app in iOS 13. Connect a drive, and it appears under Browse in the sidebar alongside iCloud Drive and On My iPhone. From there you can copy files onto it, make folders, and read them back.
Two things are worth knowing before you start.
The first is that the Photos library is not part of the Files app. Your camera roll lives in its own database, not as browsable folders, so you cannot simply drag a folder of photos across. Getting them out means either exporting them through the share sheet or using an app with access to the photo library. Both routes are covered below.
The second is that this is a copy, not a sync. Once the files are on the drive, they are independent of your phone and your Apple Account. If you later delete a photo from the phone — or the phone is lost — the copy on the drive is unaffected. That independence is the entire reason for doing it, and it is what separates a backup from a synced cloud library.
What hardware do you need?
The connector depends on which iPhone you have.
- iPhone 15 and later have USB-C. A USB-C flash drive or SSD plugs in directly, or connects with a standard USB-C cable. Nothing else is required.
- iPhone 14 and earlier use Lightning. You need a Lightning to USB adapter. Apple sells two: the plain Lightning to USB Camera Adapter, and the Lightning to USB 3 Camera Adapter, which has an extra Lightning port for power. The second one is worth the difference, for reasons covered under power below.
The drive. Any standard USB drive works — a flash drive for a few thousand photos, a portable SSD for a full library. SSDs are faster and more durable, and a 1 TB portable SSD costs roughly what a couple of years of mid-tier cloud storage does. Flash drives are cheaper, slower, and fine for smaller jobs.
Power is the most common practical problem. A phone supplies limited power over its port. A USB flash drive or a small bus-powered SSD is usually fine. A portable hard disk with spinning platters, or a larger SSD, may draw more than the phone can give — in which case the drive mounts, appears in Files, and then disconnects partway through a transfer.
The fix is to supply power separately, either with a powered USB hub, a drive that has its own power supply, or the Lightning to USB 3 adapter with a charger plugged into its second port. If your transfers keep dying at unpredictable points, power is the first thing to suspect.
How should the drive be formatted?
This decision causes more failed transfers than anything else, so it is worth getting right before you copy a single file.
| Format | Works with iPhone | Notes |
|---|---|---|
| exFAT | Yes, read and write | Recommended. Works on iOS, Android, Windows, macOS. No practical file size limit. |
| FAT32 | Yes, read and write | Cannot store any single file over 4 GB. Fine for photos, fails on long videos. |
| APFS | Yes, read and write | Apple-native, awkward on Windows. |
| HFS+ | Yes, read and write | Older Apple format, same caveat. |
| NTFS | Read only | iOS can open files but cannot write to the drive. |
Use exFAT unless you have a specific reason not to. It is the only format that is genuinely comfortable everywhere, and it removes the one limitation most likely to bite you.
That limitation is FAT32's 4 GB per-file ceiling. Most flash drives ship formatted FAT32 out of the box, and most photos are far below the limit, so everything looks fine until a long 4K recording or a ProRes clip refuses to copy. The file is not corrupt and the drive is not full — the format simply cannot represent a file that size. Reformatting as exFAT resolves it.
NTFS is the other trap, and a quieter one. A drive that has been used with a Windows PC is often NTFS, and iOS will happily show you its contents while refusing every write. If the drive appears but nothing can be saved to it, check the format before assuming the drive is faulty.
Method 1: The built-in Files app
This needs no additional software and costs nothing. It is the right choice for a one-off transfer of a manageable number of files.
- Connect the drive and confirm it appears in Files → Browse.
- Open Photos and tap Select.
- Select the photos and videos you want. To move quickly, tap the first item and drag across the grid.
- Tap the Share button, scroll down, and choose Save to Files.
- Pick the drive, choose or create a folder, and tap Save.
- When it finishes, eject the drive in Files before unplugging it.
Where this approach struggles. It works, and for a few hundred files it is perfectly reasonable. At the scale of an actual photo library, three things become painful.
You are selecting manually, and selecting several thousand items by dragging across a grid is both tedious and easy to get wrong. There is no record of what you already copied, so the next time you do this you either duplicate everything or try to remember where you stopped. And if the transfer is interrupted — a knocked cable, an underpowered drive, a phone call — you generally start again.
There is also a quality detail worth knowing: exporting through the share sheet can split Live Photos into a separate still image and video file rather than keeping them paired, and depending on the share settings it may convert HEIC images to JPEG. For a quick transfer that may not matter. For an archive you intend to keep, it does.
Method 2: A dedicated backup app
An app with direct access to the photo library avoids the manual selection problem entirely, because it can enumerate the library itself and track what has already been copied.
This is what VaultDrive does. The flow is short:
- Connect the drive to the phone.
- Open the app and choose what to include — everything, or specific albums and folders.
- Start the backup and leave it running.
What it handles that manual copying does not:
- Original quality, byte for byte. No re-encoding and no downscaling. HEIC, ProRAW, ProRes, 4K, and Cinematic all land untouched.
- Live Photos stay paired. The still and its motion clip are copied together under the same base name rather than split into two unrelated files.
- Metadata survives. Capture date, location, and camera data are preserved, so the timeline and map still work wherever you open the files later.
- Readable folder structure. Files land under
VaultDriveBackup/[Device]/in folders by media type, then year, then month — ordinary directories you can browse on any computer without the app. - iCloud originals are fetched first. If Optimize iPhone Storage is on, your phone holds previews rather than originals. A real backup needs the original, so those are downloaded before copying, and anything still unavailable is reported rather than silently skipped.
- Interruptions cost a pause, not the run. iOS suspends apps in the background, so the backup pauses when you leave and resumes from where it stopped when you return — nothing already copied is lost.
- Incremental after the first run. Subsequent backups copy only what is new.
- Nothing is uploaded. No account, no sign-up, no telemetry. The files travel over the cable only.
Core backup is free up to 200 files or 2 GB per run, enough to confirm it behaves the way you want before committing. Removing the cap is a one-time purchase rather than a subscription.
Which route suits you depends on how much you are moving and how often. That is compared in detail — including where the free built-in route is genuinely the better choice — in Files app vs VaultDrive.
How do you know the backup actually worked?
This is the step that separates a backup from a hopeful assumption, and it takes two minutes.
Compare the numbers. Check the file count and total size on the drive against what was on the phone. They will not match exactly — filesystem overhead and format differences account for small gaps — but a large shortfall means the transfer did not finish.
Open real files from the drive. Not thumbnails, which can render from cached previews even when the underlying file is broken. Open several, and deliberately include a video and a Live Photo, because those are the two that most often arrive split, truncated, or as zero-byte placeholders.
Check a date and a location. Open a photo's info and confirm the capture date is the original rather than today's date. If metadata was stripped in transit, your library will still be there but its chronology will not be.
Eject properly. In Files, tap the eject symbol next to the drive before unplugging. Pulling a drive mid-write is a reliable way to damage the directory you just spent an hour filling.
A good backup tool will do some of this for you — confirming after each copy that the file exists on the drive and that its size matches the original, flagging anything that failed, and offering to re-verify a finished backup against what is actually on the drive. But whether the software checks or you do, the copy is not a backup until something has confirmed it.
Only once that passes should you consider deleting anything from the phone. And if iCloud Photos is turned on, remember that deleting on the phone removes the photo from iCloud and every other device on your Apple Account, which is the difference between a sync and a backup.
Troubleshooting
The drive does not appear in Files. Check power first — an underpowered drive can mount and vanish. Then check that you are looking under Browse rather than Recents. Reseat the cable and try a different one; adapters and cheap cables fail more often than drives do.
The drive appears but nothing can be saved to it. It is almost certainly formatted NTFS, which iOS can read but not write. Reformat as exFAT.
A large video will not copy. The drive is formatted FAT32, which cannot hold a single file over 4 GB. Reformat as exFAT.
The transfer stops partway through, repeatedly. Power, in most cases. Use a powered hub, a self-powered drive, or the Lightning to USB 3 adapter with a charger in its second port.
Some photos are skipped as "iCloud only". Optimize iPhone Storage is on, so those originals live in iCloud and only previews are on the device. The originals have to be downloaded before they can be copied. Connect to Wi-Fi, give it time, and re-run — pulling a large library back from iCloud can take a while, and the speed is set by your connection and by Apple.
Files copied, but the dates are wrong. Whatever performed the copy did not preserve metadata. The files are intact but their capture dates have been replaced with the copy date, which matters if you care about chronology.
The drive is full sooner than expected. Check whether you are copying originals rather than optimized previews — a full-resolution library is substantially larger than what the phone reports if Optimize Storage has been running.
What about Android?
The same approach works, with two differences in Android's favour and one against. USB-C phones connect directly and older ones use a USB-A drive with an OTG adapter, and the exFAT guidance is identical.
Android's advantage is that its storage is directly browsable, so a file manager can copy folders across without exporting anything. The catch is that media is scattered across several directories — DCIM/Camera is only the start — and missing the others is the usual reason an Android backup turns out incomplete.
That has its own guide: how to back up Android photos to a USB drive.
How often should you do this?
The first backup is the slow one, because it copies everything. After that, an incremental run every few weeks takes minutes.
A reasonable rhythm for most people is monthly, plus once immediately after any trip or event that produced a lot of footage — which is exactly when a library grows fastest and when losing it would hurt most.
The drive itself is a physical object with the failure modes of a physical object. If the photos genuinely matter, two drives kept in different places is meaningfully safer than one, and it is still cheaper than renting the same amount of cloud storage indefinitely.
Frequently Asked Questions
Can I back up my iPhone photos to a USB drive without a computer?
Yes. Since iOS 13 the Files app can read and write external drives, so an iPhone can copy photos and videos straight to a USB stick or portable SSD with no Mac or PC involved. An iPhone 15 or later connects to a USB-C drive with a plain USB-C cable, and an iPhone 14 or earlier needs a Lightning to USB adapter.
How should I format a USB drive for iPhone backup?
Use exFAT. It works on iOS, Android, Windows, and macOS, and it has no practical file size limit. FAT32 also works but cannot store any single file larger than 4 GB, which a long 4K or ProRes video will exceed. APFS and HFS+ work with iOS but are awkward on Windows. Avoid NTFS, because iOS can read it but cannot write to it.
Why won't my USB drive show up in the Files app?
The three usual causes are power, format, and the connection itself. A drive that draws more power than the phone supplies will mount and then disappear, which a powered hub or a self-powered SSD fixes. A drive formatted NTFS appears but cannot be written to. Otherwise reseat the cable, try another one, and check the drive under Browse rather than Recents in the Files app.
Why can't I copy a large video to my USB drive?
Almost always the drive is formatted FAT32, which cannot store a single file larger than 4 GB. A long 4K recording or anything in ProRes will pass that limit easily. Reformatting the drive as exFAT removes the restriction, since exFAT has no practical per-file size limit and works across iOS, Android, Windows, and macOS.
Do photos lose quality when copied to a USB drive?
They should not. A direct file copy moves the original bytes, so HEIC, ProRAW, ProRes, 4K, and Cinematic files arrive exactly as they were. Quality loss happens when something re-encodes or downscales along the way, which is why it is worth confirming that whatever you use copies files rather than exports them, and that it keeps Live Photos paired instead of splitting them.
How do I know my backup actually worked?
Check three things before trusting it. Compare the file count and total size on the drive against what was on the phone, allowing for small differences in overhead. Open several files directly from the drive, deliberately including a video and a Live Photo, since those fail most often. Then eject the drive properly in the Files app rather than pulling it out mid-write.
The short version
A computer is no longer part of this. An iPhone 15 connects to a USB-C drive directly, an older iPhone needs a Lightning adapter, and the Files app has been able to write to external drives since iOS 13.
Format the drive exFAT before you start — that one decision avoids the 4 GB video limit and the NTFS write problem, which between them account for most failed transfers. Supply power separately if the drive needs it.
Then copy, verify, and eject. Verification is the part people skip and the only part that determines whether you have a backup or just a drive with some files on it.