Short answer: yes, you can back up a Mac to Dropbox, but putting files in the Dropbox folder only syncs them. A mistake made on one machine reaches the others in seconds.
You can still use that space for a real backup. It takes two things Dropbox does not do on its own: versions you control, and something that reads the copy back.
Dropbox is very good at one thing: making the same folder appear on several machines and keeping it that way. That is genuinely useful and it is genuinely not a backup, for three reasons.
~/Dropbox lives on the same
drive as everything else you own. One disk failure takes it and the original at once, which means the
second copy you thought you had was really the first copy in two places.Dropbox does keep history, and it is worth knowing exactly how much before you rely on it.
Thirty days is a real safety net for the mistake you notice. It is not an archive. The document you last opened in 2023, the photo library you have not checked since the move, the accounting file for the tax year before last: none of that is protected by a thirty day window, because you will not notice within thirty days.
Dropbox also now sells a separate product called Dropbox Backup, which is a backup tool and does keep proper history. It is a different thing from the folder, it is priced separately, and it is worth knowing it exists so you do not assume the folder is doing its job.
The pattern is: make an archive, encrypt it, drop it in the Dropbox folder, and record what you wrote so you can check it later.
tar -cJf - ~/Documents | openssl enc -aes-256-cbc -pbkdf2 -out ~/Dropbox/documents.tar.xz.encThen record the hash, in a file that travels with it:
shasum -a 256 ~/Dropbox/documents.tar.xz.enc > ~/Dropbox/documents.sha256And a month later, ask whether it is still the same bytes:
shasum -a 256 -c ~/Dropbox/documents.sha256That is a real backup, and it is better than most people have. Its limits are worth being honest about. It is one archive with one passphrase, so getting a single file back means bringing the whole thing down and decrypting it. It has no history unless you make a new dated archive each time, and then you are paying for every copy in full. And nothing runs it but you.
Here is the part nobody mentions. When a file appears in your Dropbox folder, it is on your disk. It is not necessarily on Dropbox's servers yet, and there is no public API on macOS that will tell you whether it got there.
Dropbox shows a tick in Finder. That badge comes from Dropbox's own File Provider extension and nothing else can ask it. So any tool that claims to have confirmed your upload is either reading the badge in a way that is not supported, or it is guessing.
The practical consequence: for the first minutes or hours after a backup is written, the second copy you think you have is bytes on the same disk as the first one. Copy Shelter says so in the interface, which is why the number it shows you is the number of copies it has actually checked.
None of this means the space is no good. You are already paying for it, it is off-site, and off-site is the copy most people are missing. What it needs is a real backup written into it. A folder of live files pointed at it is a different thing.
Copy Shelter treats a Dropbox folder as a destination: it writes an encrypted, versioned repository into it, so your files are unreadable to Dropbox and to anybody who gets into your Dropbox account, deleting a file on your Mac does not remove it from the backup, and old versions stay until you say otherwise. Everything is encrypted before it leaves the Mac with a key generated on your machine, and the backup is read back and checked against its hashes on a schedule. It is free for one location, and there is no storage bill from us because it is your Dropbox space.
One rule regardless of the tool: do not point the backup at a folder that is on the same disk as the things you are protecting. A Dropbox folder is on that disk. That is fine when it is a second destination and not fine when it is the only one.
Dropbox/Copy Shelter.No. Dropbox only covers what is inside the Dropbox folder, or the folders you hand to Dropbox Backup. Apps, settings and everything outside those folders are not included.
It is a good off-site place to keep a backup. On its own the sync folder is a copy that follows every change, deletions included, so it needs a backup tool writing versions into it.
You can, and it is worth doing as an off-site copy. Understand what you have: the local half is on the same disk as your originals, and until the upload finishes it is only on that disk. Treat it as a second or third copy.
Thirty days on Basic and Plus, 180 days on Professional and Business. That covers a mistake you notice. It does not cover a file quietly damaged two years ago, and that is the case a backup exists for.
In transit and at rest on their servers, with keys they hold. That protects the files from someone stealing a disk in a data center. It does not stop Dropbox, or anybody who gets into your account, from reading them. Encrypting before upload is the only version of this that is yours.
It is a separate product from the sync folder, it does keep proper history, and it is a reasonable thing to pay for. It is also a storage subscription that grows with your data. The alternative is writing a backup into space you already have, which is what this page is about.
Yes. A deduplicated, compressed backup is usually a good deal smaller than the files it protects, but it is not free. Check the size of what you are protecting before you point a backup at a 2 GB plan.
Not in the ways that matter here. Every sync service propagates deletions, keeps a limited version history, and gives macOS no supported way to confirm an upload finished. See backing up to Google Drive and to iCloud Drive for the provider-specific details.
Related: Google Drive, Proton Drive, iCloud Drive, and how to encrypt a backup.