In the past, I had used only an external hard drive for my backups. It worked great, and it backed up to folders, in a way that I could go to individual files in the backup. I decided that since I was on a laptop, I should be backing up wirelessly (so I don't have to keep it plugged in). After my first painfully long backup to my old Time Capsule, I realized the file was not a folder but a .sparsebundle file. What is this? How do I change it back?

  • 2
    A blurb from the Time Machine Wikipedia article expresses a reason as to why it uses a sparse bundle with network storage devices in better detail then Gordon Davisson's answer. "The significant difference is that when using remote storage, Time Machine uses sparse bundles; this acts as an isolation layer, which makes the storage neutral to the actual file system used by the network server, and also allows to replicate the backup from one storage to another. Commented Mar 1, 2016 at 16:02
  • 2
    Sparse bundles are mounted by OS X like any devices, presenting their content as a HFS+ formatted volume, functionally similar to a local storage." Commented Mar 1, 2016 at 16:03
  • @user3439894 You might want to add that an an answer, that's pretty good.
    – JMY1000
    Commented Mar 1, 2016 at 16:37

5 Answers 5


I'm pretty sure you can't, and you wouldn't want to. The OS only bypasses the bundle for locally attached backup destinations.

  • Direct attached storage (DAS) uses the HFS+ filesystem and /Backups.backupsdb folder structure
  • Network attached storage (NAS) uses the sparse bundle format to embed a HFS+ filesystem on whatever filesystem that the NAS uses natively.

Time Machine's backup format plays some very interesting tricks with the Mac OS Extended filesystem that aren't really possible over a generic network storage volume. It's also optimized to minimize network traffic when files change. This speeds both backup, browsing and restore operations and minimizes the volume of data file changes on the NAS for small changes on the source disk.

In order to get TM to work over a network connection, it stores a disk image (in sparse bundle format) on the network server, and mounts that locally on the client. Since it's mounted locally, the client has full access to the filesystem and can play all of the necessary tricks.

So, without the .sparsebundle, you wouldn't be able to back up over the network since it optimizes the amount of data sent to the Time Capsule when a file changes as well as reduces the load on the Time Capsule to handle easier IO to the disk.

You can still mount the sparse bundle image on any OS X machine and navigate to files. The only drawback might be if you are using an OS that doesn't have a filesystem plug in for sparse bundle storage format.

  • 9
    It would be much more informative if you'd provide actual facts about the reason Time Machine is using a sparse bundle and explaining what these "tricks" are, then saying things like... "Time Machine's backup format plays some very interesting tricks with the Mac OS Extended filesystem that aren't really possible over a network connection." and "... and can play all of the necessary tricks.", which really doesn't effectively answer the question. Commented Mar 1, 2016 at 15:55
  • 9
    @user3439894 Unfortunately, I'm not entirely sure what the details are. I think the biggest "trick" is hard links. When TM sees a file (or folder) that hasn't changed since the last backup, it doesn't store a new copy in the current backup, it uses a hard link to include the already-backed-up copy in the current backup folder. I'm pretty sure the AFP file sharing protocol doesn't support hard links. But since I'm not totally sure (and this may not be the only thing), I didn't want to include this in my answer. Commented Mar 1, 2016 at 20:13
  • Thank you! This is exactly what I was looking for. One thing though: You say that a sparse bundle image can be mounted on any OS X machine. While this may be because of my slow connection, I cannot mount the sparse bundle image. It just says, "Resource temporarily unavaible". Thanks!
    – Sam Magid
    Commented Mar 20, 2016 at 6:33
  • @SamMagid This error appears to be due to the image not being properly dismounted. I see a lot of discussion of it on the net, with a variety of possible solutions -- see this c|net article and this Apple Discussions thread. Commented Mar 20, 2016 at 6:47
  • 3
    @GordonDavisson, hard links is definitely the biggest thing. Specifically, hard links to directories, which are unsupported in other filesystems because they can create directory loops. Commented Jul 16, 2016 at 14:34

A Sparsebundle is a disk image format introduced by Apple in OSX 10.5 as a method of effectively using space for backups on a disk. This is an expandable/retractable disk that will only take up as much room as the data inside of it up to a predefined limit (in the case of TM, the size of the partition). This also allows for incremental backups in which parts of a file can be layered on top of one another so you can perform a revisional history instead of replacing a file with a full new copy each and every time.


As for why, Apple reserves the right to have their proprietary backup tool save data under whichever format they think would work best. As such, they developed their own. At this time, there is no way to make Time Machine use a different format - you will have to use a different backup utility to achieve that.

  • “In this case of TM, the size of the partition”. Sorry but Time Machine only stores a user’s files not an image of the disk or partitions on the disk. Just thought I’d point out, you kinda crossed over what you were saying. An example of the difference would be a DMG or other type of disk image including static VHDs that occupy a preallocated space whether it’s legitimately full or empty. Upvotes for everything else.
    – Tmanok
    Commented Oct 14, 2018 at 3:35
  • 1
    @Tmanok The reference was to .sparsebundle files and the amount of space they take up, not what they contain in a TM backup. In the case of Time Machine, the .sparsebundle's size limit is the size of the partition and will continuously grow until the partition is full. When creating one outside of TM, correct - they are dynamically sized up to a certain amount specified by the user.
    – smoooosher
    Commented Oct 19, 2018 at 5:59

I'm pretty sure Time Machine uses the .sparsebundle format only if you encrypt your backup.

You have two options if you want to be able to browse the contents of your backups. The first is to deselect the option to encrypt your backups. The second option, which I would recommend is to just double click on the .sparsebundle and let OS X mount it as a drive (you'll need the encryption password). That little bit of effort will get you what you want—you'll be able to browse the backups—without sacrificing security.

  • 1
    Encryption happens with FileVault whether you have a DAS volume (USB or direct connect drive) or NAS (network attached storage) like Time Capsule or a file share appliance or server. The sparse bundle format is for all NAS destinations regardless of encryption status.
    – bmike
    Commented Jul 16, 2016 at 14:05
  • 5
    This is false. I have an un-encrytped Time Machine backup going to NAS and it still uses the .sparsebundle format.
    – dmackerman
    Commented Jan 17, 2022 at 4:27

I formatted an external USB drive as APFS Encrypted format, then I ran Timemachine backup. This produced a single sparse bundle file image, which I didn't like.

I went back, reformatted the same USB drive as Mac OS Extended (Case-sensitive, Journaled, Encrypted) format and reran the Timemachine backup. This produced the Backups.backupdb browsable folder structure that I prefer.


This was hinted at in some other comments, but .sparsebundles can be mounted like a normal .dmg file, allowing you to browse the backups the way you used to. (Works on my macOS Catalina system.)

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .