How do I read octal permissions?

Each digit represents one audience in the order owner, group, others. The digits sum r=4, w=2, x=1, so 7 is 4+2+1=rwx, 6 is 4+2=rw-, 5 is 4+1=r-x, 4 is r--, and 0 is no permissions at all. Reading 755 from left to right: the owner has 7 (full access), the group has 5 (read and execute), and others have 5 (read and execute).

What are the common permission values?

644 is the standard for files — owner can read and write, everyone else can only read. 755 is for executables and directories. 600 is for private files like SSH keys, restricted to the owner. 700 is the directory equivalent for private content. 777 is world-writable and should be avoided as a security risk. 444 is read-only for everyone. Memorize these few and you'll handle the vast majority of real-world cases.

A few common reasons. Most often, you're not the file owner — only the owner or root can change permissions. The file system might not actually support Unix permissions (FAT32 and some network mounts are notorious for this). The immutable flag may be set on the file via chattr +i. Or there's a syntax error in the chmod command itself. Run 'ls -l' first to verify ownership and that the file is on a supporting filesystem.

What's the difference between octal and symbolic chmod?

Octal is numeric — 'chmod 755 file' replaces all permissions at once with what the digits encode. Symbolic is textual — 'chmod u+x file' adds the execute bit for the user without touching anything else. The symbolic form uses + to add, - to remove, and = to set; u, g, o, and a stand for user, group, others, and all. Octal is faster when you know exactly what you want; symbolic is clearer when you're modifying just one bit.

What is the sticky bit?

It's a special permission applied to directories. When set, only the file's owner can delete files inside that directory, even if other users have write access. The classic use is /tmp — anyone can create files there, but only the file's owner can delete their own files. In octal, you add 1000 to get 1755 for sticky plus rwxr-xr-x. The symbolic form is 'chmod +t'.

What are setuid and setgid?

Setuid (4000) makes a program run as the file's owner regardless of who actually runs it — sudo and ping are classic examples. Setgid (2000) does the same thing for the file's group. Setgid on a directory has the additional effect of making new files inside inherit the directory's group. These are security-critical; misuse leads to privilege escalation. The octal forms prepend 4xxx for setuid or 2xxx for setgid.

How does recursive chmod work?

'chmod -R 755 dir' applies 755 to the directory and everything inside it. The catch is that it applies the same permissions to files and directories alike, which is rarely what you want. Directories need execute (x) so you can enter them, but files typically only need read and write — not execute. For mixed cases, use the capital-X form: 'chmod -R u=rwX,g=rX,o=rX dir' applies execute only to directories, leaving regular files without it.

Chmod Calculator

Calculate Unix file permissions online with visual checkboxes. Free chmod calculator converting between numeric and symbolic modes.

Generators Developer Tools

Instant results

Numeric (Octal)

644

Symbolic

-rw-r--r--

Commands

chmod 644 filename

chmod -R 644 directory/

Common Permissions

Permission Values:

4 = Read (r)

2 = Write (w)

1 = Execute (x)

About Chmod Calculator

Calculate Unix file permissions using the chmod command. Set read, write, and execute permissions for owner, group, and others. Get both numeric (octal) and symbolic notation.

How to Use Chmod Calculator

Set the permissions

Toggle the checkboxes for read, write, and execute for owner, group, and others. Alternatively, enter the octal value directly (something like 755) and the calculator updates the checkboxes to match.

View octal and symbolic forms

The calculator shows the octal (755), the symbolic form (rwxr-xr-x), and the full command (chmod 755 filename). Both representations help verify what you're about to apply before running it.

Copy the command

Copy the 'chmod 755 filename' command to your clipboard, replace 'filename' with your actual file path, and run it in the terminal to apply the permissions.

Verify the applied permissions

After running chmod, verify the result with 'ls -l filename' in the terminal. The output should show the permissions you specified. If it doesn't match, re-run chmod and check for typos in the path or the octal value.

When to Use Chmod Calculator

Server file permissions

Linux and Unix file permissions are typically expressed as octal codes like 755 or 644. The calculator converts between octal and the human-readable rwxr-xr-x form so you can check at a glance what a given permission actually allows. It's useful when configuring web servers, writing deployment scripts, and troubleshooting permission errors that aren't immediately obvious from the command line.

SSH key setup

