Principles
UI text can make interfaces more usable and build trust. Text should be clear, accurate, and concise.
Be concise
To facilitate navigation and discovery, write UI text in short, scannable segments that focus on a limited number of concepts at a time.
To facilitate navigation and discovery, write UI text in short, scannable segments that focus on a limited number of concepts at a time.
Write simply and directly
Use simple, direct language that makes content easy to understand.
Use simple, direct language that makes content easy to understand.
Address users clearly
Address users in either the second person (you or your) or the first person (I, me, or my), depending on which is suitable and clearest...
Address users in either the second person (you or your) or the first person (I, me, or my), depending on which is suitable and clearest for the situation.
Each form of address is recommended for the following contexts:
- Second person, "you" or "your": This conversational style is appropriate in most situations; as though the UI is speaking directly to the user.
- First person, "I" or "my": In some cases, this form of address emphasizes the user's ownership of content or actions.
Avoid combining first and second person
To avoid confusing the user, avoid using "me" or "my," and "you" or "your," in the same phrase.
Communicate essential details
Communicate only essential details so users can focus on their own tasks. Sometimes the most effective UI contains no text at all.
Communicate only essential details so users can focus on their own tasks. Sometimes the most effective UI contains no text at all.
Write for all reading levels
Use common words that are clearly and easily understandable across all reading levels. Turn on Location History Enable Location History
Use common words that are clearly and easily understandable across all reading levels.
Industry terms and feature names
Avoid industry-specific terminology or names invented for UI features.
Write in the present tense
Use the present tense to describe product behavior. Avoid using the future tense to describe the way a product always acts. When you need to...
Use the present tense to describe product behavior. Avoid using the future tense to describe the way a product always acts.
When you need to write in the past or future tenses, use simple verb forms.
Use numerals
Use numerals ( “1, 2, 3,” not “one, two, three”) unless writing copy that mixes uses of numbers, such as "Enter two 3s."
Use numerals ( "1, 2, 3," not "one, two, three") unless writing copy that mixes uses of numbers, such as "Enter two 3s."
Skip unnecessary punctuation
To help readers scan text at a glance, avoid using punctuation in places where it isn't necessary. Avoid using periods on solitary sentences within these...
To help readers scan text at a glance, avoid using punctuation in places where it isn't necessary.
Periods
Avoid using periods on solitary sentences within these UI elements:
- Labels
- Hover text
- Bulleted lists
- Dialog body text
Use periods on:
- Multiple sentences
- Any sentence followed by a link (links themselves should not be full sentences)
Periods in longer text
Longer or complex sentences can use periods if doing so better suits the context. For example, if the rest of your app's flow doesn't use periods, introducing them in a few places may appear inconsistent.
Colons
Skip colons after labels.
Content structure
Begin with the objective
When a phrase describes a goal and the action needed to achieve it, start the sentence with the goal.
When a phrase describes a goal and the action needed to achieve it, start the sentence with the goal.
Reveal detail as needed
Reveal information progressively and as it's needed. In a user's first interaction, every detail doesn't need to be described. Reveal more detail about features as...
Reveal information progressively and as it's needed.
In a user's first interaction, every detail doesn't need to be described. Reveal more detail about features as the user explores them and needs more information.
Use consistent words
Use words in a consistent manner across your UI features.
Use words in a consistent manner across your UI features.
Refer to UI elements and controls by label
Labels identify what a control or element does. They appear either on or near the control itself, such as the text on a button or...
Labels identify what a control or element does. They appear either on or near the control itself, such as the text on a button or switch. To refer to a UI control or element, mention it using its label text. (don't state the type of element or control).
Writing for components
Components
The following components have specific writing guidance:
The following components have specific writing guidance: