Understanding Robocopy Output Formatting
When running robocopy without specific formatting arguments, the tool provides verbose feedback by default. This includes a header section with job details, followed by repeated blocks of data separated by long dashed lines. Each block typically lists the source file name, the destination path, and status codes such as New File or Updated File. While this verbosity is helpful for debugging specific transfer issues, it creates clutter when logging backups to a file or monitoring large-scale operations via a script.
The dashed lines are generated because Robocopy outputs two distinct lists: the directory list and the file list. By default, both are printed between every batch of copied items. To achieve a clean, minimal output that resembles a simple log entry rather than a full diagnostic trace, you need to disable these specific output streams. The most common approach involves combining several flags that target different aspects of the reporting mechanism.
Why Dashed Lines Appear
The visual separators exist to delineate the processing of directories from the processing of files. When Robocopy enters a new folder, it prints the directory structure. It then iterates through the contents, printing each file's status. Without suppression flags, these two types of entries interleave, creating the repetitive pattern of headers, dashes, and footers that characterizes standard Robocopy execution. For automated scripts or scheduled tasks, this noise makes parsing the output difficult and wastes disk space if redirected to a log file.
Using /NFL and /NDL Flags
The primary solution involves adding the /NFL and /NDL switches to your command line. The /NFL flag stands for "No File List," which prevents Robocopy from displaying the names of individual files being copied. The /NDL flag stands for "No Directory List," which stops the tool from printing the directory paths and subfolder structures during the copy process.
- /NFL: Suppresses the output of file names and their attributes.
- /NDL: Suppresses the output of directory names and their attributes.
When you combine these two flags, Robocopy skips the detailed listing phase entirely. Instead of showing every file and folder, it jumps straight to the final summary at the end of the operation. This drastically reduces the volume of text produced, eliminating the dashed lines that separate these lists. You can apply these flags alongside other standard parameters like /E (copy subdirectories, including empty ones) or /Z (restartable mode) without affecting the actual copying behavior.
Complete Command Example
Below is a typical command structure that uses these flags to produce clean output. Replace the source and destination paths with your actual directories.
robocopy "C:\SourceFolder" "D:\BackupFolder" /E /NFL /NDL /R:1 /W:1In this example, /E ensures all subdirectories are included. /R:1 limits retries to one attempt, and /W:1 sets the wait time between retries to one second. The critical components for suppressing output are /NFL and /NDL. With these present, the console will remain quiet during the transfer, displaying only the initial job header and the final summary table. This is particularly useful when integrating Robocopy into larger PowerShell scripts or batch files where intermediate progress updates are unnecessary.
If you also wish to suppress the display of skipped files, which can sometimes appear in the output even with /NFL, you can add the /NS (No Size) and /NC (No Class) flags. However, for most backup scenarios, /NFL and /NDL are sufficient to remove the visual clutter and dashed separators.
Logging Clean Output
One of the most common reasons to suppress output is to generate a clean log file for auditing purposes. You can redirect the output of the suppressed command to a text file using the /LOG: parameter. This ensures that the resulting log file contains only the essential summary data, making it easier to review later or parse with regular expressions.
robocopy "C:\SourceFolder" "D:\BackupFolder" /E /NFL /NDL /LOG:C:\Logs\BackupLog.txtThis approach creates a highly readable record of the backup job. The log will show the start time, end time, number of files copied, and any errors encountered, without the thousands of lines of file-by-file details. If you want to append to an existing log rather than overwriting it, use /LOG+ instead. This method is ideal for long-running backups where you need a historical record but do not require real-time visibility into every single file transfer.
For more advanced scenarios involving complex directory structures, consider reviewing strategies for avoiding infinite duplication to ensure your cleanup logic does not interfere with your output expectations.
Frequently Asked Questions
Does using /NFL hide error messages?
No, the /NFL flag only suppresses the list of successfully processed files. Error messages, warnings, and exceptions will still be displayed in the console or logged file. This allows you to identify failed transfers or permission issues while keeping the rest of the output clean.
Can I suppress the summary statistics too?
Robocopy does not have a flag to completely silence the final summary table. Even with /NFL and /NDL, the tool prints a summary of bytes copied, files copied, and elapsed time at the end of the job. If you need absolute silence, you would need to redirect the entire output to NUL, but this is generally not recommended for troubleshooting.
What is the difference between /NFL and /NJH?
/NFL removes the file list from the middle of the output. /NJH removes the Job Header, which is the section at the very beginning that displays the source, destination, and options used. Using both results in a minimal output containing only the final summary and any errors.
How do I handle empty directories with these flags?
Using /NFL and /NDL does not change how Robocopy handles empty directories. If you use /E, empty directories are still created at the destination. The flags only affect what is printed to the screen, not the structural integrity of the backup.
Are there alternatives to Robocopy for silent backups?
PowerShell cmdlets like Copy-Item or third-party tools like FreeFileSync offer quieter defaults. However, Robocopy remains preferred for its resume capability and robust error handling. If you switch to PowerShell, you can simply suppress output by assigning the result to a variable or using $null, though this requires more scripting effort.