Konstantin Semenenko
July 21, 2026
4
minutes read
Typography is where collaborative and design tools diverge most. Figma treats type as a system: named text styles, variables, and published libraries that propagate a change everywhere, plus licensed brand fonts shared across a team. Mural treats type as annotation, a few built-in options for readable sticky notes, with no type scale, styles, or brand enforcement. That is correct for each tool, and it breaks when teams expect brand-accurate type on a workshop board. Set type in the design tool; use boards for structure, not styling.
Fonts and typography behave completely differently across enterprise design tools, and understanding why prevents a class of avoidable frustration. Figma is built to hold typography as a system: text styles that define a type scale, variables and libraries that publish those definitions across an organization, and support for licensed brand fonts installed for a team, so changing the body typeface once updates every file that consumes the library. Mural is built for collaborative thinking, so its type support covers what that needs, a small set of readable options for sticky notes, labels, and headings on a board, with no type scale, no named styles, and no way to enforce brand fonts. Neither is deficient; they encode different jobs. The friction appears when teams expect brand-accurate typography inside a workshop board, or treat text choices made on a collaborative canvas as typographic decisions. This explains the split and where it actually breaks.
We run design systems and brand implementation for clients across these tools, so this is a practitioner's view of where typography lives and how it goes wrong.
The common misconception is that typography means picking a typeface. In production design, typography is a system of decisions: a type scale (the specific sizes and their relationships), line heights, weights, letter spacing, and the semantic mapping of each combination to a role (page title, section heading, body, caption, label). That system has to be consistent across hundreds of screens and implementable by engineers as tokens.
This is why the relevant capability in a design tool is not how many fonts it offers but whether it can hold type as named, reusable, propagating definitions. Figma does this through text styles and variables published in libraries: a designer applies "Heading/L" rather than manually setting 32px semibold with 1.2 line height, and when the scale changes, every instance updates. That is what makes typography maintainable at enterprise scale and what lets engineers implement type tokens that match, the structure that determines whether design-to-code output is faithful, covered in design-to-code in 2026. Without named, propagating styles, typography is not a system, it is a series of one-off choices that drift.
Mural offers a limited set of typefaces and basic formatting, sized for legibility on an infinite canvas at varying zoom levels. There is no type scale, no named text styles, no variables, and no mechanism to install and enforce a licensed brand font across an organization. Judged as a design tool, that is a long list of absences. Judged as what Mural is, a collaborative thinking space, it is appropriate: on a board full of sticky notes, journey maps, and clustered research, type exists to be readable and to signal hierarchy roughly, not to express brand.
There is a real argument that constrained type is a feature here. When eight people from four functions are working a board, the goal is contribution, not craft, and a full type system would add friction and invite bikeshedding about fonts during a session meant to produce decisions. So the honest framing is that Mural's typography is scoped to legibility and hierarchy, which is what collaboration needs, and it stops there deliberately, the same UX-versus-UI boundary we describe in Mural for UX and UI design.
Three failure modes recur, and all trace to expecting one tool to do the other's job.
The first is brand expectation on a collaborative board. A stakeholder sees a Mural journey map or wireframe sketch in a default typeface and reads it as off-brand or unfinished, when the board was never meant to be a brand artifact. The fix is framing, not fonts: state plainly that boards are working documents and brand typography is applied in design. The second is typographic decisions made on the wrong canvas. A rough layout in Mural where a heading "looks right" carries no information about scale, because the board has no scale, so it cannot be carried into design as a decision, only as an intent about hierarchy. The third, and most expensive, is licensing. Brand typefaces are licensed, often per seat or per platform, and a font legitimately licensed for design and web use is not automatically covered for every tool an organization uses. Font licensing is a legal question that has to be checked per tool and per use, not assumed from the fact that the company owns the font.
Practical guidance:
Figma holds typography as a system, named text styles, variables, published libraries, and support for licensed brand fonts, so type stays consistent and propagates across an organization. Mural holds type as annotation: a small set of readable options for boards, with no scale, styles, or brand enforcement, which is the right scope for collaborative thinking and a poor one for design. The breakage happens when teams expect brand-accurate typography in a workshop board, treat board text choices as typographic decisions, or assume a brand font license covers every tool. Set the type system in the design tool, use collaborative boards for structure and hierarchy, and verify licensing per platform.
If you want brand typography implemented as a real system across design and code, that is where our AI Design Team work starts.
Can you use custom brand fonts in Mural? Mural offers a limited built-in set and is not designed to install and enforce licensed brand typefaces across an organization the way a design tool does. Boards are working documents, so brand typography is normally applied later in the design tool rather than on the collaborative canvas.
How does Figma handle typography differently from Mural? Figma treats type as a system: named text styles and variables define a type scale that publishes through libraries, so one change propagates everywhere and engineers receive implementable tokens. Mural provides basic formatting for legibility on a board, with no scale, named styles, or propagation.
Why does my Mural board look off-brand? Because it is a working document, not a brand artifact. Collaborative boards use default type for legibility and fast contribution. The fix is usually framing the board correctly for stakeholders rather than trying to make it brand-accurate, which the tool is not built for.
Where should typography decisions be made? In the design tool, against a defined type scale with named styles. Collaborative boards are useful for deciding hierarchy (what matters more than what), but the actual sizes, weights, and line heights should be set where they can be named, reused, and propagated.
Do brand font licenses cover every design tool? Not automatically. Typeface licenses are often scoped by seat, platform, or use (desktop, web, application), so a font licensed for design and web use may not be covered in every collaborative or prototyping tool an organization runs. Check licensing per tool before installing.
