cheatsheet

chown Command in Linux: Change File & Directory Ownership (Ubuntu/Debian)

The chown command changes the user and/or group owner of files and directories on Linux. Use it with sudo to fix web roots, deploy trees, and restore ownership after restores or copies.

Published

Updated

Read time 11 min read

Reviewed byDeepak Prasad

chown Command in Linux: Change File & Directory Ownership (Ubuntu/Debian)
About The chown command changes the user and/or group owner of files and directories on Linux. Use it with sudo to fix web roots, deploy trees, and restore ownership after restores or copies.
Tested on Ubuntu 25.04 (Plucky Puffin); chown (GNU coreutils) 9.5; kernel 7.0.0-27-generic
Package coreutils (apt/deb) · coreutils (dnf/rpm)
Man page chown(1)
Privilege root / sudo
Distros

GNU coreutils on Linux, BSD, and macOS (options may differ slightly).

Group-only changes: chgrp.
Related guide

chown — quick reference

Basic ownership

Change the user owner, group owner, or both. Owner is unchanged if omitted; group is unchanged if omitted unless you use the owner:group form.

When to use Command
Change only the user owner sudo chown USER FILE
Change user and group together sudo chown USER:GROUP FILE
Change only the group (user stays the same) sudo chown :GROUP FILE
Change ownership of several files at once sudo chown USER FILE1 FILE2 FILE3
Set owner by numeric UID sudo chown 1001 FILE
Set owner and group by numeric UID:GID sudo chown 1001:1001 FILE

Recursive traversal

Apply ownership to a directory and everything under it. With -R, pick how symbolic links to directories are handled; only the last -H, -L, or -P on the command line counts (-P is the default).

When to use Command
Change ownership of a directory tree sudo chown -R USER:GROUP DIR
If a CLI argument is a symlink to a directory, traverse it sudo chown -R -H USER DIR
Follow every symlink to a directory found while walking sudo chown -R -L USER DIR
Do not traverse symlinks to directories (default) sudo chown -R -P USER DIR

By default, chown changes the target file a symlink points to. Use -h when you need to change the link itself.

When to use Command
Change the symlink inode, not its target sudo chown -h USER:GROUP SYMLINK
Change the referent (default behaviour) sudo chown USER:GROUP SYMLINK

Conditional and reference ownership

Safer updates when you only want to touch files that already match an owner, or when you want two paths to share the same ownership.

When to use Command
Change owner only if the current owner matches sudo chown --from=OLDUSER NEWUSER FILE
Change group only if the current group matches sudo chown --from=:OLDGROUP :NEWGROUP FILE
Copy owner and group from another file sudo chown --reference=REF FILE

Output control

Useful in scripts and when you want a clean log of what actually changed.

When to use Command
Print a line for every file processed sudo chown -v USER FILE
Print a line only when ownership changes sudo chown -c USER FILE
Suppress most file-related error messages sudo chown -f USER FILE

Safety

Block catastrophic recursive runs against / unless you explicitly override the failsafe.

When to use Command
Refuse recursive chown on / (recommended default) sudo chown -R --preserve-root USER /path
Allow recursive operations on / (dangerous) sudo chown -R --no-preserve-root USER /

Help and version

When to use Command
Show brief usage chown --help
Show coreutils version chown --version

chown — command syntax

Synopsis from chown --help on Ubuntu 25.04 (chown GNU coreutils 9.5):

text 
chown [OPTION]... [OWNER][:[GROUP]] FILE...
  or:  chown [OPTION]... --reference=RFILE FILE...

chown updates ownership metadata on disk. It does not change permission bits — use chmod for rwx. Most changes need sudo.

chown — command examples

Essential Change the user owner of one file

After a copy or restore, a file may belong to the wrong user. Set a new owner while leaving the group unchanged.

Run the command:

bash 
sudo chown nobody /tmp/chown-lab/file1.txt

Sample output:

text 
(no output on success)

Check ownership with ls -l:

bash 
ls -l /tmp/chown-lab/file1.txt

Sample output:

text 
-rw-r--r-- 1 nobody root 13 Jul  1 17:44 /tmp/chown-lab/file1.txt

The third field (nobody) is the user owner; the fourth (root) is the group owner.

Essential Set user and group in one command

Web deploys and package installs often need both owner and group fixed at once. The user:group form is the usual pattern.

