Hitchhiker's Guide to Robocopy

Robocopy is a Windows command-line tool for copying, syncing, moving, and mirroring files or folders, especially across large directories and network paths. This guide explains how Robocopy works, which switches matter most, and how to test commands safely before changing production data.

Why should you use Robocopy?

Robocopy helps Windows admins reliably transfer large sets of files across directories or networks. Use Robocopy when File Explorer or basic copy commands are too limited for large, repeatable, or network-based file transfers. It gives admins control over retries, logging, permissions, mirroring, file filters, and interrupted transfers.

While copying a few files here and there can be a simple undertaking, transferring mind-bogglingly large numbers of files or multiple folders across a network can get very complex very quickly. But to quote Douglas Adams, “Don't Panic,” because this exact scenario is what Robocopy was built to handle.

Robocopy has more options than you can shake a stick at. If you’re the type of person who buys a fully loaded car simply because it comes with all the options (even though you’ll never use half of them), then Robocopy is for you. You’ve got options for logging, scheduling, attributes, file name lengths, file types, excluding, including, file sizes, purging, and much, much more. You'll probably never use most of the options, but it’s comforting to know they’re there.

Robocopy vs. Xcopy

Use Robocopy for almost any modern Windows file copy job. It offers multithreading, robust ACL handling, mirroring, better logging, and resilient network behavior. Xcopy is still available, but it is best reserved for simple one-off copies or compatibility with old scripts. For modern admin workflows, Robocopy offers better retry handling, logging, mirroring, and permission controls.

Quick comparison

What are the main Robocopy switches?

Robocopy switches control how files are copied, filtered, retried, logged, and saved as reusable jobs. Admins commonly use switches like /E, /MIR, /Z, /COPYALL, /R, /W, /LOG, and /MT to make file transfers safer and more predictable.

If you ever want to view what additional switches can be set for a given command, simply enter the command followed by /?. For example, to return all the available options for Robocopy, run this in the Command Prompt.

As you’ll see, this command returns a long list of available Robocopy switches, letting you copy files where, when, and how you want. To make this information a little easier to digest, I’ve listed commonly used parameters in this handy-dandy table. I’ve also included my own notes on each switch, detailing what they do since the included explanation from Microsoft could be considered lackluster at best.

Copy options

File selection options

Retry options

Specialized and newer copy options

Robocopy also includes specialized switches that are useful in newer Windows environments or more advanced copy scenarios. Most admins won’t need these every day, but they’re worth knowing about for network performance, sparse files, and copy throttling.

Logging options

Job options

Remarks from Microsoft

Back in the day, using /PURGE or /MIR on the root directory of the volume caused Robocopy to apply the requested operation on files inside the System Volume Information directory as well. This is no longer the case. If either is specified, Robocopy skips any files or directories with that name in the top-level source and destination directories of the copy operation.

The modified files classification applies only when both source and destination filesystems support change timestamps (e.g., NTFS) and the source and destination files have different change times but are otherwise the same. These files are not copied by default; specify /IM to include them.

Using /LFSM requests Robocopy to operate in low free space mode. In that mode, Robocopy pauses whenever a file copy causes the destination volume's free space to go below a 'floor' value, which can be explicitly specified by the LFSM:n[KMG] form of the flag. If /LFSM is specified with no explicit floor value, the floor is set to ten percent of the destination volume's size. Low free space mode is incompatible with /MT, /EFSRAW, /B, and /ZB.

Common Robocopy examples

Always test destructive commands, especially anything using /MIR or /PURGE, with /L first. The article already emphasizes that /MIR and /PURGE can delete destination files if they no longer exist in the source.

How do you use Robocopy?

Okay, now that my fingers are nice and numb, how about we look at some Robocopy examples? The goal here isn’t to give you an example for every possible scenario. Instead, I want to provide you with a general idea of what the various parameters do and how they work. Understanding the parameters helps you envision how best to use them in your environment.

Default parameters

Let me just knock this one out of the park real quick. Even when you provide the bare minimum with your command, Robocopy still includes several parameters by default. Most of these parameters are listed as default options in the table above.

If you ever want to see what options are set by default, run the following command.

This returns the following information.

As you can see, if you don’t specify any additional parameters, the defaults are:

This is what you can expect from Robocopy if you don’t specify any other options. I added the /QUIT parameter just to make sure the job didn’t actually run since I only wanted to see what the default parameters were.

Basic copy job

While the default options are okay (albeit a bit excessive with the retry settings), usually when I copy something, my intention is to copy everything, including subdirectories. Let’s look at the Robocopy syntax that accomplishes this.

