A dark, checkerboard-patterned background with subtle variations in black and gray squares. The image has a modern and sleek feel.

Features: Multi-Language Signature Support

Multi-Language Signature Support

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.

Spain Flag
Portuguese Flag
United Kingdom Flag
Portuguese Flag
United Kingdom Flag
United Kingdom Flag

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.

How It Works

Signer types their name

In the signing flow, your user types their name as they normally would. No special input required.

Firma.dev detects the script

Firma.dev counts the characters in the name by script and picks the dominant one: Latin, Cyrillic, Greek, Japanese, or Korean. Kanji in a name that also contains Hangul is read as Korean, and as Japanese otherwise.

Signature renders with the right font

The typed name gets rendered as a signature using a curated font for that script. The signer can preview it and choose from multiple styles.

If auto-detection gets it wrong (rare, but possible with mixed-script names), signers can manually switch scripts in the signing UI.

How It Works

Signer types their name

In the signing flow, your user types their name as they normally would. No special input required.

Firma.dev detects the script

Firma.dev counts the characters in the name by script and picks the dominant one: Latin, Cyrillic, Greek, Japanese, or Korean. Kanji in a name that also contains Hangul is read as Korean, and as Japanese otherwise.

Signature renders with the right font

The typed name gets rendered as a signature using a curated font for that script. The signer can preview it and choose from multiple styles.

If auto-detection gets it wrong (rare, but possible with mixed-script names), signers can manually switch scripts in the signing UI.

How It Works

Signer types their name

In the signing flow, your user types their name as they normally would. No special input required.

Firma.dev detects the script

Firma.dev counts the characters in the name by script and picks the dominant one: Latin, Cyrillic, Greek, Japanese, or Korean. Kanji in a name that also contains Hangul is read as Korean, and as Japanese otherwise.

Signature renders with the right font

The typed name gets rendered as a signature using a curated font for that script. The signer can preview it and choose from multiple styles.

If auto-detection gets it wrong (rare, but possible with mixed-script names), signers can manually switch scripts in the signing UI.

Why This Matters for Global SaaS

Three user profile icons with name tags in purple, gold, and blue, featuring "John Smith" in different languages.

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.

Text graphic with "John Smith" translated into Cyrillic and Japanese; displayed in linked dark boxes, conveying a multilingual representation.

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.

curl -X PATCH https://api.firma.dev/functions/v1/signing-request-api/workspace-settings/{workspace_id} \
  -H "Authorization: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "language": "fr" }'

Interface Languages

Interface Languages

Separate from signature rendering, the Firma.dev signing UI, embeddable template editor, embeddable signing request editor, and notification emails are available in 15 languages:

Firma Logo Favicon

Welcome back
Tyler Brooks!
Firma Logo Favicon

Welcome back
Tyler Brooks!
Firma Logo Favicon

Welcome back
Tyler Brooks!
United Kingdom Flag

English

English

Spain Flag

Spanish

Spanish

France Flag

French

French

United Kingdom Flag

German

German

Portuguese Flag

Portuguese

Portuguese

Portuguese Flag

Italian

Italian

United Kingdom Flag

Dutch

Dutch

United Kingdom Flag

Catalan

Catalan

United Kingdom Flag

Polish

Polish

United Kingdom Flag

Czech

Czech

United Kingdom Flag

Romanian

Romanian

United Kingdom Flag

Swedish

Swedish

United Kingdom Flag

Norwegian Bokmål

Norwegian Bokmål

United Kingdom Flag

Greek

Greek

United Kingdom Flag

Russian

Russian

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

Background Image

Ready to add e-signatures to your application?

Get started with Firma.dev for free, no credit card required. Pay only €0.049 (~5¢) per envelope when you're ready to go live.

Background Image

Ready to add e-signatures to your application?

Get started with Firma.dev for free, no credit card required. Pay only €0.049 (~5¢) per envelope when you're ready to go live.

Background Image

Ready to add e-signatures to your application?

Get started with Firma.dev for free, no credit card required. Pay only €0.049 (~5¢) per envelope when you're ready to go live.

FAQ

Frequently asked questions

For any unanswered questions, reach out to our support team via email. We'll respond as soon as possible to assist you.

Do I need to pass a language or script parameter in my API calls?

Not for signatures. Script detection runs on the characters in the signer's typed name, so your API integration doesn't change. You only pass a language value if you want to control the interface or email language, as covered in the localization guide.

What fonts are used for signatures?

Latin uses Parisienne, Sacramento, and Alex Brush. Cyrillic uses Marck Script, Bad Script, and Caveat. Greek uses Zen Kurenaido. Japanese uses Zen Kurenaido and Klee One. Korean uses Nanum Pen Script and Gaegu. Every script family also offers an italic and a plain style, which signers pick from in the signing experience.

Do signatures render correctly in the final PDF?

Yes. All signatures render correctly in the signed document and the completion certificate, regardless of script.

What if a name mixes multiple scripts?

