SyncNow notices a change by comparing the live server against what it expected to see. The gap between the two is called drift, and catching it is the whole point.
How detection works
On each check, SyncNow lists the project and compares every file's fingerprint against its manifest. If a fingerprint does not match - a new file, changed contents, or something missing - that is drift. SyncNow turns it into the right event (create, modify, delete, and so on) and appends it to your timeline.
Why fingerprints, not just timestamps
- Content comparison catches edits even when a timestamp looks unchanged.
- It lets SyncNow tell a real move or rename from a brand-new file.
- It keeps the recorded history precise rather than approximate.
Good to know
How quickly drift is noticed depends on your observation interval - SyncNow spots changes on its next check, not the instant a byte changes. And noticing drift never means correcting it: SyncNow is read-only, so it records the change and leaves your files untouched.
SyncNow