TYPO3 Rich Text Editor RTE: Complete Guide for Editors, Admins and Developers

What Is the TYPO3 Rich Text Editor?

The TYPO3 RTE helps editors format content directly in the backend while keeping the final website output controlled by TYPO3 configuration and frontend styling.

What the TYPO3 RTE Does

• The TYPO3 Rich Text Editor (RTE) is the backend tool used to format rich text fields without writing HTML.
• It helps editors create structured content with headings, paragraphs, bold/italic text, lists, links, tables, email links, and anchor links.

Why Some TYPO3 Fields Look Plain

TYPO3 only shows rich text options when a field is configured to support them.

• Some fields are simple text boxes.
• Some fields open the full RTE toolbar.
• Whether the RTE appears depends on the TYPO3 configuration.

CKEditor 5 in Modern TYPO3

Modern TYPO3 uses CKEditor 5 to provide a cleaner and more flexible editing experience.

• Modern TYPO3 uses rte_ckeditor with CKEditor 5.
• Admins and integrators control the toolbar buttons, formatting options, and available styles.

Why the RTE Matters

A well-configured RTE makes content easier to edit without allowing inconsistent design choices.

• The RTE keeps website content clean, structured, easier to edit, and consistent across pages.
• Editors handle writing and formatting.
• TYPO3 configuration, frontend CSS, and site design rules control the final live appearance.

TYPO3 RTE in 2026: CKEditor 5, TYPO3 v14 LTS and Version Notes

TYPO3 RTE setup should be planned around the site’s current version, support status, and CKEditor compatibility.

Current Version Context

• As of May, 2026, modern TYPO3 RTE guidance should assume CKEditor 5.
• TYPO3 v14 LTS is the current focus for new TYPO3 projects.
• TYPO3 v13 LTS remains relevant for existing websites that are not ready to migrate yet.
• TYPO3 v12 is now legacy because free community support ended on April 30, 2026.

Why This Matters for RTE Setup

RTE behavior can change during TYPO3 Upgrades, especially when custom configuration or editor permissions are involved.

• Review toolbar settings, YAML presets, Page TSconfig, and custom CKEditor integrations.
• Check extension compatibility before upgrading.
• Test backend editing, pasted content, links, tables, and frontend rendering after migration.
• Avoid treating older CKEditor 4-based setups as current best practice.

Practical Recommendation

New and existing TYPO3 projects should choose RTE settings based on the project’s version and upgrade path.

• For new projects, prioritize TYPO3 v14 LTS.
• For existing projects, confirm whether the site is on v13, v14, or an older version.
• For TYPO3 v12 sites, plan an upgrade or arrange ELTS coverage instead of relying on free community support.

Who This Guide Is For

Different TYPO3 users interact with the RTE in different ways, from everyday content editing to deeper configuration and development work.

For Content Editors

• Helps editors format text, create links, use headings, build lists/tables, clean pasted content, avoid broken formatting, and preview content before publishing.

For Admins and Integrators

• Helps admins and integrators manage RTE presets, toolbar buttons, YAML configuration, Page TSconfig, allowed CSS classes, Link Browser options, editor permissions, and clean HTML output.

For Developers

• Helps developers understand how rich text fields are enabled, how custom fields use RTE configuration, how CKEditor 5 affects integrations, why backend and frontend output may differ, and what to check during TYPO3 upgrades.

Main Goal of This Guide

A strong TYPO3 RTE setup should make editing simple for users while keeping the website clean, consistent, and safe to maintain.

• The guide explains both how to use and configure the TYPO3 RTE.
• A good RTE setup keeps website content clean, consistent, editor-friendly, upgrade-safe, and aligned with the website design.

Where the RTE Appears in TYPO3

The RTE appears only in TYPO3 fields that are configured for rich text editing.

Common Places

• Text content elements
• Text & Media elements
• Custom backend fields
• Selected form text areas in newer TYPO3 versions

RTE vs Plain Text Fields

• RTE-enabled fields show a formatting toolbar.
• Plain text fields only allow basic text.
• This is why some TYPO3 fields support links, lists, and styling while others do not.

TYPO3 RTE vs Plain Text Field vs Content Element

TYPO3 uses different field types for different content needs, so the right choice depends on whether the content needs formatting, structure, or layout control.

A plain text field is only for basic input, while an RTE-enabled field gives editors formatting tools. For layout, media, or complex page sections, TYPO3 content elements are usually the better choice.

