Localisation 5 August 2026
Localisation Style Guide: Keeping a Brand’s Voice Across Languages
Why should the same brand speak with the same voice in every language? We look at what a localisation style guide contains, the rules that govern writing for the web and how the guide relates to the termbase.
When a brand is carried into dozens of languages, it has to keep the same personality in each of them: the same tone, the same level of courtesy, the same clarity. The document that makes this possible is the localisation style guide. A style guide tells translators what tone to write in, how to address the user and which expressions to avoid. Without one, different pages of the same product speak with different voices and the brand falls apart.
Contents
This article looks at what a style guide is, why it is needed, what it contains and which special rules apply to text written for the web. We also consider how the style guide relates to the termbase and why keeping it current matters. Our aim is to present the document not as a formality but as a genuine instrument of consistency.
What is a localisation style guide?
A localisation style guide is the document that gathers the language and formatting decisions taken for a brand or a project. During the preparation phase of quality assurance it is handed to testers and linguists together with the localisation kit. Its purpose is to make translation produced by many different people look as consistent as if it had come from a single hand. This matters both for the credibility of the brand and for the user experience.
The guide is not a document that imposes rules but a contract that establishes a shared expectation. It is where a translator learns whether to use the formal “siz” or the familiar “sen”, how to format a date and how freely a slogan may be rendered. Every decision then rests on a framework agreed in advance instead of being argued out case by case.
Style guides come in several kinds. There are monolingual guides written for the language of the source text, guides specific to a brand and guides aimed directly at localisation. Organisations such as Apple, Microsoft and Mozilla publish their own guides; these are valuable models for the industry. On a small project even a simplified version of such a document makes a large difference, because it settles most of the decisions from the outset.
Why is it needed?
Localisation projects usually involve a large number of people. Different translators, reviewers and testers work on different parts of the same product. If everyone writes according to personal preference, the result is inconsistent: a formal tone on one page and a friendly one on the next; “e-mail” in one place and “mail” in another. A style guide prevents this scattering.
Consistency is not merely an aesthetic concern. In quality evaluation, a good localisation is expected to look “locally produced” in the target culture. That calls for alignment with the writing conventions already established in the target language. The style guide puts those conventions in writing rather than leaving them to the translator’s intuition. The product then becomes natural text that does not smell of translation.
A style guide also saves time. Without one, every translator makes the same decisions from scratch and reviewers make the same corrections over and over. A shared framework removes this repetition and keeps argument to a minimum. Over the long run the guide is an investment that lowers cost and raises quality at once; it is built once and repaid on every project.
What does a style guide contain?
A good style guide covers many layers of language and form. A typical guide includes the following components:
- Form of address and overall tone (formal, friendly, neutral).
- Sentence length and readability rules.
- Date, time, number and currency formats.
- Expressions, clichés and jargon to be avoided.
- Use of the brand name and of elements that are not to be translated.
The table below summarises the main sections of a style guide and the question each of them answers. The scope of a guide may widen or narrow according to the project.
| Section | Question it answers |
|---|---|
| Tone and form of address | How do we speak to the user? |
| Formatting | How are dates, numbers and units written? |
| Word choices | Which term, which expression? |
| Brand elements | What must not be touched? |
Rules for writing for the web
Web text is read differently from print. Users read more slowly on screen than on paper and most of the time they scan the text instead of reading it; they run their eyes over the page until they find what they are looking for. A style guide for the web therefore asks that text be short, clear and scannable. Sentences are kept short and each of them carries a single idea.
Another principle of web writing is the inverted pyramid: the most important information comes first and the details are left to the end. The user is addressed directly, positive language is preferred and clichés such as “click here” are avoided. An informative register is held to be more effective than a sales-driven one; it improves both readability and recall.
These rules are not arbitrary; they rest on how the user reads a screen. People generally do not read web text from beginning to end, they scan it. Paragraphs are therefore kept short, each paragraph carries a single idea and the most important information is placed in the opening sentences. Repetitive or numerical information is moved into tables and lists. By turning these principles into rules, the style guide makes the text work on screen.
Brand voice and consistency
A brand’s voice is the personality that sets it apart from its competitors. The style guide defines that voice and keeps it intact from language to language. Preserving a brand voice does not, however, mean carrying it unchanged into every culture. The tone is sometimes fine-tuned to the expectations of the target culture; the aim is to make the same personality credible in different cultures.
This balance is the most delicate part of a style guide. A guide that is too rigid can condemn the translator to text that reads oddly in the target culture; a guide that is too loose loses consistency. A good guide states plainly which elements are fixed and which are flexible. The translator can then work freely, knowing exactly where the limits lie.
Protecting a brand voice is also a matter of not letting translation turn into a mechanical operation. A slogan or a creative headline can lose its spirit when it is rendered word for word. The style guide states how much creative licence such texts allow. The translator can then produce a version that keeps the brand’s personality while creating the same effect in the target culture. This is the point where translation meets re-creation.
Relationship with the termbase, and updating
A style guide does not work on its own; it is complete only alongside the termbase. The termbase settles which term is translated how, while the style guide defines tone and form. Together they ensure that a text is written with the right terms and in the right voice. The two are inseparable parts of the localisation kit.
A style guide is a living document. Language changes, brands develop, new content types appear. Updating the guide regularly keeps consistency from wearing away over time. This is why large technology companies publish detailed style guides and keep revising them. Even for a small agency, a short but current guide is far more valuable than a scattered archive.
Rules that change with the content type
A single style guide is not applied in the same way to every kind of text. Interface text, body content, landing pages, marketing copy and advertising each call for different rules. The micro copy on a button may be short and imperative, whereas a blog post is more flowing and explanatory. A good guide recognises the differences between these types and sets an appropriate tone for each of them.
The distinction is sharpest in web localisation. Text in a user interface is highly formulaic; expressions such as “Log in” or “Upload photo” are used in the same form wherever they appear. Body content is longer and more variable. By stating how much freedom each type allows, the style guide lets the translator make the right call. Consistency is preserved without hardening into rigidity.
Rules about images are part of the guide too. How is the alternative text for an image written, which images contain text that has to be translated, how are decorative images marked? These decisions matter for accessibility as much as for consistency. A good guide covers not only the sentences but everything that surrounds the text. Every layer of the user experience is then handled with the same care.
The Türkiye context
When a style guide is prepared for Turkish, decisions peculiar to the language come to the fore. The most basic of them is the form of address: in corporate texts the formal “siz” is usually the right choice, and the guide should say so explicitly. Date format, the decimal separator and the use of capitals must likewise be defined according to the rules of Turkish; habits carried over from English can slip quietly into the text.
Another subtlety of Turkish is deciding when an English term is kept and when it is translated. “E-posta” or “mail”, “indir” or “download”? Settling these questions in the guide keeps the text both natural and consistent. Matching the writing conventions a local reader expects is the key to making a translation feel “local”. Once the guide has fixed these decisions, every new piece of content follows the same line.
What does this mean for you?
If you are taking your brand into new markets, a style guide is the insurance policy on your consistency. To strengthen your hand you can do the following:
- Set out your brand’s tone and preferred form of address in writing.
- List the elements that are not to be translated and the preferred terms.
- Review and update the guide whenever a new content type appears.
We can help you build a style guide of your own. You are welcome to look at our localisation services and to request a quote for what you need. Our aim is for your brand to speak with the same confidence in every language.
Frequently asked questions
Are a localisation style guide and a termbase the same thing?
No. A termbase settles which term is translated how; a style guide defines tone, form of address, formatting and the general rules of writing. Together they deliver consistency.
What does a style guide contain?
Form of address, tone, sentence length, formatting rules, date and number formats, expressions to avoid and guidance on the brand voice. The aim is for different translators to produce consistent output.
Do small projects need a style guide?
On a small job with a single translator a short set of instructions may be enough. Where several translators or continuously updated content are involved, a style guide is an indispensable instrument of consistency.
Are there special rules for web text?
Yes. Web text should be short, clear and scannable. Addressing the user directly, short sentences with a single idea and the inverted pyramid are the basic rules of writing for the web.
References
Jiménez-Crespo, M. A. (2024). Localization in Translation. Routledge (Chs. 3/4/5/9/12). · Nielsen, J. & Loranger, H. (2006). Prioritizing Web Usability. New Riders.