Chmod Calculator

Understanding Unix File Permissions Without Memorizing Octal Math

File permissions are one of the first concepts that trips up developers new to Linux and Unix-based systems. The `chmod` command controls who can read, write, and execute files and directories—and getting it wrong has real consequences, from application errors to outright security vulnerabilities. Our free chmod calculator converts between the octal notation you pass to the `chmod` command and the human-readable symbolic representation, so you can verify exactly what permissions you're setting before you run the command on a production server.

Enter a three-digit octal permission code like 755, 644, or 777, and the calculator immediately breaks it down into the corresponding read, write, and execute permissions for the owner, group, and others. Or work the other way: check each permission checkbox visually and see the octal value build in real time. Either way, you leave the tool with a clear understanding of what the permission string means—and confidence that the number you're about to run on your server does what you think it does.

How Unix File Permissions Work

Every file and directory on a Unix-based system has three permission categories applied to three types of user. The three user types are the owner (the user who created or was assigned ownership of the file), the group (a collection of users who share access to the file), and others (every other user on the system). Within each category, three individual permissions can be granted or denied: read (r), write (w), and execute (x).

Read permission on a file allows its contents to be viewed. Read permission on a directory allows its contents to be listed. Write permission allows a file to be modified or deleted. Write permission on a directory allows files to be created, renamed, or deleted within it. Execute permission on a file allows it to be run as a program or script. Execute permission on a directory allows it to be entered and traversed—you must have execute on a directory to `cd` into it or access files within it, even if you have read permission.

Octal Notation: The Math Behind the Three-Digit Number

The three-digit octal notation used by `chmod` encodes all nine permissions (three for each of the three user categories) into a compact numeric format. Each digit represents one user category and is the sum of the permission values assigned to that category: read = 4, write = 2, execute = 1.

To calculate the digit for any category, add the values of the permissions you want to grant. Owner with all three permissions: 4 + 2 + 1 = 7. Group with read and execute but not write: 4 + 0 + 1 = 5. Others with read only: 4 + 0 + 0 = 4. The three digits combine to give 754—often written as `chmod 754 filename`.

The most commonly encountered octal values and their meanings: 7 (rwx) = full permissions; 6 (rw-) = read and write; 5 (r-x) = read and execute; 4 (r--) = read only; 0 (---) = no permissions at all.

The Most Common chmod Values and When to Use Each

chmod 755 — Standard Directory and Executable Permissions

This is the default permission set for web server directories and executable scripts. The owner can read, write, and execute; the group and others can read and execute but cannot write. This allows the web server process to read files and traverse directories while preventing unauthorized modification. Most web hosting environments expect top-level directories to carry 755 permissions.

chmod 644 — Standard File Permissions

The standard permission set for non-executable files: the owner can read and write, while the group and others can only read. PHP files, HTML files, configuration files, and most web assets should be set to 644. This allows the web server to read and serve them while preventing other users from modifying them.

chmod 600 — Private Files

Only the owner can read and write; group and others have no access at all. This is appropriate for SSH private keys, configuration files containing credentials, and any file that should be accessible only to the owning user. Many SSH clients refuse to use a private key file that has permissions broader than 600 for security reasons.

chmod 777 — Full Permissions for Everyone

All three user types have full read, write, and execute access. This setting is almost always a security mistake in production environments—it means any user on the system can modify or delete the file. Developers sometimes set this during troubleshooting to rule out permissions as the cause of an error, but it should never remain in place on a live system. Legitimate use cases for 777 are genuinely rare.

chmod 700 — Owner-Only with Full Access

The owner has full permissions; all other users have none. Appropriate for personal scripts, private executables, and any file where the owner needs to run it but no other user should be able to read, modify, or execute it.

Recursive Permissions: Applying chmod to Entire Directories

The `chmod` command with the `-R` flag applies the specified permissions recursively to a directory and all of its contents. However, applying a single permission set recursively to both files and directories is often incorrect—directories typically need execute permission (to be traversed) while regular files usually should not be executable. A common pattern to correctly set permissions on a web application is to use two separate commands: `find /path -type d -exec chmod 755 {} \;` for directories and `find /path -type f -exec chmod 644 {} \;` for files. This ensures directories get 755 and files get 644 without setting all files executable, which would be a security risk for PHP and HTML files that don't need execute permission.

Free, Private, and Instant

The chmod calculator runs entirely in your browser. No permission values or file information you enter are transmitted to any server. The tool is completely free with no account required. Use it to verify permissions before running a command, to decode an unfamiliar three-digit value from documentation, or to learn the permission system interactively.