Everyday Editing in TYPO3 RTE

The TYPO3 RTE gives editors the basic tools they need to structure content clearly without touching HTML.

Headings, Paragraphs and Inline Formatting

• Use headings to divide content into clear sections.
• Use paragraphs for normal body text.
• Use bold for important emphasis and italic for special terms.
• Avoid underline unless it is part of the site’s approved style.
• Press Enter for a new paragraph.
• Press Shift + Enter for a single line break.
• If the content element already has a header field, avoid adding another main heading inside the RTE.

Internal, External, Email and Anchor Links

• Use internal links to connect to other TYPO3 pages.
• Use external links for other websites.
• Use email links when visitors need to contact someone directly.
• Use anchor links to send readers to a specific section on the same page.
• Always check that links work correctly before publishing.

Bulleted and Numbered Lists

• Use bulleted lists for related points.
• Use numbered lists for steps, processes, or ordered instructions.
• Keep list items short so the content stays easy to scan.

Tables for Structured Data

• Use tables only when the information needs rows and columns.
• Add, remove, or merge cells only when it improves clarity.
• Do not use tables to create page layouts.
• Do not place images inside tables; use dedicated TYPO3 content elements instead.

Special Characters

• Use the special character option for symbols such as ©, ®, accented letters, or other characters not available on your keyboard.
• This keeps symbols consistent and avoids copying them from unreliable sources.

Source View and When to Use It

• Use source view only when the button is available and you need to inspect the underlying HTML.
• It can help identify unwanted tags, broken formatting, or pasted code from Word and other editors.
• Most editors will not need source view often, and access depends on the site’s RTE configuration.

TYPO3 RTE Best Practices for Clean Website Content

Clean RTE content depends on structure, consistency, and controlled formatting, not on adding more visual styling inside the editor.

Use Clean Structure

• Use real headings to divide content into sections.
• Do not create fake headings with bold text.
• Keep paragraphs short and easy to scan.
• Use bold only for important emphasis.
• Avoid underline unless it is part of the approved website style.

Keep Formatting Consistent

• Do not add unnecessary colors, fonts, or manual styling.
• Follow the website template instead of creating your own styles inside the RTE.
• Use descriptive link text instead of vague text like “click here.”
• Use tables only for real data that needs rows and columns.
• Preview the page before publishing to check desktop and mobile output.

Paste Content Carefully

• Use Paste as plain text when copying from Word, Google Docs, or another website.
• Remove extra spacing, broken lists, strange fonts, or hidden styles before publishing.

Avoid These RTE Mistakes

• Do not build complex layouts inside the RTE.
• Do not use tables for layout.
• Do not force custom fonts, colors, spacing, or sizes.
• Do not insert images directly unless the TYPO3 setup supports it.
• Do not paste styled content without cleanup.
• Do not add raw embeds, scripts, or custom HTML unless approved by admins.

TYPO3 RTE Configuration Basics

TYPO3 RTE configuration controls which toolbar buttons editors see, which styles they can use, and how rich text content is saved.

Where RTE Configuration Lives

RTE settings are usually managed by admins, integrators, or developers through:

• YAML files
• Page TSconfig
• Sitepackage files
• TCA field configuration

RTE Presets and YAML

TYPO3 can use different RTE presets depending on the editor role and content type. A simple editor may need only basic buttons, while advanced users may need more options.

Example basic YAML toolbar setup:

editor:
config:
  toolbar:
    items:
      - heading
      - bold
      - italic
      - link
      - bulletedList
      - numberedList
      - undo
      - redo

Registering a Custom Preset

A custom preset can be registered from the sitepackage so the setup stays maintainable.

$GLOBALS['TYPO3_CONF_VARS']['RTE']['Presets']['custom_default'] =
  'EXT:site_package/Configuration/RTE/CustomDefault.yaml';

Then assign it with Page TSconfig:

RTE.default.preset = custom_default

Best Practice

Keep the toolbar limited to the options editors actually need. Use smaller presets for regular editors and advanced presets only for users who need more control.

How to Enable RTE for Custom TYPO3 Fields

A custom TYPO3 field shows the Rich Text Editor only when the field is configured as a text field and rich text editing is enabled.

Basic TCA Setup

Use type => text, enable rich text, and assign the right RTE preset.

'custom_rte_text' => [
  'label' => 'Custom rich text',
  'config' => [
      'type' => 'text',
      'enableRichtext' => true,
      'richtextConfiguration' => 'custom_default',
      'cols' => 40,
      'rows' => 15,
  ],
],