As you can see from the screenshot above, the command copied three files and one directory from C:\Gov_Secrets to C:\Public_Knowledge. Notice that the switch /S was added automatically. This is the expected result. Any time you add /E to a Robocopy command, /S is automatically added. We’ve also instructed Robocopy to retry five times and wait 10 seconds before each retry.

How does Robocopy mirror and purge files?

/MIR is simultaneously one of the best and scariest options with Robocopy. If you know what you’re doing, /MIR is great. If you don’t know what you’re doing, you can be left with missing files and no backup.

/MIR syncs two directories. Many users see this as a great backup option, which it can be. However, keep in mind that if a file gets deleted from the source accidentally, it also gets deleted from the destination copy when the Robocopy command runs. If you think you will ever need to restore a file that may have accidentally been deleted from the source, then I would not recommend using /MIR or /PURGE.

On the flip side, /MIR and /PURGE are great at keeping your backup tidy as you clean up your source directory. If you don’t use /MIR or /PURGE, then your destination copy may balloon in size since it will never delete any files, even if you delete them from the source directory.

I’ve got a couple of interesting things to point out after running this command. Notice that the switch /PURGE was automatically added even though it wasn’t in the original command. Also notice that an extra file called “How The Universe Actually Started.txt” appeared in the destination folder. Because we ran the /MIR parameter, which automatically adds the /PURGE switch, this file was removed from the destination folder.

Remember, /MIR can be your friend, but it can also be your unreliable friend who betrays you when you least expect it. Or perhaps exactly when you expect it.

How do you move files with Robocopy?

If you just need to move multiple files and directories from one location to another, you can use the /MOV or /MOVE parameters. This is similar to cutting and pasting data from one directory to another.

I prefer copying files from one location to another rather than manually deleting the source data just in case the move job encounters an error, but to each their own. If you like to live dangerously, then /MOV and /MOVE may be the adrenaline fix you’re looking for. Consider adding the /ZB switch to help resolve any issues encountered during the move job.

Let’s break this down because this command is interesting. The description provided with the /MOVE command is a bit deceiving. /MOVE moves the files inside the source folder to a new folder and then deletes the source folder. It won’t touch subdirectories.

Imagine this. You have Folder1 and Folder2. Folder1 only has files in it, no subdirectories. /MOVE moves all the files from Folder1 into Folder2, then deletes Folder1.

Now, if you have subdirectories in Folder1, you need to include /E in order to move both files and subdirectories. This is probably what most people are trying to do with this command. The /COPYALL and /DCOPY:DAT is just to ensure everything comes over unless you don’t want to bring over permissions and such. I’ve included /ZB just in case it’s a large transfer that may get interrupted and in case permissions cause a file transfer issue. And finally, I’ve included the /R and /W parameters. I like to add these with all of my Robocopy commands to ensure something doesn’t hang forever.

How do you monitor file changes with Robocopy?

Robocopy can monitor folders for changes and run incremental passes using the /MON and /MOT switches.

/MON and /MOT allow Robocopy to continually run on a system, monitoring for file changes. This allows Robocopy to serve as a kind of pseudo-backup service. /MON:n checks for a specified number of changes before making another copy pass. /MOT:n waits for a specified period of time before performing another copy pass. These switches can be combined, so both conditions must be met before Robocopy completes another pass.

As you can see in this screenshot, Robocopy still runs as it waits for the conditions to be met. /MON:5 instructs Robocopy to wait for five changes to be detected before running another pass. /MOT:10 instructs Robocopy not to make another pass for at least 10 minutes. With this combination of /MON:5 and /MOT:10, Robocopy does not run for at least 10 minutes. After 10 minutes, if five changes have been made, then a copy pass runs. If, after 10 minutes, five changes haven’t been made, Robocopy continues to wait for those five changes before running. To end the process, simply use the CMD abort command, which is CTRL+C.

How do you filter files and folders in Robocopy?

Robocopy filters files and folders with file names, wildcards, file extensions, attributes, size, age, and include or exclude switches. Use /XF to exclude files, /XD to exclude folders, and wildcards like *.log or *.tmp to target specific file types.

From the “File Selection Options” section in the parameters table, there are 24 different parameters to filter with. Not 42, but 24. Let that sink in. That’s a lot of options, which is the whole point. Robocopy was designed to ensure users could have complete control over their copy jobs. This one’s for you, fellow control freaks.

Before we dive into the actual switches, it’s important to note that you can filter files without actually adding any switches. Here’s a basic example:

