Translation organization

Weblate organizes translatable VCS content of project/components into a tree-like structure.

  • The bottom level object is Projektkonfiguration, which should hold all translations belonging together (for example translation of an application in several versions and/or accompanying documentation).

  • On the level above, Komponentenkonfiguration, which is actually the component to translate, you define the VCS repository to use, and the mask of files to translate.

  • Above Komponentenkonfiguration there are individual translations, handled automatically by Weblate as translation files (which match Dateimaske defined in Komponentenkonfiguration) appear in the VCS repository.

Weblate supports a wide range of translation formats (both bilingual and monolingual ones) supported by Translate Toolkit, see Unterstützte Dateiformate.


You can share cloned VCS repositories using Weblate-interne URLs. Using this feature is highly recommended when you have many components sharing the same VCS. It improves performance and decreases required disk space.

Adding translation projects and components

Geändert in Version 3.2: An interface for adding projects and components is included, and you no longer have to use Django-Adminoberfläche.

Geändert in Version 3.4: The process of adding components is now multi staged, with automated discovery of most parameters.

Based on your permissions, new translation projects and components can be created. It is always permitted for users with the Add new projects permission, and if your instance uses billing (e.g. like https://hosted.weblate.org/ see Abrechnung), you can also create those based on your plans allowance from the user account that manages billing.

You can view your current billing plan on a separate page:


The project creation can be initiated from there, or using the menu in the navigation bar, filling in basic info about the translation project to complete addition of it:


After creating the project, you are taken directly to the project page:


Creating a new translation component can be initiated via a single click there. The process of creating a component is multi-staged and automatically detects most translation parameters. There are several approaches to creating component:

Von der Versionskontrolle

Creates component from remote version control repository.

Aus vorhandener Komponente

Creates additional component to existing one by choosing different files.

Zusätzlicher Zweig

Creates additional component to existing one, just for different branch.

Übersetzungsdateien hochladen

Upload translation files to Weblate in case you do not have version control or do not want to integrate it with Weblate. You can later update the content using the web interface or Weblates REST API.

Dokument übersetzen

Laden Sie ein einzelnes Dokument oder eine Übersetzungsdatei hoch und übersetzen Sie diese.

Bei Null anfangen

Create blank translation project and add strings manually.

Once you have existing translation components, you can also easily add new ones for additional files or branches using same repository.

First you need to fill in name and repository location:


On the next page, you are presented with a list of discovered translatable resources:


As a last step, you review the translation component info and fill in optional details:



Create a translation project and then add a new component for translation in it. The project is like a shelf, in which real translations are stacked. All components in the same project share suggestions and their dictionary; the translations are also automatically propagated through all components in a single project (unless turned off in the component configuration), see Übersetzungsspeicher.

These basic attributes set up and inform translators of a project:


Verbose project name, used to display the project name.


Project name suitable for URLs.


URL where translators can find more info about the project.

This is a required parameter unless turned off by WEBSITE_REQUIRED.


Text describing localization process in the project, and any other information useful for translators. Markdown can be used for text formatting or inserting links.

Kopfzeile „Language-Team“ setzen

Ob Weblate den Language-Team Header verwalten soll (dies ist zur Zeit nur eine GNU gettext Funktion).

Gemeinsamen Übersetzungsspeicher verwenden

Whether to use shared translation memory, see Geteilter Übersetzungspeicher for more details.

Der Standardwert kann durch DEFAULT_SHARED_TM geändert werden.

Zu einem gemeinsamen Übersetzungsspeicher beitragen

Whether to contribute to shared translation memory, see Geteilter Übersetzungspeicher for more details.

Der Standardwert kann durch DEFAULT_SHARED_TM geändert werden.


Configure per project access control, see Projekt-Zugriffssteuerung for more details.

Der Standardwert kann durch DEFAULT_ACCESS_CONTROL geändert werden.

Überprüfung aktivieren

Enable review workflow for translations, see Zugehörige Prüfer.

Quellenüberprüfung aktivieren

Enable review workflow for source strings, see Überprüfungen der Ausgangszeichenketten.

Hooks aktivieren

Whether unauthenticated Benachrichtigungs-Hooks are to be used for this repository.


Define language codes mapping when importing translations into Weblate. Use this when language codes are inconsistent in your repositories and you want to get a consistent view in Weblate or in case you want to use non-standard naming of your translation files.

The typical use case might be mapping American English to English: en_US:en

Multiple mappings to be separated by comma: en_GB:en,en_US:en

Using non standard code: ia_FOO:ia


The language codes are mapped when matching the translation files and the matches are case sensitive, so make sure you use the source language codes in same form as used in the filenames.


A component is a grouping of something for translation. You enter a VCS repository location and file mask for which files you want translated, and Weblate automatically fetches from this VCS, and finds all matching translatable files.

You can find some examples of typical configurations in the Unterstützte Dateiformate.


It is recommended to keep translation components to a reasonable size - split the translation by anything that makes sense in your case (individual apps or add-ons, book chapters or websites).

Weblate easily handles translations with 10000s of strings, but it is harder to split work and coordinate among translators with such large translation components.

Should the language definition for a translation be missing, an empty definition is created and named as „cs_CZ (generated)“. You should adjust the definition and report this back to the Weblate authors, so that the missing languages can be included in next release.

The component contains all important parameters for working with the VCS, and for getting translations out of it:

Name der Komponente

Verbose component name, used to display the component name.


Component name suitable for URLs.


Projekt, zu dem die Komponente gehört.


VCS to use, see Integration der Versionsverwaltung for details.


VCS repository used to pull changes.

Siehe auch

See Zugriff auf Repositorys for more details on specifying URLs.


This can either be a real VCS URL or weblate://project/component indicating that the repository should be shared with another component. See Weblate-interne URLs for more details.

Push-URL für Repository

Repository URL used for pushing. This setting is used only for Git and Mercurial and push support is turned off for these when this is empty.

For linked repositories, this is not used and setting from linked component applies.

Siehe auch

See Zugriff auf Repositorys for more details on how to specify a repository URL and Pushen von Änderungen aus Weblate for more details on pushing changes from Weblate.


URL of repository browser used to display source files (location of used messages). When empty, no such links will be generated. You can use Template markup.

For example on GitHub, use something like: https://github.com/WeblateOrg/hello/blob/{{branch}}/{{filename}}#L{{line}}

Falls Ihre Pfade relativ zu verschiedenen Verzeichnissen sind (Pfad enthält ..), sollten Sie das führende Verzeichnis durch den Filter parentdir entfernen (siehe Template markup): https://github.com/WeblateOrg/hello/blob/{{branch}}/{{filename|parentdir}}#L{{line}}

Exportierte Paketquelladresse

URL where changes made by Weblate are exported. This is important when Kontinuierliche Lokalisierung is not used, or when there is a need to manually merge changes. You can use Git-Exporter to automate this for Git repositories.


Which branch to checkout from the VCS, and where to look for translations.

For linked repositories, this is not used and setting from linked component applies.

Push Branch

Branch for pushing changes, leave empty to use Repository-Zweig.

For linked repositories, this is not used and setting from linked component applies.


This is currently only supported for Git, GitLab and GitHub, it is ignored for other VCS integrations.


Mask of files to translate, including path. It should include one „*“ replacing language code (see Sprachdefinitionen for info on how this is processed). In case your repository contains more than one translation file (e.g. more gettext domains), you need to create a component for each of them.

Zum Beispiel po/*.po oder locale/*/LC_MESSAGES/django.po.

In case your filename contains special characters such as [, ], these need to be escaped as [[] or []].

Einsprachige Basis-Sprachdatei

Base file containing string definitions for Einsprachige Komponenten.

Basisdatei bearbeiten

Whether to allow editing the base file for Einsprachige Komponenten.


Intermediate language file for Einsprachige Komponenten. In most cases this is a translation file provided by developers and is used when creating actual source strings.

When set, the source strings are based on this file, but all other languages are based on Einsprachige Basis-Sprachdatei. In case the string is not translated into the source language, translating to other languages is prohibited. This provides Qualitäts-Gateway für die Ausgangszeichenketten.

Vorlage für neue Übersetzungen

Base file used to generate new translations, e.g. .pot file with gettext.


In many monolingual formats Weblate starts with empty file by default. Use this in case you want to have all strings present with empty value when creating new translation.


Translation file format, see also Unterstützte Dateiformate.

Adresse für Fehlerberichte bei Ausgangszeichenketten

Email address used for reporting upstream bugs. This address will also receive notification about any source string comments made in Weblate.

Verbreitung von Übersetzungen erlauben

You can turn off propagation of translations to this component from other components within same project. This really depends on what you are translating, sometimes it’s desirable to have make use of a translation more than once.

It’s usually a good idea to turn this off for monolingual translations, unless you are using the same IDs across the whole project.

Default value can be changed by DEFAULT_TRANSLATION_PROPAGATION.

Vorschläge aktivieren

Whether translation suggestions are accepted for this component.

Abstimmen über Vorschläge

Turns on vote casting for suggestions, see Abstimmen über Vorschläge.

Vorschläge automatisch annehmen

Automatically accept voted suggestions, see Abstimmen über Vorschläge.


Customization of quality checks and other Weblate behavior, see Anpassen des Verhaltens mit Markierungen.

Erzwungene Qualitätsprüfungen

Liste der Prüfungen, die nicht ignoriert werden können, siehe Qualitätsprüfungen erzwingen.


Das Erzwingen der Prüfung aktiviert sie nicht automatisch, Sie sollten sie immer noch mit Anpassen des Verhaltens mit Markierungen in Übersetzungsmarkierungen oder Zusätzliche Informationen über Ausgangszeichenketten aktivieren.

Lizenzierung der Übersetzung

License of the translation (does not need to be the same as the source code license).


Die Benutzervereinbarung muss genehmigt werden, bevor der Benutzer die Komponenten übersetzen kann.

Neue Übersetzung hinzufügen

How to handle requests for creation of new languages. Available options:

Maintainer kontaktieren

Der Benutzer kann die gewünschte Sprache auswählen und die Projektbetreuer erhalten eine Benachrichtigung darüber. Es liegt an ihnen, ob Sie die Sprache zum Repository hinzufügen.

Geben Sie die URL für die Übersetzungsanweisungen an

Der Benutzer erhält einen Link zu einer Seite, die den Prozess des Beginns neuer Übersetzungen beschreibt. Verwenden Sie diese Seite, wenn ein formellerer Prozess gewünscht wird (z. B. die Bildung eines Teams von Personen vor dem Beginn der eigentlichen Übersetzung).

Neue Sprachdatei erstellen

User can select language and Weblate automatically creates the file for it and translation can begin.

Hinzufügen neuer Übersetzungen deaktivieren

There will be no option for user to start new translation.


The project admins can add new translations even if it is disabled here when it is possible (either Vorlage für neue Übersetzungen or the file format supports starting from an empty file).

Zeichenketten verwalten

Neu in Version 4.5.

Legt fest, ob Benutzer in Weblate neue Zeichenketten hinzufügen und bestehende entfernen dürfen. Passen Sie dies an Ihren Lokalisierungsprozess an – wie die neuen Zeichenketten eingeführt werden sollen.

For bilingual formats, the strings are typically extracted from the source code (for example by using xgettext) and adding new strings in Weblate should be disabled (they would be discarded next time you update the translation files). In Weblate you can manage strings for every translation and it does not enforce the strings in all translations to be consistent.

For monolingual formats, the strings are managed only on source language and are automatically added or removed in the translations. The strings appear in the translation files once they are translated.

Stil des Sprachcodes

Anpassen des Sprachcodes, der zur Generierung des Dateinamens für von Weblate erstellte Übersetzungen verwendet wird.


You can configure how updates from the upstream repository are handled. The actual implementation depends on VCS, see Integration der Versionsverwaltung.

Umbasieren (rebase)

Rebases Weblate commits on top of upstream repository on update. This provides clean history without extra merge commits.

Rebasing can cause you trouble in case of complicated merges, so carefully consider whether or not you want to enable them.

You might need to enable force pushing by choosing Git Push erzwingen as Versionsverwaltung, especially when pushing to a different branch.


Upstream repository changes are merged into Weblate one. This setting utilizes fast-forward when possible. This is the safest way, but might produce a lot of merge commits.

Zusammenführen ohne Fast-Forward

Upstream repository changes are merged into Weblate one with doing a merge commit every time (even when fast-forward would be possible). Every Weblate change will appear as a merge commit in Weblate repository.

Default value can be changed by DEFAULT_MERGE_STYLE.

Commit-, Add-, Delete-, Merge-, Erweiterungs- und Merge-Request-Nachrichten

Message used when committing a translation, see Template markup.


Bei Commit gleichzeitig Pushen

Whether committed changes should be automatically pushed to the upstream repository. When enabled, the push is initiated once Weblate commits changes to its underlying repository (see Lazy Commits). To actually enable pushing Repository push URL has to be configured as well.

Alter der Änderungen, bis ein Commit erfolgt

Sets how old (in hours) changes have to be before they are committed by background task or the commit_pending management command. All changes in a component are committed once there is at least one change older than this period.

Default value can be changed by COMMIT_PENDING_HOURS.


There are other situations where pending changes might be committed, see Lazy Commits.

Sperre bei Fehler

Locks the component (and linked components, see Weblate-interne URLs) upon the first failed push or merge into its upstream repository, or pull from it. This avoids adding another conflicts, which would have to be resolved manually.

The component will be automatically unlocked once there are no repository errors left.


Language used for source strings. Change this if you are translating from something else than English.


In case you are translating bilingual files from English, but want to be able to do fixes in the English translation as well, choose English (Developer) as a source language to avoid conflict between the name of the source language and the existing translation.

For monolingual translations, you can use intermediate translation in this case, see Zwischensprachedatei.


Regulärer Ausdruck, der zum Filtern der Übersetzung beim Scannen nach Dateimaske verwendet wird. Er kann verwendet werden, um die Liste der von Weblate verwalteten Sprachen einzuschränken.


You need to list language codes as they appear in the filename.

Some examples of filtering:

Filter description

Regulärer Ausdruck

Selected languages only


Exclude languages


Filter two letter codes only


Exclude non language files


Include all files (default)


Varianten regulärer Ausdruck

Regular expression used to determine the variants of a string, see Zeichenkette-Varianten.


Die meisten Felder können von Projektverantwortlichen oder Administratoren in der Weblate-Benutzeroberfläche bearbeitet werden.


Komponenten mit höherer Priorität werden Übersetzern zuerst angeboten.

Geändert in Version 4.15: This now also affects ordering of matched glossary terms.

Eingeschränkter Zugriff

By default the component is visible to anybody who has access to the project, even if the person can not perform any changes in the component. This makes it easier to keep translation consistency within the project.

Restricting access at a component, or component-list level takes over access permission to a component, regardless of project-level permissions. You will have to grant access to it explicitly. This can be done through granting access to a new user group and putting users in it, or using the default custom or private access control groups.

The default value can be changed in DEFAULT_RESTRICTED_COMPONENT.


This applies to project admins as well — please make sure you will not loose access to the component after toggling the status.

In Projekten teilen

You can choose additional projects where the component will be visible. Useful for shared libraries which you use in several projects.


Sharing a component doesn’t change its access control. It only makes it visible when browsing other projects. Users still need access to the actual component to browse or translate it.

Verwendung als Glossar

Neu in Version 4.5.

Ermöglicht die Verwendung dieser Komponente als Glossar. Sie können mit Glossarfarbe konfigurieren, wie es aufgelistet werden soll.

Das Glossar ist in allen durch In Projekten teilen definierten Projekten zugänglich.

It is recommended to enable Zeichenketten verwalten on glossaries in order to allow adding new words to them.

Siehe auch



Display color for a glossary used when showing word matches.

Template markup

Weblate uses simple markup language in several places where text rendering is needed. It is based on The Django template language, so it can be quite powerful.

Currently it is used in:

There following variables are available in the component templates:

{{ language_code }}


{{ language_name }}


{{ component_name }}

Name der Komponente

{{ component_slug }}


{{ project_name }}


{{ project_slug }}


{{ url }}

Übersetzungs URL

{{ filename }}


{{ stats }}

Translation stats, this has further attributes, examples below.

{{ stats.all }}

Total strings count

{{ stats.fuzzy }}

Count of strings needing review

{{ stats.fuzzy_percent }}

Percent of strings needing review

{{ stats.translated }}

Translated strings count

{{ stats.translated_percent }}

Translated strings percent

{{ stats.allchecks }}

Number of strings with failing checks

{{ stats.allchecks_percent }}

Percent of strings with failing checks

{{ author }}

Author of current commit, available only in the commit scope.

{{ addon_name }}

Name of currently executed add-on, available only in the add-on commit message.

The following variables are available in the repository browser or editor templates:


Aktueller Zweig


line in file


filename, you can also strip leading parts using the parentdir filter, for example {{filename|parentdir}}

You can combine them with filters:

{{ component|title }}

You can use conditions:

{% if stats.translated_percent > 80 %}Well translated!{% endif %}

There is additional tag available for replacing characters:

{% replace component "-" " " %}

You can combine it with filters:

{% replace component|capfirst "-" " " %}

There are also additional filter to manipulate with filenames:

Directory of a file: {{ filename|dirname }}
File without extension: {{ filename|stripext }}
File in parent dir: {{ filename|parentdir }}
It can be used multiple times:  {{ filename|parentdir|parentdir }}

… und andere Django-Vorlagenfunktionen.


Fetching VCS repository and importing translations to Weblate can be a lengthy process, depending on size of your translations. Here are some tips:

Optimize configuration

The default configuration is useful for testing and debugging Weblate, while for a production setup, you should do some adjustments. Many of them have quite a big impact on performance. Please check Produktionseinrichtung for more details, especially:

Check resource limits

If you are importing huge translations or repositories, you might be hit by resource limitations of your server.

  • Check the amount of free memory, having translation files cached by the operating system will greatly improve performance.

  • Disk operations might be bottleneck if there is a lot of strings to process—the disk is pushed by both Weblate and the database.

  • Additional CPU cores might help improve performance of background tasks (see Hintergrundaufgaben mit Celery).

Disable unneeded checks

Some quality checks can be quite expensive, and if not needed, can save you some time during import if omitted. See CHECK_LIST for info on configuration.

Automatic creation of components

In case your project has dozen of translation files (e.g. for different gettext domains, or parts of Android apps), you might want to import them automatically. This can either be achieved from the command-line by using import_project or import_json, or by installing the Komponentenerkennung add-on.

To use the add-on, you first need to create a component for one translation file (choose the one that is the least likely to be renamed or removed in future), and install the add-on on this component.

For the management commands, you need to create a project which will contain all components and then run import_project or import_json.