WordPress Block Editor vs Classic Editor: Differences and How to Choose

The WordPress block editor builds a post from separate blocks for paragraphs, images and tables, while the classic editor lets you write in one continuous editing area. For a new blog with varied layouts, learning the block editor is a practical starting point; if you depend on existing draft formats or features built for the old editing screen, the classic editor may suit your workflow after checking theme and plugin compatibility.

What are the block editor and classic editor?

The block editor and Gutenberg

A block is a small building unit of a post. Use a Paragraph block for an explanation, an Image block for a photo and a Heading block for a section heading, then select each unit to move or configure it. The block editor became the default with WordPress 5.0 in December 2018. The official block editor guide explains the workspace and its main controls.

This editor is also commonly called Gutenberg. However, the Gutenberg plugin is a separate plugin that makes newer editing features available ahead of their inclusion in WordPress. You do not need to install it for ordinary block editing.

The classic editor and Classic Editor plugin

The classic editor works more like a word processor: write in one main area and use a toolbar to format text or insert links and images. Its Visual tab provides visual editing, while its Text tab exposes HTML. HTML, or Hypertext Markup Language, describes the structure of a web document.

Classic Editor is the official plugin that restores the previous post editing screen. It is different from the Classic block inside the block editor. The Classic block is one block within the content; the plugin changes the post editing interface itself.

Also distinguish the post editor from the Site Editor. The former edits an individual post, while the latter works with headers, footers and templates when using a block theme. A classic theme can still use the block editor for posts. Installing Classic Editor does not turn a block theme’s site editing tools into a classic interface.

How does writing the same post differ?

Imagine a practice draft called “Indoor plant care.” It contains an introduction, a “Watering” heading, one photo, a supplies list and a table with two entries: “Light / Indirect light near a window” and “Water / Check the soil.” This is an editing exercise, rather than plant care advice.

Writing with the block editor

1. Open Posts → Add New, enter “Indoor plant care” in the title field and type the introduction in the content area. Press Enter to continue with another paragraph.
2. Use the + block inserter to add a Heading block containing “Watering.” Set this section heading to H2. There is no need to repeat the post title as an H1 in the body.
3. Add an Image block and upload a photo you have prepared or select one from the Media Library. Enter descriptive alternative text and check its size and alignment.
4. Add the supplies in a List block. Create a Table block with two columns and two body rows, then enable its header section to make three rows in total. Put “Item / Note” in the header and the two sample entries in the body rows.
5. Check the order of headings, paragraphs, image, list and table in List View. Select the image and try moving it with the block controls, then save the draft and preview it.

The key difference is selecting individual pieces instead of treating the entire post as one editing area. The Table block includes controls for rows and columns. To place text alongside a photo, you can use a Columns block, but also check the stacking order on narrow screens.

Writing with the classic editor

1. Enter the same post title in the title field, then write the introduction in the Visual tab.
2. Type “Watering” on its own line, select that paragraph and choose Heading 2 from the formatting menu. Making text bold does not give it a heading’s document structure.
3. Position the cursor where the photo belongs and select Add Media. Check the image, alternative text, size and alignment before inserting it. Use the toolbar’s list control for the supplies.
4. If the default toolbar has no table insertion control, add the table as HTML in the Text tab or use a compatible plugin that supplies table tools. Installed plugins can change the toolbar.
5. Save the draft and preview the heading, photo, list and table to check their order and appearance.

To practice adding a table in the classic editor’s Text tab, paste this complete example at a separate position at the end of the content, outside any image or list markup. In the block editor, place the same code in a Custom HTML block for comparison.

<table>
  <thead>
    <tr><th scope="col">Item</th><th scope="col">Note</th></tr>
  </thead>
  <tbody>
    <tr><td>Light</td><td>Indirect light near a window</td></tr>
    <tr><td>Water</td><td>Check the soil</td></tr>
  </tbody>
</table>

The expected preview is a two-column table with one header row and two data rows. Borders, colors and width depend on the theme; this code does not automatically become a Table block. To undo the exercise, remove the table markup or HTML block from the practice draft.

Both editors can use HTML and shortcodes

The block editor accepts markup through a Custom HTML block. Choose a Code block when you want readers to see the code, and Custom HTML when you want it to produce page elements. Permissions and security settings can remove some tags on saving, so check the saved result.

A shortcode is a short instruction that calls a feature supplied by a plugin or another component. Use a Shortcode block in the block editor, or enter the shortcode in the classic editor’s body. Switching editors does not remove the requirement for the theme or plugin that provides that feature.

Features, strengths and limitations

In the table, CSS means Cascading Style Sheets, the language that controls presentation such as colors and spacing. A meta box is an additional input panel in the editing screen, often used for plugin settings.

Block editor benefits and learning points

Blocks make it easier to change individual elements and build tables, buttons and columns with core tools. A repeated combination of headings, descriptions and buttons can become a pattern. Understand the difference with synced patterns: editing one can affect other places where the same pattern is used.

Beginners may confuse post settings with block settings or struggle to select an element inside nested columns. List View helps expose that structure. If you add many block plugins, their maintenance and compatibility become part of running the site too.

Classic editor benefits and limits

A continuous writing area and familiar toolbar may feel simpler for people who mostly write prose. It can also preserve workflows based on existing HTML templates and old editing-screen meta boxes.

More complex layouts may require HTML, CSS or separate tools. A text-heavy blog is not automatically faster to write in the classic editor: familiarity, article structure and installed features all affect the time required.

