chmod calculator

chmod 660

chmod 660 gives the owner and assigned group read and write permission while denying all access to other users. It is intended for shared data that trusted group members or processes must update.

Permission breakdown

660 = rw-rw----

Owner6rw-
Group6rw-
Other0---

Try it yourself

Explore chmod 660

The calculator is preset to 660. Compare it with owner-only 600 or add selected access only when users outside the group have a real need.

Live conversion

Enter a permission mode

Use three digits, each from 0 to 7.

Permission bits

Choose permissions

Owner

The file or directory owner

Group

Members of its assigned group

Other

All other users

What chmod 660 means

The owner and group digits are both 6, combining read (4) and write (2). The other-user digit is 0, and no class receives execute permission. A regular file appears as -rw-rw----. Its owner and assigned group can open and modify it, while users outside that group cannot read, change, or run it.

The absence of execute permission identifies the item as data rather than a program. Mode 660 is generally unsuitable for directories because directories need execute permission for traversal. A shared file can use 660 inside a separately configured group-traversable directory.

Collaborative data, logs, and process files

A team can use 660 for a data file that several members must edit without exposing it to every account on the system. Applications can use the same pattern when two trusted processes share a group and both need to update a database export, queue state, or another non-executable working file.

Log and Unix socket permissions are often created by a service rather than maintained manually. Configure the service, its umask, or its socket settings so the desired owner and group mode persists after restart or rotation. A one-time chmod may be overwritten the next time the service recreates the file.

660 compared with 664

Mode 664 grants the same owner and group read-write access but also lets every other local user read the file. That can be reasonable for non-sensitive shared content. Mode 660 closes the file to users outside the assigned group, which is safer for private team data, internal logs, and application state.

Before selecting either mode, verify the file group and the accounts that need write access. If only one person or process should edit the file, chmod 600 is the narrower choice. Do not add group write access as a substitute for correcting mistaken ownership.

660 compared with shared directory modes

Mode 770 gives owner and group read, write, and execute permissions while excluding other users. Its execute bits suit a private shared directory or an intentionally executable file, not ordinary data. Applying 770 to a database or log adds execution capability with no benefit.

For a team directory that remains readable and traversable by other users, chmod 775 provides the directory execute bits and controlled group write access. Configure the directory and the files inside it separately: the container may use 775 while non-executable shared files use 660.

Command example

Apply chmod 660

Use 660 on a non-executable data file whose owner and trusted group both need to read and update it.

chmod 660 /var/data/shared.db

Linux permission guides

Common permissions