Chmod Calculator
By Mustafa Bilgic · Updated 18 August 2026
The chmod calculator converts Linux file permissions between octal, symbolic, and human-readable checkbox formats. Tick the read, write, and execute boxes for owner, group, and others above, and the tool shows the matching octal number and symbolic notation instantly. Useful whenever you need to set or verify permissions on a server.
This calculator helps you understand and set permissions. Always verify the result on your server, especially when securing sensitive files.
What Chmod Numbers Mean
The chmod command sets file permissions on Linux and Unix systems using a three-digit octal number. Each digit controls permissions for a different user class: the first digit covers the file owner, the second covers the group, and the third covers all other users.
Each digit is a sum of three values: read (4), write (2), and execute (1). A digit of 7 means all three permissions are granted (4 + 2 + 1). A digit of 5 means read and execute only (4 + 1). A digit of 0 means no permissions at all.
So chmod 755 translates to: owner can read, write, and execute; group members can read and execute; everyone else can read and execute. In symbolic notation, that same permission set is written as rwxr-xr-x, where each cluster of three characters represents owner, group, and others in sequence.
Understanding this mapping between numbers and letters is the entire purpose of the calculator.
How to Use the Chmod Calculator
The tool gives you three ways to set permissions, and all three stay synchronised:
- Click the checkboxes. Nine checkboxes are arranged in a grid — read, write, and execute for owner, group, and others. Tick the permissions you want, and the octal number and symbolic string update instantly.
- Type an octal number (such as 644) into the octal field. The checkboxes and symbolic notation adjust to match the number you entered.
- Edit the symbolic notation directly (such as
rw-r--r--) if you are comfortable with that format. The octal number and checkboxes reflect the change.
All three representations describe the same permission state, so editing any one updates the other two in real time. There is no submit button — the output is live.
This makes the tool useful for learning as well as quick reference. Change a checkbox and watch the octal value move; type a digit and see which boxes light up. No account or installation is needed.
Common Permission Sets
A few permission combinations appear far more often than others on production servers:
644 (rw-r--r--) is the standard for regular files. The owner can read and write; everyone else can only read. Most website files — HTML, CSS, images — use this setting.
755 (rwxr-xr-x) is the standard for directories and executable scripts. The execute bit on a directory allows users to list its contents, so directories almost always need it. Scripts and binaries that other users should be able to run also use 755.
600 (rw-------) restricts access to the owner entirely. Configuration files that contain passwords, API keys, or private certificates typically use this setting to prevent other users on the system from reading them.
777 (rwxrwxrwx) grants every permission to every user. It effectively disables the permission system for that file or directory and is almost never the correct choice on a production server.
When Permissions Go Wrong
Permission errors are among the most common causes of unexpected behaviour on Linux servers. A web server returning a 403 Forbidden error often has a permissions problem: the server process cannot read the file because the other-user read bit is not set.
Scripts that fail with “permission denied” usually lack the execute bit. Running chmod +x on the script adds execute permission, and the script becomes runnable.
Conversely, overly permissive files create security vulnerabilities. SSH refuses to use a private key file if its permissions are too open — it expects 600 or 400 and will reject the key with a warning if group or other users have any access.
This calculator helps diagnose these situations. If you know the octal number a system report shows, enter it in the tool to see exactly which permissions are set and which are missing. If you know what access you need, tick the boxes and read off the correct chmod value to apply.
Frequently asked questions
What does chmod 755 mean?
It means the file owner has read, write, and execute permissions (7 = 4+2+1), while group members and all other users have read and execute permissions only (5 = 4+1). In symbolic notation, that is rwxr-xr-x.
What is the difference between octal and symbolic chmod notation?
Octal notation uses a three-digit number like 644, where each digit encodes permissions for one user class. Symbolic notation uses letters and operators like u+rw or g-w to add or remove specific permissions. Both achieve the same result through different syntax.
Should I ever use chmod 777?
Almost never in production. The 777 setting gives every user on the system full read, write, and execute access, which effectively disables permission-based security. It is occasionally used during local troubleshooting but should be replaced with a restrictive setting before deployment.
Do chmod permissions apply on Windows?
Traditional chmod permissions are a Linux and Unix concept. Windows uses a different access control system based on NTFS ACLs. If you are working in Windows Subsystem for Linux, chmod commands may have limited effect depending on your WSL configuration.