iCloud Drive versus local files: what actually changes

Every Mac eventually asks you to decide where a file actually lives: on this machine, or in iCloud. It looks like a small setting buried in System Settings, but it changes what happens when you lose the Mac, when your connection drops, and when you stop paying for storage. Neither option is wrong. They are built for different jobs, and most of the frustration people have with either one comes from using it for the wrong job.

What iCloud Drive actually buys you

iCloud Drive keeps a copy of your files in Apple's cloud and syncs them to every device signed into the same Apple Account. Apple's own guide to storing files in iCloud Drive on a Mac is plain about the mechanism: as long as iCloud Drive is switched on and a device is signed into the same account, that device's copy stays current. Turn it off on one Mac and Apple says so directly, that device's documents and data stop staying up to date.

In practice that buys you three real things. A file you saved on your Mac this morning is already on your phone and your other Mac by lunchtime, with nothing to copy or plug in. If this specific Mac is lost, stolen, or its drive fails, the file survives it, because a working copy already exists somewhere else entirely. And keeping that copy running, backed up and free of corruption becomes Apple's problem rather than yours, which is worth real money if you have ever rebuilt a folder structure from scratch after a drive failure.

What it costs you in return

None of that is free, in either sense of the word. iCloud Drive needs a working connection to actually move a change, so a file edited on a plane will not appear on your other devices until you are back online and it has had a moment to sync. Storage beyond the free tier requires a paid iCloud+ plan, and the arrangement is explicitly conditional rather than a one-off purchase: Apple's own instructions for downgrading or cancelling an iCloud+ plan tell you to download or remove anything over your new storage amount before you make the change, which is Apple confirming in writing that continued access to that space depends on continuing to pay for it.

The whole arrangement also rests on staying signed into the right Apple Account. Let that lapse, alongside the subscription, and files do not vanish the moment either one does, but the easy access that was the entire point of storing them there goes with it.

What staying local actually buys you

Keep a file on this Mac's own disk, or on an external drive plugged into it, and none of the above applies. There is no connection to wait for and no account to stay signed into: the file opens exactly the same in airplane mode as it does at a desk with fibre internet. There is no ongoing cost tied to that specific storage either. Once you own the drive, putting another file on it costs nothing more, this year or in five years.

It is also entirely within your control. Nobody else decides when a file gets offloaded to save space, nobody can change the terms of what you are allowed to keep, and the backup strategy, if there is one, is a decision you made rather than a default you inherited. The honest trade in the other direction is that none of this happens automatically. A local file does not follow you to a second device on its own, and if the drive holding it fails without a backup elsewhere, it is genuinely gone. Local storage does not manage itself. It just does not charge you for the privilege of not managing it.

So which one should you actually use?

Most people should use both, for different things, rather than picking a side. iCloud Drive earns its cost on anything you actually touch from more than one device: a document you edit on a laptop and finish on an iPad, a spreadsheet you check from your phone, a folder you and someone else both need current. That is exactly the job it was built for, and paying a subscription for it is a fair trade for never thinking about which version is the current one.

A large, finished archive you only ever open from one machine is the opposite case. Years of reference images, a completed project folder, a library you built once and now mostly search rather than edit, none of that benefits from being everywhere, and every gigabyte of it sitting in iCloud is a gigabyte you are quietly paying a subscription to keep synced to nowhere. Local disk, or an external drive if the Mac itself is getting tight, is the honest home for that kind of collection.

The mistake most people actually make is not choosing either side. It is leaving everything wherever it happened to land, which usually means an ever-growing iCloud bill for files that never needed to leave this Mac in the first place.

Where does Muse fit into this?

Muse stores its library in a normal, visible folder on your Mac, not in iCloud, by default. That is a deliberate choice for a library you are meant to open constantly: it is fast because there is nothing to download first, and it works exactly the same with the internet off.

It is worth stating the limitation plainly rather than skating past it, because it is a real one. A library that lives locally does not follow you to another Mac automatically. Open Muse on a second machine and you will not see what you saved on the first unless you move the library folder yourself, onto an external drive or another shared location, which where Muse stores your library covers in full. If what you actually want is a collection that shows up automatically on a phone or a second Mac the moment you save something, that is not what Muse does out of the box, and it is better to know that before you have spent a year collecting into it than to discover it afterwards.