Notice that since I included the actual file name that I wanted to copy (“My Name Is Inigo Montoya.txt”) only that one file was copied, even though there are other files in the source folder.

You can extend this functionality even further by using wildcard symbols. Wildcards are symbols that take the place of unspecified characters. There are two well-known wildcards, and there are a couple of lesser-known, or “undocumented,” wildcards.

Let’s take a look at a few wildcard examples.

With the b* parameter included, you’re telling Robocopy that you only want to copy any files that start with the letter b. In the screenshot above, you can see that “Bare Necessities.txt” and “Bear Grylls.txt” were the only files to get copied over because they both start with the letter b.

You can include the wildcard symbol anywhere in a file name. In fact, when you run the most basic Robocopy command, you can see that by default, the *.* file filter is included, which means all files will be included.

Here’s an example of using the ? wildcard.

If you need to copy only files that do not have file extensions, you could use the < wildcard. Here is an example:

Notice that only the files without file extensions were copied over. Take note that we used quotation marks surrounding the < wildcard. If you don’t enclose the < wildcard in quotes, you’ll receive an error that says, “The syntax of the command is incorrect.”

You can also extend the functionality of wildcards to include directories by adding the /S or /E switch.

What’s important to note is that when you add a file filter and include subdirectories, the filter applies to both files and folders recursively. In other words, the filter also applies to the files contained in the subdirectories that meet the filter criteria. As you can see from the example above, since I filter anything that started with the letter “a”, the folder “Area 51 Alien Communication Files” was copied, but only one of the files inside of that folder was copied.

If you’d rather specify what you want to exclude, use /XF to specify files you wish to exclude and /XD to specify directories you want to exclude.

You can also use the wildcard symbol to filter by file type. *.docx only includes files of the .docx type. *.txt only includes files of the .txt type.

If you want to include more than one filter, simply include a space between each filter.

This example copies .txt, .docx, and .jpg files that start with the letter a and b.

If you want to filter based on attributes, you can use the /IA:[RASHCNETO] to include certain attributes or /XA:[RASHCNETO] to exclude specific attributes. The switch options are as follows:

/MAXAGE, /MINAGE, /MAXLAD, /MINLAD are all useful for filtering based on the age or the access date of the file. /MINAGE is especially useful for filtering out files that haven’t been touched in years.

This command copies only files that have been modified within the last year. As you can imagine, this is great when you have those users or departments that struggle to clean up their older files.

With so many filter options, it’s difficult to cover them all, but there is one more that I would like to highlight, and that’s the /XO switch. This switch excludes files that have newer versions in the destination directory. This is useful if you have users working out of both the source and destination folders. You don’t want to accidentally overwrite a file that a user has been working on in the destination folder, and this switch stops that from happening.

How do you use Robocopy over a network?

Transferring files across the network can be stressful for any sysadmin, depending on the situation. You may need to migrate your files to a new file server, or maybe you need to capture a backup of some network files. Regardless, there are a few Robocopy switches that can help you ensure a smooth transfer process.

Note that when transferring network files, users have reported issues when targeting mapped drives, so it’s recommended that you use full UNC paths in your Robocopy commands.

These are some pretty standard options you’ll want to consider when doing a big network transfer job. We're using full UNC paths for our source and our destination. The /RH:1900-0500 option specifies that we only want Robocopy to run from 7 p.m. to 5 a.m. Once 5 a.m. hits, the Robocopy job pauses, which should prevent Robocopy from bogging down the network during work hours. We’ve included some logging options as well with /V, /TEE, and /LOG, which we will cover more in-depth in a moment.

I want to emphasize that no two network environments are the same. You'll need to evaluate your network to determine which switches and options you need to complete your file transfers. I strongly suggest you use /PURGE and /MIR cautiously when transferring critical network files, or really any vital data. Robocopy is terrific at deleting files if you're careless with your commands.

How do you enable Robocopy logging?

By default, Robocopy outputs quite a bit of information to the console window. I find this pretty sufficient for most small Robocopy jobs. However, when you're dealing with critical files or transfers of hundreds of GB or even TB of data, it’s good practice to have an actual log file to review, especially if an issue occurs.

Much like its options for everything else, Robocopy offers an abundance of logging options. While most options are user-preference settings to either minimize or maximize what data is logged, there are a few standouts.

You can see the difference between these two logs, one with the verbose switch, and one without it.

Here is an example of a command that generates a verbose log file with the date included in the file name. I use the /TEE switch to also send the output to the console window.

