chmod Command Cheatsheet

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from chmod Command Cheatsheet

chmod Command Cheatsheet explains common ways to change Unix-style permission bits using symbolic or numeric notation. The read, write, and execute bits are grouped for owner, group, and others. Their effects differ for files and directories: directory execute permission concerns traversal, while a file's execute bit allows it to be considered executable. A cheatsheet works best as a memory aid while you practice a concrete task. Read the command or syntax together with its arguments, placeholders, and surrounding context. Similar-looking options can have very different meanings, and an example written for one platform or version may need adjustment elsewhere. Keep the reference beside a small test case, use read-only examples first when possible, and check the relevant help output before applying an unfamiliar command to valuable files or a running service.

Guide updated October 13, 2026

How to use this tool

1. Identify the operation you want to perform and find the matching section of the reference. Read the whole example before copying any part of it.
2. Identify the desired access for each class, then compare symbolic and octal examples before changing a test file.
3. Review the example below and compare its expected behavior with a small sample of your own input before continuing.
4. Try the adapted example on a small test case, compare the result with the explanation, and save the command with a note about the context in which it works.

SEE IT IN PRACTICE

A worked example

chmod 644 example.txt

Owner read/write; group read; others read

The digits represent 4+2 for the owner and 4 for each remaining class, without execute permission.

Files and directories interpret permission bits differently

Read permission on a file allows reading its data, while execute permission can permit executing it as a program subject to other system rules. For a directory, read concerns listing entries and execute concerns traversing the directory to access named items. This difference explains why copying a file-oriented permission pattern recursively can make a directory tree unusable. Decide the intended access separately for files and directories rather than applying one numeric mode indiscriminately.

Mode bits are only part of effective access

Ownership, group membership, access-control lists, mount settings, and application context can affect whether a process actually has access. If a mode appears correct but an operation fails, inspect those factors before granting broader permissions. Avoid treating a permissive mode as a universal troubleshooting fix. Review the specific user and path involved, preserve the original state, and make the narrowest justified change. A cheatsheet can decode notation but cannot determine the appropriate access policy for your system.

When this tool is useful

• Decode an octal permission value
• Review a file-sharing permission choice
• Compare symbolic and numeric chmod notation

Tips for a better result

• Inspect the original permissions and apply a narrow change to a test path before considering broader changes.
• Replace example paths, identifiers, and names deliberately. Copying a reference command unchanged can target a different file, branch, service, or environment from the one you intended.
• Keep the source and the settings used for this result together. That makes a later comparison or correction easier, especially when another person needs to reproduce the same outcome.

Frequently asked questions