Verystep Guides Verystep Guides
How to Read and Set File Permissions With chmod
A tutorial tells you to run chmod 755 and you don't actually know what that hands out — here's how you check before you run it.

Each permission class — owner, group, and other — adds up its own digit from read at 4, write at 2, and execute at 1. So 644 means the owner can read and write while the group and everyone else can only read, which suits ordinary files, and 755 gives the owner full access and everyone else read and execute, which suits folders and programs. Use the Chmod Calculator both ways: tick boxes to build a value, or type a value in to decode it before you apply it with chmod. Then verify with ls -l and test as the user who needs access.
Set permissions without guessing
You've found a command in a tutorial. It says chmod 755. Or 644. Or, worryingly, 777. Should you run it? Don't guess. Work it out first, in about a minute, with the steps below. They'll tell you who can read a file, who can change it, and who can run it or step into a folder.
- Decide who needs what for owner, group, and other, starting from the least access that still works.
- Tick the read, write, and execute boxes in the Chmod Calculator and read off the octal and symbolic forms.
- Or type an octal value you found in a tutorial into the calculator and read the grid before you run anything.
- Apply the result with chmod followed by the octal value and the file or folder name.
- Run ls -l and read the symbolic string back, position by position, against the grid you expected.
- Test it as the user who actually needs access, not just as the owner who set it.
- If something fails, change one class at a time and retest, so you know which change fixed it.
Here's the arithmetic, because it's simpler than it looks. Each class adds up its own score. Read is 4. Write is 2. Execute is 1. Nothing ticked is 0. So read plus write is 6, read plus execute is 5, and all three make 7. Three classes, three digits. That's an octal value like 644 or 755, and you can now read one at a glance.
Read 644 and 755 like a sentence
Take 644, the setting you'll see on most ordinary files. The first digit, 6, is the owner: read and write, no execute. The next two digits are 4 and 4, so the group and everyone else can read the file but can't change it. In symbolic form that's rw-r--r--. Read it in three chunks of three, owner first, and each position lines up. r means read is on. w means write is on. A dash means that slot is off.
Now 755, the setting you'll see on folders and on programs you run. The owner gets 7, so read, write, and execute. The group and everyone else get 5, so read and execute, no write. Symbolically that's rwxr-xr-x. Same file content, different job, different number. If you can read those two, you can read nearly anything a tutorial throws at you.

Why do folders need execute at all? Because on a folder, execute doesn't mean run. It means enter. Traverse. A folder with read but no execute lets you list the names inside, then stops you opening any of them. Maddening, until you know. That's why folders sit at 755 while the files inside them sit at 644, and why copying a file setting onto a folder breaks things so quietly.
Three faults you'll meet, fixed calmly
First, the script that won't run. You run it and the shell says permission denied, even though you own it and you can read it plain as day. Read isn't enough. A script needs execute for the owner, so you're looking at 744 or 755, not 644. Add execute, test again. Fixed.
Second, the upload folder a web server can't write to. Your site needs the server to save images, and it can't. Here's where people reach for 777, and here's where you shouldn't. 777 hands write access to every account on the machine. On a shared or web server, that's an open door, and it's almost never the right answer. Ask instead which group the server runs as, give that group write, and stop there. 775, maybe. Deliberate, not reflexive.
Third, the folder you can list but can't enter. That's the missing execute bit from the last section, wearing a disguise. Add execute for the class that's stuck. Then retest by actually stepping into the folder, not by admiring the setting from outside it.
Habits that keep you out of trouble
Start tight. You can loosen a setting in seconds when a real need shows up. You can't un-share a file that somebody copied while it sat wide open last week. Least access first isn't caution for its own sake. It's cheaper.
Decode before you run. Any tutorial can contain a typo, and a copied command won't warn you that its number is wider than its own text describes. Ten seconds in the calculator catches that. Skipping those ten seconds? That's how 777 spreads.
And verify as the other user. A setting can look perfect from your account and still fail for the group member or the server process that actually needs it. Log in as them, or test the exact action they need. If it works for them, it works. If it only works for you, it doesn't.
Open the Chmod Calculator and tick the read, write, and execute boxes for owner, group, and other to get the octal and symbolic forms at once. Or type in an octal value from a tutorial and read the grid it produces before you run a single command. It's a ten-second check, and it beats undoing a setting that's too open.
Last verified November 14, 2026 — permission values checked against standard Unix chmod practice: read 4, write 2, execute 1 per class, with 644 for typical files and 755 for typical directories and executables.
Frequently asked questions
What does 644 mean?
It means the owner can read and write the file, scoring 4 plus 2, while the group and everyone else can only read it, scoring 4 each. In symbolic form it reads rw-r--r--. You'll see it on most ordinary files, and it's a sensible default for content that shouldn't be run.
When should I use 755 instead?
Use it for folders and for files you run, like scripts and programs. The owner gets read, write, and execute. The group and everyone else get read and execute. Folders need that execute bit so you can step into them, which is why they don't share the file setting of 644.
Is 777 ever the right answer?
Almost never, and not on a shared or web server. It lets every account read, write, and execute, so anyone can change your files. If a server process needs write access, give write to its group instead and stop there. Don't reach for 777 just because a upload failed once.
Why can I list a folder but not open anything in it?
The folder is missing execute for your class. Read lets you see the names inside. Execute lets you traverse the folder and open them. Add execute for the class that's stuck, then test by stepping into the folder, not just by listing it again.
How do I check a setting after I change it?
Run ls -l and read the symbolic string in three chunks of three, owner, group, then other, and match each chunk against the grid you expected. Then test the real action as the user who needs it. A setting that only works from your own account hasn't passed yet.
More guides

How to Use an Auto Loan Calculator to Compare Two Offers
Two dealers can quote payments that look almost identical and still be selling you loans that cost hundreds of dollars apart. The calculator shows you where the gap hides.

How to Build a Debt Payoff Order: Avalanche vs Snowball, Step by Step
Paying extra money toward debt only works if the extra money has a target. This guide builds that target: an ordered list, made two different ways, so you can see exactly where each spare dollar goes.

How to Project Compound Growth (and Read the CAGR Mode)
This calculator does two jobs in one place: it projects a balance forward at a rate you set, and it works backwards from two balances to the steady rate that links them.