Chmod Calculator

The chmod command (short for change mode) is a foundational Unix and Linux utility that controls who can read, write, or execute a file or directory. Every file on a Unix-like system carries a set of permission bits that determine access for three distinct classes of users: the file's owner, members of the file's associated group, and others (everyone else on the system). Understanding and correctly setting these permissions is one of the most important skills for system administrators, web developers, and DevOps engineers alike.

Unix file permissions have existed since the earliest days of the operating system, dating back to the 1960s and 1970s. The model is elegantly simple: nine permission bits arranged in three groups of three. Each group controls Read (r), Write (w), and Execute (x) access for one of the three user classes. This design has proven remarkably durable — it powers billions of Linux servers, macOS machines, Android devices, and embedded systems today.

A chmod calculator removes the mental arithmetic required to convert between permission descriptions and the numeric codes that the chmod command actually uses. Instead of remembering that "owner can read and write, group can read, others can read" translates to the octal value 644, you simply check the boxes and let the calculator generate both the octal code and the ready-to-paste terminal command for you.

Whether you are deploying a web application, writing a shell script, securing a configuration file, or troubleshooting a "permission denied" error, this chmod permission calculator gives you the exact command you need in seconds.

The chmod calculator converts your checkbox selections into an octal number and a symbolic notation string by assigning a fixed numeric weight to each permission type. Read access is worth 4, Write access is worth 2, and Execute access is worth 1. For each of the three user classes — Owner, Group, and Others — the calculator sums whichever weights are enabled.

The three resulting digits (each between 0 and 7) are then concatenated left-to-right to form the familiar three-digit octal permission code. For example, if the owner has read and write (4 + 2 = 6), the group has read only (4), and others have read only (4), the octal result is 644. The calculator simultaneously builds the symbolic representation, replacing each enabled bit with its letter and each disabled bit with a dash, then prepends a hyphen for regular files — giving -rw-r--r-- for the same example.

You can also work in reverse: type any three-digit octal value (such as 755) into the octal input field, click Apply, and the checkboxes will update to reflect the corresponding permissions. The calculator uses a bitwise AND operation to extract each bit: val & 4 for read, val & 2 for write, and val & 1 for execute.

Octal (base-8) notation is the standard way to represent Unix file permissions numerically. Because each permission group has exactly three bits (read, write, execute), and three binary bits can represent values from 0 to 7, a single octal digit perfectly encodes all possible states for one user class. Stringing three such digits together covers owner, group, and others in nine bits total — exactly matching the nine permission slots in Unix's permission model.

The table below shows every possible octal digit and its meaning:

When you see a permission like 755, you read it as: owner = 7 (rwx), group = 5 (r-x), others = 5 (r-x). This is the standard permission for publicly accessible directories and executable scripts on web servers worldwide.

Besides octal numbers, chmod accepts a human-readable symbolic notation that spells out permissions using letters and operators. The symbolic form uses u for user (owner), g for group, and o for others, combined with = (set exactly), + (add), or - (remove) and the permission letters r, w, x.

For example, the octal command chmod 755 filename has an equivalent symbolic form: chmod u=rwx,g=rx,o=rx filename. Both commands produce the same result — they just express it differently. The octal form is more compact and common in scripts and documentation; the symbolic form is often preferred when you want to make incremental changes (like chmod +x script.sh to add execute permission without touching anything else).

The chmod calculator generates both forms automatically. The octal command is the most broadly recognized and fastest to type; the symbolic command is more self-documenting and safer when you want to add or remove a single bit without accidentally resetting the others.

On most Linux distributions and macOS, you can also apply permissions recursively using the -R flag: chmod -R 755 /var/www/html. Be cautious with recursive chmod — it applies the same permissions to every file and subdirectory, which can break things if files and directories need different permissions (directories typically need execute to be traversable, while regular files usually should not be executable).

After years of Unix and Linux convention, a handful of permission patterns have become standard defaults for specific types of files and directories. Knowing these patterns by heart — and understanding why each one is recommended — will help you make better security decisions.

The key principle is least privilege: grant only the permissions that are genuinely required for the file's purpose. If a file does not need to be executed, remove execute bits. If a file contains sensitive data, remove group and others read bits. This approach limits the blast radius of any security breach or misconfiguration.

File permissions are the first line of defense in Unix security. Incorrect permissions are among the most common causes of both accidental data exposure and deliberate exploitation. Understanding the security implications of each permission setting is critical for anyone deploying applications or managing servers.

World-writable files (777 or any octal ending in 7) are a serious risk in multi-user or web-hosting environments. Any process running on the system — including a compromised web application — can overwrite these files. Attackers who gain limited access to a server frequently look for world-writable directories to plant malicious scripts.

SUID and SGID bits (represented by an s in the symbolic notation) are advanced permission features not covered by a basic three-digit chmod but worth knowing. An SUID executable runs with the file owner's privileges rather than the caller's. These bits require extra scrutiny and should never be set unnecessarily.

Web server files typically follow the pattern of 644 for files and 755 for directories. The web server process (often running as www-data or nginx) belongs to the file's group, so it can read files without being the owner. Config files holding database credentials or API keys should always be 600 or 640 — never readable by others.

SSH keys have strict requirements: OpenSSH refuses to use private keys unless they are set to 600 (owner read/write only). The .ssh directory itself should be 700. This is one of the most common permission mistakes new Linux users make, and it causes authentication failures that look cryptic until you check the permissions.