< Back to Newsroom

SSP goes multilingual — 13 new languages and a docs site

·4 min read·By SSP Editorial Team
SSP brand cover with database, shield-check, zap, and cpu icons; headline reads 'SSP goes multilingual'.

SSP Wallet now speaks 14+ languages. Between August 2024 and February 2025, we rolled out 13 new locales — from Czech in v1.7.0 through Malay and Thai in v1.14.0 — and along the way shipped a major UX win: SSP now defaults to your operating system's language instead of always opening in English. Alongside that final language batch, we also launched docs.sspwallet.io, the official documentation site.

TL;DR

  • 13 new languages added across v1.7.0 → v1.14.0, bringing SSP to 14+ supported locales.
  • SSP now defaults to your system language with English as a fallback.
  • Translations flow through Crowdin; community contributions land via GitHub.
  • Product names (SSP, SSP Wallet, SSP Key, multisig) stay in English everywhere.
  • docs.sspwallet.io is live as the official documentation home.

The rollout timeline

Localization wasn't a single drop — it was a steady cadence across six releases:

  • v1.7.0 (Aug 2024): Czech.
  • v1.8.0 (Nov 2024): Filipino, Russian.
  • v1.10.0 (Jan 2025): Spanish, Vietnamese, Finnish, Japanese, Hungarian.
  • v1.12.0 (Feb 2025): Slovenian, Ukrainian, Portuguese.
  • v1.14.0 (Feb 2025): Malay, Thai.

That's 13 net-new locales in six months. v1.14.0 also shipped refreshed translations for Czech and Indonesian (Indonesian was part of the original launch set), so even the languages we'd already supported got attention as the catalog grew. The pattern was deliberate: ship one or two languages, watch how the strings render in real screens, fix whatever breaks, then ship the next batch. A wallet UI has tight space constraints — German compound words and Vietnamese diacritics behave very differently in a button label — and the only way to catch those issues is to actually run the locale against the live interface.

Default to your system language

Before v1.10.0, SSP always launched in English regardless of what your device was set to. That made sense when there were three languages to choose from. It stopped making sense once we crossed a dozen.

In v1.10.0 we flipped the default: SSP now reads your system preference and uses it if we support that locale, falling back to English when we don't. You can still override it manually in settings, but for most people the wallet now opens in their own language on first run. It's a small change with an outsized impact — most users never touch the language picker, so the default is the experience.

Translation quality and community contributions

We use Crowdin to manage strings across all 14+ locales. Every release pulls in updated translations, and contributors can suggest fixes, alternate phrasings, or new locales through pull requests on GitHub. Native speakers reviewing native speakers tends to beat machine translation every time, and the community has been generous with corrections.

A note on what does not get translated: product names. SSP, SSP Wallet, SSP Key, and the term "multisig" stay in English across every locale. Brand consistency matters, and the security model behind multisig is the same regardless of the UI language wrapped around it.

And: docs.sspwallet.io is live

The same release that added Malay and Thai also flipped the switch on our documentation site. docs.sspwallet.io is now the home for setup guides, hardware-key walkthroughs, troubleshooting, and the deeper technical reference. The in-app help still covers the common questions, but anything that needs screenshots, longer explanations, or version-specific guidance now lives at docs.

It's a separate surface from the newsroom and the in-app academy on purpose: docs are evergreen, versioned, and built to be searched. If you've been hunting through Discord for a setup answer, try the docs first — it's probably there.

What's next for languages

Adding a language is the easy part. Keeping it current as the wallet evolves is the real commitment. Every new feature — Account Abstraction, new chain support, hardware-key flows — ships with English strings first and then propagates through the translation pipeline. Our Wave 1 locale set is the baseline we promise to maintain release-over-release.

If you spot a translation that reads awkwardly, or you'd like to nominate a language we don't yet support, the Crowdin project and our GitHub issues are both open. The roadmap from here is depth, not breadth: better translations of the strings we already have, and faster turnaround on the new ones we add. A self-custody wallet is, in many ways, a trust interface. The clearer it reads in your own language, the better you can verify what you're signing — and that's the entire point.

Sources: v1.10.0, v1.12.0, v1.14.0.

Share this article

Related articles