Robocopy Copy Files With Progress: How to Watch a Long Job

Robocopy is built into Windows and shows progress as it copies. This guide explains how to run it, read what it prints, and keep an eye on a long transfer.

Windows file copy dialog at 21% complete, copying 9 items from Documents to Desktop at 1.83 GB/s, over a blue wallpaper.
In this article

Yes, Robocopy shows progress. When you copy files with Robocopy in a Command Prompt or Windows Terminal window, it prints each file name and a running percentage for the file it is working on, which Explorer’s drag and drop does not give you in text form. [1] For a closer look, read Best File Copy Software for Windows.

Robocopy is a command-line copy tool included in Windows since Windows Vista, so Windows 10 and 11 already have it. [1] Microsoft’s tool is built for copying whole folders reliably, and it can resume over network connections that drop out. [1] Related reading: How to Move Files Without Copying in Windows.

This article walks you through running a job, reading what the console prints, and handling big jobs so you can tell how far along a long copy really is.

What should you know before you start?

Robocopy needs no setup: you type the command, a source and a destination, and it runs. The basic form is below, and it comes from Robocopy’s documented syntax, where each path can be a drive path or a network share. [1]

robocopy source destination

If a path contains spaces, wrap it in quotes. For example:

robocopy "C:\My Documents" "D:\Backup Folder"

Where to run it

Open Command Prompt or Windows Terminal. To get a Command Prompt quickly, press Win+R and type cmd in the Run dialog. [2] You don’t download anything, because Robocopy ships with Windows. [1]

Windows 10 and 11

The command is the same on both versions, so the examples here work on either. Windows 10 is past or at the end of its support window, so Windows 11 is the better long-term choice.

Safety: some switches delete files

Switches such as /MIR mirror the source to the destination, which can delete files in the destination that are not in the source. One example in the sources uses /MIR together with /MT:40. [2] Back up the destination first, and try any new command on a small test folder before pointing it at real data.

A good test is to create two small folders with a few dummy files, run your command between them, and look at the result. Once the outcome is what you expected, repeat the command on the real folders.

A person sits at a desk in a home office and looks over folders of files on a computer monitor before a backup.

How do you copy a folder with Robocopy and see progress?

Copying a folder with Robocopy takes one command, and the progress appears in the same window as it runs.

  1. Open Windows Terminal or Command Prompt. Robocopy is included with Windows, so there is nothing to install. [1]

  2. Type the command with the source first, then the destination. The syntax is ROBOCOPY source destination [file [file]… ] [options], and a path can be a drive path or a network share path. [1]

  3. For a network copy, use a command like this one, which copies a folder to a share on another server:

robocopy "C:\Users\a-jes\Documents\SQL Server Management Studio\Extended Events" "\\SQL2014AG2\C$\Users\a-jes\Documents\SQL Server Management Studio" /z

[3]

The first path is the source and the second is the destination. The /z switch at the end turns on restartable mode, which helps if the connection drops. Quotes around each path keep the spaces in folder names from breaking the command. 4. Press Enter and watch the window. Robocopy prints a percentage for each file as it copies, which is useful with large files. [1] File names scroll past as the job moves through the folders. 5. Let it run until the prompt returns. When the job ends, Robocopy prints a summary table of what it did, so you can see the counts for the whole job.

To copy only certain files, add a file name or wildcard after the destination. This example copies just the compressed XML files from one folder:

robocopy "C:\Users\a-jes\Documents" "\\SQL2014AG2\C$\Users\a-jes\Documents" *.xml.gz /z

[3]

If you leave the file part out, Robocopy copies everything, because the default is all files. [1]

How do you read Robocopy’s progress output?

Robocopy’s output tells you two things at a glance: which file it is working on and how far along that single file is. It does not show a percentage for the whole job.

The per-file percentage

The progress indicator on the command line is most useful when copying large files. [1] If you are copying a 40 GB backup file followed by many small documents, the counter will sit on that one big file for a long time. That is normal and does not mean the job has stalled.

The file names

The names scrolling past show where Robocopy is in your folder tree. If you copy Documents and the listing is working through a folder starting with the letter M, you are roughly partway through. Treat this as a rough guide, not a measurement.

The final summary

When the job ends, Robocopy prints a summary table. Read its counts for what was copied, what was skipped because the file already matched, and what failed. A nonzero failed count means some files did not make it, so scroll up through the listing to find them.

Restartable mode for shaky connections

If you are copying across a network that may drop, add /z. Robocopy works over network connections subject to disruption or outages, with a resume copying feature. [1] A network example that uses it looks like this:

