Chmod Calculator
755 — Standard executable
644 — Standard file
600 — Private file
| Read | Write | Execute | Value | |
|---|---|---|---|---|
| Owner | 7 | |||
| Group | 5 | |||
| Others | 5 |
rwxr-xr-xchmod 755 filenameCalculate Unix file permissions in numeric (octal) and symbolic formats. Toggle read, write, and execute for owner, group, and others.
How to Use Chmod Calculator
- Click the permission checkboxes (Read, Write, Execute) for Owner, Group, and Others.
- The numeric (octal) and symbolic values update instantly.
- Alternatively, type a numeric value like 755 to set the checkboxes automatically.
- Use the preset buttons for common permissions (644, 755, 777, etc.).
- Copy the numeric value or the full chmod command with the Copy button.
Understanding Unix File Permissions
Unix-like systems use a permission model with three classes: Owner (the file creator), Group (users in the same group), and Others (everyone else). Each class can have Read (r), Write (w), and Execute (x) permissions. The numeric (octal) representation assigns Read = 4, Write = 2, Execute = 1, and sums them per class.
For example, 755 means the owner has full access (7 = 4+2+1), while group and others can read and execute (5 = 4+1). Directories need execute permission for users to list their contents.
Common Permission Patterns
755 is the standard for directories and executable scripts — owner has full control, everyone else can read and traverse. 644 is the default for regular files — owner reads and writes, everyone else reads only. 600 is for sensitive files like SSH private keys and .env files — owner only, no access for anyone else. 700 is the equivalent for private directories.
Symbolic vs Octal Notation
Octal notation (chmod 755) sets all permissions at once. Symbolic notation (chmod u+x) modifies specific permissions without touching others. Symbolic is safer for incremental changes — chmod g+w file adds group write without affecting owner or others. Octal is better when you want to set exact permissions from scratch. Both achieve the same result; it's a matter of precision vs convenience.
Why 777 Is Almost Always Wrong
chmod 777 gives every user on the system full read, write, and execute access. This is a security risk — any process or user can modify or delete the file. It's the "I don't understand permissions so I'll just open everything" approach. If something only works with 777, the real fix is figuring out which user or group actually needs access and granting only that. Web servers should never serve files with 777 permissions.