How to Secure Joomla File and Folder Permissions
Secure Joomla permissions by giving the web server only the access it actually needs. On typical Linux hosting, directories commonly use 755 and files 644, but ownership and the PHP execution model matter just as much as the numeric mode. Avoid blanket permission changes and never leave the site world-writable as a troubleshooting shortcut.
Back up and identify the hosting ownership model first
Before changing permissions recursively, create a current backup and determine which account owns the Joomla files and which user runs PHP. A site can fail to write even with apparently normal modes when files were uploaded, restored, or migrated under the wrong owner.
- Confirm the Joomla document root.
- Check the owner and group on representative files and directories.
- Ask the host which ownership model it supports if you do not control the server.
Do not use permission changes to hide an ownership problem. Correct ownership is usually safer and more predictable than making files broadly writable.
Apply a least-privilege baseline
For conventional Unix/Linux Joomla hosting, 755 for directories and 644 for files are common starting values. They allow the owner to write while other identities receive only the access normally needed to traverse directories and read site files.
Managed hosting, ACLs, containers, FastCGI/PHP-FPM pools, or deployment systems may support different or tighter modes. Follow the host's documented model rather than forcing a generic recipe.
Do not recursively set the site to 777. World-writable content gives unrelated processes or accounts unnecessary write access and can make a compromise much worse.
Check the directories Joomla must write to
- Sign in to Joomla Administrator.
- Open System → System Information.
- Review the Folder Permissions tab.
- Note any required directory Joomla reports as unwritable.
- Correct that directory's ownership or permission at the hosting layer, then refresh the report.
Do not make every directory writable because one path fails. Cache, logs, temporary storage, media, and extension installation must work, but executable application code should not be writable by identities that do not need to modify it.
Protect configuration.php and executable code
configuration.php contains sensitive site configuration and should not be writable by unrelated accounts. PHP files need to be readable by the runtime but should only be writable by the authorized owner or deployment/update process.
Also remove old archives, database dumps, editor backups, and credential files from public directories. Permissions cannot compensate for leaving sensitive copies exposed through the web server.
Verify Joomla still works after the change
- Load frontend and Administrator pages.
- Upload a test media file if uploads are used.
- Clear Joomla cache and confirm cache/log writing works.
- Test a configuration save.
- Confirm extension update/install operations can write only where expected.
- Recheck ownership after migrations, restores, or deployment changes.
If a normal Joomla operation fails, inspect the exact path and owner instead of loosening the entire site. The goal is a repeatable least-privilege configuration, not the smallest number that happens to work.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.