The typeface looks right. Will it work everywhere your brand appears?
Choose brand typography by how it performs in the places the organisation needs to use it: long text, headings, tables, presentations, print and websites. Review readability, available weights, character coverage, licence terms and fallback behaviour before approving the visual choice. A typeface can suit the brand’s character while still requiring a different implementation for a website or an editable office template.
Put the advice into practice
Make your expertise look as considered as the work behind it
Bring brand, sales material and digital design into one coherent presentation.
Discuss your design briefTest the type with real document tasks
A short wordmark or a large heading does not reveal how a family handles a dense report, a responsibility table or a mobile service page. Create a small test set using the organisation’s actual content types. Include long headings, paragraphs, numerals, punctuation, links and any languages or symbols the work requires.
Inspect hierarchy as a system. Decide how the main heading, section heading, body text, caption and table label differ. Size alone is not the only tool: weight, spacing and placement can help establish structure. The aim is a clear reading order that remains usable when the content changes.
Check the characters that can cause ambiguity in practical work, such as similar-looking letters and numerals. Review how currency, dates, reference codes and tabular figures appear where they matter. A visually appealing family may be well suited to headings while another role needs a more restrained treatment.
Write a type specification that covers roles and conditions
| Role | Decision to document | Where to test it |
|---|---|---|
| Primary headings | Approved family and weight, size range and line spacing | Long report headings, presentation titles and narrow screens |
| Body copy | Family, regular and emphasis styles, comfortable line length | Several paragraphs in print, PDF and browser |
| Tables and numbers | Numeral style, alignment and treatment of dense information | A realistic financial or responsibility table |
| Secondary details | Caption, source note and link treatment | Reduced-size print and mobile layouts |
| Fallbacks | Approved alternatives when the preferred face is unavailable | Office tools, browser loading conditions and required character sets |
The table is a specification framework, not a finished set of values for every brand. Select and test the actual families and settings for the project. Keep the result practical enough that a document user or developer can apply it without reconstructing the designer’s intention.
Match the font arrangement to the actual use
Check the licence for the source and usage involved. Creating a finished PDF is different from giving several staff editable templates, hosting a webfont or embedding type in another product. Do not assume that a designer’s access automatically covers every future use by the organisation.
Adobe’s font-licensing FAQ distinguishes finished artwork with properly embedded or rasterised font data from documents that reference live, editable fonts. It also addresses client and web use. Other font sources have their own terms, so confirm the actual arrangement rather than generalise one provider’s licence to all fonts.
Record the family, source, licence holder, permitted uses and the owner of any ongoing account dependency. Keep those details with the brand assets. This helps a future website developer, presentation designer or internal team understand what they can use without relying on an old email exchange.
Where a tool cannot use the preferred family reliably, agree an appropriate alternative. A deliberate fallback is more consistent than each person selecting a substitute independently.
Review the website and everyday tools separately
On a website, the preferred font may not be immediately available or may lack a character needed by the content. CSS supports an ordered font-family list and font matching; the W3C CSS Fonts specification describes that mechanism. Test the chosen fallback so headings, buttons and paragraphs remain readable under the relevant conditions.
Check actual weight files and loading behaviour rather than styling every element as though the whole family is present. A browser can display a different result from a design application when the available fonts or settings differ. The implementation review should include mobile layouts and the content the site will really carry.
For editable documents, test on the applications and accounts the team uses. In a hypothetical organisation, a heading family works in the designer’s environment but is unavailable in a shared presentation tool. The solution may be an approved alternative or a properly supported licence and workflow, depending on the actual requirements.
Our discussion of design systems in Canva covers a related handover issue. Typography becomes a usable brand asset when the rules account for the team’s real tools and documents.