When Not to Use RTE

Not every custom field needs formatting.

• Avoid RTE for short labels, SEO titles, metadata fields, technical values, and simple form inputs.
• Use plain text fields when the content must stay simple and controlled.

Why the Field May Show as Plain Text

If the RTE does not appear, the field configuration may be incomplete.

• enableRichtext is not enabled.
• No valid richtextConfiguratio is assigned.
• The field is not configured as type => text.
• The custom preset is not registered.
• YAML or TSconfig has an error.
• User permissions restrict RTE access.

How to Customize the TYPO3 RTE Toolbar

The RTE toolbar should include only the controls editors need for their content workflow.

Basic Toolbar Setup

Manage toolbar buttons in the RTE YAML preset. Keep common options like headings, bold, italic, links, lists, undo, and redo.

editor:
config:
  toolbar:
    items:
      - heading
      - bold
      - italic
      - link
      - bulletedList
      - numberedList
      - undo
      - redo

Role-Based Toolbars

Different editor groups can use different presets.

• Use a simple toolbar for regular editors.
• Use a larger toolbar for advanced editors or admins.
• Assign presets through Page TSconfig or field-level RTE configuration.

RTE.default.preset = editor_basic
RTE.config.tt_content.bodytext.preset = editor_advanced

Advanced Toolbar Options

Add advanced controls only when they support the editing workflow.

• Enable source editing only for trained users.
• Add fullscreen for long-form content.
• Add word count only where editorial limits matter.

Configuring Links in TYPO3 RTE

Links need clear configuration because editors use them often, and poor link handling can affect SEO, accessibility, and user experience.

Use the TYPO3 Link Browser

The TYPO3 Link Browser gives editors a controlled way to create different link types.

• Internal page links
• External website links
• Email links
• File links
• Anchor links

editor:
config:
  toolbar:
    items:
      - heading
      - bold
      - italic
      - link
      - bulletedList
      - numberedList

Add Approved Link Styles

Link classes should come from the website’s approved design system.

• Use classes for button links, arrow links, or highlighted links.
• Do not let editors manually create random link styles.

RTE.default.proc.allowedClasses := addToList(btn-primary, btn-secondary, arrow-link)
editor:
config:
  style:
    definitions:
      - { name: 'Primary Button Link', element: 'a', classes: [ 'btn-primary' ] }
      - { name: 'Arrow Link', element: 'a', classes: [ 'arrow-link' ] }

Write Better Link Text

Good link text should explain where the user will go.

• Use descriptive text such as “View TYPO3 upgrade services.”
• Avoid vague text like “click here” or “read more” when it appears without context.
• Keep link text useful for readers, search engines, and screen readers.

Allowed HTML, CSS Classes and Content Cleanup

This configuration decides which HTML, CSS classes, and pasted formatting are allowed before RTE content is saved and rendered on the frontend.

Control Allowed HTML

Use htmlSupport to allow only the markup editors actually need.

editor:
config:
  htmlSupport:
    allow:
      - { name: 'p', attributes: false, classes: false, styles: false }
      - { name: 'h2', attributes: false, classes: false, styles: false }
      - { name: 'h3', attributes: false, classes: false, styles: false }
      - { name: 'a', attributes: true, classes: true, styles: false }

Define Approved CSS Classes

Only allow classes that already exist in the frontend design system.

RTE.default.proc.allowedClasses := addToList(btn-primary, btn-secondary, table-striped, arrow-link)

Remove Inline Styles

Strip unwanted inline styles from pasted or table-based content.

RTE.default.proc.entryHTMLparser_db.tags.table.fixAttrib.style.unset = 1
RTE.default.proc.entryHTMLparser_db.tags.table.fixAttrib.width.unset = 1
RTE.default.proc.entryHTMLparser_db.tags.table.fixAttrib.height.unset = 1

Keep Pasted Content Clean

Pasted content should not carry hidden formatting from Word, Google Docs, or other websites.

• Use Paste as plain text when needed.
• Remove unnecessary tags, classes, and inline styles.
• Preview the frontend after cleanup.

Backend Preview vs Frontend Output

The TYPO3 backend editor is for content editing, while the live website uses frontend CSS, templates, and TYPO3 processing to control the final design.

Why They May Look Different

