Choose between the Backend Editor and Frontend Editor
Both Page Builder editors change the same WordPress content. The difference is the working view, not a separate page format.
Which editor fits the task?
| Task | Recommended view | Why |
|---|---|---|
| Reorder complete sections | Backend Editor | The row hierarchy and drop targets are explicit. |
| Diagnose invalid nesting | Backend Editor | Parent and child relationships are easier to inspect. |
| Change several column layouts | Backend Editor | Structural controls remain visible without page decoration. |
| Adjust copy while watching the design | Frontend Editor | The rendered context is immediately available. |
| Check spacing or image crop visually | Frontend Editor, then public preview | It gives faster visual feedback, while preview confirms the saved result. |
| Work on Raw HTML or complex settings | Backend Editor | Dialogs and structure are less obscured by the frontend layout. |
Switch safely
- Finish the component dialog you are editing.
- Save or update the post.
- Switch editor mode.
- Confirm that the expected rows and components are present before continuing.
Do not keep the same page open for editing in multiple browser tabs. A later save from a stale tab can replace newer content.
What the Frontend Editor does not replace
The Frontend Editor is still an editing surface. After using it:
- use the appropriate WordPress save action;
- open Preview or the public URL;
- check responsive widths;
- verify interactions while signed out.
Theme styles, cached output, login state, and third-party scripts can make an editor view differ from the final visitor experience.
When an editor is unavailable
Editor availability can be limited by the current post type or by Page Builder role settings. If Frontend Editor or Page Builder is missing, follow Troubleshoot the builder interface instead of converting the page to another editor.