How to Show Hidden Files on Mac: The Complete 2026 Guide
· how to show hidden files on mac, macos hidden files, finder tips, terminal commands, mac maintenance
Most advice on how to show hidden files on Mac stops too early. It gives you the Finder shortcut, you press it, hidden files appear, and that seems like the whole story.
It isn't. On macOS, seeing a hidden file and changing whether that file is hidden are two different things. If you miss that distinction, you'll run into the classic problem: a folder shows up, then later seems to disappear again, and you assume Finder is broken. Usually it isn't. You just used a temporary visibility toggle when you needed a permanent file-state change.
That difference matters most when you're cleaning up app leftovers in ~/Library, checking config files, or trying to make one specific folder stay visible for later work.
Table of Contents
- Why Most Guides on Hidden Files Are Incomplete
- What Are Hidden Files and Why Does macOS Use Them
- The Keyboard Shortcut The Fastest Way to Peek
- Using Terminal for a Persistent View
- Advanced Methods for Control and Cleanup
- Frequently Asked Questions About Hidden Files
Why Most Guides on Hidden Files Are Incomplete
The common advice is simple: press Command + Shift + . in Finder and hidden files appear. That's useful, but it's only half the answer.
The missing piece is that Finder visibility is not the same thing as file metadata. Apple Community discussions highlighted in GraphPad's hidden file FAQ point out that many beginner guides only cover Finder toggles. Those toggles reveal items temporarily, but they don't alter a file's hidden status. If you want a file to stay visible, you need a different approach, such as chflags nohidden or renaming dotfiles.
Temporary visibility and permanent change are different jobs
Think of the Finder shortcut as lifting a curtain. The files were already there. You're only telling Finder to display them for the moment.
Changing a file with chflags nohidden is different. That changes the file or folder's hidden flag so it no longer depends on Finder's temporary display state. If you're trying to keep one folder visible for repeated access, the shortcut alone won't solve the problem.
Practical rule: Use the Finder shortcut for inspection. Use
chflags nohiddenwhen you want one specific item to remain visible.
People often get tripped up during app cleanup. They open ~/Library, remove a few support files, close the window, come back later, and assume macOS "hid everything again." Usually they only toggled Finder's view.
What actually works for real tasks
Use the method that matches the job:
- Quick check in Finder: Use the keyboard shortcut.
- Always show hidden items in Finder: Use the Finder preference change in Terminal.
- Keep one item permanently visible: Use
chflags nohidden. - Open your user Library quickly: Use Finder's Go menu with the Option key.
If you separate those use cases, hidden files stop being confusing. They're just another part of macOS that needs the right tool.
What Are Hidden Files and Why Does macOS Use Them
macOS hides files for a reason. In most cases, the system is trying to protect settings, reduce clutter, or keep application internals out of the way until you need them.
That doesn't mean hidden files are mysterious. It means they usually aren't meant for casual editing.
Three kinds of hidden items you'll run into
Most Mac users eventually encounter three broad categories.
- Dotfiles like
.zshrcor.gitignore. These start with a period. They usually store configuration for shells, tools, and developer workflows. - System-protected files and folders that macOS doesn't want users modifying casually. These exist to keep the operating system stable.
- Application data and caches, often stored in places like
~/Library. There, app preferences, containers, logs, support files, and cache data tend to live.
If you're uninstalling apps manually, the third category is the one you'll touch most often. That's where leftover support files and caches tend to remain after the app itself is gone.
The safety rule that matters
Hidden doesn't mean dangerous. It means handle with intent.
A good rule is simple:
| Type of hidden item | Typical use | Risk level if edited casually |
|---|---|---|
| Dotfiles | User or tool configuration | Moderate |
| System-protected files | Core macOS behavior | High |
App data in ~/Library | Preferences, caches, support files | Varies |
Look first. Delete later. If you can't identify what a hidden file belongs to, leave it alone.
When people get into trouble, it usually isn't because they revealed hidden files. It's because they started deleting broad groups of files they didn't recognize. App leftovers are a fair target when you know which app created them. Random hidden system folders are not.
The Keyboard Shortcut The Fastest Way to Peek
The fastest answer to how to show hidden files on Mac is still the best one. In Finder, press Command + Shift + .
Mac-focused guides consistently treat this as the quickest built-in method. MacSales' Sonoma and Ventura walkthrough describes it as the fastest way to toggle hidden files in Finder, and notes that revealed items appear translucent. That visual cue is useful because it reminds you these aren't normal Finder items in the current view state.
How to use the Finder toggle
This method is straightforward:
- Open Finder.
- Go to the folder you want to inspect.
- Press Command + Shift + .
- Look for newly visible files and folders, often shown as translucent.
- Press the same shortcut again to hide them.
That translucency matters more than it seems. It tells you Finder is showing hidden content without changing the underlying file status.
When this method is the right one
The Finder shortcut is ideal when you need a fast peek and nothing more.
Use it when you want to:
- Check for leftover app support files inside
~/Library - Inspect dotfiles in your home folder
- Confirm a folder exists before using Terminal
- Avoid changing system-wide settings just to look around once
It isn't the best method if you work with hidden files constantly. Repeatedly toggling Finder gets old fast, especially if you're moving between folders during cleanup or troubleshooting.
A quick visual walkthrough helps if you want to see the shortcut in action:
<iframe width="100%" style="aspect-ratio: 16 / 9;" src="https://www.youtube.com/embed/8HvedBfa7S0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>Revealing hidden files in Finder is a viewing choice, not a permanent file change.
That's why this is the safest starting point. You get access without altering metadata, and you can turn the view off just as quickly.
Using Terminal for a Persistent View
If you always want Finder to show hidden items, use Terminal instead of constantly repeating the keyboard shortcut.
This method changes a Finder preference rather than doing a one-time visual toggle.
The commands that change Finder visibility
According to Norton's Mac hidden files guide, the standard command is:
defaults write com.apple.finder AppleShowAllFiles YES
Then restart Finder so the change takes effect:
killall Finder
To hide them again later, reverse the preference:
defaults write com.apple.finder AppleShowAllFiles NO
Then restart Finder again:
killall Finder
This works because you're editing Finder's AppleShowAllFiles setting. Unlike the keyboard shortcut, the result is persistent until you change it back.
When persistent visibility makes sense
This is the better option if you spend a lot of time in hidden locations.
A few good use cases:
- Developers working with dotfiles every day
- IT admins inspecting user libraries and support files regularly
- Power users cleaning multiple app remnants in one session
- Testers who install and remove many apps and need constant Finder visibility
There are trade-offs, though.
| Method | Best for | Main drawback |
|---|---|---|
| Finder shortcut | Quick one-off inspection | Temporary |
Terminal AppleShowAllFiles | Ongoing access across Finder | Adds visual clutter everywhere |
Once this setting is on, Finder becomes noisier. You'll see more files, more folders, and more things you probably don't need in daily work. That's why I treat it as a working mode, not a permanent lifestyle setting, unless you're already comfortable in macOS internals.
Advanced Methods for Control and Cleanup
This is the part most hidden-file guides skip. Sometimes you don't want all hidden files visible. You want one file or one folder to stop being hidden.
That's a different job, and the right command is chflags.
How to unhide one specific file or folder
To permanently remove the hidden flag from a specific item, use:
chflags nohidden /path/to/item
If the target is your user Library folder, the command would be:
chflags nohidden ~/Library
This doesn't globally change Finder. It changes that item's hidden status.
That's often the cleanest choice when you keep returning to the same place. It gives you targeted visibility without turning Finder into a wall of translucent clutter.
If you only care about one folder, don't change Finder for the whole system.
You can also go the other direction and hide something intentionally with chflags hidden, which is useful for keeping personal working folders out of the way without changing Finder defaults.
How to get into Library when you're cleaning leftovers
For quick access, Finder already gives you a better route than full-time hidden-file mode.
Open Finder, click Go in the menu bar, then hold Option. The Library entry appears in the menu, letting you jump into ~/Library directly. That's often the fastest path when you're checking app support folders, caches, saved states, or preference files.
If you're cleaning app data, it also helps to know what cache files do before deleting them. This guide on how to clear app cache on Mac gives a practical breakdown of what belongs to apps and what should be approached carefully.
Manual cleanup works, but it has a known weakness. App leftovers are rarely in one obvious folder. They're often spread across caches, support directories, preferences, containers, and logs. That's why experienced Mac users inspect first, then remove only what they can clearly tie back to the app.
Frequently Asked Questions About Hidden Files
Why do hidden files seem to hide themselves again
Because the Finder shortcut is only a view toggle. Users often notice hidden files seem to reset after a reboot or when moving between folders, and that behavior is commonly tied to Finder state rather than a permanent file attribute, as shown in this YouTube hidden files walkthrough.
If that keeps happening, use the Terminal Finder setting for persistent visibility, or use chflags nohidden on the one folder you need permanently visible.
Is it safe to delete hidden files
Sometimes. Not always.
It's generally safer to remove hidden files when you can clearly identify them as app leftovers, caches, logs, or support files tied to software you've already removed. Be far more careful with system-level hidden folders and anything you don't recognize. If storage pressure is the main issue, this guide to MacBook storage management is a better starting point than deleting random hidden items.
How do you hide your own files on purpose
You have two common options:
- Use
chflags hiddenon a file or folder if you want Finder to treat it as hidden. - Rename a file with a leading period if you want it to behave like a dotfile.
The first is better for ordinary files and folders. The second is common in Unix-style configuration workflows.
If you regularly install and remove apps, hidden leftovers in ~/Library add up fast. Crufti is a native Mac utility built to find and remove app leftovers safely, with local-only processing, review before removal, and cleanup focused on the files uninstallers usually miss.