File Extension Guide📖 What is an APP File?
An APP file is a Mac application, the kind of thing you double-click to launch a program like Safari or a game. The twist that catches almost everyone out is that a .app is not really a single file at all. It is a folder, quietly holding everything the program needs, that macOS chooses to show you as one neat icon.
This little sleight of hand is deliberate. Apple wanted apps to feel like a single object you can drag, drop and trash in one go, without the clutter of the dozens of pieces that actually make up a program. So the Finder, the part of macOS that shows your files, treats a folder whose name ends in .app as a sealed parcel. Double-click it and instead of opening the folder to show what is inside, your Mac launches the application waiting within. The proper name for this arrangement is an application bundle, and it is the standard way every Mac program is packaged.
Because of this design, a .app is best thought of as a self-contained box. Everything the program relies on, its actual code, its icons, its sounds and its settings, lives together inside that one bundle. That is why installing a Mac app is often as simple as dragging a single .app into your Applications folder, and why removing it can be as easy as dragging that same item to the Trash. Understanding that a .app is really a folder in disguise is the key to everything else about it, from how you peek inside one to why it will not run on a Windows PC.
Key Characteristics
- A macOS application you double-click to run
- Really a folder shown as one file
- Self-contained, holding all the app needs
- Drag to install, drag to Trash to remove
Good to Know
- Proper name is an application bundle
- Finder shows it as a sealed parcel
- Peek inside with Show Package Contents
- Will not run on Windows
⚡ Quick Facts
| File Extension | .app |
| What It Is | A macOS application bundle |
| Really | A folder shown as a single file |
| Platform | macOS (Apple) |
| To Run It | Double-click in Finder |
| To Look Inside | Right-click, Show Package Contents |
| Runs On Windows | No, it is Mac software |
| Key Inner File | Info.plist |
📦 A Folder Shown as a File
The idea that a single icon is secretly a folder full of parts is the heart of what a .app is, so it is worth seeing exactly how the trick works and why Apple bothered.
On a Mac, the Finder is told to treat certain folders as packages, meaning it hides their inner workings and presents them as one object. A folder whose name ends in .app is the best known example, but the same idea appears elsewhere, since some documents saved by Apple programs are also folders dressed up as single files. The reason is tidiness and safety. A modern program is not one lump of code but a collection of many pieces, and shuffling those around by accident would break it. By sealing them inside a package, macOS lets you handle a complex app as easily as a single photo, while quietly protecting its parts from stray clicks and drags. The result is the experience Mac users take for granted, where an application is just one thing you move, launch or delete, even though a small world of files is bundled up inside.
🔍 What is Inside a .app?
Open up an application bundle and you find a small, orderly structure rather than a jumble, because every Mac app follows the same basic layout. Knowing the main parts makes it clear how the whole thing hangs together.
At the top sits a single folder named Contents, and everything else lives within it. Inside Contents is a folder called MacOS, which holds the app's actual executable, the real program code that runs the moment you launch it. Beside it is a Resources folder, the app's storeroom, filled with supporting material like icons, images, sounds, fonts and translations into other languages. A small but important file named Info.plist acts as the app's identity card, listing details such as its name, version and the settings macOS needs to launch it correctly. There is also a piece called the code signature, tucked in its own folder, which lets your Mac check the app has not been tampered with since its maker released it. Larger apps add more, such as a Frameworks folder for shared code libraries or a Plugins folder for optional add-ons, but the core is always the same, an executable to run, resources to draw on and an Info.plist to describe it all.
Inside a typical application bundle
MyApp.app (looks like one file, is really this folder) Contents/ Info.plist the app's identity and settings MacOS/ the executable, the code that runs Resources/ icons, images, sounds, languages _CodeSignature/ proof the app is untampered
🗂️ How to Show Package Contents
Since a .app is a folder in disguise, macOS gives you a way to lift the lid and look inside, which is handy for curiosity or for retrieving a resource, as long as you tread carefully.
To peek within an app, find it in the Finder, hold Control and click it, or right-click if your mouse allows, and choose Show Package Contents from the menu that appears. The bundle then opens like an ordinary folder, letting you browse the Contents folder and everything nested inside it. People do this to grab an icon or an image from the Resources folder, to read documentation a developer left in there, or simply to see how an app is built. The one firm rule is to look but not touch. Moving, renaming or deleting anything within a bundle can stop the app working, and worse, it can break the code signature that macOS relies on to trust the app, after which your Mac may refuse to open it at all. If you want to keep a file you find inside, copy it out rather than dragging the original, and leave the bundle itself exactly as it was.
🖱️ How to Open an APP File
Opening an APP file usually means one of two things, either running the program or looking inside it, and on a Mac both are simple once you know which you want.
To run the application, just double-click the .app in the Finder and macOS launches it, exactly as you would expect of any Mac program. The first time you open an app downloaded from outside the App Store, your Mac may pause to check it is safe, and you can give permission through a prompt or through the Privacy and Security settings. If instead you want to explore the bundle, use the Control-click and Show Package Contents route rather than a double-click, since double-clicking will only launch the app. You can also reach a .app from the Terminal, treating it as the folder it truly is, which developers sometimes do to run an app with particular options. For most people, though, opening an APP file simply means double-clicking it to start the program, which is the whole point of the tidy single-icon design.
🪟 APP Files on Windows and Linux
A common disappointment is downloading a Mac app onto a Windows or Linux machine and finding it will not run, so it helps to know what you can and cannot do with a .app away from a Mac.
The blunt truth is that a macOS application cannot run on Windows or Linux, because the program inside is built specifically for Apple's system and speaks a language those other systems do not understand. On Windows or Linux a .app does not even appear as a single app, it shows up as an ordinary folder, since only the Mac's Finder performs the trick of sealing it into one icon. You can open that folder and browse its parts, and an archive tool such as WinRAR can sometimes pull individual files out of it, which is occasionally useful for extracting an image or reading a text file within. What you cannot do is make the program itself run. If you genuinely need to use a Mac app on a PC, the only real routes are to run macOS in a virtual machine or to find a version of the software built for Windows, since the .app you have will stay inert on anything but a Mac.
📥 .app vs .dmg vs .pkg
When you download Mac software you often meet a .dmg or a .pkg rather than a .app straight away, and it helps to know how these three relate, because only one of them is the actual program.
The .app is the application itself, the thing that ends up in your Applications folder and that you launch. A .dmg and a .pkg are just two ways of delivering that .app to you. A .dmg is a disk image, a kind of virtual disk that mounts on your desktop when you double-click it, usually showing a window that invites you to drag the .app into your Applications folder. A .pkg is an installer package that runs a guided set-up instead, placing files where macOS needs them, which suits software that has to weave itself more deeply into the system. In both cases the goal is the same, to get a working .app onto your Mac, and once that is done the .dmg or .pkg has served its purpose. That is why you can usually delete the downloaded disk image or installer afterwards, since the app is now living safely in your Applications folder.
| Format | What it is | How you use it | Keep it? |
|---|---|---|---|
| .app | The application itself | Double-click to run | Yes, this is the program |
| .dmg | A disk image wrapper | Mount, drag app to Applications | Delete after installing |
| .pkg | An installer package | Run the guided installer | Delete after installing |
🛠️ "App Is Damaged and Can't Be Opened"
One of the most common scares with a .app is a message saying it is damaged and cannot be opened, or that it should be moved to the Trash. It sounds alarming but the file is usually fine, and knowing the real cause makes it easy to handle.
Despite the wording, this is almost never actual damage. It is Gatekeeper, the Mac's app-safety check, refusing to run an app it cannot verify, most often because the app was downloaded from outside the App Store and has not been notarised by Apple. macOS marks downloaded apps with a quarantine flag and blocks anything it cannot confirm as trusted, and newer versions of macOS enforce this more strictly, so an app that once opened may suddenly be blocked. The safe fix, when you genuinely trust the app, is to right-click it and choose Open rather than double-clicking, which gives you a one-time option to run it anyway, or to visit System Settings, open Privacy and Security, and use the Open Anyway button that appears there after a blocked attempt. Getting a fresh copy from the developer's official site or the App Store often clears it too, since a clean download arrives properly signed. The one rule to hold onto is trust, since these checks exist to stop harmful software, so only override the warning for an app whose source you are sure of, and if you cannot vouch for it, move it to the Trash as macOS suggests.
🔒 Are APP Files Safe?
Because a .app is a program that runs on your Mac, it is fair to ask whether opening one is safe, and the honest answer is that it depends entirely on where the app came from.
An application from the Mac App Store or from a maker you trust is safe, and running it is an everyday act no different from using any program. The caution is the same as with any software, since a .app downloaded from an unknown website could in principle contain something harmful, exactly as a program could on any system. Apple builds in real protection here. A feature called Gatekeeper checks apps before they run, favouring those that Apple has notarised, which means scanned and approved, and warning you before opening anything unsigned or from an unidentified developer. That warning is worth heeding rather than clicking past. The sensible habits are the familiar ones, get your apps from the App Store or the developer's official site, pay attention when your Mac flags something as unverified, and be wary of an app that arrives from an unexpected email or a dubious download. Treated that way, APP files are a safe and normal part of using a Mac.
❓ Frequently Asked Questions
An APP file is a macOS application, the kind of program you double-click to run on a Mac. The surprising part is that a .app is not really a single file, it is a folder that macOS shows as one icon. Apple designed it this way so an app feels like a single object you can drag, drop and delete in one go, even though a whole collection of files is bundled up inside. The proper name for this is an application bundle. When you double-click a .app, your Mac does not open the folder to show its contents, it launches the application waiting within. That is why a .app is best pictured as a self-contained box holding everything the program needs, from its code to its icons and settings.
On a Mac, opening an APP file to run it is as simple as double-clicking it in the Finder, which launches the program just like any other Mac application. The first time you open an app downloaded from outside the App Store, your Mac may pause to check it is safe, and you can allow it through the prompt or the Privacy and Security settings. If instead you want to look inside the bundle rather than run it, hold Control and click the app, then choose Show Package Contents, since a plain double-click will only launch it. Developers can also open a .app from the Terminal, treating it as the folder it really is. For most people, though, opening an APP file just means double-clicking it to start the program.
A .app is a folder because a modern program is not one lump of code but a collection of many pieces, the executable, icons, sounds, settings and more. Rather than scatter these across your disk, macOS gathers them into a single folder and then tells the Finder to treat that folder as a sealed package, showing it as one icon. This gives you the best of both worlds, the program stays neatly organised inside while feeling like a single object you can move, launch or trash in one action. It also protects the app, since hiding its parts inside a package makes it far less likely you will drag or delete something by accident and break the program. So the folder is real, macOS simply chooses to present it as a single file.
To look inside a .app on a Mac, find it in the Finder, hold Control and click it, or right-click, and choose Show Package Contents from the menu. The bundle then opens like a normal folder so you can browse the Contents folder and everything within it. People do this to grab an icon or image from the Resources folder, to find documentation a developer left inside, or just to see how the app is built. The important rule is to look but not touch. Moving, renaming or deleting anything inside can stop the app working and can break its code signature, after which your Mac may refuse to open it. If you want to keep something you find, copy it out rather than moving the original.
No, a macOS application cannot run on Windows, because the program inside is built specifically for Apple's system and Windows does not understand it. On a Windows PC a .app does not even show as a single app, it appears as an ordinary folder, since only the Mac's Finder seals it into one icon. You can open that folder and browse its parts, and an archive tool such as WinRAR can sometimes extract individual files from it, but you cannot make the actual program run. If you need to use the software on a PC, your only real options are to run macOS inside a virtual machine or to find a version of the program that was built for Windows. The .app itself will stay inert on anything that is not a Mac.
Whether a .app is safe depends on where it came from. An app from the Mac App Store or a developer you trust is safe, and running it is an everyday act. A .app from an unknown website could in principle contain something harmful, just as any program could on any system. Apple builds in protection through a feature called Gatekeeper, which checks apps before they run, favours those Apple has notarised, and warns you before opening anything unsigned or from an unidentified developer. That warning is worth heeding. The sensible habits are the usual ones, get apps from the App Store or the developer's official site, take notice when your Mac flags something as unverified, and be wary of an app arriving from an unexpected email or a dubious download.
The Info.plist is a small but essential file inside every application bundle, acting as the app's identity card. It is a property list, a kind of structured settings file, and it tells macOS the key facts it needs to handle the app, such as its name, its version number, which file inside is the executable to launch, which icon to show, and what permissions the app requests. When you double-click a .app, macOS reads this file first to work out how to start the program correctly. You will find it in the Contents folder if you use Show Package Contents to look inside. As with everything else in the bundle, you should leave it alone, because altering it can confuse macOS about how to start the app.
Despite the wording, the app is almost never actually damaged. The message comes from Gatekeeper, the Mac's app-safety check, refusing to run an app it cannot verify, usually because the app was downloaded from outside the App Store and has not been notarised by Apple. macOS tags downloaded apps with a quarantine marker and blocks anything it cannot confirm as trusted, and newer macOS versions do this more strictly, so an app that used to open can suddenly be blocked. If you trust the app, the safe fix is to right-click it and choose Open rather than double-clicking, which offers a one-time run, or to use the Open Anyway button under System Settings, Privacy and Security. Re-downloading a fresh copy from the official source often clears it too. Only override the warning for an app whose source you trust.
A .app is the actual application, the program that lives in your Applications folder and that you launch. A .dmg is a disk image, a virtual disk used only to deliver that app to you. When you double-click a .dmg it mounts on your desktop and usually shows a window inviting you to drag the .app into your Applications folder. So the .dmg is just the packaging, while the .app is what you keep and use. Once you have dragged the app across and it is installed, the .dmg has done its job and can be deleted to free up space. A .pkg works similarly but runs a guided installer instead of a drag-and-drop window, and it too can be removed once the app is in place.
For most apps, uninstalling is as simple as dragging the .app from your Applications folder to the Trash and then emptying it, since the bundle holds nearly everything the app needs. Apps installed from the Mac App Store can also be removed from Launchpad. The one loose end is that some apps leave behind small support files, such as preferences and caches, tucked away in your Library folder. These are usually harmless and take little space, but if you want a thorough clean-up you can remove them too, or use a dedicated uninstaller tool that finds the leftovers for you. For an app that came with its own uninstaller, running that is the tidiest route. In short, trash the .app for a quick removal, and clear the Library leftovers as well if you want nothing left behind.
Yes, and there are a few routes depending on how far you want to go. Developers build a proper .app using Apple's Xcode, which compiles their code and assembles the whole bundle, complete with an executable, resources and an Info.plist. If you just want to wrap a script or a simple task into something double-clickable, the built-in Automator app can save a workflow as an application, and third-party tools can turn a shell script into a basic .app as well. Because a .app is really just a folder with a set structure, it is possible to assemble one by hand too, though that is fiddly and best left to those who enjoy tinkering. For most people the practical answer is Automator for simple jobs and Xcode for real software.
The Terminal treats a .app as the folder it really is, and offers a simple command to launch it. Using the open command followed by the path to the app starts it just as a double-click would, while open with a name flag lets you launch an installed app by name. This is handy when you want to start an app from a script, pass it particular options, or open it on a Mac you are controlling remotely. Because the Terminal sees the true structure, you can also navigate inside the bundle as an ordinary folder to inspect its parts, which developers do when troubleshooting. For everyday launching, though, the Finder double-click is simpler, and the Terminal route is mainly useful for automation or when you need the extra control it allows.
A .app is not a virus in itself, it is simply the standard form every Mac program takes, and the overwhelming majority are perfectly safe. Because it is a program that runs on your Mac, though, a malicious one could in principle be disguised as an ordinary app, which is exactly why where it came from matters so much. Apps from the Mac App Store are checked by Apple, and those from known developers are usually signed and notarised, meaning Apple has scanned them. The warning signs to watch are an app that arrived from an unexpected email, a dubious download site, or one your Mac flags as being from an unidentified developer. If you stick to the App Store and official developer sites, heed Gatekeeper's warnings, and avoid running apps you cannot vouch for, a .app is a safe and normal part of using a Mac.
📝 Summary
An APP file is a macOS application bundle, the program you double-click to run on a Mac, shown by the .app extension. What sets it apart is that it is not really a single file but a folder that the Finder shows as one icon, a deliberate design that lets an app feel like a single object you can drag to install or trash to remove while a whole collection of files sits bundled inside. Open one up and you find an orderly structure, a top-level Contents folder holding a MacOS folder with the executable code that runs when you launch the app, a Resources folder of icons, sounds and languages, an Info.plist file that acts as the app's identity card listing its name, version and settings, and a code signature that lets macOS confirm the app has not been tampered with. You look inside by holding Control, clicking the app and choosing Show Package Contents, which opens the bundle like a folder, though the firm rule is to look but not touch, since moving or changing anything within can break the app and its signature. To run a .app you simply double-click it, allowing Gatekeeper to check an app from outside the App Store the first time. A macOS application will not run on Windows or Linux, where it appears merely as a folder you can browse but not launch, so using Mac software on a PC means either running macOS in a virtual machine or finding a Windows build. As for safety, a .app from the App Store or a trusted developer is perfectly safe, the care being reserved for apps from unknown sources, where heeding your Mac's Gatekeeper warnings keeps you on solid ground.