
Signatures that render correctly, no matter the language.
Your signers type their names in Japanese, Russian, Greek, Korean, or any Latin-based language, and Firma.dev renders each one with signature fonts chosen for that script. Characters never break or fall back to empty boxes, and the signing interface around them is available in 15 languages.
Supported Writing Systems
Firma.dev automatically detects and renders signatures in 5 script families:
Script
Languages Supported
Signature Font
Latin/Western
English, Spanish, French, German, Portuguese, Italian, Dutch, Catalan, Polish, Czech, Romanian, Swedish, Norwegian
Parisienne, Sacramento, Alex Brush
Cyrillic
Russian, Ukrainian, Bulgarian, Serbian
Marck Script, Bad Script, Caveat
Greek
Modern Greek (including ά, έ, ί, ό and other accented characters)
Zen Kurenaido
Japanese
Hiragana, Katakana, Kanji
Zen Kurenaido, Klee One
Korean
Hangul
Nanum Pen Script, Gaegu
Every script family also comes with an italic and a plain style, so a signer who wants a cleaner mark doesn't have to pick a cursive one. For how detection and font selection work in detail, see Multi-Script Signature Support.
Why This Matters for Global SaaS

Global Name Rendering
If you're building software for international markets, your users expect their names to display correctly. A Russian name set in a Latin fallback font looks broken, and a Japanese name that shows up as empty rectangles tells your customer the product wasn't built with them in mind.
Universal Script Support
Names render correctly in the signing experience, in the final signed PDF, and in the completion certificate. Your integartion code stays the same whether your signer is in São Paulo, Seoul, or Stockholm, and every signature carries the same audit trail and is legally binding in 55+ countries.
Zero extra API parameters.

Control the signing language from your integration
Signature fonts take care of themselves. The interface language is something you can set per account, override per customer, or leave to the signer's browser.
Account and workspace defaults
Set language on your company to choose the default language for signing notification emails, then override it on any workspace. If each of your customers has their own Customer Workspace, each one can send in its own language. A signing request's language takes priority over its workspace, and a workspace's takes priority over the company.
Embedded signing
Append ?lang= to any signing URL to force the interface language inside your iframe. Embedded components run in non-persistent mode, so Firma.dev never overwrites the language setting of the app hosting it.
Automatic detection
For direct links, Firma.dev matches the signer's browser language on the first visit and remembers their choice on return visits. Unsupported languages fall back to English.
Separate from signature rendering, the Firma.dev signing UI, embeddable template editor, embeddable signing request editor, and notification emails are available in 15 languages:















Your signers see buttons, instructions, and emails in their own language. Combined with multi-script signatures, that gives them a fully localized signing experience.








