LOCALIZATION GUIDE · no

Localize App Store Screenshots to Norwegian

Norsk

Norway = ~5M people, extremely high per-capita ARPU.

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

Why Norwegian matters

Norway (~5M) has one of the highest per-capita app spends on the planet, so even this tiny market repays proper localization. The defining wrinkle is that Norwegian has two official written standards (Bokmål, used by roughly 85-90% of the population, and Nynorsk), and virtually every app localizes to Bokmål only, which every Norwegian reads comfortably regardless of their own primary form.

English (source)

Book your next adventure in one tap

35 chars

Bestill ditt neste eventyr med ett trykk

40 chars

Localization tips for Norwegian

  1. 1 Localize to Bokmål (nb) unless you have a specific Nynorsk audience. Bokmål is universally readable in Norway.
  2. 2 In Xcode use the 'nb' locale/.lproj (Bokmål) while App Store Connect simply lists it as 'Norwegian'; mismatching these is a common metadata slip.
  3. 3 Norwegian uses æ, ø, å in that order at the end of the alphabet. Distinct from Swedish's ä/ö and identical to Danish, so don't reuse a Swedish font mapping that lacks ø.
  4. 4 Default to informal 'du'; the formal 'De' is effectively extinct and looks archaic even in banking apps.
  5. 5 Budget ~20% more width; Norwegian builds single-word compounds ('skjermbilde', 'brukeropplevelse') that overrun English-sized buttons.
  6. 6 Lean into the 'Janteloven' sensibility. The cultural aversion to boasting means confident, plain claims outperform hype-heavy superlatives.

Fonts for Norwegian

Inter, Roboto and Source Sans 3 cover æ, ø, å well. The must-check glyph is 'ø' (o with a slash): some fonts omit it or draw the stroke so thin it vanishes at small sizes and reads as a plain 'o' (which changes words), and the ring on 'å' must stay crisp too.

Most common mistake

Shipping the generic 'no' locale in Xcode instead of 'nb' (Bokmål). iOS doesn't resolve 'no' consistently across versions, so your carefully translated strings can silently fall back to the English base localization on some devices.

Norwegian localization FAQ

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

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

Does text expansion affect Norwegian screenshot design?

Norwegian 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 Norwegian.

Does Shotlingo automatically localize screenshots to Norwegian?

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

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

If Norwegian 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 Norwegian automatically

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

Try Shotlingo free →
Other localization guides