Gutenberg Blocks vs. Classic HTML: The Right Way to Publish a Converted PDF
When you rebuild a PDF as a WordPress page, the converter can output native Gutenberg blocks or clean Classic editor HTML. Both can be fully accessible. The right choice depends on how your team actually edits.
Accessibility is not the deciding factor here, and that is the point. A well-built converter produces WCAG 2.1 AA output either way: real headings, table headers with scope, alt text. The decision is about editing workflow and long-term maintenance. Here is how to choose.
1The Short Version
Choose Gutenberg blocks if
- Your team already edits in the block editor
- You want editors to restyle and rearrange content later
- You use a block theme or block patterns
Choose Classic HTML if
- Your team still works in the Classic editor
- You want portable, semantic markup with no block comments
- You may migrate platforms later and want clean HTML
2What Each Output Actually Is
Gutenberg output wraps content in block markup, the HTML comments WordPress uses to make content editable as blocks. Classic output is plain semantic HTML that renders identically but carries no block wrappers.
<!-- wp:heading {"level":1} -->
<h1>FY 2026 Adopted Budget</h1>
<!-- /wp:heading --><h1>FY 2026 Adopted Budget</h1>
3Accessibility Parity
This is where teams overthink it. The rendered HTML is what assistive technology reads, and both outputs render the same semantic elements: an h1 is an h1, a table with header scope is a table with header scope. Neither format is more or less accessible. What matters is that the converter enforces alt text and correct heading order before publishing, which is a converter question, not a Gutenberg-versus-Classic question. If you want the underlying standard, see our breakdown of WCAG 2.1 AA for government websites.
4The Real Tradeoffs
| Consideration | Gutenberg | Classic HTML |
|---|---|---|
| Later editing | Visual, block by block | HTML or visual editor |
| Portability | Block comments travel with it | Clean, portable markup |
| Restyling | Block styles and patterns | CSS only |
| Migration off WordPress | Needs stripping | Drops in anywhere |
5On Drupal, the Same Logic Applies
If you run Drupal instead, the parallel choice is Paragraphs versus CKEditor 5 HTML, and we cover it in Layout Builder vs. Paragraphs for a converted PDF. The principle holds on both platforms: pick the format your editors will actually maintain.
See both outputs side by side
PDF to WordPress Page shows you the Gutenberg blocks and the Classic HTML for the same document, so you can decide with real output in front of you.
See PDF to WordPress Page