How do Robocopy job files work?

Robocopy job files save source paths, destination paths, file filters, and switches in a reusable .rcj file. Use /SAVE to create a job file and /JOB to run that saved configuration again. This could be very helpful if you find yourself running the same long list of Robocopy commands over and over again. Robocopy commands can grow exceedingly long, especially if you have to include a lot of filter options.

Here’s how to save and call upon job files via Robocopy:

• /SAVE:job_name → Saving a Robocopy job is as simple as adding the /SAVE command to the end of your Robocopy command. Make sure it is the last switch added to the command, as any other options added after the /SAVE switch will not be saved. The file will be saved with a .rcj extension.

• /JOB:job_name → Calling a Robocopy job file is just as simple as saving it. Simply enter the /JOB switch with the name of the job file you want to run.

Here is a simple example to create a Robocopy job file.

As you can see, I’ve purposefully included the /MIR option after the /SAVE option. If I view my job file, /MIR is not there.

Now, if I add the /MIR parameter before the /SAVE parameter, my copy options look like this.

To run a job, execute Robocopy with the /JOB:file_name option. When the job file runs, you’ll see all of the parameters passed by it.

If you want to edit a job file, but you don’t want to run a command to do it, you can modify job files with any text editor. By default, the job files are filled with comments, though they can be trimmed down to the bare minimum parameters if that’s more your style.

Here’s a job file I edited to contain the bare minimum information.

And here is the result from running the job file.

As you can see, without the comments, the job file is much smaller, and all that’s really needed is the source, destination, and switches.

Two other options I’d like to briefly discuss related to Robocopy jobs are the /NOSD and /NODD parameters. These options let you leave the source and destination locations out of your job files. When you run the job file, you need to include the information. This is useful if you need to run the same job in multiple locations.

• /NOSD → No source specified. This will automatically be added to the job file when you leave the source directory out of the command.

• /NODD → No destination specified. This will automatically be added to the job file when you leave the destination directory out of the command.

When you call this job, you want to include the source and destination information. The job contains the options you previously saved, but you can append more options that aren’t in the job file if you wish.

You can see in this example that I’ve called the job file, though I’ve also included the /COPYALL switch, which wasn’t included in the job file.

The filter m* from the job file remained intact, and the /COPYALL option was also included.

How do you safely test a Robocopy command?

Since we like to play it safe with utilities that can easily wipe out an entire file server, it’s a good habit to test our Robocopy commands before running them on production data. We want to do whatever we can to prevent an oh no, not again type of situation.

Running your commands against test files and folders is a great way to ensure your command is doing what you want it to do. However, there is one other testing method that you should probably start using before you go full contact IT on your network, and that’s the /L switch.

• /L → Provides details about the command you are running, with all of the files and folders that would be affected, without actually running the command.

You can use the /L switch to give you a preview of what will happen when you actually run your command. I like to also send the results to a log file for review.

As you can see, the job looks like it runs and returns all of the results, but if I view the destination folder, it will be empty, just like in my dreams.

Another easy way to tell if the job didn’t actually run is you won’t have the percentages next to the file indicating the copy status.

Now let’s remove the /L switch and compare the actual results.

As you can see, with the /L switch removed, the copy status of the files is displayed.

What do Robocopy return codes mean?

Here is a list of the Robocopy return codes and their meanings. Exit codes 0–7 are success codes, and anything >= 8 indicates a failure.

How do you troubleshoot common Robocopy errors?

Start by dry‑running with /L and logging to a file, then fix paths, quoting, permissions, timestamps, and retry settings. Add /Z (or /ZB if needed) for flaky networks, remove risky /MIR until tested, and tune /R and /W to avoid long retry stalls.

Quick triage checklist

1. Rerun with /L /TEE /LOG:"C:\Logs\robocopy_diag.txt" /V /FP /TS.

2. Verify quoted paths and use UNC instead of mapped drives.

3. Run elevated; add /B or /ZB if hitting ACL issues.

4. Set retries: /R:5 /W:10.

5. For timestamp weirdness between filesystems, add /FFT and optionally /DST.

How do you run Robocopy with PDQ Connect?

Looking to run a Robocopy job against remote and on-prem machines? PDQ Connect has your back. Sign up for a free trial to give it a try.

1. In PDQ Connect, click Packages > Create package.

   

2. Give your package a name.

3. Click Add install step > Add script step.

4. Set the type to Cmd, enter the Robocopy command you want to run against targets.

   

5. Add the success codes 0,1,2,3,4,5,6,7.

