7z your Mac opens. rar it will not.

what your Mac opens by itself: zip, 7z and tar

Archive Utility is built in and has no window of its own — it runs when you double-click a file it recognises, unpacks beside the original and quits. no app to install and nothing to configure.

• zip — double-click, done. the same app makes them: select files in Finder, right-click, «Compress».
• 7z — also double-click. this surprises people, and half the pages ranking for it are still selling an app for the job.
• tar, tar.gz, tar.bz2, tar.xz and gz — all handled, including the two-step ones where the archive is compressed and then bundled.
• dmg — not an archive at all but a disk image, which is why it mounts instead of unpacking.

the .dmg files in that list are worth a separate thought: they are installers, they are never cleaned up, and they are a routine double-digit share of a full disk — what «system data» is actually using

Apple documents the zip half of this and stops there, which is a fair part of why the rest is so widely misreported: zip and unzip files and folders on Mac

does macOS open 7z natively?

yes, and it has for years. Archive Utility declares the 7-zip type as one it handles, and the system lists it as the default application for it — you can see the claim yourself in the Launch Services database. a .7z on your Desktop opens on a double-click with nothing installed.

the command line goes further than the Finder does. macOS ships bsdtar, and its manual page lists 7-zip in both directions: it reads the format and it writes it. so `tar -xf archive.7z` unpacks one, and `tar -c --format=7zip -f out.7z -C folder .` makes one — no app, no helper, no download.

does Terminal open rar?

mostly, and almost nobody mentions it. the same bsdtar is built on libarchive, and libarchive reads rar — so `tar -xf archive.rar` unpacks a great many of them straight from a Terminal window, with nothing installed and nothing downloaded.

the support is documented as limited, and the limits are worth knowing before you rely on it: RARv3 archives read, including self-extracting ones; solid archives — the ones made with WinRAR's «create solid archive» — do not, and neither do encrypted ones. you find out immediately, because it stops and says so rather than producing a broken folder.

the exact scope of that support is in the manual page that ships with your Mac, `man 5 libarchive-formats`, and in the project's own table: libarchive: formats read and written

what none of this gives you is a double-click. there is no Finder handler for rar, so the file has no icon of its own, opens in a text editor if you insist, and cannot be unpacked without a trip to the Terminal. that is the actual gap — not the one the product pages describe.

and when you make a zip on a Mac to send onward, it carries a folder of Apple metadata that confuses everyone on the other end: what __MACOSX in a zip is

opening rar with an archive manager, and what it costs

every result you will find for this recommends an archive manager, and any of them will unpack your file. the part nobody mentions on the way in is what installing one changes about your Finder.

an archive manager wants to become the default app for archives — usually all of them, not just the format you were missing. from then on zip and 7z go through it too, opening its window and its progress bar for a job macOS was already doing silently. that is a lot of app for one file a colleague sent you.

open rar files without downloading any software

the other popular answer is a web unpacker: drag the archive into a page, download the contents back. it works, and the price is that the archive goes to somebody else's server and is unpacked there.

for a game mod that is nothing. for anything with a document in it, that is the whole decision, and no privacy page changes the arithmetic — you have handed over the file. the Terminal route above does the same job on your own machine, and for one archive it is genuinely faster than the upload.

the same question comes up about where a Mac app is downloaded from at all, and the answer is less obvious than it looks: the App Store version versus the one from the site

how hop opens rar and 7z

hop's archives module opens a window you drop things into — ⌘V works too, and several files at once. what you add waits in a list until you press the button, so a stray drop costs nothing. archives are unpacked; ordinary files dropped in are packed into one archive instead.

rar and 7z need code macOS does not expose to applications, so hop fetches a small signature-verified helper (~6 mb) the first time one of those turns up — once, not per file. everything else works out of the box.

