Layer 1 · Global guidelines

adidas Running
Localization Global Guidelines

The single source of truth. One voice, every language.

00 · How this works

Two layers. One voice.

Layer 1 (this document) defines the global principles. Layer 2 is the local one-pager each language builds: the same principles brought to life in the target language, with real before/after examples. Layer 2 never replaces Layer 1, it applies it. A living glossary holds the fixed terms.

01 · The localization team

Localization at design stage.

The adidas Running Localization Team is a one-of-a-kind in-house team built on the belief that great experiences are local by design.

We make sure that localization is deeply embedded in product, tech, and marketing from the earliest stages of development. This allows us to shape campaigns and features ahead of launch, making sure they connect naturally with users around the world.

As part of the adidas ecosystem, the adidas Running app acts as a digital coach, supporting health, movement, style, and performance while delivering a personal and inspiring experience that keeps users engaged with the brand across touchpoints.

02 · The adidas Running app

A digital coach. A gateway to the community.

The adidas Running app is a digital coach at the heart of the adidas sports and adiClub experience. It supports users before, during, and after each workout with personalized guidance, motivation, and meaningful performance data.

Designed to evolve with its users, the app offers adaptive training plans aligned with individual goals and progress. It motivates through virtual challenges and races, and connects users to a global community through friendly competition, leaderboards, and shared experiences.

Integrated opportunities such as raffles, rewards, points, and exclusive adidas benefits make the app an essential gateway into the adidas Runners community and the adiClub loyalty program.

As an integral part of the adidas ecosystem, the adidas Running app serves as a key channel to engage consumers across multiple touchpoints, combining health, movement, and community while keeping them connected to the adidas experience and fostering deeper, ongoing relationships with the brand.

03 · Tone of voice

A team that supports you. Not one who commands you.

The adidas Running tone reflects adidas brand values and running culture. It should sound like a knowledgeable coach: by your side, never barking orders.

We at adidas keep it simple. We cut through the noise and focus on what matters. Every word has intent. Every message is clear, direct, and confident. We say less, but we mean more. Because simple is powerful.

We are individual, yet inclusive. Rooted in positivity and purpose. Intentional with every word so it feels real, honest, and brings people in. We create a sense of community and belonging, without losing what makes each voice unique. Fresh, never generic. Always human.

We keep it real. Friendly, yet respectful. Conversational, never filled with jargon. We speak like we are right there next to you. Sharing, guiding, inviting. We show energy without shouting. Confidence without ego. We entice, but we do not boast.

We are optimistic. Calm. Encouraging. Always ready when needed, never demanding attention. Clear in what we say. Honest in what we mean. And always moving people forward.

Do
  • Confident, not arrogant
  • Motivating, not exaggerated
  • Human, not robotic
  • Inclusive, not individualistic
Don't
  • Aggressive competitive framing
  • Pressure-based language
  • Judgmental or exclusionary phrasing
  • Individualistic messaging
Before · CTA
Beat all the other users.
After · CTA
Stronger together.

Motivation through progress, not pressure

Highlight progress over time. Reinforce consistency. Celebrate effort, not perfection. A number alone motivates no one, interpret it.

Before · raw data
9:41100%
Summary
8.2 km

Total distance.

Close
After · data with meaning
9:41100%
Run
8.2 km

You ran further than last week.

Share with the crew

Technical localization guidelines for numbers

Define how numeric values must appear according to language and locale conventions. This ensures clarity, consistency, and trust. Once correctly formatted, add context to make the number meaningful.

1. Decimal separators

2. Thousands separators

3. Unit spacing & symbols

4. Number formatting rules

5. Distance units in marketing content

For language-specific number, date and unit conventions, always refer to your dedicated language guidelines.
04 · UX writing principles

Don't translate words. Localize usability.

These principles set the direction. The linguist applies the judgement: cultural rhythm, register and the context of each string decide how they land in practice.

Do
  • Sentence case, always
  • Short sentences, active voice
  • One idea per line
  • Adapt punctuation to local norms
  • Spell out acronyms on first use
Don't
  • ALL CAPS or Title Case for body copy
  • Semicolons and nested clauses
  • & / + symbols where unnecessary
  • Emojis in errors or critical messages
  • Directional references (see above / click right)
Before · CTA
More
After · CTA
View runs
Before · CTA
Click here
After · CTA
Join challenge
Before · CTA
Learn more
After · CTA
Set a goal
Punctuation varies by language. French uses a non-breaking space before ; : ! ?; Spanish opens questions and exclamations with ¿ and ¡; Japanese uses full-width punctuation (、 。). These are illustrative, always follow your dedicated language guidelines for the actual rule.
05 · Mobile-first · language reference

Different languages. Different challenges.

The universal rule first: if a message doesn't work on a small screen, it doesn't work. Beyond that, every language has its own primary challenge.

Languages and cultures differ significantly: some expand in length, others require gender agreement, different word order can affect placeholders and emphasis, and tone can vary from formal to very casual. Some markets expect minimal copy, others need more explanation. Alphabets, symbols, and writing systems can also impact design. This is why you should always adapt, not translate, based on linguistic and cultural realities.