Run the command:

bash 
sudo chown root:root /tmp/chown-lab/file1.txt

Verify:

bash 
ls -l /tmp/chown-lab/file1.txt

Sample output:

text 
-rw-r--r-- 1 root root 13 Jul  1 17:44 /tmp/chown-lab/file1.txt

Both the user and group columns now show root.

Common Change only the group with a leading colon

When the user is correct but the group is wrong, prefix the group name with : so chown knows you are not renaming the user.

Run the command:

bash 
sudo chown :users /tmp/chown-lab/file1.txt

Verify:

bash 
ls -l /tmp/chown-lab/file1.txt

Sample output:

text 
-rw-r--r-- 1 root users 13 Jul  1 17:44 /tmp/chown-lab/file1.txt

The user stayed root; only the group changed to users.

Common Recursive chown on a directory tree

Use -R when an entire project or upload directory should share one owner and group — common after unpacking tarballs as root.

Run the command:

bash 
sudo chown -R nobody:users /tmp/chown-lab

Verify the tree:

bash 
ls -lR /tmp/chown-lab

Sample output (trimmed):

text 
/tmp/chown-lab:
total 12
-rw-r--r-- 1 nobody users 13 Jul  1 17:44 file1.txt
-rw-r--r-- 1 nobody users  5 Jul  1 17:44 file2.txt
drwxr-xr-x 2 nobody users 40 Jul  1 17:44 subdir
lrwxrwxrwx 1 nobody users  9 Jul  1 17:44 symlink1 -> file1.txt

/tmp/chown-lab/subdir:
total 0

Every file and subdirectory under the path picked up the new ownership.

Common Change ownership only when the current owner matches

The --from option skips files that do not match the current owner. That helps scripts avoid fighting manual fixes.

Run the command when the file is owned by nobody:

bash 
sudo chown nobody /tmp/chown-lab/file1.txt
sudo chown --from=nobody root /tmp/chown-lab/file1.txt

Verify:

bash 
ls -l /tmp/chown-lab/file1.txt

Sample output:

text 
-rw-r--r-- 1 root nogroup 13 Jul  1 17:44 /tmp/chown-lab/file1.txt

If the owner does not match --from, nothing changes and there is no error:

bash 
sudo chown --from=nobody nobody /tmp/chown-lab/file1.txt
ls -l /tmp/chown-lab/file1.txt

The owner stays root because the file is no longer owned by nobody.

Common Copy ownership from a reference file

When two config files should match, --reference copies both user and group from a template file instead of typing names twice.

Run the command:

bash 
sudo chown root:root /tmp/chown-lab/ref.txt
sudo chown nobody /tmp/chown-lab/file1.txt
sudo chown --reference=/tmp/chown-lab/ref.txt /tmp/chown-lab/file1.txt

Verify both files:

bash 
ls -l /tmp/chown-lab/ref.txt /tmp/chown-lab/file1.txt

Sample output:

text 
-rw-r--r-- 1 root root 13 Jul  1 17:44 /tmp/chown-lab/file1.txt
-rw-r--r-- 1 root root 13 Jul  1 17:44 /tmp/chown-lab/ref.txt

file1.txt now matches ref.txt for both owner and group.

Advanced Verbose and changes-only output

-v prints every file touched; -c prints only lines where ownership actually changed. Both are handy in automation logs.

Show all processing with -v:

bash 
sudo chown -v root /tmp/chown-lab/file1.txt

Sample output:

text 
changed ownership of '/tmp/chown-lab/file1.txt' from nobody to root

Show output only when something changes with -c:

bash 
sudo chown -c root /tmp/chown-lab/file1.txt
sudo chown -c nobody /tmp/chown-lab/file1.txt

Sample output (second run only):

text 
changed ownership of '/tmp/chown-lab/file1.txt' from root to nobody

Re-running -c with the same owner produces no lines.

chown — when to use / when not

Use chown when Use something else when
  • You need to change who owns a file or directory (user and/or group)
  • A deploy or restore left files owned by root or the wrong service account
  • You are fixing ownership on a tree with -R after cp -a or rsync
  • You want conditional updates with --from or matching ownership from a template with --reference
  • You only need to change rwx permission bits → chmod
  • You only need to change the group, not the user → chgrp
  • You need ACL entries beyond user/group/other → setfacl / ACLs
  • Ownership should follow NFSv4 or rich ACL policy → export and ACL tools, not plain chown alone

