Superscript Removed in New Klaviyo Editor — Workarounds or Code Recovery Options?

​@Cindy Keyes Hi there! 

Great question here, and you're definitely not alone — this has been one of the most common frustrations since the editor upgrade.

To quickly summmarize: Klaviyo replaced the old text editor (TinyMCE) with a new one called TipTap, and in the process the source code view was removed from text blocks, table blocks, and split blocks. So inline HTML like the <sup> tag can't be typed directly into text blocks anymore. The dedicated HTML block still supports raw code though, which is now the supported path for this kind of formatting.
 

Getting your old code back

You can recover the HTML from any existing template by going to Content > Templates, clicking the three-dot menu on the template card, and selecting Export Template. That gives you the full rendered HTML you can pull your superscript markup from. Just don't try to re-import the export — it's best used as a reference to copy specific snippets from.
 

The recommended approach going forward

You don't need to rebuild your whole email in HTML. The cleanest workflow is to keep everything in standard drag-and-drop text blocks, and drop in an HTML block for any line that needs superscript formatting. One important tip: keep the full sentence inside the HTML block rather than splitting it between a text block and an HTML block. Splitting mid-sentence creates spacing and rendering inconsistencies across email clients.

Before going the HTML route, try pasting the Unicode trademark or registered mark symbols directly into a standard text block. They're standard UTF-8 characters that Klaviyo supports. Whether they render as true superscripts depends on the email client and font, but for a lot of brands it looks close enough and saves the hassle.
If you're dealing with superscripts throughout most of your emails, a hybrid email template is probably the most scalable approach. It gives you full HTML control over the coded portions while keeping drag-and-drop regions for your team to edit without touching code. The help article on creating hybrid templates covers the setup: How to create a hybrid email template
 

On the product side — native superscript and subscript controls in the text editor toolbar have been submitted as feedback by multiple people. I don’t have a specific timeline to share, but if you haven't used the in-app feedback option yourself, adding your voice helps.

Hope this gets you unblocked! Would love to hear from others whether the full-sentence HTML block approach has been rendering consistently in your testing.

 

Temi@Klaviyo