While we aim to sound like one consistent global brand, we operate with a strong local mindset. Shape the voice to your language and culture so users feel the product speaks directly to them. The experience should feel native, personal, and culturally relevant, never like a translation.

For language-specific nuances and requirements, always refer to your dedicated language guidelines.
06 · Placeholders & variables

A variable is not a finished sentence.

Placeholders like {name}, {count} or {distance} carry data the linguist never sees. The sentence around them has to hold for every value, in every language. This is where literal translation breaks.

Reordering is allowed and expected, even when the English source shows another order. The source order is not binding, place each variable where your language needs it.
Do
  • Keep every placeholder token intact and unchanged
  • Always understand what each placeholder represents, and feel free to reorder placeholders within the sentence to match the natural grammar of your language
  • Make the sentence work for any gender or number. Anticipate what will be inserted and adjust grammar accordingly
  • Check case, agreement, and inflection around variables (especially for DE, PL, TR)
  • Test plurals carefully: most languages require more than two forms
  • Don't assume prior localization experience, double-check that placeholders are used correctly and sound natural in context (yes, even if it feels obvious)
Don't
  • Modify, translate, split, or remove any placeholder tokens
  • Keep the original placeholder order if it sounds unnatural in your language
  • Assume the placeholder is neutral; ignoring its meaning can break grammar or context
  • Force a masculine default or singular form if the variable could be plural or gendered
  • Ignore case, agreement, or inflection rules around variables (especially in DE, PL, TR)
  • Rely only on singular/plural English logic. Many languages need more forms
  • Leave sentences that feel unnatural just because they “match the source”
  • Guess how a placeholder behaves (if unclear, check or flag instead of risking errors)
  • Assume everyone will understand placeholders intuitively (yes, even if it seems obvious)
Morphology is per language. Polish has 7 cases and 3 plural forms; Turkish suffixes follow vowel harmony; Korean particles depend on the final letter; gendered languages must agree with an unknown value. When in doubt, restructure so the variable doesn't force a form.
What broken localization looks like

The most common real-world failures, and what causes them.

  • Truncation / overflow — text expands past the UI and gets cut off (DE, FR, FI especially). Cause: no length check against the component.
  • Gender mismatch — a sentence assumes a gender the variable does not carry. Cause: a masculine default forced onto an unknown value.
  • Broken grammar around a placeholder — case or agreement breaks once the value is inserted (DE, PL, TR). Cause: the sentence was built for the English value only.
  • Plural bug — “1 days left” or a wrong plural form. Cause: only singular/plural English logic, missing the language’s other forms.
  • Culture miss — an idiom or reference that does not land, or reads oddly. Cause: literal translation instead of adaptation.
07 · Accessibility & inclusion

Accessibility is usability, preserved across languages.

This is not about translating content. The linguist preserves meaning, clarity, usability and inclusiveness, not just words, so the experience works for everyone.

Do
  • Use common vocabulary in the target language
  • Prefer verbs over abstract nouns
  • Break long sentences when they help comprehension
  • Adapt expressions, do not translate them
Don't
  • Literal translation of English simplicity
  • Over-long sentences (especially DE, FR, IT, PL)
  • Loan words when a local equivalent is clearer
  • Culture-specific metaphors that don't land locally
Inclusion is structural, not decorative. Address the user directly, keep wording gender-neutral by construction, and never assume ability, body or background.
08 · Types of content

Different content, different needs.

Everything so far, tone, transcreation, length, placeholders, accessibility, comes together here. What you localize falls into two families: product copy that removes friction, and marketing copy that creates connection. Read the type before you write a single word, because the same sentence can be right in one place and wrong in another.

What you localize spans UX/UI strings (product) and digital marketing content (marketing), hosted in the app, the app stores, and sometimes the web. Below, the two families and how to give each one your best.

Product · functional + intuitive

The goal is clear, fast understanding. No friction. The user is mid-run, mid-tap, mid-decision, so every word earns its place.

UI / UX copy (app strings)

All the short texts users see and interact with inside the app (buttons, labels, error messages, navigation) that guide them through the experience.

It feels natural, scans in a glance, and is never ambiguous or long.

Before · UI string
Tap here to begin a new running activity now
After · UI string
Start run

Release notes

Short updates in the app stores explaining what’s new or improved in the latest version, designed to motivate users to update.

It sparks curiosity and keeps a positive, energetic tone.

CRM copy: push, in-app, and email

Short user communications (push notifications, in-app messages, emails) used to inform, guide, or motivate users to engage with the app.

CRM (push, in-app, email) sits under Product, not because of where the message comes from, but because of how it is written. The content often originates in marketing (campaigns, launches, promos), and that overlap is normal. What defines the category is the linguistic treatment: functional microcopy that is short, action-led and bound by strict character limits. Keep the marketing intent, apply the product discipline.
Accessibility in CRM and email, everything you need is here

