[Hg2491]

As the title says.

TIA,
Hg +

[Cold Warrior]

sparse expands itself to fit your data. You can compact it using this method: macosxhints.com - Compact sparse disk images via the command line

[Hg2491]

Thank you very much...

[Cold Warrior]

No problem. It only took me 2 edits to fix spelling and a small error. Time for bed!

[CharlesS]

The thing about SPARSE images, though, is that they tend not to be as reliable as fixed-size disk images, and are easier to corrupt.

[zro]

Any time I've tried to overfill a sparse image the Finder won't let me.

[reader50]

A sparse image means only the used space is actually allocated on disk.

Example: create a 40 MB image, and specify a sparse image type. The image file will be created, and the image mounted. The mounted image will show 40 MB size, with about 10 used - mostly by the journal. Now check the image file, it will be 10 MB in size.

As you add files, the image will fill up. The image file will always be the largest size the image gets used to. ie - fill the image to 35 MB, then delete some files back down to 20 MB. The image file will reach 35 MB, and stay there. If you ever fill the image all the way to 40 MB, then the image file will finally reach 40 MB - the entire image space will be allocated on disk.

[Aegis]

Ah, I had misunderstood this as well. I thought sparse would infinitely expand as needed. Thanks for clearing that up.

[zro]

Ah, gotcha. Never paid much attention. I always figured that's how a regular dmg behaved.