HTML & email translation with the links intact

Translate the copy, leave the markup

HTML translation that respects the markup is rare. Most tools either flatten the whole thing into plain text or break the styling. Transept parses the HTML, translates only the text nodes, and reassembles it so the email renders identically — in the new language.

1. I.

   Paste or upload the HTML

   Drop in a transactional email, a marketing template, a landing page export, or any HTML fragment. Inline styles, `<img>` alt text, `<a>` link text, dropped links — all of it is preserved.

2. II.

   Translate, with span and link styling kept

   Text inside a `<span>` keeps its color. A bolded sentence stays bolded. A link reads the localized anchor text but points at the same URL. Hard-won fixes for the formatting drift other tools introduce.

3. III.

   Preview in-app

   See the rendered email or page next to the source. Catch a tone slip or a CTA that needs polishing before it ships to the audience.

4. IV.

   Copy back out, or export

   Copy the translated HTML straight into your ESP — Customer.io, Klaviyo, Mailchimp, SendGrid — or your CMS. The markup is unchanged.

For everyone who ships HTML for a living

Questions, answered without the fluff

• Will it break my inline styles or my tracking pixels?+
  No. The parser treats `style` attributes, `data-*` attributes, hidden tracking pixels, and conditional comments as opaque — they pass through unchanged. Only the human-readable text gets translated.
• What about anchor text on links?+
  Link text is translated; the `href` is not. So a "Read more →" becomes "Lire la suite →" but the URL it points at stays exactly the same.
• Can I translate a full landing page export, not just an email?+
  Yes. Any HTML fragment works — emails, landing pages, support article exports, embed snippets. The same markup-preserving translation runs on all of them.
• Does my CTA copy stay punchy in the target language?+
  You control it. Pin CTA text in your glossary so it gets a single deliberate translation, or steer regenerations with a direction like "shorter" or "more urgent".
• Does Transept work with Customer.io, Klaviyo, Mailchimp, or SendGrid?+
  Yes — for any ESP that lets you paste HTML into a template. Copy your source template, paste it into Transept, translate, then paste the translated HTML back into the ESP. We’re working on direct integrations for the top ESPs; for now the paste workflow is reliable.
• What about Liquid, Handlebars, or other templating syntax?+
  Liquid `{% %}` blocks, Handlebars `{{ }}` variables, and similar templating syntax pass through as opaque tokens — the translator never sees them, the output preserves them exactly. Pin any visible variable names in your glossary if you want a deterministic translation when they appear in fallback text.
• Can I translate a Webflow or Framer landing page export?+
  Yes — any HTML export works. Inline styles, classes, IDs, data attributes — all preserved. Test once with a sample page; once you trust the round-trip, scale to whole campaigns.
• What if my email has dynamic content blocks (CIO segments, Liquid logic)?+
  Static text inside dynamic blocks translates normally; the logic itself passes through. For complex conditional content, translate each branch separately and reassemble in the ESP — or paste the full template at once and the conditional structure is preserved, just translated where text exists.
• Will the email render the same in Outlook after translation?+
  The structure is preserved exactly, so Outlook-specific quirks (conditional comments, table-based layouts, inline styles) survive. Always send a test through Litmus or your own Outlook account before a campaign goes live — that’s a general email QA step, not specific to translation.

Keep reading around this capability

• FeatureBatch translation without the spreadsheet→A 30-file launch kit into 12 languages used to mean a spreadsheet, a project manager, and a week. With batch translation, it’s a queue you…
• FeatureVision Proofread sees what readers see→Some translation problems only show up when the page is rendered — a CTA that ran long and broke the layout, a label that wrapped onto two…
• FeatureA glossary the AI actually follows→Character names, product terms, branded phrases, client-specific vocabulary. Build a glossary once — manually, by upload, or seeded from a…
• Use caseLocalize a landing page, CTA and all→Import the page or paste the HTML. Translate with CTA copy pinned, product terms enforced, and a marketing styleguide steering the tone.…
• Use caseLocalize the launch kit, all of it→Email, landing page, FAQ, release notes, social posts — the assets that make a launch. Run them through Transept as one bundle with a…