How to Change File Permissions in Linux (chmod Guide)

If you’ve ever stared at a string like rwxr-xr-x and wondered what it means, you’re not alone. Linux file permissions can feel like a secret code, but once you learn how the numbers work, you’ll be able to lock down your files and open them up with confidence—this guide explains the most common numeric permission codes from 600 to 777 with real-world examples like web server directories and shared folders.

File permission bits: 9 positions (rwx for owner, group, others) ·
Common file permission: chmod 644 (owner read/write, everyone else read) ·
Common directory permission: chmod 755 (owner full, group/others read+execute) ·
Recursive flag: -R for folder-wide changes

The table below summarizes the most important chmod facts.

How to use chmod to change file permissions in Linux?

The chmod command is the standard tool for controlling who can read, write, or execute a file. Its numeric mode lets you set all permissions at once using a three-digit octal number.

What is the chmod command structure?

• Basic syntax: chmod [options] mode file (NERSC Documentation).
• Options include -R for recursive changes (NERSC).
• Symbolic mode (e.g., u+x) is also available, but numeric mode is more precise for bulk changes.

How to set permissions using numeric mode (e.g., 755)?

Each digit represents a user class: owner, group, and others. Calculate the digit by adding the values of the permissions you want to grant: read (4), write (2), execute (1).

• For chmod 755 script.sh, the owner gets 7 (rwx), group gets 5 (r-x), others get 5 (r-x) (Swarthmore College Guide).
• To apply to a directory: chmod 755 /var/www/html.
• Use chmod -R 755 /var/www/html to change every file and subdirectory inside it (NERSC).

Bottom line: The numeric mode gives you precise control over every permission bit. For most directories, 755 is the safe default; for regular files, 644 keeps content readable but only editable by the owner.

This understanding forms the base for making secure permission decisions.

What does chmod 777 mean in Linux?

777 is the numeric code that grants read, write, and execute permissions to the owner, group, and everyone else. It’s often used out of convenience, but comes with serious security risks.

What is the difference between chmod 777 and 755?

The only difference is the third permission digit: 7 (rwx) versus 5 (r-x). With 777, any user on the system can modify the file or directory. With 755, only the owner can write.

• chmod 777 myfile – full access for all users (TheServerSide).
• chmod 755 myfile – owner only can write; group and others can read and execute.

When should you use chmod 777?

• Almost never on production systems. Avoid it for any file that contains sensitive data.
• Temporary scenarios on isolated local machines (e.g., a personal virtual machine) where you want to eliminate permission issues quickly.
• For internal USB drives or temporary project folders where no one else has access to the system.

The trade-off: Convenience now vs. a potential security hole later. If you must use 777, limit it to specific files and revert to 755 or 644 as soon as possible.

What is chmod 644 in Linux and when to use it?

644 is the standard permission for most regular files: the owner can read and write, while the group and others can only read. It’s the default for new files on many Linux distributions.

What does chmod 600 do to a file?

• chmod 600 private.key gives the owner read and write permissions, and removes all access from group and others (Swarthmore College Guide).
• This is the recommended permission for SSH private keys, credentials, and any other sensitive data.
• For comparison, chmod 644 config.ini would expose the file to reading by everyone – fine for public settings, not for secrets.

Bottom line: Use 600 for anything that should remain private, 644 for files that need to be readable but not editable by others, and 755 for executable scripts and directories.

These are the three pillars of safe permission management.

How to change file permissions for a folder in Linux?

Changing a folder’s permissions is just like changing a file’s, but you’ll often need the recursive flag to affect everything inside.

How to apply permissions recursively with chmod -R?

• chmod -R 755 /var/www/html sets all files and subdirectories inside /var/www/html to 755 (NERSC Documentation).
• This is common for web server document roots where you want directories to be executable (enterable) but files to remain readable.
• Caution: Recursive 777 on /home or /etc can break system security. Always double-check the path before adding -R.

Always verify the directory path before using recursive flags.

What is the difference between chmod 755 and 777?

The one‑digit difference (5 vs. 7 for the “others” class) changes whether strangers can write to your files. That small change has large security implications.

Which permissions are safe for a web server directory?

• For most web directories, chmod 755 /var/www/html is the standard (Swarthmore College Guide).
• For files served by the web server, chmod 644 index.html works because the web server reads them as “others.”
• Avoid 777 on any directory accessible from the internet – it allows any user to upload or modify files, turning your server into a malware distribution point.

The pattern: Three common codes cover 90% of use cases: 600 (private), 644 (public readable), 755 (public executable). 777 is rarely necessary and always risky.

How to change file permissions in Linux from root to user?

Sometimes you need to transfer ownership before setting permissions, especially when moving files from a system account to a user.

How to transfer ownership before changing permissions?

• Use chown to change the file owner: sudo chown www-data:www-data /var/www/file (Red Hat).
• Then set permissions: chmod 644 /var/www/file.
• If the file originally belonged to root, you must use sudo with chown; once it belongs to the user, you can run chmod without sudo.

Proper ownership combined with correct permissions ensures secure file access.

Step-by-step guide: Change file permissions on Linux

1. Open a terminal and navigate to the directory containing the file.
2. Check current permissions with ls -l.
3. Determine the desired numeric code (e.g., 644 for normal files, 755 for directories).
4. Run chmod 644 filename to apply.
5. For directories, add the recursive flag: chmod -R 755 /path/to/directory.
6. Use ls -l again to verify the change.

Following these steps methodically prevents common permission errors.

These facts are supported by authoritative Linux documentation.

Quotes from the community

“The chmod command modifies the file mode bits of each given file according to mode, which can be either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new mode bits.”

— Red Hat (Official Linux Documentation)

“One common mistake is using 777 for web directories. You should use 755 unless you have a very specific reason. 777 is almost never appropriate on a production server.”

— Stack Overflow Community (Top Answer on Unix Permissions)

For the average Linux user working on a shared hosting server or a home lab, the safest rule is: start with 755 for directories, 644 for files, and only tighten permissions to 600 for secrets. The one code to avoid at all costs is 777 – it might save you one `sudo`, but it can cost you your entire system’s integrity.

If you are new to Linux, learning how to change file permissions in Linux is essential for system security.

Frequently asked questions