When two source files map to the same destination name, Keep Both preserves both by assigning one of them a unique destination filename instead of overwriting an existing copy.
This is the safest default when you cannot confidently choose which version should win.
For the complete process, start with how to merge two folders without overwriting duplicate files. If the original paths provide useful context, also review how to combine folders while preserving their structure.
A Filename Conflict Does Not Tell You Which File Is Correct
Old folders often contain names such as:
final.docx
report.pdf
image.jpg
budget.xlsx
The same name may represent completely different content.
Automatically replacing the first file with the second is not conflict resolution. It is a destructive choice.
First Check Whether the Files Are Actually Identical
Before renaming both, compare contents where practical.
If two report.pdf files are byte identical, keeping two renamed copies may just create clutter.
If they differ, preserve both unless you have enough context to choose one.
This gives a useful decision tree:
- Same destination path?
- If no, copy normally.
- If yes, are contents identical?
- If yes, keep one or skip the redundant copy.
- If no, Keep Both, Skip, or deliberately Replace.
Safe Renaming Rules
A Keep Both implementation should generate predictable unique names.
For example:
report.pdf
report (2).pdf
report (3).pdf
A timestamp or source label can also work if it remains readable.
The rename logic should:
- Preserve the extension.
- Avoid another collision.
- Show the final name before writing.
- Remain deterministic within the job.
- Keep enough of the original filename to identify the file.
Use Source Labels for Complex Merges
If you are merging many archives, names such as:
report [Laptop].pdf
report [USB].pdf
can make the origin easier to understand than simple numbering.
The final interface may support one rename style, but the content should not promise a specific style unless it is implemented.
The essential capability is preserving both versions without overwriting.
Keep Both Versus Skip
Keep Both copies the incoming conflict under a new name.
Skip leaves the existing destination file unchanged and does not copy the incoming conflict.
Use Skip when the destination is curated and you intentionally do not want new conflict files mixed in.
Use Keep Both when future review is more important than immediate tidiness.
Keep Both Versus Replace
Replace chooses a winner.
That can be appropriate after manual review.
For example, if contract-v2.pdf has been confirmed as the signed final agreement and the destination holds an outdated unsigned version under the same name, replacement may be deliberate.
The merge tool should never assume that a newer timestamp always means “better.”
Preview Makes Keep Both Manageable
Keeping both can create many renamed files.
A conflict preview can group them so you can decide whether the merge needs deeper duplicate comparison or more selective source choices.
For example, 4,000 conflicts across two backup drives might indicate that you are merging near copies of the same archive.
Running exact content checks on the conflict set can reveal how many are actually redundant.
Preserve Context
When using Preserve Folder Structure, a renamed conflict remains inside its relative directory.
Example:
Clients/Acme/Contracts/agreement.pdf
Clients/Acme/Contracts/agreement (2).pdf
That is usually easier to review than flattening both into a huge root folder.
Do Not Delete the Sources Immediately
After a complex merge, keep the original folders until you have reviewed the destination.
A completed activity report is useful, but it is not a substitute for a recovery copy.
For important archives, verify selected merged files before retiring old storage.
Review the Rename Pattern Before a Large Merge
A naming rule that looks harmless for one conflict can become confusing across hundreds of files. Before starting a large job, inspect several planned Keep Both names.
A useful rename should make each file unique without hiding the original identity. The extension must remain correct, and the generated suffix should not accidentally create a name that already exists.
For instance, if the destination already contains report.pdf and report (2).pdf, the next incoming conflict cannot simply be renamed to report (2).pdf. The merger has to continue until it finds an unused name.
The preview should show the exact destination path after renaming, not merely say “Keep Both.” This lets you spot unreadable or unexpected naming patterns before thousands of files are copied.
Treat Modification Dates as Context, Not Authority
A newer modification date can help you understand a conflict, but it does not prove that the newer file is the version you want. A file can receive a newer timestamp after export, restoration, or another copy operation.
When two same name files differ, preserve both if the content cannot be judged confidently. You can compare, open, or organize the versions later without having destroyed one during the merge.
Conclusion
To merge folders and keep both files, treat name collisions as review points, compare contents when useful, assign a unique destination name, and preview that rename before copying.
Use Free Online Folder Merger with Keep Both as your default conflict rule when preservation matters more than choosing an immediate winner.