Zip mac os x folder

This built-in system is fairly basic, which is why so many third-party apps are also available. A quick look at the Mac App Store revealed over 50 apps for zipping and unzipping files. Below are instructions that show you how to compress and decompress files and folders using the zipping tool built into the Mac.

It's a basic tool, but it gets the job done. But don't bother to look for it in the Applications folder; it's not there. Apple hides the app because it's considered a core service of the OS. Apple and app developers can use core services to enhance an application's capabilities. The Archive Utility had a number of settings that could be modified and you can try making changes some time later.

Right now it is a better idea to get use to the utility as configured in its default state, you can always try new settings later on. The Archive Utility may be hidden away, but that doesn't mean you can't access its services. Apple makes zipping and unzipping files and folders extremely easy by allowing the Finder to access and use the Archive Utility app. The name of the item you select will appear after the word Compress, so the actual menu item will read Compress "item name.

The Archive Utility will zip the selected file; a progress bar will display while the compression is occurring. The original file or folder will be left intact. You'll find the compressed version in the same folder as the original or on the desktop, if that's where the file or folder is located , with. Compressing multiple files and folders works just about the same as compressing a single item. The only real differences are in the names of the items that appear in the pop-up menu, and the name of the zip file that is created. Select the items you want to include in the zip file.

You can command-click to select non-adjacent items. This time, the word Compress will be followed by the number of items you have selected, such as Compress 5 Items. Once again, a progress bar will display.

Unzip from the Finder

When the compression is finished, the items will be stored in a file called Archive. Explanation of resource fork at Wikipedia. People produce data, wrap it up, store it on different mediums and so on. They need to know what is needed or what is not needed. Hiding it keeps them in the dark. The age old bad idea of hiding things from users: A programmer, concerned with expediency of accomplishing his own work, abuses something in the domain of the end user, to make it easy for himself.

In this case he stored meta data in the user's data space, he then hid it from the user. He missed the big picture: The user won't become aware of the hidden details.

When he packages his data and ships it somewhere unanticipated by the programmer, missing parts won't get shipped or unknown parts will arrive which neither the user nor the recipient can explain. Hiding things from the user is bad. It assumes the user is stupid, when more accurately it is the programmer being stupid, or lazy. To be clear, this bad habit is not confined to MAC.

It is everywhere. It's a consequence of programmers falling in love with their own schemes and vendors prioritizing their own goals ahead of the needs of the end user. Programmers and vendors: Please keep things in the open. When you hide them, you make yourself stupid and the user uninformed. Mac OS X users can install a 3rd-party archiving utility like Keka , then tell it to not use Resource Forks, then set it as the default compressor.

• Zip for Mac: Zip & Unzip Files with Winzip Mac Edition?
• How to compress folders on a mac without DS_Store files - .
• intel compiler for mac os x.

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service , privacy policy and cookie policy , and that your continued use of the website is subject to these policies. Home Questions Tags Users Unanswered. Ask Question. Yada Yada 3 7 They are super-irritating, yes, and usually pointless as the resource forks are so often empty.

And hey, it could be worse, it could be storing two copies of each file with the same name, one for the data and one for the resource fork, often making it impossible to access either, like pre-OSX Mac used to. Oh Apple, why do you hate standard file formats? These days, the same effect is achieved by storing resources as individual files, most of which look pretty much like standard file formats. Nothing wrong with metadata as such, it's just that Apple have such a knack of making up their own formats and messing up existing formats with gratuitously incompatible extensions!

Having the content-type data as metadata is in itself a great thing and it saddens me that OS X is moving towards the Windows hack of file extensions as an alternative. Sigh, OSes eh? But yes, at least the format they made up for this does not do any real harm, other than slightly cluttering directory listings and wasting essentially 1 inode and 1 block per empty resource fork extracted, unless you use something like NTFS which will store the file contents in the MFT for such small files , in which case it just wastes the "inode" MFT entry.

Can be fixed after the fact by zip -d filename. It's not just resource forks, anything beyond basic file contents gets put in the AppleDouble file. Apple's moving away from resource forks, but toward things like extended attributes that'll also get stored in the AppleDouble container. You make it sound like a feature. If you want metadata, use a different format, not a Mac. Just discovered:

1. How to Zip Files in Mac OS X;
2. microsoft office 2010 for mac with crack!
3. Compress files & folder in the Terminal Command Line in macOS Sierra?
4. How to Zip and Unzip Files and Folders on a Mac;
5. mac mini i5 2.5 review;