HTML Translate

HTML translate="no": When and How to Use It

The HTML translate="no" attribute is a small feature that solves a very practical problem: some parts of a page should not be translated.

If you localize HTML content, this attribute can help protect brand names, codes, and specific terms that must stay unchanged across languages.

What does translate="no" do?

It signals that the content of an element should not be translated.

Example:

<span translate="no">HTML Translate</span>

In this example, the product name stays unchanged even if the surrounding sentence is translated.

When should you use it?

Use translate="no" for content such as:

  • brand names
  • product names
  • SKUs and serial numbers
  • legal entity names
  • code fragments
  • UI terms that must remain in one language

When should you not rely on it alone?

translate="no" is helpful, but it is not a complete localization strategy.

It does not replace:

  • consistent terminology management
  • HTML-aware translation workflows
  • browser testing after translation
  • review of attributes and links

Think of it as a protective hint, not a full translation system.

Example in context

<p>Translate your site with <span translate="no">HTML Translate</span> in minutes.</p>

A correct translated result keeps the brand name intact while translating the rest of the sentence.

Common use cases

Protecting brand names

Brand terms are often mistranslated when they look like normal words.

Preserving technical tokens

If a page contains short command names, product tiers, or license codes, translate="no" can help keep them stable.

Mixed-language interfaces

Some apps intentionally keep parts of the UI in English. In that case, the attribute prevents over-translation.

Important limitation

Even if you use translate="no", you still need a safe HTML translation workflow. The attribute does not protect the rest of the document from broken structure, misplaced tags, or translated technical attributes.

Best practice

Use translate="no" together with these rules:

  • translate only visible page text
  • do not translate class, id, or data-*
  • preserve inline tags
  • test the output in a real browser

For the broader workflow, see How to Translate HTML Files Without Breaking Layout and Translate HTML Code Without Breaking Tags.

More guides

Looking for more? Visit the full HTML Translate blog.