Hey @rarguello,
Thank you for sharing this. And @Nick I appreciate your reply here, and I will say that you are definitely not alone in feeling this way about the new change. I completely understand: the source code view inside text blocks was genuinely useful for exactly the kind of fine-grained formatting you're describing (superscript, custom inline HTML, etc.), and its removal is a real workflow change for many users.
Just to provide the full picture: Klaviyo recently migrated the email editor's underlying text editing engine from TinyMCE to a newer system called TipTap. TinyMCE was reaching end-of-life, and the newer engine delivers cleaner output and better copy-paste handling. However, TipTap uses structured formatting instead of raw HTML, so it can’t edit custom HTML inside a text block like the old source view could. From my understanding, this wasn't a casual product decision; it was a necessary infrastructure change. More details are in Klaviyo's official help article on the upgrade.
@rarguello: for the body copy styling issue, here are a few things to try:
- Instead of using <p> or <div> tags alone, try applying inline styles directly in your HTML block to match your body font. For example: <p style="font-family: [YourFont], sans-serif; font-size: 16px; color: #333333; line-height: 1.5;">Your body copy here.</p> — replace the values with whatever your body style settings are.
- Check whether there are conflicting inline styles already in your HTML block. The new TipTap-based editor can sometimes inject additional inline styling into content, which may be overriding your expectations.
- As a best practice, Klaviyo recommends setting all your base styles in the email's main Styles tab first, then using HTML blocks only for the elements that truly need custom code. This keeps your code weight lower and reduces the chance of style conflicts.
- If you want your HTML block content to visually match your body text style as closely as possibly, try sending yourself a test email and use your browser's developer tools to inspect what CSS is being applied to your regular text blocks — then mirror those values in your HTML block's inline styles.
For superscript specifically, there isn’t currently an equivalent built-in replacement for the old source editing workflow in text blocks, so using HTML is still the main workaround. You should be able to use <sup>text</sup> there without issue.
I definitely understand why that’s frustrating, especially if you used source editing regularly. I’d be happy to pass this along as product feedback as well.
Temi@Klaviyo
