Firma.dev Now Speaks 14 Languages: Czech, Swedish, Dutch, Romanian, and Norwegian Added

Firma.dev now supports 14 languages for the full signer journey, after adding Czech, Swedish, Dutch, Romanian, and Norwegian Bokmål this month. That's five new languages on top of the nine already live, and every one of them covers more than just the buttons on screen.

More than a translated button

Translating a signing interface is the easy part. A legal e-signature product also has to translate the legal consent statement a signer accepts before signing, the completion certificate generated afterward, and the emails that carry the signing link in the first place. Get the UI right and leave the consent language in English, and the legal record stays seperate from what the signer actually understood, which matters if that signature is ever challenged. Our guide on localizing e-signature flows for international users walks through the same problem in more depth.

Five languages, five specific markets

Czech and Romanian cover Central and Eastern Europe, where diacritics on names and dates are common and easy to get wrong. Swedish and Norwegian Bokmål extend Firma.dev into the Nordics. Dutch rounds out Benelux. None of these were chosen at random... they map directly to where Firma.dev customers have been asking for native-language signing.

What's actually localized, end to end

Every one of the five new languages covers the same ground as the original nine:

• Invitation and reminder emails sent to the signer

• The signing ceremony interface itself

• The legal consent statement recorded at the moment of acceptance

• Date formatting, including localized month names

• The completion certificate generated once signing finishes

Completion certificates render Czech and Romanian diacritics correctly, with embedded fonts rather than a fallback that silently drops accent marks. A name like "Kučera" or a date rendered in "listopad" shows up exactly as it should on the legal record, not as a stripped-down approximation.

Norwegian, handled correctly

Browsers report Norwegian in a few different ways, usually as "no" or occasionally "nn." Firma.dev detects both and maps them to "nb" automatically, so a Norwegian signer never quietly falls back to an English signing page just because their browser reported a locale code the platform didn't recognize. It's a small detail... but it's exactly the kind of thing that breaks silently if nobody builds for it on purpose.

Three levels of control

Language is settable per company, per workspace, or per individual signing request, with the most specific setting winning:

{
  "signer_language": "cs"
}

{
  "signer_language": "cs"
}

{
  "signer_language": "cs"
}

Set a company-wide default, override it at the workspace level for a specific market, and override that again on a single signing request when one particular signer needs something different. A platform serving customers across five countries can run all five languages through one integration without branching any logic on its own end.

Nothing breaks

Existing setups using the original nine languages behave exactly as they did before this shipped, and nothing about how you recieve or send a signing request changes unless you deliberately opt into one of the five new codes. API v1.33.0 widened the language enum from 9 to 14 across workspace and company settings, per-signing-request email language, signer terms, and email template defaults, and validation errors now list all 14 codes if you pass one that isn't supported.

The consent language recorded in each of the 14 languages still carries the same legal weight, aligned with frameworks like the U.S. ESIGN Act and eIDAS's SES and AdES tiers. A signer who understands the consent language in their own language is far more likely to have genuinely agreed to what they're signing, which matters if that signature is ever challenged.

For a SaaS platform building a multi-language e-signature workflow across more than one country, or an agency sending contracts across borders, this closes a gap that used to mean either building your own translation layer or asking signers to sign in a language that wasn't theirs.

Get started with Firma.dev for free, no credit card required.