Hide Home Folder on Mac (Terminal Permissions)

To make your Mac home folder less visible in Finder, set its hidden flag with chflags hidden "$HOME". To limit directory access to your account, first inspect ownership and ACLs, then consider chmod 700 "$HOME". These changes do different jobs: hiding affects display, while permissions control access. Neither replaces FileVault, careful backups, or testing.

Plan the Change and Inspect the Home Directory

Before changing anything, confirm that Terminal is pointing to your own home folder and record its current state. A hidden flag changes Finder’s display; a permission change can affect access. Inspect first, make one change at a time, and keep the commands specific to "$HOME".

The home folder usually holds personal files and application data. For a low-maintenance approach, you may only need to hide it in Finder. If your goal is to restrict access by other local accounts, review permissions and ACLs before changing the folder mode.

In Terminal, run:

printf '%s\n' "$HOME"
ls -ldOe "$HOME"

The first command prints the path that the shell treats as your home directory. The second shows its permissions, owner, macOS file flags, and any access-control-list entries. In the output, check that the owner is your account and note the current mode and flags before proceeding.

You can record the mode separately:

stat -f '%Lp %N' "$HOME"

This records the numeric POSIX permission mode and path. Keep the output if you may need to restore the original mode. Do not assume that a standard-looking mode means there are no ACLs; read the full ls -ldOe output.

Confirm Ownership, ACLs, and Access Requirements

Ownership identifies the account that owns the directory. POSIX permissions set access for that owner, a group, and everyone else. ACLs are additional access rules that can grant or deny access, so check them before relying on the mode shown by a simple file listing.

Review the owner and group in the ls -ldOe output. The owner should match the account you intend to protect. If it does not, stop and find out why before changing permissions. Do not use chown as a quick fix; changing ownership can cause other problems.

Look below the directory’s listing for ACL entries. If entries appear, read them before using chmod. ACL rules may affect access beyond what the three POSIX permission groups suggest. Do not remove ACLs blindly, and do not assume chmod 700 resolves every access rule.

Also consider what needs access to your home folder. Other local accounts, shared workflows, and software may rely on existing access. Restricting the folder can disrupt those uses, so make the change only when limiting that access is appropriate.

• If you only want less visibility in Finder, use the hidden flag and leave permissions unchanged.
• If you want to limit access by other accounts, inspect ownership and ACLs first.
• If you are unsure why an ACL exists or what depends on it, pause rather than deleting or rewriting rules.

Apply POSIX Permissions and the Finder Hidden Flag

Use the two changes for different goals. chmod 700 sets owner read, write, and search access on the home-directory entry, with no access for group or others through POSIX mode bits. chflags hidden marks the folder as hidden for Finder display. Neither command encrypts the folder.

Restrict directory access with chmod

After checking the owner, ACLs, and access needs, run:

chmod 700 "$HOME"

The mode 700 means the owner has rwx, while group and others have ---. For a directory, the execute bit allows traversal: a user needs it to enter the directory or reach items inside it by path. This command changes the home-directory entry only. It does not recursively change the permissions of files and folders inside.

A mode of 750 is different: the owner has rwx, the group has r-x, and others have no access. Use it only when access by the group is intentional and you understand which group applies. Do not choose it just because it seems like a middle ground.

Avoid running:

chmod -R 700 "$HOME"

The recursive option changes permissions throughout your account. That can break executable files, shared items, and application-specific access. If a specific file needs tighter permissions, assess that file on its own. For example, chmod 600 <file> gives the owner read and write access, with no access for group or others; it is not a blanket fix for every application file.

Hide the folder in Finder

If you also want the home folder hidden in Finder, run:

chflags hidden "$HOME"

This sets the macOS hidden flag. It affects how Finder presents the folder, not who is allowed to access it. The path still works in Terminal, and the folder is not encrypted. A user or process with sufficient access may still reach it.

