# 🌍 Native multilingual support without duplicating columns **URL:** \ **Category:** Feature Requests\ **Tags:** data-sync, api, actions, custom-code\ **Created:** [April 28, 2025, 11:15pm UTC](https://community.glideapps.com/t/native-multilingual-support-without-duplicating-columns/81606 "2025-04-28T23:15:19Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Alexis-Driing](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/alexis-driing/32/70158_2.png) [@Alexis-Driing](https://community.glideapps.com/u/Alexis-Driing)\ **Post date:** [April 28, 2025, 11:15pm UTC](https://community.glideapps.com/t/native-multilingual-support-without-duplicating-columns/81606/1 "2025-04-28T23:15:19Z")
Hi everyone 👋, I wanted to share an idea that could really simplify the way we manage multilingual apps in Glide. Today, when we want to create an app in multiple languages, we have to duplicate every text field for each language (FR, EN, ES, etc.), which quickly makes the database complicated and harder to maintain. **What if Glide could offer:** - Automatic detection of the user’s device or browser language, - A single text field containing all translations in a structured way (like JSON or key-value pairs), - And automatically display the right language version based on the user’s settings? **Benefits could include:** - Cleaner and lighter data structure, - Much easier updates and maintenance, - A much better user experience, especially for international apps. Has anyone else faced the same challenges? Would love to hear your thoughts and maybe gather more interest around this idea! 🙌 ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [April 29, 2025, 3:35am UTC](https://community.glideapps.com/t/native-multilingual-support-without-duplicating-columns/81606/2 "2025-04-29T03:35:42Z")
> [@Alexis-Driing](#): > > Today, when we want to create an app in multiple languages, we have to duplicate every text field for each language (FR, EN, ES, etc.) No, that’s not necessary at all. > [@Alexis-Driing](#): > > - A single text field containing all translations in a structured way (like JSON or key-value pairs), > - And automatically display the right language version based on the user’s settings? That’s exactly what I usually do. > [@Best way to create an app with multiple languages](https://community.glideapps.com/t/best-way-to-create-an-app-with-multiple-languages/66358/8): > > Not exactly. I’ve been using variations of this approach for about 3 years now, and the approach has evolved and been refined with each new App that I’ve implemented it in. The current approach works as follows: I have a separate “Strings” table. This table has one row for each text snippet that is used anywhere in the App. I have a JSON column that contains the translations for each supported language. It looks something like this: { "translations": { "zh": "输入总工作时间", "ms": "Masu… There is also [https://www.weglot.com/](https://www.weglot.com/), which I know others have used successfully with Glide Apps. ---
**Author:** ![Mazen](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mazen/32/84042_2.png) [@Mazen](https://community.glideapps.com/u/Mazen)\ **Post date:** [May 8, 2025, 11:18pm UTC](https://community.glideapps.com/t/native-multilingual-support-without-duplicating-columns/81606/3 "2025-05-08T23:18:51Z")
There’s multiple ways to do it, and all of it is still kind of complicated, I agree that a multilingual app is a very nice and needed feature, hope we hear a good news about it soon. ---
**Author:** ![Stef](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/stef/32/48261_2.png) [@Stef](https://community.glideapps.com/u/Stef)\ **Post date:** [June 5, 2025, 10:39am UTC](https://community.glideapps.com/t/native-multilingual-support-without-duplicating-columns/81606/4 "2025-06-05T10:39:11Z")
+1