Why is Time Machine backing up to .sparsebundle file? 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?
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.