The Chmod Command and Linux File Permissions Explained

So you’ve sliced your way through all the common misconceptions about Linux, found a flavor of Linux that you like, but now you’re confused because you haven’t the faintest clue about terminal commands and Linux file permissions?

Or maybe you have a website that’s hosted on a Linux server and you’ve run into some file permission issues that can only be solved with some command line magic.

Regardless, one of the most essential Linux commands to learn


An A-Z of Linux – 40 Essential Commands You Should Know




An A-Z of Linux – 40 Essential Commands You Should Know

Linux is the oft-ignored third wheel to Windows and Mac. Yes, over the past decade, the open source operating system has gained a lot of traction, but it’s still a far cry from being considered…
Read More

is a small but powerful command called chmod. But before we explain what the command does, we have to first understand a little bit about how Linux handles file security.

The Basics of Linux File Permissions

Linux operating systems are actually Unix-like systems (understanding Linux vs. Unix), and Unix-like systems approach file permissions like so:

Every file has an owner, which determines the file’s “user class.” Every file also has a group, which determines the file’s “group class.” Any system user who isn’t the owner and doesn’t belong in the same group is determined to be others.

All files on Unix-like systems have permissions assigned to all three classes, and these determine which actions can be taken by said classes for the given file.

The three actions available on a Unix-like system are: read (the ability to open and view the contents of the file), write (the ability to open and modify the contents of a file), and execute (the ability to run the file as an executable program).

In other words, a file’s permissions determine whether or not:

  • The owner can read, write, and execute the file.
  • The group can read, write, and execute the file.
  • Anyone else can read, write, and execute the file.

Linux file permissions can be displayed in two formats.

The first format is called symbolic notation, which is a string of 10 characters: one character that represents the file type, then nine characters that represent the file’s read (r), write (w), and execute (x) permissions in order of owner, group, and others. If not permitted, the dash symbol (-) is used.

For example:

-rwxr-xr--

This means it’s a regular file with read, write, and execute permissions for the owner; read and execute permissions for the group; and only read permissions for everyone else.

The second format is called numeric notation, which is a string of three digits that each represent user, group, and other permissions, respectively. Each digit can range from 0 to 7, and each digit’s value is obtained by summing the class’s permissions:

  • 0 means no permissions allowed.
  • +1 if the class can execute the file.
  • +2 if the class can write to the file.
  • +4 if the class can read the file.

In other words, the meaning of each digit value ends up being:

  • 0: No permission
  • 1: Execute
  • 2: Write
  • 3: Write and execute
  • 4: Read
  • 5: Read and execute
  • 6: Read and write
  • 7: Read, write, and execute

So the above example (-rwxr-xr--) would be 754 in numeric notation.

That’s Linux file permissions in a nutshell.

What Is Chmod?

On Unix-like systems, chmod is a system-level command that stands for “change mode” and allows you to manually change the permission settings of a file.

Not to be confused with chown, which is another system-level command on Unix-like systems that stands for “change owner” and lets you assign ownership of a file to another user, or chgrp, which stands for “change group” and assigns a file to a different group. These are important to know, but not as commonly used as chmod.

What Does Chmod 644 Mean?

Setting a file’s permissions to 644 makes it so only the owner can access and modify the file however they want while everyone else can only access without modifying, and nobody can execute the file—not even the owner. This is the ideal setting for files that are publicly accessible because it balances flexibility with security.

What Does Chmod 755 Mean?

Setting a file’s permissions to 755 is basically the same thing as 644 except everyone also has execute permissions. This is mainly used for publicly accessible directories because the execute permission is needed in order to change into a directory.

What Does Chmod 555 Mean?

Setting a file’s permissions to 555 makes it so that the file cannot be modified at all by anyone except the system’s superuser (learn more about the Linux superuser


What Is SU & Why Is It Important to Using Linux Effectively?




What Is SU & Why Is It Important to Using Linux Effectively?

The Linux SU or root user account is a powerful tool that can be helpful when used correctly or devastating if used recklessly. Let’s look at why you should be responsible when using SU.
Read More

). This isn’t as commonly used as 644, but it’s still important to know because the read-only setting prevents accidental changes and/or tampering.

What Does Chmod 777 Mean?

Setting a file’s permissions to 777 makes it so anyone can do anything they want with the file. This is a huge security risk, especially on web servers! Literally anyone can access the file, modify it however they want, and execute it on the system. You can imagine the potential damage if a rogue user got their hands on it.

How to Use Chmod on Linux

The chmod command has a simple format:

chmod [permissions] [file]

Permissions can be given in numeric notation, which is the best format to use when you want to assign specific permissions for all classes:

chmod 644 example.txt

Permissions can also be given in symbolic notation, which is useful when you only want to modify the permissions of a particular class. For example:

chmod u=rwx example.txt
chmod g=rw example.txt
chmod o=rw example.txt

You can modify permissions for multiple classes, such as this example which sets the owner to read/write/execute but the group and others to read/execute:

chmod u=rwx,g=rw,o=rw example.txt

When assigning the same permissions to multiple classes, you can combine them:

chmod u=rwx,go=rw example.txt

But the beauty of using symbolic notation shines when you only want to add or remove the permission for a particular action for a particular class.

For example, this adds the execute permission for the file’s owner:

chmod u+x example.txt

And this removes the write and execute permissions for other users:

chmod o-wx example.txt

Lastly, if you want to apply a particular set of permissions to all files and folders within a particular directory (i.e. a recursive chmod), use the -R option and target a directory:

chmod -R 755 example_directory

While the chmod command looks a bit crazy at first glance, it’s actually quite simple and entirely logical. If you understand the above, you’ve basically mastered chmod!

Learn More About Mastering Linux

Commands like chmod, chown, and chgrp are just the tip of the Linux iceberg. If you’re brand new to the operating system, we recommend checking out these neat tricks for Linux newbies as well as these Linux commands you should never run.

But most importantly, you’d do best by checking out our comprehensive beginner’s guide to Ubuntu and Linux


Ubuntu: A Beginner’s Guide




Ubuntu: A Beginner’s Guide

Curious about Ubuntu, but not sure where to start? Everything you could possibly need to get started with the latest version of Ubuntu is right here, written in easy-to-understand, plain English.
Read More

, which will teach you everything you need to know to get started and familiarized enough to feel comfortable.



via MakeUseOf.com
The Chmod Command and Linux File Permissions Explained