Feature request: Danish (da-DK) UI localization for Claude desktop app / claude.ai
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Summary
Please add Danish (da-DK) as a selectable display language in the Claude desktop app and claude.ai, and ideally Swedish and Norwegian as well.
Current behavior
The interface is available in a limited set of languages. Danish is not one of them. Claude responds fluently in Danish, but all UI elements (menus, buttons, settings, help texts) remain in English or another supported language.
Requested behavior
- Danish available under the display language setting
- Ideally: automatic detection of OS/browser locale
- Ideally: Swedish and Norwegian added at the same time
Why
- Accessibility: Many Danish professionals, especially in the public and social sector, work exclusively in Danish. An English UI is a barrier to adoption, even though the model itself handles Danish well.
- Public sector adoption: Danish municipalities and regions operate in Danish. A localized UI lowers the barrier for organizational rollout.
- Low marginal cost: Language capability already exists in the model. Only UI strings need translation.
- Nordic scope: Danish, Swedish and Norwegian together cover roughly 20 million users with overlapping needs.
If you agree, please add a 👍 to this issue so demand can be measured.
Proposed Solution
Add Danish (da-DK) as a selectable display language in the existing language setting of the Claude desktop app and claude.ai.
Suggested approach:
- Translate the UI strings (menus, buttons, settings, slash command descriptions, help text, system messages) into Danish, using the same localization framework already used for the currently supported languages.
- Automatically detect the OS/browser locale on first launch and apply Danish if available, with the option to change it manually.
- Keep English as the fallback for any strings not yet translated.
- Ideally, roll out Swedish (sv-SE) and Norwegian (nb-NO) at the same time, as the Nordic languages share many terms and the same user needs.
The model itself already handles Danish well, so this is purely a UI localization task — no model changes are needed.
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
I introduce AI tools to colleagues and caseworkers in the Danish social sector, and I have previously worked as an implementation consultant for new case-documentation systems. The English interface is consistently the first barrier people hit — before they even get to experience how well Claude handles Danish.
Additional Context
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