Email accessibility matters because many of our users live with a disability, sometimes one we are not aware of. Writing accessibly reaches them, and it works for everyone: with an average reading age of around 12, we should always write inclusively.

  • According to the WHO, over one billion people live with some form of disability.
  • Globally, at least 2.2 billion people have near or distant vision impairment.
  • Colour blindness affects about 1 in 12 men (8%) and 1 in 200 women (0.5%).
  • An estimated 15% of people have dyslexia, meaning they have trouble reading.
  • By 2050, nearly 2.5 billion people are projected to have some degree of hearing loss.

If our emails are not accessible, adidas loses these users and creates a poor experience for them.

How emails are read

Emails are scanned in a Z or F pattern, and most users spend only about 10 seconds, so the action you want the user to take must be front and centre.

When you write
  • Descriptive and meaningful subject lines: people using screen readers or other assistive tech rely on them to quickly identify the purpose of the email.
  • Clear and concise language: simple words help people with cognitive disabilities or limited reading skills understand the message.
  • Conversational tone: it makes the email easier to read and understand, particularly for people with cognitive disabilities.
  • Descriptive links: say what the link does, “Join Challenge”, never “click here”.
  • Meaningful alt text for images: library images carry alt text at aDL level; for any icon we create, check that meaningful alt text is added.
When you design or brief
  • Left-align copy: it keeps consistent character and word spacing, which people with dyslexia may prefer. Note: this does not apply to right-to-left markets or languages.
  • Give copy space: ample white space eases reading throughout and helps guide people with limited sight.
  • Sufficient contrast: low contrast between text and background is hard to read for people with visual impairments.
  • Test for accessibility: check the content so every user, regardless of disability, can access and understand it.
Handled by the platform (SFMC)
  • Semantic HTML, a text-only version, and keyboard accessibility are managed by SFMC, so the email works with screen readers, low connectivity, and keyboard navigation.

Email, in particular

Email looks like infinite space, but it is not. The subject competes in a crowded inbox and the preheader is the preview right after it; together they decide whether the email is opened, and both get cut off on mobile. The subject (around 30 characters) leads with the most important word, the preheader extends it without repeating, there is one main action, and every zone makes sense on its own. Front-load meaning.

It feels like a friendly team, never an aggressive call to action, and it works for everyone, on any device, with or without assistive technology.

Before · Email subject
Your weekly training summary report is now available to view
After · Email subject
Your week is in
Marketing · emotional + engaging

The goal is to inspire, motivate and create connection. Here you have more room to feel, but never more room to ramble.

Units in marketing: use kilometres only in headers, and kilometres and miles (kilometres first) in body copy, sub-heads and descriptions.

Challenges & virtual races

Inside the Community tab, in-app fitness events where users join activities with specific goals (distance, frequency), designed to motivate participation, create a sense of achievement, and engage the community.

Titles stay short and engaging within strict limits, and may remain in English when specified. Descriptions explain how it works and motivate, very clear and mobile-first, with no long paragraphs.

The title reads like a real event; the description is understood in seconds and makes people want to join.

Campaign cards & raffle cards

Small in-app promotional cards with short, impactful messages that highlight features, offers, or rewards, often linking users to other experiences (the flagship app, blog content, partners, or deeper in-app content).

Pure marketing, highly engaging, with very little space. Carry the core message only, and adapt product names using the adidas e-com references and the project brief.

Impactful and concise, never a literal translation.

App Store content: headlines & images

Marketing visuals used in the app stores to promote the app, including short slogan-like headlines and supporting texts such as mock user names and comments, designed to attract attention and convince users to download.

This is the first impression. Keep it highly engaging and natural, with a strong value proposition. Transcreate, never translate literally, and adapt sample names and comments so they feel local.

It feels native and appealing, and builds trust instantly.

Blog articles

Longer-form content within the app that shares expert tips, training advice, and storytelling around sports, adidas products, campaigns, or community initiatives, designed to inform and engage.

Here readability and expertise matter most. There are no strict space limits, but optimize for mobile reading with short sentences and clear paragraphs, and adapt the structure rather than translating it.

Do not invent content, and validate any cultural addition before it ships.

Special app experiences

Limited-time, campaign-driven in-app experiences that combine storytelling, design, and interactive content to engage users beyond standard app features.

These are hybrid: combine the clarity of product with the storytelling of marketing, always reading the visual design and the user journey as you write.

Engaging and seamless, fully part of the app.

Audiovisual content: subtitles & dubbing

Short videos (athlete features, community stories, campaign clips, occasional training content) designed to inspire, motivate, and engage users within the app.

Follow the specific audiovisual guidelines from this style guide, and protect timing, readability and natural spoken language above a literal match.

The principles behind every type

Whatever the content, the same instincts apply.

  • Keep it short, and mobile-first, always
  • Make it sound native in your language
  • Localize the intent, not the words
  • Understand the context before you translate
  • Adapt, never translate literally
  • Respect character limits strictly

Great experiences are local by design.