Skip to main content
Howard3
New Member
September 10, 2026

Localized Viewer and Prototype Experience for External Stakeholders

  • September 10, 2026
  • 0 replies
  • 12 views

Figma is no longer used only by designers and developers.
In many real-world projects, designers share Figma files or prototypes with external stakeholders such as clients, managers, marketing teams, legal teams, and other non-design users for review and approval.
These viewers did not necessarily choose Figma themselves, and many of them may not be familiar with Figma or comfortable using an English interface.
This creates unnecessary friction in the review process.

The intended journey should ideally be:
Open shared link → Review the design

But in practice, it can become:
Open shared link → Understand an unfamiliar English interfaceFigure out how to navigate the prototype viewer → Review the design

There is another common scenario where this becomes even more problematic.
After a client receives a prototype or shared file, they may need to share it with other members of their internal team. At this point, they have to interact with Figma's sharing interface themselves.

This interface involves concepts such as access levels, roles, permissions, and sharing restrictions. For users who are already unfamiliar with Figma, having all of these options presented in English creates additional uncertainty.
This is particularly important because sharing permissions are not merely navigation controls. Users need to understand the consequences of their choices before changing access or inviting someone.

As a result, a client who simply wants to share a design internally may hesitate because they are unsure:

  1. Who currently has access.
  2. Whether someone can only view or can also edit.
  3. Which permission should be selected.
  4. Whether changing a setting will affect other users.
  5. Whether the link can safely be forwarded to another colleague.

In this situation, language becomes more than a usability inconvenience. It creates friction around understanding access and permissions.
This is especially noticeable in markets where Simplified Chinese / Traditional Chinese is commonly used, where designers and developers may be comfortable working with Figma in English, but their clients and stakeholders may not be.

I don't think the entire Figma editor necessarily needs to be localized first. A more focused solution could be to localize the Prototype, Comment, and Sharing experiences for external stakeholders.
For example, commonly used interface elements such as:

  • Comment
  • Present
  • Full screen
  • Scaling options
  • Request access
  • Sign in
  • Prototype navigation instructions
  • Share Prototype
  • Copy link
  • Access levels
  • Permission descriptions

could support additional languages, including Simplified Chinese / Traditional Chinese.

Ideally, this localization should also remain consistent when the viewer opens sharing, permission, commenting, or other collaboration interfaces from that shared experience.
Localization is not only an editor accessibility issue. It is also a stakeholder collaboration issue, because viewers often never chose Figma in the first place.

External stakeholders should not need to learn the language of a design tool before they can confidently review, comment on, or share a design with their team.
Improving localization for the viewing, review, and sharing experience could make Figma much easier to introduce to clients and non-design stakeholders, especially in international and multilingual projects.