Chmod

chmod Calculator

Convert chmod numeric and symbolic permissions

Automation & DevOps
🔒 100% client-side — your data never leaves this page
Maintained by Evan•Updated: September 30, 2026
Options
Permissions

Enter octal or symbolic permissions first to convert them and generate a chmod command immediately; common permission scenarios are available in Advanced mode.

Numeric
Symbolic
chmod cmd
chmod 755 file
ReadWriteExecuteOctal
Owner (u)7
Group (g)5
Others (o)5
🔒 Processed locally in your browser
Output
Numeric (octal)755
Symbolicrwxr-xr-x
chmod commandchmod 755 filename
Recursivechmod -R 755 dirname/
What each bit means
Owner (u)rwxread + write + execute
Group (g)rwxread + execute
Others (o)rwxread + execute
Common permissions
777rwxrwxrwxFull access for everyone (avoid)
755rwxr-xr-xExecutable / directories
644rw-r--r--Standard file
600rw-------Private file (SSH keys)
750rwxr-x---Scripts, group readable
664rw-rw-r--Group writable file
400r--------Read-only (config files)
700rwx------Private directory
Page reading mode

The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.

About this tool

Convert the nine ordinary Unix permission bits between a visual matrix, three octal digits and rwxr-xr-x notation. Copy a single-path command or inspect its recursive form. Special bits, symbolic operations such as u+x, ACLs and ownership are outside this calculator.

Production Snippets

Three different access needs

text

755 = rwxr-xr-x  (directory / executable example)
644 = rw-r--r--  (ordinary readable file example)
600 = rw-------  (private file example)
4755 = unsupported special bits; not converted to 475

Frequently Asked Questions

What do 755 and 644 mean?

755 gives the owner rwx and group/others r-x. 644 gives the owner rw- and group/others r--. They are common examples, not universally correct permissions for every path.

Can I enter 0755, 4755 or u+x?

0755 is accepted as 755. A nonzero fourth digit, s/t permission letters and symbolic operations such as u+x are rejected because the matrix only models nine ordinary permission bits.

Does execute mean the same thing on files and directories?

For a file, x permits execution where the file format and system allow it. For a directory, x allows searching/traversing it; reading its entry list is a separate r permission.

Should I copy chmod -R or use 777 to fix access?

Review the target tree first. -R applies a mode to children too, while files and directories often need different modes. 777 gives everyone write access; investigate ownership, group membership and required access instead of choosing it by default.

Keep browsing