Overview
File and folder permissions control who can read, write, or execute files on your hosting account. Incorrect permissions are a common cause of website errors. This guide explains how to change permissions using the cPanel File Manager.
Understanding Permission Numbers
Permissions are represented by a three-digit number (e.g., 644, 755):
- 644 — Standard for files: owner can read/write, others can read only.
- 755 — Standard for folders/directories: owner can read/write/execute, others can read/execute.
- 600 — Restrictive: only the owner can read/write (useful for config files).
- 777 — Full access for everyone (avoid this — it is a security risk).
Step-by-Step Instructions
- Log in to cPanel using your account credentials.
- Under the Files section, click on File Manager.
- Navigate to the file or folder whose permissions you want to change.
- Right-click on the file or folder and select Change Permissions from the context menu.
Alternatively, select the file/folder and click the Permissions button in the toolbar at the top. - In the Change Permissions dialog, check or uncheck the boxes for Read, Write, and Execute for each category (Owner, Group, World). The numeric permission value updates automatically.
- Click Change Permissions to save.
Recommended Permissions for Common Applications
- WordPress: Folders
755, files644,wp-config.phpset to440or600. - General websites: Folders
755, files644.
Important Notes
- Never set permissions to
777— this allows anyone to modify your files and is a serious security vulnerability. - If your website shows a 500 Internal Server Error or a 403 Forbidden error, incorrect file permissions are often the cause.
- Changes take effect immediately — no restart is required.
Troubleshooting
- 403 Forbidden error: The file or folder may have permissions set too low (e.g.,
600on a publicly accessed file). Set files to644and folders to755. - 500 Internal Server Error: Check that folders are set to
755and PHP files to644. A000or777permission can also cause this. - Cannot save changes: Ensure you are modifying the correct file and that your cPanel account owns the file.