# Translation weweb and i18next o

**URL:** <https://community.weweb.io/t/translation-weweb-and-i18next-o/20268>\
**Category:** Ask us anything\
**Created:** [October 29, 2025, 11:23am UTC](https://community.weweb.io/t/translation-weweb-and-i18next-o/20268 "2025-10-29T11:23:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\
**Post date:** [October 29, 2025, 5:24pm UTC](https://community.weweb.io/t/translation-weweb-and-i18next-o/20268/2 "2025-10-29T17:24:46Z")

</div>

Hi Philbert 👋

This looks like a comprehensive set of tools for translation, haven’t heard of anyone using it yet.

Most people end up indeed using our own built in translation system, if not another solution is to use your backend to help you with that as well:

> [@How to manage translations](https://community.weweb.io/t/how-to-manage-translations/2543/2):
>
> I have worked on very large application and we used additional columns for the translations. In our case, the customer created a form (Field labels and input values stored in base language columns). Then, using additional columns, they added translated version of the labels in the languages they wanted to support. Our customer customers then visit the form, select the language they want and see the form in their native language. When the user enters in a value into the form and saves, that w…

---

_[View the full topic](https://community.weweb.io/t/translation-weweb-and-i18next-o/20268)._