Firma.dev uses whichever script has the most characters in the name. Kanji alongside Hangul counts toward Korean, and Kanji on its own counts toward Japanese. For edge cases, signers can override the choice, and the signature renders in whichever script family they select.

Which languages is the signing interface available in?

English, Spanish, French, German, Portuguese, Italian, Dutch, Catalan, Polish, Czech, Romanian, Swedish, Norwegian Bokmål, Greek, and Russian. Japanese and Korean are supported for signatures, but the interface isn't translated into them yet. The localization guide lists the language code for each.

Can I set the language of notification emails?

Yes. Set the language field at the company level for an account-wide default, or at the workspace level to override it for a specific customer workspace. Each level inherits from the one above it unless you override it.

Does embedded signing follow my app's language?

Pass your app's locale in the lang URL parameter, for example ?lang=es. Inside an iframe, Firma.dev doesn't store a language preference, so it won't override the language your host app has set. See embeddable signing for every supported URL parameter.

What happens if a signer's browser language isn't supported?

The interface falls back to English. Signature rendering isn't affected, so the signer's name still renders in its own script. The localization guide explains the detection order.

FAQ

Frequently asked questions

For any unanswered questions, reach out to our support team via email. We'll respond as soon as possible to assist you.

Do I need to pass a language or script parameter in my API calls?

Not for signatures. Script detection runs on the characters in the signer's typed name, so your API integration doesn't change. You only pass a language value if you want to control the interface or email language, as covered in the localization guide.

What fonts are used for signatures?

Latin uses Parisienne, Sacramento, and Alex Brush. Cyrillic uses Marck Script, Bad Script, and Caveat. Greek uses Zen Kurenaido. Japanese uses Zen Kurenaido and Klee One. Korean uses Nanum Pen Script and Gaegu. Every script family also offers an italic and a plain style, which signers pick from in the signing experience.

Do signatures render correctly in the final PDF?

Yes. All signatures render correctly in the signed document and the completion certificate, regardless of script.

What if a name mixes multiple scripts?

Firma.dev uses whichever script has the most characters in the name. Kanji alongside Hangul counts toward Korean, and Kanji on its own counts toward Japanese. For edge cases, signers can override the choice, and the signature renders in whichever script family they select.

Which languages is the signing interface available in?

English, Spanish, French, German, Portuguese, Italian, Dutch, Catalan, Polish, Czech, Romanian, Swedish, Norwegian Bokmål, Greek, and Russian. Japanese and Korean are supported for signatures, but the interface isn't translated into them yet. The localization guide lists the language code for each.

Can I set the language of notification emails?

Yes. Set the language field at the company level for an account-wide default, or at the workspace level to override it for a specific customer workspace. Each level inherits from the one above it unless you override it.

Does embedded signing follow my app's language?

Pass your app's locale in the lang URL parameter, for example ?lang=es. Inside an iframe, Firma.dev doesn't store a language preference, so it won't override the language your host app has set. See embeddable signing for every supported URL parameter.

What happens if a signer's browser language isn't supported?

The interface falls back to English. Signature rendering isn't affected, so the signer's name still renders in its own script. The localization guide explains the detection order.

FAQ

Frequently asked questions

For any unanswered questions, reach out to our support team via email. We'll respond as soon as possible to assist you.

Do I need to pass a language or script parameter in my API calls?

Not for signatures. Script detection runs on the characters in the signer's typed name, so your API integration doesn't change. You only pass a language value if you want to control the interface or email language, as covered in the localization guide.

What fonts are used for signatures?

Latin uses Parisienne, Sacramento, and Alex Brush. Cyrillic uses Marck Script, Bad Script, and Caveat. Greek uses Zen Kurenaido. Japanese uses Zen Kurenaido and Klee One. Korean uses Nanum Pen Script and Gaegu. Every script family also offers an italic and a plain style, which signers pick from in the signing experience.

Do signatures render correctly in the final PDF?

Yes. All signatures render correctly in the signed document and the completion certificate, regardless of script.

What if a name mixes multiple scripts?

Firma.dev uses whichever script has the most characters in the name. Kanji alongside Hangul counts toward Korean, and Kanji on its own counts toward Japanese. For edge cases, signers can override the choice, and the signature renders in whichever script family they select.

Which languages is the signing interface available in?

English, Spanish, French, German, Portuguese, Italian, Dutch, Catalan, Polish, Czech, Romanian, Swedish, Norwegian Bokmål, Greek, and Russian. Japanese and Korean are supported for signatures, but the interface isn't translated into them yet. The localization guide lists the language code for each.

Can I set the language of notification emails?

Yes. Set the language field at the company level for an account-wide default, or at the workspace level to override it for a specific customer workspace. Each level inherits from the one above it unless you override it.

Does embedded signing follow my app's language?

Pass your app's locale in the lang URL parameter, for example ?lang=es. Inside an iframe, Firma.dev doesn't store a language preference, so it won't override the language your host app has set. See embeddable signing for every supported URL parameter.

What happens if a signer's browser language isn't supported?

The interface falls back to English. Signature rendering isn't affected, so the signer's name still renders in its own script. The localization guide explains the detection order.