• The RTE preview shows an editing view, not the exact frontend layout.
• Fonts, spacing, colors, and responsive behavior are controlled by the website’s CSS.
• TYPO3 may also transform or clean saved RTE content before rendering it on the frontend.

What Editors Should Do

• Use the RTE for structure, not final design decisions.
• Check the frontend preview before publishing.
• Review links, tables, spacing, and mobile display on the live page view.

Images, Media and Embeds in TYPO3 RTE

Images and media need proper layout, responsiveness, and accessibility support, so they should usually be handled outside the RTE text field.

Recommended Approach

• Use dedicated TYPO3 content elements for images, videos, media blocks, and embeds.
• Use Text & Media elements when text and visuals need to appear together.
• Add images inside the RTE only if the TYPO3 setup explicitly supports and controls it.

Why This Matters

• Images inside RTE text can create layout, mobile, and accessibility issues.
• Tables should not be used to place or align images.
• Dedicated content elements make media easier to manage, style, and keep responsive.

Common TYPO3 RTE Problems and Fixes

Most TYPO3 RTE issues come from configuration, permissions, pasted formatting, or differences between backend editing and frontend rendering.

Problem	Likely Cause	Actionable Fix
RTE not loading	Broken YAML, cache issue, or backend configuration problem	Check YAML syntax, clear TYPO3 caches, and reset backend user configuration
Missing toolbar buttons	Toolbar options are restricted by preset or user role	Review the assigned RTE preset and editor permissions
Source view missing	Source editing is disabled for that setup	Enable it only for trained users if needed
Pasted content looks broken	Hidden formatting from Word, Google Docs, or another website	Use Paste as plain text or remove formatting before publishing
Custom styles not appearing	CSS classes are not allowed or not loaded in the RTE	Check allowed classes and the RTE content CSS setup
Links not working	Incorrect link type, broken target, or Link Browser issue	Recreate the link through TYPO3 Link Browser and test it
Tables look different on frontend	Frontend CSS controls table styling	Preview the page and use only approved table styles
YAML changes not applied	Preset not registered, cache not cleared, or wrong file path	Confirm preset registration, file path, and clear caches
RTE works for admin but not editor	Role or permission difference	Compare backend user permissions and assigned RTE configuration
CKEditor plugin issue after upgrade	Old plugin is not compatible with CKEditor 5	Review plugin compatibility and replace outdated CKEditor 4 integrations

TYPO3 RTE and CKEditor 5 Migration Notes

Older TYPO3 RTE setups may need review because CKEditor 5 changed how editor plugins, configuration, and custom integrations work.

What to Check During Migration

• CKEditor 4 plugins do not automatically work with CKEditor 5.
• Review old YAML files and Page TSconfig settings.
• Test custom CKEditor plugins before using them on production.
• Check how pasted HTML behaves after migration.
• Compare backend editing output with frontend rendering.
• Confirm that all TYPO3 extensions depending on RTE behavior support the target TYPO3 version.

Migration Priority

• Start with the toolbar and presets.
• Then review allowed classes, link handling, table behavior, and pasted content cleanup.
• Finally, test real editor workflows so configuration issues are caught before publishing.

Final TYPO3 RTE Checklist

Use this checklist before publishing content and when reviewing the RTE setup for editors.

Editor checklist	Admin / integrator checklist
Heading order is correct.	Correct RTE preset is selected.
Links are tested.	Toolbar is simplified by editor role.
Pasted content is cleaned.	Allowed CSS classes are defined.
Tables are used only for real data.	TYPO3 Link Browser is configured.
No unwanted inline styling is left.	Unsafe inline styles are stripped.
Images or media use the right TYPO3 content elements.	Frontend output is tested.
Frontend preview is checked.	Editor rules are documented.
Mobile view is reviewed before publishing.	RTE configuration is retested after TYPO3 upgrades.

Summary

A well-configured TYPO3 RTE helps editors create clean, structured content while keeping formatting aligned with the website’s design system.

The RTE is useful for everyday tasks such as writing text, adding links, creating lists, using tables, and cleaning pasted content. However, it should be used for content structure, not for building layouts or forcing custom design styles.

For the best results, editors should follow simple formatting rules, preview content on the frontend, and avoid adding images or complex layouts directly inside the RTE. Admins and integrators should keep toolbar options controlled, define approved styles, and review the setup after TYPO3 upgrades.

When the RTE is configured properly, TYPO3 content becomes easier to edit, more consistent across pages, and safer to maintain over time.