robocopy "C:\Users\a-jes\Documents" "\\SQL2014AG2\C$\Users\a-jes\Documents" *.xml.gz /z

The source and destination come first, *.xml.gz limits the copy to files with that pattern, and /z turns on restartable mode. [3]

How can you speed up and monitor a big copy job?

To speed up a big copy, add the /MT switch with a thread count so Robocopy copies several files in parallel. This helps most when a folder holds many large files, and it can be much faster than a normal Ctrl+C, Ctrl+V copy. [2]

  1. Open Command Prompt or Windows Terminal.

  2. Run the command with /MT: followed by the number of threads you want:

robocopy \\machineA\folderA D:\folderB /MIR /MT:40

This example starts 40 threads to do the copy job in parallel. [2] The first path is the source, the second is the destination, and /MT:40 sets the thread count.

  1. Look closely at /MIR in that example. It mirrors the source to the destination, which means files that exist only at the destination can be deleted. If you only want to copy, leave /MIR out and use a copy option such as /E for subdirectories, including empty ones. [1]

  2. Keep the window open and watch the file listing as it advances. The names scrolling past show how far through the folder tree the job has moved.

  3. If the disk or network struggles, lower the number. Fewer threads, such as /MT:8 instead of /MT:40, may be gentler on a slow disk or network connection.

When the prompt returns, the job is done and the summary table appears.

What mistakes should you avoid?

Most Robocopy problems come from a few habits that are easy to avoid once you know them.

Closing the window mid-job

Robocopy runs inside the console window, so closing that window ends the copy. A half-finished job leaves only some files at the destination. Keep the window open until the summary table appears, and if a network link drops, rerun the same command rather than starting from a different folder.

Trusting the percentage for the whole job

The percentage on screen describes the file being copied right now. It does not tell you how much of the folder is done, so use the scrolling file names to judge where you are.

Mixing up source and destination

Robocopy reads the source first and the destination second, in this form: ROBOCOPY source destination [file [file]… ] [options] [1]. Swapping them copies in the wrong direction. Say you want a school folder copied to a USB drive: the folder path comes first and the drive path second. Read the line aloud before pressing Enter.

Overlooking long paths

Very long paths are a real reason people reach for Robocopy instead of Explorer. One forum poster needed it because their folders had very long paths that could not be copied and accessed otherwise [4]. Their company also did not allow registry tweaks, so enabling long path support was not an option, and they relied on Robocopy for such tasks [4]. If Explorer chokes on deeply nested folders, Robocopy is worth trying.

Quick questions about Robocopy progress

Is there a graphical progress window?

Robocopy itself is command-line only, but graphical options exist. Community front-ends wrap Robocopy in a window, and some users point to tools such as TeraCopy as graphical alternatives. [5] If you want a point-by-point comparison, see the Robocopy vs TeraCopy article.

Can PowerShell show a progress bar?

Yes, a PowerShell script can draw its own bar with the Write-Progress cmdlet. One community script, for example, calls it with an activity title, a status such as “Progress 0%” and a percent-complete value while it copies files. [4]

Write-Progress -Id 1 -Activity "Copying shortcut contents from $srcDir to $destDir" -Status "Progress 0%" -PercentComplete 0

The -Activity text is the bar’s title, -Status is the line beneath it, and -PercentComplete sets how full the bar is. Your script has to update that value as it works.

Does Robocopy work on Windows 10 and 11?

Yes. Robocopy has been included in Windows since Windows Vista and remains available in later versions, including Windows 10. [1] It also has a progress indicator on the command line that is useful when copying large files. [1] Nothing needs to be installed, so you can open a terminal and run it right away.

Which Robocopy approach should you use?

Start with the plain command: robocopy source destination prints each file name and a running percentage, which is all most copy jobs need. [1] Run it first on a modest folder so you know what normal output looks like.

Once that works, add /MT with a thread count for big jobs. The example robocopy \\machineA\folderA D:\folderB /MIR /MT:40 starts 40 threads to copy in parallel. [2] Treat 40 as a starting point you tune after testing, not a rule.

That example also uses /MIR, so back up the destination before you mirror anything.

Sources

  1. RoboCopy Syntax and Command Line Switches and Examples – ProjectDox Customer Portal

  2. Sometimes you meet a situation that it costs too much time to copy a folder from a place to another…

  3. Oh, and there’s a really easy tool to copy files built into Windows – Robocopy.

  4. Powershell script to extract all folders and files from .lnk in recursive folders

  5. RoboCopy front-end