LOCALIZATION GUIDE · da

Localize App Store Screenshots to Danish

Dansk

Denmark = ~6M people, high ARPU, premium market.

Text expansion
+20%
vs English
Layout risk
Medium
overflow severity
Locale code
da
App Store Connect

Why Danish matters

Denmark (~6M) is a premium, high-ARPU market where English literacy is near-universal but Danish-language listings still win consumer trust. The trap is that Danish looks almost identical to Norwegian Bokmål on the page ('øje' vs Norwegian 'øye' for 'eye') yet is a separate language, and Danish counts in a base-20 system where 50 is 'halvtreds' and 70 is 'halvfjerds', so number-heavy copy needs a native who knows those aren't typos.

English (source)

Save money automatically every single month

43 chars

Spar penge automatisk hver eneste måned

39 chars

Localization tips for Danish

  1. 1 Danish uses æ, ø, å as distinct letters after z. Identical to Norwegian, but the two languages are not interchangeable, so never reuse Norwegian copy.
  2. 2 Budget ~20% more width; Danish stacks nouns into single compounds ('skærmbillede', 'brugeroplevelse') that overflow English-sized buttons.
  3. 3 Default to informal 'du'. The formal, capitalized 'De' is essentially archaic and sounds stiff or ironic; even banks address customers as 'du'.
  4. 4 Danish marks 'the' with an enclitic suffix, not a separate word: 'a screenshot' is 'et skærmbillede' but 'the screenshot' is 'skærmbilledet'. Machine translation sometimes botches this.
  5. 5 Spelled-out numbers use the vigesimal system ('halvtreds' = 50, 'tres' = 60, 'halvfjerds' = 70). Have a native check any counts, discounts or prices.
  6. 6 Keep the tone dry and understated; Danish marketing favors subtle humor and plain claims over American-style superlatives.

Fonts for Danish

Inter, Roboto and Source Sans 3 all include æ, ø, å. Verify the 'æ' is a true single ligature glyph (not a cramped a+e), and that 'ø' keeps a visible slash at small sizes. A slash that fades makes 'øl' (beer) read as 'ol' and signals a broken font.

Most common mistake

Buying one 'Scandinavian' translation and reusing it for both Denmark and Norway because the text looks so similar. Danes instantly catch Norwegian spellings ('melk' instead of 'mælk' (milk), 'løk' instead of 'løg' (onion), 'øye' instead of 'øje' (eye)), and the Norwegian-flavored listing reads as lazy, costing exactly the trust localization was meant to build.

Danish localization FAQ

What App Store Connect locale code should I use for Danish?

Use da when adding Danish (Dansk) screenshots in App Store Connect or Google Play Console. Using the wrong code means your localized screenshots never reach Danish users.

Does text expansion affect Danish screenshot design?

Danish runs +20% vs English on average character count. You should design buttons and headlines with explicit overflow headroom, because text that fits in English will break in Danish.

Does Shotlingo automatically localize screenshots to Danish?

Yes. Shotlingo auto-translates your App Store screenshot text to Danish (Dansk) with AI that respects text expansion, and platform-appropriate fonts. Export the localized bundle ready for App Store Connect locale da.

Do I have to translate my App Store screenshots to Danish?

If Danish is a major market for your app, yes. Unlocalized screenshots significantly reduce conversion, because users scroll past copy they cannot read. Even partial localization (headlines only) typically beats English-only.

Localize your screenshots to Danish automatically

Shotlingo handles expansion, fonts, and App Store Connect locale codes for you. Free to try.

Try Shotlingo free →
Other localization guides