About

Tool No. 33 of Pikkola, first published 19 November 2026

A permission mode is arithmetic wearing letters. One wrong character changes who can rewrite a file, and the machine does not warn anyone.

Why this page exists

Every other notation in a shell shows you something. A path shows its folders, a date shows its parts, a number is a number. A mode like 755 is three sums pressed together, and rwxr-xr-x is the same sums written out. People learn them by repetition, then copy them from an old project when a new one needs a mode, and the shape of the mistake is always the same: one digit too generous, in the direction of 7.

This page is the middle step. Tick the three layers, read the octal, copy the line. The warning under the builder exists for the case that matters, where a mode is open to every account on the machine.

How it reads a mode

Each layer gets one digit: read is 4, write is 2, execute is 1. The nine bits are three additions. A fourth digit in front carries setuid (4), setgid (2) and sticky (1), which is why 4755 is the familiar 755 with one bit added.

The symbolic form is the same nine bits in the same order, one character each, with a dash where a bit is absent. A special bit that lands on an execute bit takes that letter's place in lowercase: s for setuid or setgid, t for sticky. With the execute bit clear it is uppercase, S or T, and the letter means something tighter than it looks.

A umask is a subtraction instead of a value: it is what the system removes from 666 for a new file and 777 for a new directory. That is why umask 022 leaves 644 and 755 behind. It cannot add an execute bit, so the conversion runs one way only in that respect, and the page says so where it matters.

What it does not decide

The page knows the notation, not your server. It cannot tell whether a file needs to be executable, whether the group that owns it is the one that serves it, whether the filesystem is mounted with options that ignore these bits, or whether the service runs as the owner at all. It builds the line; running it is yours.

Two cases get an explicit warning rather than a quiet result. A recursive change from / is flagged, because one paste rewrites every file on the machine. A 777 is flagged, because the permission is almost never what was meant.

What it keeps

Nothing. The mode, the paths and the names live in the tab, and the page has no endpoint to send them to. The Content-Security-Policy sets connect-src 'none', the theme and the language are the only things written to local storage, and the copy buttons write to the clipboard only when pressed. The privacy page has the detail.

Who runs it

Pikkola Lab, a small studio that publishes free tools which run in the browser. You can write to [email protected] about a mode that is missing, a letter it reads wrong, or anything else on this page.

Other tools

Contact

[email protected].