Dear Community,
We are using QField extensively in Luxembourg, where projects often need to work in multiple languages (LU / FR / DE / EN etc.). It would therefore be extremely helpful if interface elements and project fields could be easily translated or switched between languages.
This topic was already mentioned during the last QField Partner Meeting. There is also an initiative where people can contribute to translations – and we would like to encourage everyone to participate and help move this forward: 
From what I understand, automatic translation in QField projects is not yet available.
@QField-Team Is this something that might be planned in a future update?
So far the question remains:
Do you have examples of bilingual or multilingual QField projects, and how did you structure them efficiently? Duplicating fields for each language quickly becomes complicated from a data management perspective.
Thanks for any feedback!
Warm regards,
Tommy from COFT-Team
1 Like
Hello Tommy,
There is this entry in the QField docs on multilingual QField projects: Multilingual Project Support - QField Ecosystem Documentation
I myself have not used this before, so I have no idea how it works or performs, but it seems to address a lot of your questions?
Hi,
There is a way to do it through configured aliases and dynamic lists.
You can have a ‘seting’ table with a “language” field.
For each field, you can configure aliases based on the value of “language” from another table.
(Alternatively, you could save the language value from the seting table, in every table, and use it for the aliases to make it faster.)
The same approach can be used with lists: they would need to be translated into each required language on the same table and then filtered based on the selected language, before populating the required fields.
I don’t know how QField would behave with a large project and many languages. My tests didn’t work two years ago because aliases weren’t supported, but now it should work.