Multi-language to Next.js website
Hey! Wasn't there a tool that does multi-language support for a website with llm? I know there is an i18next, but it still requires rewriting half of an app and making translations myself. Wasn’t there any fancy AI autotranslator that does it?
The closest thing I found is to add a script to load the google translator to the client.
Would really appreciatee advises
6 Replies
please dont tell me there is no such thing, coz i'll have to build it myself... these json files as translation storage are complete nonsense in 2025
Translate your app | Tolgee
Open-source localization platform developers enjoy working with. With in-app translation, seamless integrations, and collaborative tools, scaling multilingual apps becomes easy. Sign up for free.
If you automated the translation you have to consider the quality of the output do you know the languages you are targeting?
Set i18next up first then work on translations. Give it to a good LLM (Gemini & Claude are good at this) and use structured output to make things easier.
Give it your base language file. You can improve from there if necessary
Google AI Studio
Google AI Studio is the fastest way to start building with Gemini, our next generation family of multimodal generative AI models.
first of all, i think i18n is horrible dev experience…
second, if I read correctly, it still doesn’t solve the problem with the db (i don’t wanna store so many column_de, column_fr).
for now i just activated google translate script on the website and use toggle with cookies to save language pref, but I will think of some solution that less pain in the ass then i18n…
You shouldn't need duplicate columns in the database, internationalization is a client side thing.
As an example, you can still render the same
date_created column in different languages on the client, it just requires that you pass a language argument to whatever date string-ification function you're using.
If you're talking about translation databases, if you want different files for different languages, consider using https://github.com/amannn/next-intl, where you'll have an en.json, jp.json, etc. You could also attempt to make your own internationalization system, although getting it to work with SSR, and be typesafe might be a little bit tricky.