How N-way folder comparison works
Add your sources, click Compare, and see a consolidated result showing the status of every file across all sources.
Add any combination of sources
Each source can be a different type. Mix and match freely:
- Local folders on your machine or a network drive
- Git branches (read directly via libgit2, no checkout)
- GitHub repositories via the REST API
- Archives: ZIP, TAR, 7Z, RAR, ISO
- FTP/SFTP remote paths (Premium tier)
- Web URL sources (Premium tier)
One consolidated result
The results view shows every file once, with a status column per source. You can see at a glance which sources have the file, whether it differs, and which source is the outlier when most agree but one does not.
Example: three-folder comparison
Here is what a 3-way comparison result looks like. The outlier column shows where one source differs from the other two.
The blue cell marks the outlier - the source that disagrees with the majority.
Minority difference highlighting
When most sources agree and one does not, DirectoryCompare Pro flags the outlier automatically.
What is minority difference highlighting?
In a 4-way comparison, if three sources have identical content for a file and one source has a different version, that one source is the minority. DirectoryCompare Pro detects this pattern and flags the outlier source directly in the results view.
This is useful for deployment comparisons where you expect dev, staging, and prod to match a release candidate, and you want to immediately see which environment has drifted. Instead of reading through every row, the outlier is already highlighted for you.
Filter toolbar: cut through the noise
Large directory comparisons can produce hundreds of rows. The filter toolbar lets you focus on what matters.
Filter modes
- All files: the complete unfiltered result, every file in every source.
- Differences only: shows only rows where at least one source disagrees. The fastest way to find what changed.
- Identical only: confirms which files are the same across all sources - useful for verifying a sync.
- Minor differences: isolates rows flagged as minor (whitespace, line endings, timestamps) so you can dismiss them separately from meaningful changes.
Per-row copy arrows
Resolving differences is a one-click operation per file, not a separate merge step.
Copy to resolve a difference
Each row in the results view has copy action arrows. Click the arrow to copy a file from one source to another. You control the direction: left-to-right, right-to-left, or broadcast from the authoritative source to all others.
This is useful when you have identified a production config that drifted and you want to overwrite it from the staging version in a single click.
Open in diff viewer
Double-click any file row to open it in the full diff viewer. For N-way sources, the diff viewer shows all versions side by side with per-line highlighting. You can see exactly which lines differ between each pair of sources.
Plugin viewers extend this to STL/OBJ (3D geometry), WAV (audio waveform), and ACF (audio config) files.
Use cases for N-way folder comparison
Dev / staging / prod
The classic three-environment deployment check. Load all three as sources and instantly see which files have drifted between environments. Filter to Differences to focus on what needs syncing.
Backup verification
Compare your live directory against two or three backup snapshots simultaneously. Confirm which backup contains the version of a file you need, without running multiple sequential comparisons.
Branch divergence
Add main, develop, and a feature branch as three sources. See which files have changed in each branch and identify merge conflicts before they become a problem.
Release verification
Compare a Git tag, a build output folder, and a production deployment archive all at once. Verify that what shipped matches the source that was tagged for the release.
Multi-version archive diff
Add v1.0.zip, v1.1.zip, and v2.0.zip as sources. Track how a distributed package evolved across versions without extracting each archive manually.
Parallel workstream merge
When two developers have been working in separate local copies of the same folder, load both copies plus the shared baseline as a 3-way comparison to see what changed on each side.
Compare three folders at once - free for 7 days
N-way comparison is available on the Standard tier. Full 7-day trial starts automatically on first launch, no sign-up required.
Download DirectoryCompare ProFrequently asked questions
How many folders can I compare at once?
There is no fixed limit. DirectoryCompare Pro supports arbitrary N-way comparison - you can add 2, 3, 4, or more sources. Practical limits are determined by your machine's available memory and the size of the folders being compared. Most users work with 2 to 5 sources in a single comparison session.
Can I mix local folders with Git branches?
Yes. Each source is configured independently, so you can add a local folder as source 1, a Git branch as source 2, and a GitHub repository as source 3 - all in the same comparison. The source types are completely interchangeable.
What is minority difference highlighting?
When you compare three or more sources and most of them have the same version of a file but one source has a different version, DirectoryCompare Pro highlights the outlier source in that row. This makes it easy to spot the one environment or branch that has drifted, without reading through every cell in the results grid.
Is there a limit on folder size?
There is no hard file count limit enforced by the application. Very large directories (hundreds of thousands of files) will use more memory and take longer to scan. Directories with millions of files may benefit from using folder filters to narrow the comparison scope before running.
Is N-way comparison in the free tier?
N-way comparison (more than 2 sources) requires the Standard tier ($39/year) or the 7-day full-featured trial. The Basic (free forever) tier covers 2-way comparison. Licenses are activated inside the app via Help → Register / Activate.
Does it work on Linux?
Yes. N-way comparison and all source types work identically on Linux x86_64 and Windows 10/11. Download the Linux tarball from the download page.