Keeping the Archive Sane: Robocopy for Photo and Video Backups

I use Robocopy when I back up my photos, videos, and other media files.

Is it the most advanced backup software in the world? Probably not. It does not give me a beautiful interface, version history, cloud sync, or clever archive management.

But it is already included with Windows, and it runs from Command Prompt, PowerShell, or Windows Terminal. It is fast, scriptable, and transparent. Most importantly: I can see exactly what it is going to do before I let it touch anything.

For my kind of workflow, that matters more than a shiny backup application.

I work with photos, videos, field recordings, project files, and various bits of media that slowly grow into something that needs to be taken seriously. Not necessarily because every file is important, but because some of them are. And I do not always know which ones until much later.

So I try to keep my archive simple enough that I can understand it when I come back tired, distracted, or six months removed from the original project.

Robocopy Lives in the Command Line

Robocopy is a command-line tool included with Windows.

That means you do not open it like a normal application. You run it from Command Prompt, PowerShell, Windows Terminal, or a script file.

For example, in PowerShell:

robocopy "D:\Media" "I:\Media" /S /COPY:DAT /DCOPY:T /L

This is one of the reasons I like it. There is no project file, no hidden database, and no interface trying to be clever. It is just a command: source, destination, rules.

It also means the commands can be saved and reused. Once I know a command works, I can keep it in a text file, turn it into a .cmd or .ps1 script, or simply copy and paste it the next time I need it.

That is not as friendly as clicking a big backup button.

But it is very clear.

Why I Separate Photos and Videos

My media folder is split into a few main areas:

D:\Media\Audio
D:\Media\Music
D:\Media\Photo
D:\Media\Video

The important part here is that photos and videos live in separate root folders.

That might seem obvious, but it makes a big difference over time. Sometimes I go out and only shoot stills. Sometimes I only record video. Sometimes I do both. If everything ends up in one big mixed camera folder, I have to keep checking what is actually inside each date folder.

I prefer this:

D:\Media\Photo\Camera Images\2026
D:\Media\Video\Camera Images\2026

That way, a date folder under Photo contains photos. A date folder under Video contains videos. It is boring, predictable, and easy to understand.

That is exactly what I want from an archive.

Moving Video Files Out of the Photo Archive

One thing I use Robocopy for is separating video files from a camera import folder.

For example:

robocopy "D:\Media\Photo\Camera Images\2026" "D:\Media\Video\Camera Images\2026" *.mp4 /S /MOV /COPY:DAT /DCOPY:T /L

This looks more complicated than it is.

The first path is the source folder. The second path is the destination. The *.mp4 part tells Robocopy to only care about MP4 files.

The switches at the end control how the copy behaves:

/S

Copy subfolders, but not empty ones.

/MOV

Move files after they have been copied successfully.

/COPY:DAT

Copy file data, attributes, and timestamps.

/DCOPY:T

Preserve directory timestamps.

/L

List only. Do not actually copy, move, or delete anything.

That last one is important.

Dry Run First

The /L switch is my safety button.

With /L, Robocopy only shows what it would do. It does not actually do it. No files are copied. No files are moved. No files are deleted.

That means I can test the command first, read the output, and check that the source and destination paths are correct before I remove /L and run the command for real.

When dealing with years of photos and videos, this is not paranoia. It is basic self-defense.

A small typo in a path can turn into a very bad afternoon.

And there is one more important thing to remember: Robocopy is not a friendly photo application with a nice undo button. If you move, overwrite, or delete files with the wrong command, you should not assume that the Recycle Bin will save you.

The command line does what you tell it to do.

That is both the beauty and the danger of it.

Preserving Timestamps

I also care about timestamps.

A media archive is not just a pile of files. It is a timeline. File dates, folder dates, and original capture dates can all help later when trying to understand when something was recorded, imported, edited, or backed up.

I learned this the annoying way.

At one point I realized that a large backup — more than 20,000 photos — had been copied in a way that changed the file timestamps to the copy date instead of keeping the original dates.

That was a bad afternoon.

The photos themselves were not lost, but the archive suddenly became much harder to search and browse. For me, original timestamps are important because they are searchable. They help me find images by time and date without having to open every file or rely on memory.

I eventually solved it with a combination of ExifTool and a small script. The files could be restored from their embedded photo metadata, while the folders were easier: many of them were already named by date, so the script could read the date from the folder name and apply it back to the folder timestamp.

I do not remember every detail of how I solved it, but I remember that it took time. And more importantly, it was an unnecessary mistake.

That is why I use:

/COPY:DAT /DCOPY:T

The first one preserves file data, attributes, and timestamps. The second one helps preserve timestamps on directories.

It sounds like a small detail, but small details matter when an archive starts spanning years.

Backing Up the Full Media Folder

I also use Robocopy to copy my internal media archive to an external drive.

For example:

robocopy "D:\Media" "I:\Media" /S /A-:SH /COPY:DAT /DCOPY:T /L

Again, /L means this is only a dry run.

The idea here is simple: copy my media folder from the internal drive to an external drive while preserving the structure and timestamps.

The /A-:SH switch removes system and hidden attributes from the copied files. In my case, I do not want strange system or hidden attributes following along and making the backup harder to browse.

This is not a complete backup strategy with version history, snapshots, ransomware protection, or automatic integrity checks. It is a controlled file copy.

But controlled file copies are still useful.

Especially when they are easy enough that they actually get done.

Why I Keep Coming Back to Robocopy

After all of this, a reasonable question is why I bother with Robocopy at all.

There are plenty of backup applications available, many of them with polished interfaces, scheduling, version history, and cloud integration. Some of them are excellent.

But for my media archive, I often prefer something simpler.

When I run a Robocopy command, I know exactly what the source is, what the destination is, which files are included, and what will happen when the command runs. If I am unsure, I can add /L and perform a dry run first.

That level of transparency fits the way I work.

I am not trying to build an enterprise backup system. I am trying to keep a growing collection of photos, videos, and other media organized and safely copied to another location without introducing unnecessary complexity.

For that job, Robocopy does exactly what I need.

A Note About Mirroring

Robocopy can also mirror folders, but I am careful with that.

The /MIR switch can make the destination match the source, including deleting files from the destination if they no longer exist in the source.

That can be useful in the right situation.

It can also be dangerous.

For my photo and video archive, I prefer to be conservative. I would rather run a controlled copy, check the result, and avoid accidentally deleting something that only exists on the backup drive.

When in doubt, I dry run first.

Future Me Is the Real Audience

The older I get, the more I realize that good organization is not about being neat for the sake of being neat.

It is about reducing friction later.

Future me should not have to solve a mystery every time he opens the archive. He should not have to wonder whether a folder contains photos, videos, audio, exports, or some strange mix of everything.

He should be able to open the folder and understand what is going on.

That is the whole point.

Robocopy is just one small tool in that workflow. But it is a good one. It is already there, built into Windows, waiting quietly in the command line.

Not glamorous.

Not modern.

Not exciting.

Just a dependable old workhorse that shows up when there is real work to do.

And sometimes that is exactly what a working archive needs.

Because in the end, the best backup tool is not the one with the flashiest interface. It is the one you trust enough to keep using, year after year, as the archive grows and the memories pile up.