{"id":9359,"date":"2020-10-28T05:50:48","date_gmt":"2020-10-28T02:50:48","guid":{"rendered":"https:\/\/unihost.com\/help\/?p=9359"},"modified":"2026-08-17T12:42:28","modified_gmt":"2026-08-17T09:42:28","slug":"how-to-recursively-change-the-files-permissions-in-linux","status":"publish","type":"post","link":"https:\/\/unihost.com\/help\/how-to-recursively-change-the-files-permissions-in-linux\/","title":{"rendered":"How to Recursively Change the File’s Permissions in Linux"},"content":{"rendered":"

Changing permissions on a single file is easy with chmod. Doing it across a whole directory tree – hundreds of files and folders – is where people get it wrong. The blanket command chmod -R 755 works, but it makes every file executable, which is incorrect for normal web files. This guide covers the recursive commands and, more importantly, the correct way to set files and directories to different permissions.<\/span><\/p>\n

The Basics: chmod -R<\/span><\/strong><\/h2>\n

The -R (recursive) flag applies chmod to a directory and everything inside it:<\/span><\/p>\n

chmod -R 755 \/path\/directory<\/span><\/pre>\n
This sets every file and folder to 755. It’s fine for directories, but files usually shouldn’t be executable – so applying 755 to everything is not what you want for a website.<\/span><\/p>\n
The Correct Way: Files 644, Directories 755<\/span><\/strong><\/h2>\n
Standard, secure permissions are 644 for files (read\/write for owner, read for others) and 755 for directories (which need the execute bit to be entered). Use find to apply each correctly:<\/span><\/p>\n
# set all directories to 755:<\/span>\r\nfind \/path\/directory -type d -exec chmod 755 {} \\;<\/span>\r\n\r\n# set all files to 644:<\/span>\r\nfind \/path\/directory -type f -exec chmod 644 {} \\;<\/span><\/pre>\n
This is the command experienced admins use. -type d matches directories, -type f matches files, so each gets the right permission in a single pass.<\/span><\/p>\n
Changing Ownership Recursively (chown)<\/span><\/strong><\/h2>\n
Permissions and ownership are separate. To recursively change the owner and group – for example to your web server user:<\/span><\/p>\n
sudo chown -R www-data:www-data \/path\/directory<\/span><\/pre>\n
Replace www-data with the correct user for your setup (e.g. nginx, apache, or your username).<\/span><\/p>\n
\n
⚠<\/span><\/p>\n
Never use chmod -R 777. It gives every user full read, write, and execute access, which is a serious security risk and a common cause of hacked sites. If something only works with 777, the real issue is ownership, not permissions \u2014 fix it with chown instead.<\/strong><\/span><\/p>\n<\/div>\n
Quick Reference<\/span><\/strong><\/h2>\n\n\n\n\n\n\n\n\n
Permission<\/span><\/th>\nMeaning<\/span><\/th>\nUse for<\/span><\/th>\n<\/tr>\n<\/thead>\n
644<\/span><\/td>\nOwner read\/write, others read<\/span><\/td>\nFiles<\/span><\/td>\n<\/tr>\n
755<\/span><\/td>\nOwner full, others read\/execute<\/span><\/td>\nDirectories, scripts<\/span><\/td>\n<\/tr>\n
600<\/span><\/td>\nOwner read\/write only<\/span><\/td>\nPrivate config, keys<\/span><\/td>\n<\/tr>\n
777<\/span><\/td>\nEveryone full access<\/span><\/td>\nAvoid \u2014 security risk<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
FAQ<\/span><\/h2>\n
Q: How do I recursively change permissions in Linux? – Use chmod -R for a blanket change, or, better, use find with -type f and -type d to set files to 644 and directories to 755 separately.<\/span><\/p>\n
Q: Why shouldn’t I use chmod -R 755 on everything? – Because it makes files executable, which is incorrect and insecure for normal web files. Files should be 644 and only directories 755.<\/span><\/p>\n
Q: Is chmod 777 safe? – No. 777 gives everyone full access and is a common security hole. If a script needs it to work, the real problem is ownership – use chown instead.<\/span>