LingoHub supports importing and exporting Glossaries in CSV format. This allows you to manage terms, translations, and metadata in bulk using spreadsheet software like Microsoft Excel or Google Sheets.
💡 Prefer XML standards? If your team uses standardized translation exchange formats, check out our guide on How to import and export Glossaries using TBX?.
How to prompt a Glossary import or export
Import a Glossary
Click AI in the top navigation bar and select Glossary under Context.
Select the Glossary you want to update.
In the top-right header, click Import.
In the pop-up, drag and drop your CSV file (max. 1 file, up to 10MB) or click browse.
Click Import.
⚠️ Important: Importing a CSV file will overwrite existing terms in your Glossary. Make sure your file follows the specifications below before uploading.
Export a Glossary
Click AI, then Glossary and select your Glossary.
Click the dropdown arrow next to the Import button in the top-right header and select Export.
In the pop-up, choose Download as CSV.
(Optional) Check Send me an email with the link when the file is ready to download.
Click Download.
💬 Please note: During export, LingoHub exports the full list of supported CSV header fields by default. Even if optional fields contain no value for certain terms, the header columns are preserved in the file.
Specifications: CSV header fields overview
LingoHub reads and exports Glossary CSV files row-by-row using the entryId field to group source terms, target translations, and metadata together.
Field name | Required / Optional | Default value | Description |
| Required | / | Unique term ID. |
| Optional | / | AI Context definition for the term. |
| Optional | TRANSLATE | Defines if the term should be localized or left untranslatable. |
| Optional | ENFORCED | Controls Quality Check (QC) validation rules. |
| Required | / | Content / text of the term. |
| Required | / | Language code of the term (ISO 639-1). |
| Optional | / | Custom matching pattern (used only if termMatching is CUSTOM). |
| Optional | / | Algorithm used for term matching. |
| Optional | / | Case sensitivity configuration. |
| Optional | / | Administrative recommendation status. |
| Optional | / | Grammatical part of speech/text. |
| Optional | / | Grammatical gender classification. |
| Optional | / | Grammatical number classification. |
| Optional | / | Classification type of the entry. |
Specifications: Allowed values for metadata fields
entryTranslationPreference
TRANSLATE: The term can be translated into target languages (Default when empty).NEVER_TRANSLATE: The term must stay in the original source language across all target locales.
entryEnforcementStatus
ENFORCED: The term is validated and prompts quality checks (QC) if missing or incorrect (Default when empty).INFORMATIONAL: Displays the term in the editor for reference without prompting quality checks.
termMatching
FUZZY("fuzzy"),PREFIX("prefix"),EXACT("exact"),CUSTOM("custom")
termCaseSensitive
YES("yes"),PERMISSIVE("permissive"),NO("no")
termUsageStatus
PREFERRED("preferredTerm-admn-sts")ADMITTED("admittedTerm-admn-sts")NOT_RECOMMENDED("deprecatedTerm-admn-sts")
termPartOfSpeech
NOUN("noun"),VERB("verb"),ADJECTIVE("adjective"),ADVERB("adverb"),PROPER_NOUN("properNoun"),OTHER("other")
termGrammaticalGender
MASCULINE("masculine"),FEMININE("feminine"),NEUTER("neuter"),OTHER("other")
termGrammaticalNumber
SINGULAR("singular"),PLURAL("plural"),MASS("mass"),DUAL("dual"),OTHER("other")
termType
FULL_FORM("fullForm"),ACRONYM("acronym"),ABBREVIATION("abbreviation"),SHORT_FORM("shortForm"),VARIANT("variant"),PHRASE("phrase")
Need more help?
Couldn't find what you were looking for? We are here to help! Reach out to our team at [email protected], and we will gladly assist you.