# Naming Features Across Languages | Vitra.ai

> Feature names are the terminology decision with the widest blast radius. Which to keep in English, which to translate, and what it costs to change your mind.

**Canonical URL**: https://www.vitra.ai/saas/saas-feature-naming
**Source**: This is the Markdown rendering of https://www.vitra.ai/saas/saas-feature-naming, generated at build time from that page.

---

3 min read

# Naming Features Across Languages

Feature names are the terminology decision with the widest blast radius. Which to keep in English, which to translate, and what it costs to change your mind.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Senior Product Manager , Vitra.ai
Updated Aug 17, 2026

![Naming Features Across Languages](https://www.vitra.ai/static/images/blog/saas-feature-naming.jpg)

Table of contents

[One decision, many surfaces](#one-decision-many-surfaces)

[Product noun or description](#product-noun-or-description)

[Keeping English is not always safer](#keeping-english-is-not-always-safer)

[Record it where it binds](#record-it-where-it-binds)

[Changing a name later](#changing-a-name-later)

[FAQ](#faq)

Contributors

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Senior Product Manager

Subscribe to our newsletter

Subscribe

> **Quick answer —** Decide per feature whether the name is a product noun or a description. Product nouns stay in English everywhere; descriptive names translate. Changing the decision later means re-approving everything that mentions it.[Vitra.ai Universe](https://www.vitra.ai/platform) ships product and customer content in every language.

## One decision, many surfaces

A feature name appears in the interface, the help centre, release notes, onboarding email, the marketing site, sales decks, support macros and the API.

Getting it wrong is not one correction. It is a correction everywhere, in every language, and a period where customers and staff use two names for one thing.

## Product noun or description

That is the test, and it resolves most cases.

Feature name

Treat as

Why

A coined product name

Product noun — keep

It is a name, like a trademark

A capitalised branded module

Product noun — keep

Findable, supportable

"Bulk export"

Description — translate

It describes an action

"Two-factor authentication"

Description — translate

Established local terms exist

An acronym you invented

Keep, but explain once

No local equivalent exists

The failure mode is the middle ground: a lightly branded descriptive name like "Smart Sync" that some markets translate and others do not, producing exactly the inconsistency the decision exists to prevent.

Decide it explicitly and record it.

## Keeping English is not always safer

Teams default to keeping everything in English because it feels lower risk. It is lower effort, which is different.

A descriptive feature left untranslated makes the product read as foreign and makes the feature harder to find in local search — a customer looking for two-factor authentication in German searches the German term.

## Record it where it binds

Pin every decision in a [glossary](https://www.vitra.ai/general/translation-glossary-management) so a general match cannot overwrite it, and hold it in [memory](https://www.vitra.ai/features/translation-memory) so every surface resolves the same way without anyone remembering to check.

That is what makes the interface, the [help centre](https://www.vitra.ai/saas/help-center-translation) and the announcement agree by default rather than by diligence.

## Changing a name later

It happens, and it is expensive. Everything mentioning the old name has to be found and updated in every language, the help centre and the interface fall out of step for however long that takes, and customers keep using the old name for about a year regardless. Budget a rename as a project rather than an edit. Run [quality control](https://www.vitra.ai/features/quality-control) across the corpus after any rename so the stragglers surface, and expect support to see both names for longer than you would like.

## FAQ

**Should feature names be translated?** It depends whether the name is a product noun or a description. Coined and branded names stay in English everywhere; descriptive names like bulk export or two-factor authentication should translate.

**Is keeping everything in English safer?** It is lower effort rather than lower risk. A descriptive feature left untranslated makes the product read as foreign and makes the feature harder to find in local search.

**Where should naming decisions be recorded?** In a pinned glossary so a general translation match cannot overwrite them, and in shared memory so every surface resolves the same way without anyone having to remember.

**What does renaming a feature cost?** Finding and updating every mention in every language, plus a long period where customers and support use both names. A quality pass across the corpus after a rename surfaces the stragglers.

Our blog

## Lastest blog posts

Tool and strategies modern teams need to help their companies grow.

Automotive

[Automotive Brochure Localization by Market](https://www.vitra.ai/automotive/automotive-brochure-localization)
A car brochure is a spec grid, a legal footer and a photo library, all market-specific. What actually has to change, and why the layout decides the schedule.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Aug 18, 2026

Automotive

[Automotive Campaign Localization Across Markets](https://www.vitra.ai/automotive/automotive-campaign-localization)
Campaigns run through national companies and dealer networks, so one master becomes hundreds of files. Where the offer text and the disclaimers actually break.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Aug 18, 2026

Automotive

[Car Service Manual Translation for Technicians](https://www.vitra.ai/automotive/automotive-service-manual-translation)
A workshop manual is read mid-repair by someone with the car on a lift. What that demands of procedures, torque figures and fault codes, in every language.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Aug 18, 2026

[View all posts](https://www.vitra.ai/blog/page/1)

---

## Structured data

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://www.vitra.ai/saas/saas-feature-naming"
  },
  "headline": "Naming Features Across Languages",
  "image": [
    {
      "@type": "ImageObject",
      "url": "https://www.vitra.ai/static/images/blog/saas-feature-naming.jpg"
    }
  ],
  "datePublished": "2026-08-17T00:00:00.000Z",
  "dateModified": "2026-08-17T00:00:00.000Z",
  "author": [
    {
      "@type": "Person",
      "name": "Samhitha J Bhatt"
    }
  ],
  "publisher": {
    "@type": "Organization",
    "name": "Vitra.ai",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.vitra.ai/static/images/vitra-v-logo.png"
    }
  },
  "description": "Feature names are the terminology decision with the widest blast radius. Which to keep in English, which to translate, and what it costs to change your mind."
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://www.vitra.ai"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Saas",
      "item": "https://www.vitra.ai/saas"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Naming Features Across Languages",
      "item": "https://www.vitra.ai/saas/saas-feature-naming"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Should feature names be translated?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "It depends whether the name is a product noun or a description. Coined and branded names stay in English everywhere; descriptive names like bulk export or two-factor authentication should translate."
      }
    },
    {
      "@type": "Question",
      "name": "Is keeping everything in English safer?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "It is lower effort rather than lower risk. A descriptive feature left untranslated makes the product read as foreign and makes the feature harder to find in local search."
      }
    },
    {
      "@type": "Question",
      "name": "Where should naming decisions be recorded?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "In a pinned glossary so a general translation match cannot overwrite them, and in shared memory so every surface resolves the same way without anyone having to remember."
      }
    },
    {
      "@type": "Question",
      "name": "What does renaming a feature cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Finding and updating every mention in every language, plus a long period where customers and support use both names. A quality pass across the corpus after a rename surfaces the stragglers."
      }
    }
  ]
}
```