Translate your Blazor app instantly
Drop-in translation for Razor pages and components. Cache with Redis or MemoryCache, support RTL/LTR, and keep full control with admin overrides.
<TranslatedHead Key="Home.Title"
Fallback="Home"
MetaDescriptionKey="Home.MetaDescription"
MetaFallback="Test application" />
<h1 class="text-3xl font-bold">
<TranslatableText Key="Home.Message" Text="Hello, world!" />
</h1>
<p class="text-slate-300">
<TranslatableText Key="Home.Body" Text="Welcome to your new app." />
</p>Works great with
Everything you need to translate Blazor
Designed for real production apps—fast, cache-friendly, and SEO-aware.
Drop-in components
Use <TranslatableText>, <TranslatedHead>, and a language selector to internationalize pages without rewrites.
Smart caching
Pluggable stores: MemoryCache or Redis, with sane defaults and export/import tools.
SEO head support
Translate <title> and meta description per language for better discovery.
RTL/LTR aware
Auto-switch direction for Arabic/Hebrew, keep layouts tidy.
Azure-powered
Translation is powered by Azure Translator (for now).
Admin overrides
Override any key per language from a simple dashboard—great for brand tone.
How it works
Three simple steps to go multilingual.
Add the package
dotnet add package Translazor
Wrap texts
<TranslatableText Key="Home.Body" Text="Welcome to your new app." />Choose a cache
MemoryCache for simple sites, Redis for scale. Switch any time.
Try the live demo
Switch languages, inspect the cache, and export/import translations.
Simple pricing
Start free, upgrade when you need more seats or features.
Developer
Most popular
- All Free features
- Redis caching
- Admin overrides
- SEO head translations
- 3 languages
Team
Agencies & SaaS
- Unlimited languages
- Priority support
- Bulk export/import
- Multi-tenant ready
FAQ
Does it work with Blazor Server?
Yes. Blazor Server is supported. WebAssembly support may be added later.
Can I switch cache stores?
Yes, toggle between MemoryCache and Redis via configuration without code changes.
Is my SEO preserved?
Use the TranslatedHead component to localize <title> and meta description per language.
What do I need to use it with Azure?
Just an Azure Translator resource and an API key (and region, if required). No extra services needed.
What do I need to use it with Azure?
Just an Azure Translator resource and an API key (and region, if required). No extra services needed.
Do you store my text or translations?
No. Your content is sent to Azure Translator for translation, and only the translated result is cached on your server (optional).
How can I control Azure translation costs?
Caching and page-level reuse reduce repeated calls, so you translate once and serve many times.