6. Click Save, and your package is now ready to deploy to your targets.

How do you run Robocopy with PDQ Deploy?

Need to run a Robocopy job against multiple machines? PDQ Deploy will have you transferring files all over the place in no time. PDQ Deploy allows you to deploy a command or batch file with just a few clicks. Don’t have PDQ Deploy? Download a free trial so that you can follow along.

1. With PDQ Deploy open, click New Package.

2. Give your package a name.

3. Click New Step > Command.

   

4. Enter the Robocopy command you want to run against targets.

5. Add the success codes 0,1,2,3,4,5,6,7.

   

6. Click Save, and your package is now ready to deploy to your targets.

What are alternatives to Robocopy?

I've never really given it much thought, but there are a lot of different ways to move a file. Let’s go over a few other common methods of transferring files and see how they stack up to the competition.

Drag and drop

Hover your mouse over a file, click and hold, drag the file to another location such as another open folder or the desktop, then let go of the file.

Right-click, copy/cut, and paste

Right-click on a file and select Copy or Cut. Right-click anywhere in the destination folder and select paste. Copy obviously copies the file. Cut removes the file from the current location once it’s been moved to its new destination. This is usually my go-to method when I need stuff moved and don’t really care about the details.

Ribbon menu

Select the file you want to copy and select Home from the ribbon menu. Next, select Move to or Copy to. If the destination you want is in the list of locations, select it; otherwise, select Choose location… and browse to the destination folder, then select either Move or Copy. (I’d be interested to see how many people actually use this method. As for me, I’m far too lazy.)

Command Prompt

If you’re old school or aspire to be a hacker one day, then you’ve obviously been using Command Prompt to transfer files. The commands you want to use are the move or copy command. Here’s the syntax.

or 

Example:

PowerShell

PowerShell is the option of choice for those sysadmins who try to accomplish everything, and I do mean everything, with PowerShell. Need to rename a shortcut on a desktop? PowerShell. Need to reboot? PowerShell. But how does it compare to Robocopy? Well, I know a few PowerShell fanatics, and even they usually stick with Robocopy, though they may launch it from the PowerShell console instead of the Command Prompt. I think it’s because they prefer the color blue.

Here’s the syntax:

or

Example:

PowerShell cmdlet table

PowerShell has cmdlets that overlap with some Robocopy workflows, especially copying, moving, deleting, checking paths, and creating folders. They aren’t one-to-one replacements for Robocopy switches, but they’re useful for smaller file tasks or for wrapping Robocopy in larger automation scripts.

Robocopy or PowerShell?

Xcopy

Xcopy (extended copy) has been around for a long time. We’re talking DOS 3.2 long. Xcopy was developed to provide more functionality than just the “copy” command. Xcopy is still available to use with Windows 11, Windows 10, and Windows Server 2019, though it has been deprecated in favor of Robocopy.

Here's the syntax.

Example:

There are many more parameters that can be used with Xcopy; this is just the basic usage.

File copy step in PDQ

PDQ allows you to build custom packages that you can then deploy to hundreds or even thousands of targets. One option when creating a package in PDQ is the file copy step. With the file copy step, you simply select a source and a target folder. It’s about as simple as it gets. Okay, maybe it’s not quite as simple as the drag and drop method, but when you need to do it for hundreds of computers, this option is one of the best.

In PDQ Connect

1. Launch PDQ.

2. Click Packages > Create Package.

3. Name your package.

4. Click Add install step > Add file copy step.

5. Select your source folder.

6. Select your target folder.

7. Click Save.

In PDQ Deploy

1. Launch PDQ Deploy.

2. Click New Package.

3. Name your package.

4. Click New Step > File Copy.

5. Select your source folder.

6. Select your target folder.

7. Click Save.

Your new package is ready to be deployed to all of your adoring fans … I mean users.

It’s really quite impressive how many options one tool can have for a task as simple as copying files. However, once you dive into the intricacies of file copying, you begin to realize why Robocopy has such a massive number of options. When it comes to protecting data, you need to account for every what-if scenario you may encounter along the way.

Hopefully, this blog has cleared up some of Microsoft's vague parameter explanations and you’ve gained a better understanding of how to implement these options into your Robocopy commands. Honestly, the best way to understand how most of these options work is to simply test them out.

The best way to learn Robocopy is to test each command with /L, review the output, and only then run it against real data. That one extra step can save you from a very long afternoon with a very uncomfortable amount of silence.

Now, if you’ll excuse me, I need to go ice the nubs where my fingers used to be.