Explain Unix file permission octal

This capability turns the three octal digits into explicit read, write, and execute rights for the file owner, the file's group, and everyone else. It also returns the familiar symbolic form, making it easy to review a permission value before using chmod, documenting a deployment, or investigating an access problem.

Read the three digits by audience

A standard Unix permission octal has three meaningful digits, and each position describes a different audience. The first digit belongs to the owner, usually the user account that owns the file. The second belongs to the group associated with the file. The third applies to others, meaning users who are neither the owner nor members of that group for this access check. Enter a value such as 755 and the result keeps those audiences separate instead of presenting one unexplained number. It reports each original digit, three boolean rights, a short English sentence, and the combined symbolic form. A conventional leading zero is accepted, so 0755 is interpreted in the same way as 755. This tool deliberately focuses on the ordinary three permission classes. It does not interpret a separate leading digit for setuid, setgid, or the sticky bit. Keeping the scope explicit prevents a four-digit special-mode value from being silently described as if it were an ordinary owner, group, and others permission.

Understand how each octal digit becomes rights

Each octal digit is a compact sum of three flags. Read contributes 4, write contributes 2, and execute contributes 1. A digit of 7 therefore means all three rights because 4 plus 2 plus 1 equals 7. A digit of 6 means read and write, while 5 means read and execute. A zero grants none of the three rights. The conversion is performed independently for owner, group, and others, which is why 754 becomes owner read, write, and execute; group read and execute; and others read only. The symbolic result expresses the same information as three rwx triplets. A missing right is shown with a hyphen, so 754 becomes rwxr-xr--. For a regular file, read permits viewing content, write permits changing content, and execute permits running it as a program when the format and system allow that. For a directory, these bits have related but different operational effects, especially execute, which controls traversal. The result explains flags rather than predicting every filesystem operation.

Validate permissions before applying them

Permission mistakes are often small strings with large consequences. Granting write access to others can let unrelated accounts alter a file, while removing execute from a directory can block access even when read is present. Use the explanation as a review step before running chmod, placing a mode in an infrastructure template, or approving a deployment change. The structured fields are also useful in automation: a policy check can inspect the others.write value directly, while a human reviewer reads the matching sentence. Invalid notation fails clearly. Any digit outside the octal range, such as 8 or 9, produces an input error instead of a misleading conversion. Values must otherwise contain exactly three permission digits, with only an optional conventional leading zero. The capability does not inspect a real path, account membership, access-control lists, umasks, mount options, or ownership, so it cannot promise that a particular process will gain access. It explains precisely what the supplied basic mode says and leaves environmental authorization checks to the operating system.