Current Permission
{{ fullNumeric }}
{{ fullSymbolic }} Special {{ specialOctal }} Directory File
Presets
Permissions

{{ label }}

Special Bits
Direct Editing
Options
Target
Umask Explorer
umask
File base
Dir base
File →
Symbolic
Dir →
Symbolic
Field Value Copy
Numeric {{ fullNumeric }}
Symbolic {{ fullSymbolic }}
chmod command {{ command }}
ls -l preview {{ lsOutput }}
User / Group / Others {{ uTriplet }} · {{ gTriplet }} · {{ oTriplet }}
Operation Effect Copy
{{ item.operation }} {{ item.description }}

            
:

Introduction:

u g o and rwx triplets on a card

Unix file permissions describe what the owner, group, and others can do with a file or directory. You can express them in octal digits or with letters that stand for read, write, and execute. Converting between these views makes it easier to check commands and explain changes.

Pick bits for each of the three triplets and include setuid, setgid, or sticky when needed. The numeric code and symbolic form update together. You can preview an ls -l style string and a full chmod command before you run it.

When a umask applies it clears permission bits from a base mode at file creation. Use the umask helper to see the resulting octal for files and directories and the matching symbolic form.

The tool helps you plan and explain permission changes. Apply them in a terminal only when you are sure they match your intent and the target path.

Technical Details

Each triplet encodes read, write, and execute as bits with weights four, two, and one. The three octal digits represent user, group, and others in that order. An optional leading digit carries setuid, setgid, and sticky bits with weights four, two, and one.

Symbolic ↔ octal mapping
Scope Symbolic Octal Notes
Userr w x4 2 1 → 0–7Sum of set bits
Groupr w x4 2 1 → 0–7Sum of set bits
Othersr w x4 2 1 → 0–7Sum of set bits
Specialu+s g+s o+t4 2 1 → 0–7Leading digit

Umask basics

A umask clears bits from a base mode. Files often start from 666 and directories from 777. Subtract the mask bitwise to get the resulting mode. For example 022 on files yields 644 and on directories yields 755.

I/O and validation

Inputs and outputs
Input Accepted Families Output Encoding/Precision
Numeric or symbolic modeOctal 0000–07777; u=,g=,o= formsNumeric, symbolic, chmodExact strings
Recursive, verboseBooleansCommand flagsLiteral
UmaskOctal 000–0777File and dir resultsExact strings

Privacy & compliance

No paths or commands are sent anywhere. Results are computed locally.

Assumptions & limitations

  • Symbolic operations follow u/g/o with + − = and respect copies like g=u.
  • Special bits show as s or S and t or T depending on execute.
  • Preview string is illustrative and not a real filesystem query.
  • Umask examples assume typical base modes; systems can vary defaults.

Edge cases & error sources

  • Invalid octal digits are ignored.
  • Empty symbolic groups leave prior bits unchanged unless = is used.
  • Copy operations require a valid source group.
  • Locale formatting does not affect the raw strings.