Lesson

Synchronisation

Synchronisation keeps your files identical and current across multiple devices; it is a powerful convenience for daily life. But it has a boundary, and this lesson's most important sentence is that boundary: synchronisation is not a backup.

Foundation · 11 min

In this lesson you will learn

  • Explain what synchronisation does using a simple model
  • List syncing's everyday benefits
  • Show with two concrete scenarios why synchronisation is not a backup
  • Check what is being synced on your own devices

How syncing works

Synchronisation's model is the mirror: your phone, your computer and the cloud each hold a reflection of the same folder. When you add, change or delete a file on one device, the change is soon applied to the other reflections. Photo syncing, notes apps showing the same notes everywhere, your cloud folder carrying identical content on phone and computer — it is all this mechanism. The aim is a single current truth everywhere, and for that aim it works beautifully.

Syncing's real benefits

Synchronisation delivers three big conveniences. Continuity across devices: the document you start on the computer, you continue on the phone. Device replacement: switch to a new phone and the synced data arrives with your account. And the shared work we saw in the previous lesson: the shared document stays current for everyone. These benefits are real, and they make synchronisation a cornerstone of modern digital life. The problem is not synchronisation; it is expecting from it something it cannot do.

Why it is not a backup

A backup is defined as an independent copy you can return to when the original is harmed. Synchronisation provides no such independence; on the contrary, it keeps every copy bound to the original. Two scenarios make this clear. Scenario one: you delete a file by mistake. Syncing does its job and propagates the deletion to every device; the file vanishes from everywhere at once. Scenario two: a file gets corrupted, or malicious software encrypts your files. Syncing faithfully carries the damaged state everywhere too. In both cases, "the copy on my other device" does not save you — because it is not a backup but a reflection of the same reality. Some services' recycle bins and limited version history offer partial protection; but they are limited in time and scope, and are no substitute for a deliberate backup routine.

The right division of labour

The right mental model: synchronisation is a convenience tool, backup is an assurance tool, and you need both. Syncing carries the daily flow: current files on every device. Backup is for the dark day: deletion, corruption, loss, theft, an encryption attack. The difference is tested with one question: "If I deleted this file by mistake today, could I get it back a week later?" If the answer rests on syncing alone, it is no. We will build the yes in the Backup and Restore lesson, with the 3-2-1 rule.

Sync settings deserve deliberate use too: most services let you choose folder by folder, and you can leave large, fast-changing folders out of syncing. For anyone on a limited data plan, restricting sync to wireless networks is another setting that matters. Knowing which folders are synced prevents both surprise data usage and the puzzlement of "why isn't this file on my phone?". In short, syncing is a tool to configure once with intent — not to set up and forget.

Common mistake: The comfort of "it's in the cloud, I'm safe"

"My photos sync to the cloud, nothing can happen to them" is this module's most dangerous comfort. A synced photo deleted by mistake is deleted everywhere; if the account is hijacked or locked, the cloud copy becomes unreachable too. The cloud, operating in sync mode, is not a backup; a backup is a copy that lives independently of the original. The cloud can become part of a backup — but through a deliberate backup arrangement, not through trusting sync.

Today's practice

Take an inventory of your devices today: what is being synced on your phone and computer? Check the sync status of photos, notes, documents and contacts in settings, and make a three-column note: things only on the device, things synced, things genuinely backed up. The third column will probably come out short; that note is the starting point of the next lesson.

Summary

  • Synchronisation is a mirror mechanism keeping the same content current on all devices
  • It is indispensable for continuity, device replacement and shared work
  • It is not a backup, because it propagates deletions and corruption just as faithfully
  • Recycle bins and version history are partial, time-limited protection; not a backup routine
  • The test question: if I deleted this by mistake today, could I get it back a week later?

Check your understanding

Questions and answer order are shuffled on every attempt. Results stay in your browser.

First published: 2026-08-12Last reviewed: 2026-08-12Editorial status: working editionReport an error