SSH is fussy about permissions. Private keys need 600, public keys need 644, and the .ssh directory itself needs 700. If the permissions are too permissive, SSH simply refuses to use the keys, which produces confusing errors. The calculator helps verify and calculate the correct values when you're setting up SSH access from scratch or debugging a key that mysteriously stopped working.

Web server troubleshooting

Apache or Nginx returning 403 errors is often a permission problem. Files typically need 644 and directories 755 for the web server user to read them. The calculator helps debug questions like 'what does 700 actually allow?' or 'what octal gives the owner read and write but nothing else?' without trying random values until something works.

Linux administration

DevOps engineers and sysadmins work with chmod regularly. The calculator is useful for permissions audits, security reviews of how files are configured, scripts that need to change permissions programmatically, and training new admins who haven't internalized the octal encoding yet.

Chmod Calculator Examples

Standard file at 644

Input

Octal: 644

Output

Owner has rw- (read and write). Group has r-- (read only). Others have r-- (read only). Symbolic form: rw-r--r--.

The standard file permission for content the world can read but only you can edit. The owner gets read and write, everyone else gets read only. There's no execute bit, so the file can't be run as a program — appropriate for documents and configuration files.

Executable at 755

Input

Octal: 755

Output

Owner has rwx (full access). Group has r-x (read and execute). Others have r-x (read and execute). Symbolic form: rwxr-xr-x.

The standard permission for executables and directories. The owner has full control, while everyone else can read and execute. This is the default for programs in /usr/bin and for most directories — the execute bit on a directory is what lets you cd into it.

SSH private key at 600

Input

Octal: 600

Output

Owner has rw- (read and write). Group has --- (no access). Others have --- (no access). Symbolic form: rw-------.

Restrictive permissions where only the owner has any access at all. SSH requires this for private keys and refuses to use a key that's more permissive. The same pattern is used for secrets, configuration files containing credentials, and other sensitive data.

Tips & Best Practices for Chmod Calculator

1.The three octal digits are owner, group, and others, in that order. Each digit sums read (4), write (2), and execute (1) — so 7 is rwx, 6 is rw-, 5 is r-x, 4 is r--, and 0 is no permissions at all. Once you've seen these a few times, reading them becomes automatic.
2.Most cases are covered by a small set of values. Files at 644 (everyone can read, only you can write), executables at 755, directories at 755 (you need execute to enter a directory), and sensitive files at 600 (owner only) handle about 95% of what you'll encounter.
3.Avoid 777 in production. World-writable permissions are a real security risk and almost never the right answer. Use them only for temporary debugging, and never leave them in place permanently — they're a common audit finding.
4.Symbolic chmod is often clearer than octal for incremental changes. 'chmod +x file' adds the execute bit, 'chmod u+w file' adds write for the user, and 'chmod o-r file' removes read for others. These leave existing bits alone rather than replacing the whole permission set.
5.Special bits add a fourth octal digit. 1000 is the sticky bit (used by /tmp), 2000 is setgid, and 4000 is setuid (used by sudo). They're uncommon, but they exist and can produce surprising behavior when set deliberately or accidentally.
6.Recursive chmod applies the same permissions to everything. 'chmod -R 755 dir' is fine for code directories where you want files executable, but applying file permissions to directories — or vice versa — can break things. Use 'chmod -R u=rwX,g=rX,o=rX dir' (capital X means execute only on directories) to avoid that pitfall.

Frequently Asked Questions

It's the Unix command for changing file and directory permissions. There are three permissions — read (r), write (w), and execute (x) — and three audiences they apply to — the owner (user), the group, and everyone else (others). That's 9 bits total, which is conventionally expressed as a three-digit octal number. For example, 755 corresponds to rwxr-xr-x.

Chmod Calculator

Commands

Common Permissions

About Chmod Calculator

How to Use Chmod Calculator

Set the permissions

View octal and symbolic forms

Copy the command

Verify the applied permissions

When to Use Chmod Calculator

Server file permissions

SSH key setup

Web server troubleshooting

Linux administration

Chmod Calculator Examples

Standard file at 644

Executable at 755

SSH private key at 600

Tips & Best Practices for Chmod Calculator

Frequently Asked Questions

Related Tools

UUID Generator

Password Generator

Random String Generator

Fake Data Generator

Cron Expression Generator

htpasswd Generator