chown vs chgrp vs chmod

chown chgrp chmod
Changes User owner and/or group owner Group owner only Permission bits (rwx)
Typical form USER:GROUP :GROUP or GROUP 755, u+x, …
Privilege Usually needs sudo Usually needs sudo Owner or sudo depending on file

See chmod for modes and chgrp when the user owner is already correct.

Commands that often appear in the same ownership and permissions workflow.

Command One line
chown Change user and/or group owner (this page)
ls List files with owner, group, and mode
id Show UID, GID, and group membership for a user

Browse the full index in our Linux commands reference.

chown — interview corner

What does the chown command do in Linux?

Every file and directory has a user owner and a group owner stored in the inode. The chown command — short for change owner — updates one or both of those fields.

Check current ownership:

bash 
ls -l /etc/hosts

Sample output:

text 
-rw-r--r-- 1 root root 258 Jul  1 12:00 /etc/hosts

The third column is the user owner; the fourth is the group owner. Changing ownership usually requires root or sudo because it affects access control.

A strong answer is:

"chown changes the user owner and/or group owner of files and directories. I read ownership with ls -l and use sudo chown user:group when fixing deploy trees or restored backups."

What is the difference between chown and chmod?

They solve different problems. chown answers who owns the file (user and group names in ls -l). chmod answers what that owner, the group, and others may do — read, write, or execute.

Command Changes
chown alice:dev file Owner alice, group dev
chmod 640 file Permissions rw-r-----

You often use both after a tarball unpack: chown to fix the service account, chmod to lock down secrets.

A strong answer is:

"chown changes who owns the file; chmod changes rwx permission bits. After restores I typically chown to the app user, then chmod to tighten world-readable files."

What does chown -R do?

The -R (recursive) flag applies the ownership change to the named directory and every file and subdirectory under it. It is the usual fix when an entire web root or home tree has the wrong owner.

bash 
sudo chown -R www-data:www-data /var/www/myapp

Combine with --preserve-root so an accidental chown -R against / is rejected. GNU chown prints:

text 
chown: it is dangerous to operate recursively on '/'
chown: use --no-preserve-root to override this failsafe

A strong answer is:

"chown -R walks a directory tree and sets the same owner on every entry. I always double-check the path and rely on --preserve-root to block mistakes on /."

Can chown use numeric UID and GID?

Yes. Symbolic names are readable; numeric IDs are reliable across hosts where usernames differ.

bash 
sudo chown 1001:1001 /srv/data/file

Look up IDs with:

bash 
id -u alice
id -g devteam

NFS and container volume mounts often document ownership by number, not name.

A strong answer is:

"chown accepts UID and GID numbers — I use them when usernames differ between systems or when matching NFS uid maps."

Troubleshooting

Symptom Likely cause Fix
Operation not permitted Not root and not the file owner Run with sudo or change only files you own
invalid user / invalid group Name not in /etc/passwd or /etc/group Create the account/group first, or use a valid numeric UID/GID
cannot access 'FILE': No such file or directory Wrong path or race in a script Fix the path; use -f to suppress the message if missing files are expected
it is dangerous to operate recursively on '/' -R targeted / with --preserve-root Narrow the path; never use --no-preserve-root unless you fully intend to
Symlink owner unchanged but target changed Default dereference behaviour Add -h if you meant to change the link inode
--from appears to do nothing Current owner does not match Confirm with ls -l; adjust --from or drop it
Rohan Timalsina

is a technical writer and Linux enthusiast who writes practical guides on Linux commands and system administration. He focuses on simplifying complex topics through clear explanations.

Related Articles

devops

Git Fix: error cannot open .git/FETCH_HEAD permission denied (Complete Guide)

Learn how to fix the Git error "cannot open .git/FETCH_HEAD: permission denied" during git pull or git fetch. …

12 min readlinux

How to Set SFTP umask in Linux

Learn how to set SFTP umask in Linux with OpenSSH internal-sftp, sftp-server, Match User, Match Group, …

8 min readlinux

Remove dot(.) in Linux Permissions the RIGHT way!

Step by step instructions to remove dot in Linux permission section for file and directory. What is the …

6 min read