Troubleshooting
WordPress Theme Editor Not Showing: Causes and How to Fix It

Short answer
On block themes, the theme file editor moved to Tools, Theme File Editor. If it is not there either, DISALLOW_FILE_EDIT in wp-config, a security plugin, your host or your user role has disabled it. Remove the setting or ask your host to restore access.
Key takeaways
- Block themes show the editor under Tools, not Appearance.
- DISALLOW_FILE_EDIT in wp-config.php hides both file editors.
- Security plugins often disable the editor as hardening.
- Only administrators, or Super Admins on multisite, see it.
- Use a child theme or SFTP for safer code changes.
Why is the WordPress theme editor not showing?
The theme file editor usually disappears because a block theme moved it to Tools > Theme File Editor, or because DISALLOW_FILE_EDIT, a security plugin, your host or your user role has switched it off.
Start by checking the Tools menu. Since WordPress 5.9, sites running a block theme show the file editor there instead of under Appearance.
If it is not under Tools either, something is deliberately hiding it. The fixes below cover each cause in order, from the quickest check to the least common.
| Cause | Where to look | Fix |
|---|---|---|
| Block theme active | Tools menu | Open Tools > Theme File Editor |
| DISALLOW_FILE_EDIT set | wp-config.php | Set it to false or remove the line |
| DISALLOW_FILE_MODS set | wp-config.php | Remove it if you need editors and updates |
| Security plugin setting | Plugin hardening options | Turn off the disable-editor option |
| Host restriction | Hosting dashboard or support | Ask the host or use SFTP |
| Not an administrator | Users > Profile | Log in as an admin |
| Multisite network | Network Admin | Use a Super Admin account |
Is the theme editor under Tools now?
Yes, on block themes such as Twenty Twenty-Four and Twenty Twenty-Five, the editor is at Tools > Theme File Editor, while Appearance > Editor opens the visual Site Editor instead.
This move confused many people. The label Editor under Appearance now means the block-based Site Editor, which edits templates visually rather than PHP or CSS files.
The change was discussed on the WordPress core tracker in ticket 54382. The Plugin File Editor moved to Tools at the same time for block themes.
Classic themes still show Theme File Editor under Appearance. If you switch between a classic and a block theme, the menu item moves with it.
How do you check DISALLOW_FILE_EDIT in wp-config.php?
Open wp-config.php with your host's file manager or SFTP, search for DISALLOW_FILE_EDIT, and change true to false or delete the line to bring the editor back.
The line looks like define( 'DISALLOW_FILE_EDIT', true );. It removes both the theme and plugin file editors from the dashboard.
WordPress recommends this setting as a security measure. The WordPress hardening guide explains that it stops attackers from editing code even if they get admin access.
If you cannot find the file, see where to find wp-config.php. The wp-config.php documentation also lists every constant you might see there.
Also look for DISALLOW_FILE_MODS. It hides the editors too, and it blocks plugin and theme installs and updates from the dashboard.
Could a security plugin be hiding the editor?
Yes, many security plugins include a hardening option that disables the theme and plugin file editors, often by adding DISALLOW_FILE_EDIT for you.
Plugins known to offer this kind of setting include Sucuri Security and All In One WP Security. The option usually sits in a hardening or file system section.
Turn the option off, reload the dashboard, and check the menu again. Some plugins remove their wp-config.php line when you untick the box, while others need a manual edit.
Our guide on what a security plugin does explains why these hardening settings exist. Consider turning the protection back on after you finish editing.
Does your host disable the theme editor?
Some managed WordPress hosts disable the file editor on all sites for security, and you may not be able to override it from inside WordPress.
Hosts can set the constant in a file you cannot edit, or block it at the platform level. In those cases, editing wp-config.php does nothing.
Check your host's documentation or ask support. They will usually point you to SFTP, SSH or a Git workflow instead.
Our guide on getting FTP access to WordPress shows where hosts keep these credentials.
Do you have the right user role?
Only users with the edit_themes capability can see the theme file editor, which on single sites means Administrators and on multisite means Super Admins only.
Editors, Authors and Contributors never see the file editor. Check your role under Users > Profile, or ask the site owner.
On a multisite network, site administrators lose access to the editor. A Super Admin can find it in the Network Admin area under Themes.
A role editor plugin or custom code may also have removed the capability from administrators. Look for role management plugins if the role looks right but the menu is still missing.
Can a theme or plugin remove the editor menu?
Yes, a plugin or theme can remove the menu item with code even when the feature is technically enabled, so test by switching themes or disabling plugins.
Admin cleanup plugins and white-label tools often hide menu items to simplify the dashboard for clients. Check their settings for a hidden-menu list.
To test for a conflict, deactivate plugins one by one and reload the admin screen. If the editor returns, the last plugin you turned off was hiding it.
Is your site on WordPress.com or a locked-down plan?
On WordPress.com, the theme file editor is only available on plans that allow custom plugins and themes, so lower plans never show it.
WordPress.com runs a managed version of WordPress. Code access depends on the plan, and the details change over time, so check the current plan comparison on WordPress.com.
Some page builder hosting and website builder services that run WordPress behind the scenes also lock file access. If your dashboard looks different from a standard install, that may be why.
In these cases there is no setting to change inside WordPress. Upgrading the plan or moving to self-hosted WordPress is the only way to get the editor.
What if the editor shows but will not save?
If the editor appears but shows an error when you click Update File, file permissions, a failed loopback check or a PHP error in your change are the usual causes.
WordPress tests PHP edits by making a request back to your own site, called a loopback. If a firewall or security plugin blocks that request, saving fails with a message about being unable to communicate with the site.
Check Tools > Site Health for loopback warnings. Fix those first, then try saving again.
If WordPress says the file is not writable, the server user cannot change it. Your host can correct ownership, or you can edit the file over SFTP instead.
Should you use the theme file editor at all?
For small CSS tweaks it can be handy, but editing PHP files in the dashboard is risky because one typo can crash your site and lock you out.
WordPress tries to catch fatal errors before saving a PHP file, but it cannot catch every problem. If something does break, you will need file access to undo the change.
Safer options include:
- A child theme so updates do not overwrite your changes. See what a child theme is.
- Additional CSS in the Customizer or Site Editor styles for design tweaks.
- A code snippet plugin for small PHP functions.
- SFTP and a code editor for real development work.
Our guide on adding code to WordPress compares these options in more detail.
What should you do after restoring the editor?
Make your change, test the site, and then consider turning DISALLOW_FILE_EDIT back on so the editor is not left open for attackers.
Keep a copy of any file before you edit it. Paste the original into a text file on your computer so you can restore it quickly.
Clear your cache after editing CSS or templates. If changes still do not appear, see our guide on CSS changes not showing.
Hosting guides such as Liquid Web's article on the missing theme file editor cover the same checks, which helps if you want a second walkthrough.
Frequently asked questions
Where is the theme file editor in WordPress 6?
With a block theme active, go to Tools and choose Theme File Editor. With a classic theme, it is under Appearance as Theme File Editor. Appearance, Editor on block themes opens the visual Site Editor, not the code editor.
How do I enable the theme editor in wp-config.php?
Open wp-config.php, find the line that defines DISALLOW_FILE_EDIT as true, and change it to false or delete it. Save the file and reload the dashboard. Also check that DISALLOW_FILE_MODS is not set to true.
Is it safe to enable the WordPress theme editor?
It is safe for careful, short use, but leaving it on gives anyone with admin access a way to change code. Many site owners turn it on for a quick fix, then disable it again. SFTP is a safer long-term choice.
Why can my client not see the theme editor?
The client likely has an Editor or lower role, which cannot edit theme files. Only administrators have the needed capability on single sites. Grant admin access only if the client truly needs it.
What is the difference between the Site Editor and the Theme File Editor?
The Site Editor is a visual tool for changing templates, styles and patterns with blocks. The Theme File Editor shows raw theme files such as PHP and CSS. They serve different needs, and block themes offer both.
Sources
- Hardening WordPress WordPress Developer Resources
- Editing wp-config.php WordPress Developer Resources
- Ticket 54382 WordPress Core Trac
- Sucuri Security WordPress.org Plugins
- Theme File Editor missing Liquid Web
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