Which editor fits your blog?

• Starting a new blog: first learn Paragraph, Heading, Image, List and Table in the default block editor. You do not need elaborate layouts immediately. If you plan to use a block theme, learn how post editing relates to site editing.
• Mostly text and photos: both editors can work well. Build the same draft in each and compare the tasks you repeat, such as revising paragraphs, moving photos or changing tables.
• Many introduction pages or repeated layouts: consider blocks and patterns first. Assess the result in your current theme and on mobile, rather than judging only by the editor canvas.
• Existing HTML drafts or dedicated integrations: keeping the classic editor may be reasonable. Check whether those features support block editing and whether your theme meets Classic Editor’s requirements.

Choose according to repeated tasks and maintenance costs, rather than novelty or popularity alone. Compare in a copied environment with the same theme and plugins, changing only the editor. Changing the theme at the same time makes the source of a difference harder to identify.

Installing Classic Editor and choosing an editor

These steps assume a self-hosted WordPress installation, permission to install plugins and a classic theme. The official Classic Editor listing says it does not support block themes and full site editing. If settings are missing or the interface does not change on a block theme, check that limitation before assuming a fault. Managed services such as WordPress.com may restrict plugin installation by plan or administration policy.

1. Back up and record the current setup. Back up the database and files, and note the active theme, plugins and default editor settings. First test in staging, a separate test copy of the site, before changing the live site.
2. Go to Plugins → Add New Plugin and search for “Classic Editor.” Compare the plugin and author with the official distribution page, then install and activate it.
3. Under Settings → Writing, select the default editor for all users. Choose classic to retain the existing classic workflow, or block if new posts should begin with blocks.
4. Choose whether to allow users to switch editors. Enable switching and save if you want to compare per post. On a shared site, agree with the team on how to handle mixed editing workflows.
5. Open Posts → All Posts, check the available editing links and open a practice draft. Depending on the version and settings, use links in the post list or the editing screen’s switch menu. When permitted, a post reopens in the editor last used for it.
6. Check both a new post and an existing post. Changing the default does not convert every existing article into individual blocks. Preview the results before applying the approach to live content.

If the settings are absent, check permissions, the theme type and other plugins that control editor availability. A multisite network administrator may restrict these settings. Identify the restriction before installing several competing plugins to force a change. Menu wording and placement can vary with WordPress, plugin versions and the hosting environment.

Switching existing posts and restoring them safely

The Classic block and Convert to blocks

An older classic post opened in the block editor may appear inside a Classic block. You can edit it there or choose “Convert to blocks” to split the content into elements such as paragraphs, headings and images. Enabling the block editor and converting the stored content into individual blocks are separate actions.

Complex tables, custom HTML and older plugin formatting may not split exactly as intended. Check the content and layout after conversion; keeping some material in a Classic or HTML block can be appropriate. There is no need to bulk-convert existing posts that already display correctly.

In the other direction, editing a block post in the classic editor can change its structure or attributes. Blocks store comments and settings as well as HTML. Removing those in the Text tab or reprocessing formatting can lead to recovery prompts when the block editor opens the post again. Some dynamic blocks also depend on plugin execution and cannot be replaced by simply copying HTML.

A check and recovery procedure

1. Avoid saving directly over live content. Obtain a restorable backup and record the title, body, excerpt, featured image, category and public URL. Use staging or a separate practice draft.
2. Start with one representative post. Include tables, images, captions, lists, shortcodes and additional blocks, rather than testing only plain text. Keep the original page for comparison.
3. Make one change at a time. Switch the editor or convert one Classic block, then save. Do not combine this with theme replacement or plugin cleanup.
4. Compare the preview or public page. Check heading levels, links, image alt text, table columns, shortcode output and mobile wrapping. Content being visible in the editor does not prove that its functionality works.
5. Stop further saves if something is wrong. Before saving, Undo may help. After saving, inspect an available revision from before conversion and restore it, or use a backup. Revision retention depends on site settings; revisions do not restore all files and plugin settings.
6. Restore content and settings separately. Restore the required body, then return the default editor and related settings to their recorded values and check again. Deactivating Classic Editor does not undo changes already saved to the content. Decide whether to proceed with other posts only after checking recovery.

Frequently asked questions

Which editor is used more?

There is no single reliable figure here for the current share of all WordPress users. In the official 2023 WordPress survey, 60% of respondents reported using Gutenberg. That describes 2023 respondents, rather than an exclusive worldwide market share in 2026; people can use both editors. In October 2026, the Classic Editor listing displayed over eight million active installations, but installations are neither people nor a count of sites using only that editor.

Will switching editors improve SEO or speed?

The editor’s name does not guarantee better search engine optimization (SEO) or speed. Assess the final page, including readable content, clear titles and useful links, as discussed in Google’s SEO Starter Guide. Themes, images, scripts, ads and added blocks can affect loading. Measure the same content under the same conditions, and distinguish the responsiveness of the administration interface from visitors’ page loading speed.

Can a classic theme use the block editor?

Yes. “Classic theme” describes the theme’s architecture, not the editor used for posts. Support for wide alignment, colors and editor styling varies by theme. The Site Editor separately requires a block theme.

Can different posts use different editors?

In a supported setup, Classic Editor’s switching option allows an editor to be chosen per post. That does not guarantee that repeatedly saving the same article in both editors will preserve everything. Keep existing content in a compatible workflow and test a copy before adopting another approach.