Choice	Command	What it changes	What it does not do
Hide in Finder	chflags hidden "$HOME"	Finder display flag	Restrict access or encrypt files
Restrict POSIX access	chmod 700 "$HOME"	Home-directory mode bits	Recursively change contents or remove every ACL
Allow group access	chmod 750 "$HOME"	Owner and group mode bits	Make access safe without checking the group
Tighten one file	chmod 600 <file>	That file’s mode	Review application needs or protect other files

For many privacy-focused users, hiding alone is the less disruptive option. Choose chmod 700 only when the access restriction is needed and compatible with your setup.

Verify Access and Restore Visibility

Verification confirms that the intended change took effect and helps you spot an unexpected result. Recheck the directory after each command. If you need to undo a change, restore only what you recorded or reverse the specific flag; do not guess at earlier settings.

Run:

ls -ldOe "$HOME"

After chmod 700, the mode should show owner access and no POSIX group or other access. After chflags hidden, the flags field should include hidden. Read any ACL entries again, because mode bits alone do not describe every access rule.

You can restore Finder visibility with:

chflags nohidden "$HOME"

This removes the hidden flag; it does not restore a previous permission mode. If chmod 700 caused a problem, restore the mode only if you recorded the prior value and understand that other ACL rules may still apply. If access remains unclear, stop and review the ACL entries rather than removing them at random.

Illustrative troubleshooting scenarios

These examples are common decision patterns, not reports of a specific user or guaranteed outcomes. They show why it helps to separate Finder visibility from access control and to make one change at a time.

• Finder looks cluttered, but no access restriction is needed: Apply chflags hidden "$HOME", then verify the flag. If you later need the folder visible, use chflags nohidden "$HOME".
• You want other local accounts to have less access: Check the owner, ACLs, and sharing needs first. If the change is appropriate, apply chmod 700 "$HOME" and verify the result. Do not change all contents recursively.
• A workflow stops working after a mode change: Review the previous mode you recorded and the current ACL output. Restore the prior mode only when you know it; otherwise, identify the access requirement before making another change.

A hidden flag is a display choice, not a security boundary. For protection of data at rest, use FileVault, Apple’s built-in disk encryption, and keep a sound backup. Permissions and encryption address different risks.

Conclusion and FAQs

A careful setup starts with inspection, not a command copied without context. Use chflags hidden to reduce Finder visibility, and consider chmod 700 only when owner-only POSIX access suits your needs. Verify the result, preserve the original mode, and leave unfamiliar ACLs intact until you understand them.

Does hiding my home folder protect its files?
No. The hidden flag affects Finder display. It does not deny access, encrypt data, or prevent access by a user or process that already has permission.

What command hides my home folder in Finder?
Run chflags hidden "$HOME" in Terminal. Confirm the change with ls -ldOe "$HOME". To show it again, run chflags nohidden "$HOME".

What does chmod 700 "$HOME" do?
It gives the owner rwx access to the home-directory entry and removes POSIX group and other access. It does not recursively change the folder’s contents.

Should I use chmod 700 and chflags hidden together?
Only if both goals fit your setup. The first changes POSIX access; the second changes Finder display. Check ownership, ACLs, and required sharing before restricting access.

Will chmod 700 remove ACL entries?
Do not rely on it to remove ACLs. Inspect the output from ls -ldOe "$HOME" before and after, and do not delete ACL entries unless you know why they exist.

Can I use chmod -R 700 on my home folder?
No. A recursive change can break executable, shared, and application-specific permissions. Apply changes only to the directory or individual files that need them.

How do I restore the previous permissions?
Use the mode you recorded before making a change, and verify the result. Do not guess the original mode; ACLs may also affect access.

Does chmod 700 encrypt my home folder?
No. It changes POSIX permissions on the directory entry. Use FileVault for at-rest encryption, and keep backups for recovery.

Why can the folder still be reached after I hide it?
The hidden flag is not an access control. The folder remains reachable by path in Terminal, and access still depends on permissions, ACLs, and the authority of the user or process.

(This article was written by one of our staff writers, Richard Montclair. Visit our Meet the Team page.)