Troubleshooting
Advanced Custom Fields Wysiwyg Editor Not Working: Causes and How to Fix It

Short answer
Check the browser console for JavaScript errors and run a plugin conflict test. Then make sure the visual editor is not disabled in your user profile, review the field's Tabs and Delay Initialization settings, and exclude admin scripts from optimisation plugins.
Key takeaways
- JavaScript errors from other plugins are the most common cause.
- A profile setting can hide the Visual tab for one user only.
- Delay Initialization makes the field look plain until clicked.
- Repeaters and the block editor can leave TinyMCE blank until reload.
- Front-end problems usually come from how the value is output.
Why is the ACF WYSIWYG editor not working?
The ACF WYSIWYG field usually breaks because of a JavaScript error, a disabled visual editor in your user profile, field settings such as Delay Initialization or Tabs, a script optimisation plugin, or a TinyMCE problem inside the block editor.
The WYSIWYG field in Advanced Custom Fields is built on TinyMCE, the same editor used by the classic WordPress editor. When it fails, it often fails in one of a few recognisable ways:
- The editor box is blank or grey and you cannot type.
- The Visual tab is missing and only the Text tab shows.
- The toolbar buttons are missing.
- The editor works, but content disappears after saving or looks wrong on the front end.
- The editor breaks after you drag a repeater row or flexible content layout.
Each symptom points to a different cause. Work through the sections below in order, testing after each change.
If you are new to ACF, our guide on how to use Advanced Custom Fields explains field groups and field types first.
Is a JavaScript error stopping the editor?
A JavaScript error from another plugin or the theme is the most common cause, because TinyMCE stops loading as soon as an earlier script fails; check your browser console for red errors.
To check:
- Open the post where the field is broken.
- Right-click the page and choose Inspect, then open the Console tab.
- Reload the page and look for red error messages.
The error message often names the file that failed, such as a script from a slider, form or SEO plugin. That plugin is your first suspect.
The MDN guide to browser developer tools explains the console if you have not used it before.
If you see no useful error, run a conflict test. Deactivate all plugins except ACF, switch to a default theme, and check the field. Then reactivate plugins one by one until it breaks again. Our plugin conflict guide covers this process step by step, including how to do it safely on a live site.
Is the visual editor disabled in your profile?
If only the Text tab shows, check Users > Profile, because the option to disable the visual editor when writing also hides the Visual tab in ACF WYSIWYG fields.
WordPress lets each user turn the visual editor off. It is easy to tick by accident, and it only affects your account, so other users may see the editor working fine.
To fix it:
- Go to Users > Profile.
- Find Visual Editor near the top.
- Untick Disable the visual editor when writing.
- Click Update Profile and reload the post.
If another user reports the problem, check their profile setting rather than yours.
Are the field settings causing it?
ACF's WYSIWYG field has settings for Tabs, Toolbar, media buttons and Delay Initialization, and a setting chosen on purpose can look like a bug.
Open ACF > Field Groups, edit the group and open the WYSIWYG field. Check these settings:
| Setting | What it does | Symptom if set unexpectedly |
|---|---|---|
| Tabs | Shows Visual and Text, Visual only or Text only | One tab missing |
| Toolbar | Full or Basic toolbar | Missing buttons |
| Show Media Upload Buttons | Shows the Add Media button | No way to add images |
| Delay Initialization | Loads TinyMCE only after you click the field | Plain box until clicked |
Delay Initialization is designed to speed up screens with many WYSIWYG fields. The field shows as a simple box and only becomes a full editor when you click into it. People often mistake this for a broken editor. Turn it off if it confuses editors.
The ACF WYSIWYG Editor documentation lists every field setting.
Is the editor blank inside the block editor?
A blank or unclickable WYSIWYG field in the block editor is often a TinyMCE loading issue between ACF and Gutenberg, which can be helped by updating, toggling Delay Initialization, or testing the classic editor.
When ACF field groups sit in meta boxes below the block editor, TinyMCE has to start inside a page that was not designed around it. Timing problems can leave the editor blank.
This is a known type of issue. WordPress core has tracked reports such as Trac ticket #63691 about blank TinyMCE editors with ACF and the block editor.
Things to try:
- Update WordPress, ACF and any related plugins to the latest versions.
- Turn Delay Initialization on or off and compare.
- Move the field group position from Side to Normal in the group settings.
- Test with the Classic Editor plugin to confirm whether the block editor is involved.
If the classic editor fixes it and you prefer that workflow, our guide on going back to the classic editor shows how.
Does it break inside repeaters or flexible content?
TinyMCE can lose its state when a repeater row or flexible content layout is dragged, collapsed or duplicated, which leaves the editor blank or uneditable until the page is reloaded.
TinyMCE editors are tied to their position on the page. When ACF moves them, it has to restart the editor. If another script interferes, the restart fails.
Try these steps:
- Save the post and reload the page after reordering rows.
- Update ACF Pro, since repeater and flexible content handling has improved over time.
- Turn on Delay Initialization for WYSIWYG fields inside repeaters, which reduces the number of editors running at once.
- Use a Textarea field instead if you only need plain text.
Pages with dozens of WYSIWYG fields can also become slow and unstable. If a layout needs many rich text areas, consider fewer, larger fields.
Are caching or optimisation plugins breaking the scripts?
Minify, combine and defer settings in optimisation plugins can break TinyMCE in the admin, so exclude admin pages or the TinyMCE files from optimisation and clear the cache.
Most optimisation plugins only touch the front end. Some apply settings to logged-in users or admin screens as well, and some server-level tools do the same.
Check:
- Whether your optimisation plugin has an option to apply to logged-in users, and turn it off.
- Whether files from
wp-includes/js/tinymce/are being combined or deferred. - Whether a CDN or server tool rewrites admin scripts.
After any change, clear every cache layer. Our guide on how to clear cache in WordPress covers plugin, server and browser caches.
Also try a private browser window. Browser extensions such as ad blockers and grammar tools can inject scripts into editors and break them.
Why does WYSIWYG content look wrong on the front end?
If the editor works but output is wrong, the cause is usually how the value is displayed: get_field and the_field apply formatting, while raw values, escaping and shortcodes behave differently.
Common output problems:
- No paragraphs: you used
get_field( 'name', false, false ), which returns the raw value without formatting. - Shortcodes not running: use the formatted value so ACF applies WordPress content filters.
- Some HTML removed: recent ACF versions escape output from
the_field()for security, which can strip unsafe tags.
A typical template snippet looks like this:
<?php
$text = get_field( 'intro_text' );
if ( $text ) {
echo $text; // already formatted by ACF
}
?>
ACF explains its output escaping changes in its HTML escaping documentation. If you need iframes or scripts, read it before changing anything, because relaxing escaping has security trade-offs.
For more display options, see our guide to displaying Advanced Custom Fields in WordPress.
How do you find the cause when nothing else works?
Turn on WordPress debugging, test on a staging copy with only ACF active, and note the exact versions before contacting ACF support.
A clean test isolates the problem fast:
- Create a staging copy of the site.
- Enable debugging as shown in our guide on enabling debug mode in WordPress.
- Deactivate everything except ACF and use a default theme.
- If the field works, reactivate items one at a time.
- If it still fails, note your WordPress, ACF and PHP versions, plus any console errors.
The WordPress debugging documentation explains the constants you can add to wp-config.
With that information, ACF support or the ACF forum on WordPress.org can usually point to the cause quickly.
Quick fix checklist
Most broken WYSIWYG fields are fixed by one of a handful of checks, so run through them before deeper debugging.
- Check the browser console for errors.
- Untick Disable the visual editor when writing in your profile.
- Review the field's Tabs, Toolbar and Delay Initialization settings.
- Update WordPress and ACF.
- Exclude admin scripts from optimisation and clear caches.
- Test without other plugins and with a default theme.
- Check how your template outputs the value.
If the fields are missing entirely rather than broken, see our guide on ACF fields not showing in the admin.
Frequently asked questions
Why is my ACF WYSIWYG field blank?
A blank field usually means TinyMCE failed to start. Check the browser console for errors, test with other plugins deactivated, update ACF and WordPress, and toggle the Delay Initialization setting. Blank editors are also common after dragging repeater rows, so save and reload the page.
Why is the Visual tab missing in ACF?
Either the field's Tabs setting is set to Text only, or your user profile has the option to disable the visual editor ticked. Check the field settings in the field group, then check Users > Profile and untick the visual editor option.
What does Delay Initialization do in ACF?
It stops the WYSIWYG editor from loading until you click into the field. This speeds up edit screens with many editors. The field shows as a plain box until clicked, which some people mistake for a broken editor.
Why does ACF remove HTML from my WYSIWYG output?
Recent ACF versions escape output from the_field to protect against unsafe HTML. Some tags may be removed. Read the ACF documentation on HTML escaping before changing this behaviour, because allowing more HTML has security trade-offs.
Can a caching plugin break the ACF editor?
Yes. If an optimisation plugin minifies, combines or defers scripts for logged-in users or admin pages, TinyMCE can fail to load. Exclude admin pages and TinyMCE files from optimisation, then clear all caches.
Sources
- WYSIWYG Editor Advanced Custom Fields
- HTML Escaping Advanced Custom Fields
- Ticket #63691 WordPress Trac
- Debugging in WordPress WordPress Developer Resources
- Advanced Custom Fields WordPress.org
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.


