Laravel gives you __(), trans_choice() and a lang directory, and leaves the rest to you. The rest is where multilingual apps break: a plural rule that works in English and fails in Polish, a queued email sent in the wrong language, a validation message nobody translated, a date that reads fine in one locale and wrong in the next.
These tutorials each take one of those problems and work through it with code you can run. They assume you already know how to call __() and want to know what happens at the edges: which locale a queued job runs in, how Laravel picks a plural form, what Carbon does when a locale is missing, how Livewire components keep their language between requests.
Every example was run against a current Laravel release before it was published. Where the framework behaves in a way the documentation does not spell out, the article shows the source that decides it.
Three locales compete in a multi-tenant app: the tenant's default, the user's preference, and the request. Get the precedence wrong and you leak one tenant's language — or their custom copy — to another.
Most localization bugs are silent — missing keys fall back, plural forms degrade quietly, queue jobs leak locale. Here are the Pest tests that turn those into build failures.
1,234.50 or 1.234,50? €1,234.50 or 1.234,50 €? Laravel's Number class knows. Here's what it gets right, why you should store money as integers, and the currency-vs-locale distinction people conflate.
Your app is in Spanish, the confirmation email arrives in English. The locale doesn't survive the queue — here's the fix, plus the subject line and worker leakage nobody catches.
You don't need a separate RTL stylesheet. Tailwind's logical properties plus one dir attribute handle most of it — here's what they cover, and the parts you still have to think about.
Sessions don't exist, so the locale has to come from the request. Here's how Accept-Language negotiation actually behaves in Laravel, the fallback that silently misfires, and how to keep API responses cacheable.
__() works the same inside Livewire — until the second request. Here's why locale resets on every update, which middleware actually runs, and how to keep validation and JS text translated.
format() never localizes. translatedFormat() translates the words but keeps your ordering. isoFormat() is the one you usually want. Here's the difference, with real output in five languages.
Validation messages are the largest block of user-facing text most Laravel apps never translate. Here's the full structure — custom, attributes, nested rule types — and how to stop it drifting out of date.
Laravel's plural rules aren't CLDR — they're derived from Zend Framework code. Here's what that means for your lang files, why Polish and hyphenated locales silently break, and how to write forms that survive every language.
Names, counts, dates — make your Laravel translations dynamic with placeholders. Learn how AI preserves variables automatically across languages.
Publish the language files with php artisan lang:publish, wrap user-facing strings in __(), and set the locale per request in middleware. Once strings are externalized, adding a language is a content task. The Laravel localization guide on this site walks through the full setup.
PHP files with short keys suit application strings you want grouped and namespaced, such as validation or auth messages. JSON files keyed by the source sentence suit content-heavy apps where inventing a key for every string slows the team down. Both can be used in the same project.
trans_choice() selects a form using built-in plural rules for the active locale, so a Polish or Arabic string needs every form that language defines, separated by pipes. Supplying only two forms produces wrong text for some numbers rather than an error.
We'd like to use analytics and marketing cookies to understand how the site is used. They stay off unless you accept them. Cookie Policy
Essential
Required for the site to work
Google Analytics, to see which pages help
Measuring and personalising ads