Account

What new tool do you want?

Developer Tools

Chmod Calculator

Convert Linux file permissions between numeric (755) and symbolic (rwxr-xr-x) notation, with a plain-English breakdown and the chmod command.

How to use

  1. 1Enter permissions as a number (644, 0755, 4755) or letters (rwxr-xr-x).
  2. 2Copy the chmod command or read what each group can do.

How it's calculated

Each digit is the sum of read (4), write (2) and execute (1) for owner, group and others. An optional leading digit sets setuid (4), setgid (2) and sticky (1).

Frequently asked questions

What does chmod 755 mean?

The owner can read, write and execute (7); group and others can read and execute (5). It's the usual setting for programs and directories.

What's the difference between 644 and 600?

644 lets everyone read the file but only the owner write it. 600 hides it from everyone except the owner — use it for private keys and secrets.

Why is chmod 777 dangerous?

Anyone on the system can modify or replace the file. It's almost never the right fix for a permissions error.

A worked example of the special bits

Entering -rwsr-xr-x (symbolic) converts to octal 4755, and that leading 4 — not part of the familiar three-digit 755 — specifically means setuid is set, shown as the lowercase s replacing the owner's execute bit in the symbolic form. Setuid on an executable means it runs with the permissions of the file's owner rather than the user who launched it (classically how passwd lets any user change their own password by briefly running as root) — it's a meaningfully different and more powerful bit than the regular rwx permissions, which is why the calculator breaks it into its own "Special" output rather than folding it into owner/group/others.

Why 644 and 600 look almost identical but serve different purposes

644 (rw-r--r--) lets the owner read and write while everyone else can only read — the standard default for files meant to be publicly readable, like a web server's static assets or a README. 600 (rw-------) removes all access for group and others entirely, which is the correct permission for anything sensitive: SSH private keys, .env files with secrets, database credentials. The numeric difference is small (644 vs 600) but the security implication is large — 644 on a private key file means every other local user on the system can read it.

Why 777 is treated as a warning sign, not a fix

chmod 777 grants read, write and execute to literally everyone on the system — owner, group, and others alike — which means any other user or process on a shared or compromised system can modify, replace, or execute that file at will. It's a common panic-mode fix for a confusing "permission denied" error, but it almost always papers over the real problem (wrong owner, wrong group, a misconfigured service user) rather than solving it — the FAQ's framing ("almost never the right fix") reflects that 777 trades away the entire point of having a permissions system in exchange for making an error message go away.

Three digits mean the special bit is zero

The permissions box opens on 755. A number of three or four octal digits is accepted. Three digits are padded on the left, so 755 is the same as 0755 and the special digit is zero: no setuid, setgid, or sticky bit. A letter form can be ten characters starting with a dash, d, or l, and that first mark is ignored. Anything else that is not a number like 755 or letters like rwxr-xr-x stops with that example in the message. I hit that when I paste a longer listing line that still has the owner and size attached.

Related tools

More: Developer Tools