Chmod Calculator

Convert between octal (755) and symbolic (rwxr-xr-x) Linux file permissions. See a visual permission grid with detailed breakdowns for Owner, Group, and Other.

Ad Space

How Does the Chmod Calculator Work?

The Chmod Calculator is a free online tool that converts Linux and Unix file permissions between octal (numeric) and symbolic notation. File permissions in Unix-like operating systems control who can read, write, and execute files and directories. The chmod command (short for "change mode") is used to modify these permissions, and understanding the notation is essential for system administrators, developers, and anyone working with Linux servers.

Every file and directory in a Unix-like system has three sets of permissions: one for the owner (user who created the file), one for the group (users who share a common group), and one for others (everyone else). Each set can include read (r), write (w), and execute (x) permissions. In octal notation, each permission is represented by a number: read is 4, write is 2, and execute is 1. The sum of these values gives the permission digit for each category.

Understanding Octal Permission Values

Permission values:
Read (r) = 4
Write (w) = 2
Execute (x) = 1

Example: 755
Owner: 7 = 4+2+1 (rwx) — full access
Group: 5 = 4+0+1 (r-x) — read and execute
Other: 5 = 4+0+1 (r-x) — read and execute

Common Permission Values

Certain permission combinations are used frequently in Linux system administration:

When to Use Chmod

You need to set correct file permissions when deploying web applications, configuring SSH keys (which require 600 or 400), setting up cron jobs, managing shared directories on multi-user systems, and securing sensitive configuration files. Incorrect permissions are one of the most common causes of "permission denied" errors on Linux servers. Web servers like Apache and Nginx require specific permission settings on document roots, scripts, and upload directories to function correctly while maintaining security.

This calculator eliminates the need to memorize permission values by letting you type an octal code like 755 and instantly see the symbolic representation, or enter symbolic notation like rwxr-xr-x to get the numeric equivalent. The visual grid makes it easy to verify exactly which permissions are granted to each user category before running the chmod command on your server.

Frequently Asked Questions

What does chmod 755 mean?

Chmod 755 sets the file permissions to rwxr-xr-x. The owner (7 = 4+2+1) gets read, write, and execute permissions. The group (5 = 4+0+1) and others (5 = 4+0+1) get read and execute permissions but cannot write. This is the most common permission for directories and executable scripts on Linux servers.

What is the difference between chmod 644 and 755?

Chmod 644 (rw-r--r--) gives the owner read and write permissions, while group and others can only read. Chmod 755 (rwxr-xr-x) adds execute permission for all three categories. Use 644 for regular files like HTML pages and configuration files. Use 755 for directories and executable scripts that need to be run.

Why does SSH require chmod 600 for private keys?

SSH requires private key files to have 600 (rw-------) or 400 (r--------) permissions to ensure only the file owner can read them. If a private key file has group or other read permissions, SSH will refuse to use it because other users on the system could potentially read your private key, which would be a security vulnerability.

What is the difference between octal and symbolic chmod notation?

Octal notation uses three digits (e.g., 755) where each digit represents permissions for owner, group, and other. Symbolic notation uses letters (e.g., rwxr-xr-x) where r=read, w=write, x=execute, and a dash means no permission. Both represent the same permissions — octal is more concise for setting all permissions at once, while symbolic is easier to read at a glance.

What does chmod 777 do and is it safe?

Chmod 777 (rwxrwxrwx) grants full read, write, and execute permissions to the owner, group, and all other users on the system. This is generally NOT safe for production use because it allows any user to modify or execute the file. It is sometimes used temporarily during debugging but should be replaced with more restrictive permissions like 755 or 644 afterward.