Skip to content

chmod Calculator

Convert Linux file modes between 755 and rwxr-xr-x, tick permissions, test changes like g+w, and see what setuid, setgid, sticky and umask do.

Type a mode the way you have it (755, 2775, rwxr-x---, or a whole ls -l column like drwxrwsr-x), or tick the boxes, and get every other form plus what it actually lets each person do, which is different for files and folders. Try a change like g+w,o-rwx to see exactly what chmod would do: it's modelled on GNU chmod (Linux) and checked against it, including the umask and directory quirks that catch people out.

Mode
Read (4)Write (2)Enter / search (1)Digit
Owner (u)
7
Group (g)
5
Others (o)
5
Special
0
Octal
755
As ls -l shows it
drwxr-xr-x
Numericchmod 755 folder
Symbolicchmod u=rwx,g=rx,o=rx folder
Folder and contentsfind folder -type d -exec chmod 755 {} + && find folder -type f -exec chmod 644 {} +

chmod -R would give files the folder's execute bits too; these find commands set folders and files separately (files get read and write only).

What it allows

  • The owner can list what's inside, enter it and open what's inside, create, delete and rename anything inside, even other people's files.
  • Members of the group can list what's inside, enter it and open what's inside.
  • Everyone else can list what's inside, enter it and open what's inside.
  • Deleting or renaming a file depends on the folder's write permission, not the file's.

Try a change

What chmod would do to the mode above. Comma-separate several: u+x,g-w,o=

chmod argument
umask

umask

With umask 022, new files start as 644 (rw-r--r--) and new folders as 755 (rwxr-xr-x). The umask removes bits from 666 for files and 777 for folders; it never adds execute to files. Set it with umask 022 in a shell profile.