How to Find Hidden Files on Mac: A Complete Guide

MacOS hides certain files and folders by default — not to be difficult, but to protect you from accidentally modifying or deleting system-critical data. If you're troubleshooting an app, managing storage, or working with development tools, knowing how to surface those hidden files is an essential skill.

Why Does Mac Hide Files in the First Place?

Apple deliberately conceals files that fall into a few broad categories:

• System files — core macOS components that, if deleted, can break your operating system
• Library folders — app preferences, caches, and support files tucked away from everyday view
• Dot files — files whose names begin with a period (.), a Unix convention for configuration files like .bash_profile or .zshrc
• Application bundles — package files that appear as a single icon but contain entire folder structures underneath

Most users will never need to see these. But for developers, power users, and anyone digging into disk usage or app behavior, they matter.

Method 1: The Keyboard Shortcut in Finder 🔍

The fastest way to reveal hidden files in any Finder window:

1. Open Finder
2. Navigate to the folder you want to inspect
3. Press Command + Shift + . (period)

Hidden files and folders will immediately appear, shown in a slightly greyed-out state to distinguish them from visible items. Press the same shortcut again to hide them.

This toggle works in any Finder location — your Home folder, Desktop, external drives, or anywhere else. It's temporary and non-destructive: you're just changing what's visible, not modifying the files themselves.

Method 2: Using Terminal to Show Hidden Files System-Wide

If you want hidden files to stay visible persistently across all Finder windows, Terminal gives you that control.

Open Terminal (found in Applications → Utilities) and type:

defaults write com.apple.finder AppleShowAllFiles TRUE killall Finder 

Finder will restart and hidden files will remain visible until you reverse it with:

defaults write com.apple.finder AppleShowAllFiles FALSE killall Finder 

This approach is useful for developers or anyone who regularly works with configuration files and doesn't want to re-toggle visibility constantly.

Method 3: Accessing the Hidden Library Folder Directly

The ~/Library folder (your user Library, distinct from the system-level one) is hidden by default and contains app preferences, saved states, caches, and support files. It's one of the most commonly needed hidden locations.

To access it without enabling all hidden files:

• Open Finder
• Click the Go menu in the menu bar
• Hold down the Option key — Library will appear in the dropdown
• Click Library

Alternatively, use Go → Go to Folder (Command + Shift + G) and type ~/Library to navigate there directly.

Method 4: Go to Folder for Specific Hidden Paths

The Go to Folder dialog (Command + Shift + G in Finder) lets you jump directly to any path — including hidden ones — without making all hidden files visible globally.

Common hidden paths worth knowing:

This method is precise — you're navigating to exactly what you need without exposing everything else.

Method 5: Using Terminal to List Hidden Files

If you're comfortable with the command line, ls with the right flags gives you detailed visibility:

ls -la ~/ 

The -a flag shows all files including dot files. The -l flag displays them in a detailed list format showing permissions, size, and modification date. This is particularly useful when looking for hidden configuration files in your Home directory.

What You Might Find — and What to Be Careful With 🛑

When hidden files become visible, you'll encounter:

• Dot files like .DS_Store (Finder metadata), .gitignore, or .env files
• System directories like /private, /usr, or /var
• App internals — right-clicking an app and selecting Show Package Contents reveals the file structure inside .app bundles

The important distinction: visibility doesn't equal safety to edit. Seeing a file and knowing what it does are two different things. System-level hidden files exist for a reason, and modifying or deleting the wrong one can cause application errors or, in more serious cases, OS instability.

For Library files, caches are generally safe to clear (apps will rebuild them). Preference files inside ~/Library/Preferences are more sensitive — changes there affect how specific apps behave.

The Variables That Shape Your Approach

Which method makes the most sense depends on factors specific to your situation:

• How often you need access — occasional access favors the keyboard shortcut or Go to Folder; regular access may warrant the Terminal toggle
• Technical comfort level — Finder-based methods require no command-line knowledge; Terminal methods are more powerful but demand more care
• macOS version — the keyboard shortcut and Terminal commands have been consistent across recent macOS versions, but interface locations can shift between major releases
• What you're actually looking for — a developer managing dot files has different needs than someone trying to free up disk space by clearing caches

The right combination of methods depends on what you're trying to accomplish and how comfortable you are navigating the file system once those hidden layers become visible.