• covered: zip, rar, 7z, tar, tar.gz, tar.bz2, tar.xz and gz.
• the result lands on the Desktop by default — or next to the original, or in any folder you pick.
• hop unpacks rar and never creates it: the format is proprietary, and an app that offers to make one is offering something it cannot legally do properly.
• a failed job leaves nothing behind — no half-unpacked folder to find and delete later.

what it adds over the Terminal route

two things, and neither is «it unpacks rar» — you already have that. the first is the double-click: hop's settings offer to take rar only when no Apple app owns it, and can take it back from a third-party manager you installed once. zip, 7z and the native formats stay with Archive Utility. turn it on and a rar unpacks in Finder beside itself in a small progress window, which is the Archive Utility behaviour extended to the one format that lacks it.

the second is the archives `tar` refuses. a solid rar and an encrypted rar are exactly the cases where the built-in route stops, and they are not rare — they are what you get from anyone who packed a large folder with WinRAR's defaults.

the module also works with its row hidden from the panel, so if the only thing you ever want is that Finder double-click, nothing has to sit in your way.

the module in full — what it packs, where results land, and how the Finder default is handled: archives on the features page

on never creating rar: the format's own licence forbids using its source to re-create the compressor, which is why no honest tool on any platform offers it — the unrar licence

when it still will not open

the rar file opens in TextEdit

that is the missing handler, not a broken archive: with nothing claiming the type, the Finder hands the file to whatever will take it. the file is fine — open it from the Terminal, or give the type to something that understands it.

«can't open rar as archive»

• the archive is in parts — part1.rar, part2.rar, or .z01, .z02 next to a .zip. open the first part with the rest sitting beside it in the same folder; opening part two on its own fails no matter what you use.
• it is solid, or encrypted. that is where the built-in route stops by design — see above — and it is the most common reason `tar -xf` refuses a file that a manager opens fine.
• the download is truncated. an archive that stops mid-file reports damage rather than a missing format — check the size against what the page promised before blaming the app.
• it asks for a password you do not have. encrypted rar and 7z hide the file names too, which is why you sometimes cannot even see what is inside.
• the extension lies. a file named .rar that is really a zip, or the reverse, happens with things generated on a server; the format is read from the contents, so a rename fixes nothing and is not the problem either.

if a manager you installed years ago is still holding your archives and you want it gone properly: uninstall an app with its leftovers

and if it refuses to go at all, that is a different problem with its own five causes: an app that will not delete

frequently asked questions

why can't my Mac open rar files?

there is no handler for the type. rar is a proprietary format owned by its author, and while the code to read it is present in the system libraries, nothing in the Finder claims the file — so a double-click hands it to a text editor instead of reporting an error.

does macOS open 7z natively?

yes. Archive Utility declares the 7-zip type and the system lists it as the default for it, so a .7z opens on a double-click with nothing installed. most pages ranking for this question say otherwise.

does Terminal do it?

for zip, tar and 7z, yes. for rar, mostly: `tar -xf archive.rar` reads a great many of them through libarchive. what it will not do is solid archives and encrypted ones, and it tells you rather than failing quietly.

can i open a rar without installing anything?

from the Terminal, usually yes. in the Finder, no — there is no handler, and nothing you can switch on adds one.

should i use an online rar extractor?

only for something you would be happy to email to a stranger. the archive is uploaded and unpacked on someone else's machine; the Terminal command does the same work on yours, faster than the upload for a single file.

can hop create rar archives?

no, and no honest tool on macOS can — the format's licence forbids using its source to re-create the compressor. hop packs into zip and 7z and leaves the making of rar to the format's owner.

will hop take over my zip files?

not unless you ask. its default-app setting offers rar when no Apple app owns it — zip, 7z, tar and the rest stay with Archive Utility, and the card shows the real state, so it cannot claim a default that Finder has actually given to something else.

the tool behind this

done with file archives

other things people do

• «unable to expand». what error 79 and error 1 are telling you.archives
• your Mac has a speed test. it has no window.speed test
• the pdf is 40 mb and the form accepts 10file converter