File Permission Explainer
Explain Linux file permission patterns, practical access outcomes, and security posture for files and directories.
Input
Enter a numeric or symbolic permission and choose whether you want to interpret it as a file or a directory.
Result
Permission translation, practical meaning, and security posture for the selected context.
Breakdown
Owner can list directory entries, create, rename, or delete entries, and enter or traverse the directory.
Group can do nothing.
Others can do nothing.
How this behaves
As a file permission set, 700 means the owner can read the file, modify the file, and execute the file, the group can do nothing, and others can do nothing.
As a directory permission set, 700 means the owner can list directory entries, create, rename, or delete entries, and enter or traverse the directory, the group can do nothing, and others can do nothing.
This permission set is broadly balanced for many practical Linux scenarios. It is neither aggressively locked down nor obviously overexposed.
Common presets
Permission interpretation quick guide
The same rwx triplet means different things depending on whether the target is a file or a directory.
Read
For a file, read allows content viewing. For a directory, read allows listing entries.
Write
For a file, write allows content changes. For a directory, write allows creating, renaming, and deleting entries when execute also allows traversal.
Execute
For a file, execute allows running it. For a directory, execute allows traversing or entering it.
Related tools
Use the neighboring permission tools when you need translation or default-mode calculation.