Chmod Permission Calculator

Tick the read, write, and execute boxes for owner, group, and others to get the octal (e.g. 755) and symbolic (e.g. rwxr-xr-x) permissions, plus a ready-to-run chmod command. Supports setuid, setgid, and the sticky bit.

Presets:
Read (4)Write (2)Execute (1)
Owner
Group
Others
Octal
644
Symbolic
rw-r--r--
chmod 644 filename

Understanding Unix File Permissions and chmod

Every file and directory on a Unix-like system (Linux, macOS, BSD) has permissions that control who can read, write, and execute it. The chmod ("change mode") command sets those permissions, and it accepts two notations: octal (numbers like 755) and symbolic (letters like rwxr-xr-x). This calculator converts between them instantly so you never have to do the math in your head.

The Three Permission Types and Three Classes

Permissions apply to three classes of user — the file's owner, its group, and others (everyone else) — and each class can have three permissions:

Add the values for each class to get its octal digit: read + write + execute = 4 + 2 + 1 = 7. So 755 means the owner has 7 (rwx), and group and others each have 5 (r-x).

Common Permission Sets

Special Permission Bits

A fourth, leading octal digit controls three special bits:

A lowercase s/t means the execute bit is also set; an uppercase S/T means the special bit is set but execute is not.

Frequently Asked Questions

It gives the owner read, write, and execute (7 = 4+2+1) and gives the group and others read and execute (5 = 4+1). In symbolic form that's rwxr-xr-x. It's the standard for directories and executable scripts.
644 lacks execute mode bits; 755 includes them. Directory search permission permits traversal, while directory read permits listing names. Choose classes according to the access needed rather than granting everyone access by default.
Type the symbolic string (like rwxr-xr-x) into the Symbolic field and the octal appears instantly. Each group of three letters becomes one digit: r=4, w=2, x=1, added together.
777 generally grants more access than necessary. Investigate ownership, ACLs, parent-directory search permission, and application requirements rather than applying it as a blanket fix. 644 and 755 are examples, not universal remedies.
On a shared directory, the sticky bit restricts deletion and renaming by users with directory write access. The entry owner, directory owner, and suitably privileged processes are exceptions; it is not an owner-only guarantee.