A copy operation can finish successfully without answering the strongest possible question: Does the destination file contain the same data as the source file?
To verify copied files after synchronization, read the source and destination data and compare their contents. This provides stronger evidence than matching only filenames, sizes, or timestamps.
Verification follows the same foundations used to sync two folders without installing software: compare first, approve the plan, then confirm the results. If you only need the changed subset, begin by comparing two folders and copying only changed files.
Copy Completion and Verification Are Different
When a file write completes, the application knows that the browser's write operation returned successfully.
Verification performs a separate check.
This distinction matters because metadata alone does not prove byte equality.
Two files can share:
- The same filename
- The same extension
- The same file size
- Similar modification times
and still contain different data.
What Exact Content Comparison Does
Exact content comparison reads both corresponding files and checks whether their contents match.
The exact implementation can compare chunks rather than loading huge files into memory all at once. The important principle is that equality is determined from file data, not just metadata.
The official FreeFileSync desktop documentation describes content comparison as a bitwise consistency check and its post copy verification setting as a binary comparison of source and target.
Why Verification Takes Longer
Verification requires additional I/O.
If you copy a 4 GB video and then verify it by reading both source and destination, the storage devices must perform substantial additional work.
On a fast SSD this may be acceptable. On an external hard drive, USB device, or slow storage, it can be more noticeable.
For that reason, users may choose exact verification selectively for important copies rather than treating every low value temporary file the same way.
Verification Does Not Prove Everything
A successful exact comparison can show that the source data read during verification matches the destination data read during verification.
It does not prove:
- The source file was correct before the copy.
- The hardware can never fail later.
- The file will remain readable forever.
- The filesystem metadata is identical.
- Every application specific structure inside the file is valid.
For example, two identically corrupted files still match each other.
Practical Verification Workflow
Step 1: Compare the folders before synchronization
Identify what actually needs to be copied.
Step 2: Run the approved synchronization
Copy missing or changed files.
Step 3: Verify the files that were written
Read the source and destination contents for copied files and compare them.
Step 4: Surface failures individually
If archive.zip does not verify, report that file rather than hiding the issue behind a total success percentage.
Step 5: Retry only where appropriate
A retry can be useful for a transient read or write error. Repeated failures may indicate permission, storage, hardware, or file access problems that need investigation.
Example: Verify a Backup Copy
Source:
Projects/Release/build.zip
Destination:
External/Projects/Release/build.zip
Metadata says both files are 1.8 GB.
That is useful but incomplete.
Exact verification reads both copies. If every compared chunk matches, the destination has the same content as the source observed during the check.
If a mismatch appears, the tool should flag the file and avoid implying that the backup is verified.
Exact Compare Before Sync Versus Verification After Sync
These are related but different.
Exact comparison before sync asks whether existing source and destination files already match.
Verification after sync asks whether the files that were just copied now match the source.
You can use one or both depending on the workflow.
For a large folder, it may be efficient to use metadata comparison to identify what needs copying, then verify the copied subset.
Hashing Versus Direct Content Comparison
A tool can verify files by comparing cryptographic hashes or by directly comparing content. Either approach must read the relevant file data to produce strong content based evidence.
FreeFileSync.online should describe the actual method implemented rather than claiming a hash algorithm that is not used.
The master product concept calls for copy verification and exact content comparison, so published UI copy should remain method neutral unless the final implementation defines the algorithm.
Browser Considerations
Browser file handles can provide readable File objects for user selected files. MDN's FileSystemFileHandle.getFile() documentation describes how a handle exposes the current on disk state.
If the file changes after a File object is obtained, a fresh read may be needed to represent the new state. A verification workflow should therefore read the intended current source and destination states rather than relying on stale objects.
Conclusion
To verify copied files after synchronization, compare the actual source and destination contents after the write completes. Treat verification as stronger evidence of matching data, not as a guarantee against every form of corruption or future hardware failure.
Use Free Online File Sync for comparison and synchronization, and enable verification when the additional confidence justifies the extra reads.