Free template · No signup
A translation glossary records the wording a team has agreed to use. This free template helps you capture a term's meaning, target locale, preferred translation and approval owner instead of keeping an unexplained word list.
Use it for recurring product labels, campaign claims and protected brand names. Start with terms that cause disagreement or affect meaning rather than collecting every word in a document.
The sample row is a fictional product label, workspace. Its definition makes clear that it means a collaboration area, not a physical office. Leave the target wording pending until a qualified reviewer approves it.
Edit the worked example. These fields are processed in your browser and are not sent to a Vitra server. Page analytics, if enabled, are separate.
Your handoff, ready to edit
workspace
A collaboration area containing projects and members. Example: Create a workspace for your campaign team.
Spanish (es-MX)
Pending local language review
Use the collaboration meaning. Keep the fictional brand name Luma unchanged. Do not substitute the term used for a physical office.
Owner: product language reviewer. Status: draft. Reference: workspace settings screenshot, source version 2.
0 of 4 checks selected. This is not a quality score or release approval.
Free. No signup required. Markdown includes selected checks; CSV contains the editable fields. Changes are not saved after leaving or reloading this page.
The most useful first rows are the terms your team already debates. A product feature, a repeated benefit claim or a specialist label deserves an agreed definition. Common words only need a row when their meaning or treatment is specific to your work.
A central brand owner can explain the concept and protected name. A reviewer who knows the target market checks the wording. Record both decisions where needed. One English definition can support several target locales without pretending the preferred term is identical everywhere.
This CSV is a working template. TMS products have different column names, required fields and import options. Confirm the target schema, map the columns and test a few rows before uploading a large glossary. Keep the reviewed source sheet as a reference.
When the job repeats
Keep approved wording close to the translation job. Use Vitra TB when you need richer concept-based terminology alongside the glossary.
A glossary records preferred terms and usage guidance. Translation memory stores previous source and target content for reuse. A team may need both; the glossary does not replace the review of a reused sentence.
Treat it as a planning sheet first. Check the current glossary or terminology import fields and map the columns before importing. This page does not promise a one-click import or publish a private import schema.