Robocopy does not display real-time per-file copy speeds in its standard output; it only provides a summary of the average speed and total bytes transferred at the end of the job. To track progress, you must analyze the exit codes and the final statistics block, while "Skipped" files are those that already exist with identical timestamps and sizes, meaning they were intentionally ignored to save time.
Understanding Robocopy Output Limits
Many users assume that running robocopy source dest /E will show a live meter for each file being copied. This is a common misconception. The tool is designed for high-throughput batch operations, not interactive monitoring. Consequently, the console remains silent or scrolls rapidly through file names without providing granular performance metrics for individual items. You cannot rely on the visual output during execution to determine if the process is stuck or how fast a specific large file is moving.
The only reliable speed metric available is the average transfer rate calculated across the entire operation. This value appears exclusively in the summary section printed after the copy task completes. If you need to monitor progress in real-time, you must use external tools or check the destination folder size periodically, as Robocopy itself lacks a built-in progress bar feature.
Interpreting the Summary Statistics
Once the command finishes, look for the detailed statistics block at the bottom of the output. This section contains the critical data points you need to evaluate performance. It lists the number of files copied, the total bytes transferred, and the elapsed time. From these numbers, you can derive the effective throughput.
The summary typically includes lines such as:
- Total Copies: The count of files successfully written to the destination.
- Total Bytes: The aggregate size of all copied data.
- Total Time: The duration from start to finish.
To calculate the average speed, divide the Total Bytes by the Total Time. For example, if 10 GB were copied in 100 seconds, the average speed was approximately 100 MB/s. Note that this is an average, not a peak speed. Network congestion or disk latency may cause fluctuations that this single number smooths over.
Using Exit Codes for Quick Checks
Instead of parsing text output, you can check the error level immediately after the script ends. A value of 0 indicates no errors. Values between 1 and 7 indicate various success states with minor issues. Higher values suggest significant failures. This method is faster than reading the full log but provides less detail about speed.
Decoding "Skipped" Files
The term "Skipped" often confuses new users who fear data loss. In Robocopy, a skipped file is one that exists in both the source and destination directories and has not changed since the last sync. Specifically, Robocopy compares the file timestamp and size. If both match, the file is considered up-to-date and is skipped.
This behavior is intentional and efficient. It prevents unnecessary I/O operations on unchanged data. If you see many skipped files, it means your backup or sync job is working correctly by avoiding redundant work. However, if you suspect files have changed but Robocopy still skips them, check if the timestamps were preserved during previous transfers. Using the /MT flag for multi-threading can sometimes affect how timestamps are handled depending on the version, though generally, /COPYALL preserves attributes strictly.
Forcing Re-Copy of Skipped Files
If you need to overwrite existing files regardless of their status, use the /IS (Include Same) switch. This forces Robocopy to copy files that are already present and identical. Be cautious with this option, as it increases processing time significantly for large datasets. Alternatively, /IT (Include Tweaked) copies files that have different timestamps but identical content, which might be useful if you want to update metadata without changing the binary content.
Monitoring Large Transfers
Since Robocopy does not provide internal progress bars, consider using third-party utilities like robocopygui or PowerShell scripts that wrap the command. These tools can parse the log file in real-time and display a graphical interface showing current speed and remaining time. For simple command-line environments, you can redirect output to a log file using the /LOG:filename.log parameter. Then, use another terminal window to tail the log file and watch for updates.
Another approach is to use the /R:n and /W:n switches to control retries and wait times. Setting these to low values can help keep the process responsive if network drops occur, preventing long pauses that might look like a frozen speedometer. Combining /Z (restartable mode) ensures that if the connection breaks, the copy resumes from where it left off rather than starting over, preserving the integrity of your speed measurements across interruptions.
Frequently Asked Questions
Can I see the speed of each individual file?
No, Robocopy does not support per-file speed reporting. It aggregates data into a summary average upon completion. You must estimate individual file speeds based on the overall average or use external monitoring tools.
Why are my files marked as Skipped even though I changed them?
Robocopy skips files based on matching timestamps and sizes. If you edited a file but Windows did not update its timestamp correctly, or if you restored from a backup with old timestamps, Robocopy may skip it. Use /IS to force a re-copy.
What does a high number of "Extra Files" mean?
"Extra Files" indicates files present in the destination directory that do not exist in the source. This is normal for mirrors or incremental backups. It does not imply an error, but you can delete them using the /PURGE switch if desired.
How do I prevent Robocopy from failing on read-only files?
Use the /R:0 switch to set zero retries. By default, Robocopy retries failed operations three times. Setting it to zero stops immediately on access denied errors, allowing your script to handle the failure logic instead of waiting.
Is there a way to get a progress percentage?
Not natively. You would need to pre-calculate the total size of the source folder and then compare it against the growing size of the destination folder using a separate script. Robocopy itself does not expose this percentage dynamically.