{"id":13359,"date":"2026-10-09T23:26:36","date_gmt":"2026-10-09T23:26:36","guid":{"rendered":"https:\/\/resizemyimg.com\/blog\/?p=13359"},"modified":"2026-10-09T23:42:12","modified_gmt":"2026-10-09T23:42:12","slug":"chmod-r-chmod-vs-chown-for-managing-linux-file-permissions","status":"publish","type":"post","link":"https:\/\/resizemyimg.com\/blog\/chmod-r-chmod-vs-chown-for-managing-linux-file-permissions\/","title":{"rendered":"Chmod -R: chmod vs chown for Managing Linux File Permissions"},"content":{"rendered":"

chmod -R<\/code> should be used to change permissions, while chown -R<\/code> should be used to change ownership.<\/strong> Mixing them up is one of the fastest ways to break a Linux site, expose private files, or cause a service to stop writing logs. A careful admin treats recursive permission changes as a sharp tool, not a quick fix.<\/p>\n

TLDR:<\/strong> chmod -R<\/code> changes what users can do with files, such as read, write, or execute them. chown -R<\/code> changes who owns those files and which group controls them. For example, after deploying 18,000 website files, an admin might run chown -R www-data:www-data \/var\/www\/site<\/code>, then set directories to 755<\/code> and files to 644<\/code>. In one common hosting case, correcting ownership first can remove most 403 Forbidden<\/code> errors without making files dangerously writable.<\/p>\n

What chmod -R<\/code> Actually Does<\/h2>\n

chmod<\/code> means change mode<\/em>. It controls file permissions. The -R<\/code> flag means recursive<\/em>, so the command applies to a directory and everything inside it.<\/p>\n

A command like this changes permissions across an entire directory tree:<\/p>\n

chmod -R 755 \/var\/www\/html<\/code><\/pre>\n
That command gives the owner full access, while the group and others get read and execute access. For directories, execute means a user can enter the directory. For files, execute means the file can be run as a program or script.<\/p>\n
The catch is that files and directories usually need different permissions.<\/strong> Applying 755<\/code> to every file may mark plain text, images, and PHP files as executable. It may not break the app, but it is messy and risky. Honestly, it feels like Linux lets one short command create a half-hour cleanup job far too easily.<\/p>\n\"\"\n
What chown -R<\/code> Actually Does<\/h2>\n
chown<\/code> means change owner<\/em>. It changes the user and group assigned to files or directories. The -R<\/code> flag makes it recursive, just like with chmod<\/code>.<\/p>\n
A typical web server command looks like this:<\/p>\n
chown -R www-data:www-data \/var\/www\/html<\/code><\/pre>\n
This sets both the owner and group to www-data<\/code>. That user is often used by Apache or Nginx on Debian and Ubuntu systems. On CentOS, AlmaLinux, or Rocky Linux, the web user may be apache<\/code> or nginx<\/code>.<\/p>\n
chown<\/code> does not grant read, write, or execute rights by itself.<\/strong> It only changes who the permission rules apply to. If a file has mode 600<\/code>, only the owner can read and write it. Changing the owner changes which user gets that access.<\/p>\n
chmod<\/code> vs chown<\/code>: The Core Difference<\/h2>\n