chmod 755 and rwx Permissions Explained

chmod sets Unix file permission bits for owner, group, and other. Each triad is read (r=4), write (w=2), execute (x=1). Sum them per triad to get an octal digit. 755 is rwxr-xr-x: owner full, everyone else read+execute.

Common modes

Mode	Symbolic	Typical use
755	rwxr-xr-x	Directories, executables
644	rw-r--r--	Regular files
600	rw-------	Private keys, secrets
700	rwx------	Private scripts/dirs

How the math works

For one triad: r+w+x → 4+2+1=7.
755 = owner 7, group 5 (4+1), other 5.

Directories need execute to be entered (cd). Files need execute to run as programs. Missing execute on a directory is a classic “permission denied” even when r is set.

Calculate with TryDevSnip

Open TryDevSnip chmod Calculator, toggle rwx checkboxes, and read the octal/symbolic result. Handy when you are writing Dockerfile chmod lines or fixing a deploy script.

Privacy one-liner: the calculator runs in your browser; not uploaded to our servers for processing.

Also useful: HTTP status codes when “forbidden” is an HTTP 403 rather than filesystem mode.

Deploy sanity check

After chmod, verify with ls -l (or stat) that the mode matches what you intended — especially after copying files from Windows or unzipping archives that reset execute bits. Scripts that “work on my machine” often fail in CI because the file was 644 and never gained +x.

FAQ

What about setuid/setgid/sticky bits?

They add a leading digit (e.g. 4755). Use carefully — security sensitive.

Why 755 for folders but 644 for files?

Folders need x to traverse; most files only need read for others.

Does chmod sync to Windows the same way?

NTFS ACLs differ. chmod on WSL/Git may be emulated — check your environment.

Is chmod -R 777 ever OK?

Almost never on shared systems. It disables meaningful access control.