01 / Workflow detail
The short answer: comparing two folders in Windows 10 and 11
Windows has no built-in window that shows the differences between two folders. File Explorer can show two folders side by side, but you compare names, dates, and sizes yourself, one directory at a time.
Two built-in commands can list differences without installing anything. In Command Prompt, robocopy "C:\Folder A" "C:\Folder B" /L /E /NJH /NJS /NP /NDL lists the files that are new or different in the first folder. /L means list only, so nothing is copied, and /E includes subfolders. Robocopy compares sizes and dates, not contents. In PowerShell, Compare-Object (Get-ChildItem "C:\Folder A" -Recurse -File) (Get-ChildItem "C:\Folder B" -Recurse -File) -Property Name, Length lists the files whose name or size differs.
For a visual folder diff that checks content, finds moved files, and opens each changed file, use a folder comparison app. The steps below use Diff Anything.
02 / Workflow detail
How to compare two folders on Windows
Open Diff Anything and select a folder (directory) for each side of the comparison. Place the known baseline on the left and the folder you want to check on the right. For example, compare the previous release output with the candidate release output, using the same directory level on each side.
Open Folder options and keep Recursive enabled to include subfolders. Review the ignore list before trusting the result: if the task is to check a release package, a rule that hides its build output defeats the purpose of the comparison.
Use the tree layout to follow the directory structure or the table layout to scan paths. Search for a specific file and filter the results by status. Open a changed pair to see the content difference before deciding which version to keep.
03 / Workflow detail
Understand missing, changed, and moved files
Read each status relative to your chosen baseline. If the candidate is on the right, Right only is an addition and Left only is something absent from the candidate. Neither status is an instruction to copy or delete the file.
Folder comparison results, with the original on the left| Result | What it tells you |
|---|
| Right only | The path exists only in the right folder. If the right side is your newer copy, this is an addition. |
|---|
| Left only | The path exists only in the left folder. It is missing from the right side; that does not mean it should automatically be deleted. |
|---|
| Changed | The paired files differ under your selected content, size, or timestamp settings. Open the pair to inspect the change. |
|---|
| Moved | Matching file content was found at another relative path. Review the old and new locations together. |
|---|
| Conflict | The same relative path has different entry types, such as a file on one side and a folder on the other. |
|---|
| Identical | The entries match under the active comparison rules. With semantic comparison enabled, this can mean equivalent structured content rather than identical bytes. |
|---|
| Unverified | Content was not verified, for example because of the selected size settings, a read error, or a file changing during the scan. Resolve the cause before treating it as a match. |
|---|
| Contains changes | A folder contains differences further down the tree. Expand it to review the individual entries. |
|---|
04 / Workflow detail
Check content, not just names and dates
Two files can have the same name and size and still contain different data. A newer modification date also does not tell you what changed. Choose the checks that answer your question in Folder options: Compare file sizes, Compare small-file content, Compare hashes, and Ignore timestamps.
For a byte-level check of the included files, enable Compare hashes and turn off Semantic structured files. For a configuration review, leave semantic comparison enabled: supported JSON, YAML, XML, CSV, and environment files can compare by their parsed content within the maximum content size. For example, reordered JSON object keys need not count as a meaningful change.
Identical means a match under those settings. It does not certify files excluded by your patterns, hidden-file setting, or preview limit. Review warnings and Unverified entries before concluding that two folders match.
05 / Workflow detail
Compare two files on Windows
To compare two files instead of two folders, choose File on each side, or drop both files onto the window. With Auto selected, Diff Anything picks the comparison from the file type.
Text and code open as a side-by-side diff with the changed lines and words highlighted. Excel and other spreadsheet workbooks are compared cell by cell. PDF and Word documents are compared by their extracted text, and images can be reviewed with an overlay. You can also open any Changed file straight from a folder comparison, which starts the same file comparison for that pair.
The built-in alternative is Command Prompt: fc file1.txt file2.txt prints the lines that differ between two text files, and fc /b compares two files byte by byte.
06 / Workflow detail
Set up a useful Windows folder comparison
Choose equivalent roots. Comparing a release directory against a parent containing several releases makes normal nesting look like missing files. If nearly everything appears on only one side, check the selected roots before changing your filters.
Review Ignore patterns for generated directories such as node_modules, dist, build, or target. Excluding these can help when comparing source projects, but keep them visible if they are the output you need to verify. Use Include only these patterns when the question concerns a specific part of the tree.
Check Case-sensitive paths when folders have crossed operating systems: decide whether README.md and readme.md should pair up. Hidden files includes dot-prefixed paths; review that setting and the ignore rules when configuration files belong in the comparison. If files are actively being written, wait for the copy or build to finish and rerun the comparison.
07 / Workflow detail
Check a copied folder, release, or configuration
A folder diff is most useful when the result answers a specific question:
- Did the copy include everything? Compare the original and destination folders, look for Left only entries, and enable content hashing for the included files. Matching names and sizes alone do not prove a complete copy.
- What changed in the release? Compare two equivalent output directories. Review added and removed assets as well as changed files; remove ignore rules that hide the output under review.
- Which configuration values changed? Include the relevant JSON, YAML, XML, CSV, or environment files and use semantic comparison within the content-size limit. Open a changed pair for the detailed result.
08 / Workflow detail
What is included in Free and Pro?
Free lets you try folder comparison with a preview of the first 100 collection items and 10 new comparison sessions per local day. Free file comparisons are limited to 5 MiB per side, and nested folder content checks are also subject to the Free content-size limit. A preview is useful for evaluating the workflow; it is not a complete review of a larger folder tree.
A one-time Pro purchase removes the collection-preview and daily-session limits and unlocks larger sources within technical limits. Pro also adds folder synchronization, report export, and saved comparison profiles and history. Start with a small, representative pair of folders to see whether the review fits your work.
09 / Workflow detail
Synchronize selected changes with Pro
Comparing folders reads the sources; it does not automatically make either side match the other. If you decide to update a folder, select the intended entries, choose left-to-right or right-to-left, and review the synchronization preview. Check every create, update, delete, and move before applying the plan.
Diff Anything checks for stale results, shows progress, supports cancellation, and offers one-click undo after a successful synchronization. Recovery information also supports rollback after interrupted work. Keep both folder roots available and verify the destination after the operation. For important files, retain a separate backup.