Glossary & terminology

    Your terminology. Consistent across every translation.

    Keep defined terms, entity names and approved wording consistent across every page and every document. Fewer repeated corrections. Faster review. Output your team can trust.

    No credit card required · Your first translation in minutes.

    Trusted by teams at
    Franklin TempletonLaSalleKearneyYaraShimadzuRBC Royal Bank of Canada

    Fluent is not the same as consistent

    A translation can read perfectly and still force your team to check every occurrence of every important term.

    The same term quietly changes

    “Agreement” becomes agreement in one clause and contract in another. Both sound plausible. Only one matches the defined term your team approved.

    Distinct roles become interchangeable

    Shareholders, partners and members can collapse into the same word in another language. The output reads smoothly while the meaning loses precision.

    Approved names get translated

    Entity names, product names, tickers and trademarks are changed when they should have stayed exactly as written.

    Terminology your team can rely on

    Set it once. Apply it across the whole body of work.

    The same approved term across every page

    Your glossary applies throughout the document, so the wording on page 1 still matches the wording on page 400 — and the next document in the same project follows it too.

    • Defined terms stay consistent from first page to last
    • The same terminology carries across related documents
    • Multi-word phrases are controlled, not just single words
    • Works on native files and scanned documents
    Start translating
    Master agreement400 pages
    Page 1Agreement
    Page 400Agreement
    Glossary appliedConsistent throughout

    Names stay exactly as your business uses them

    Protect the words that should never be translated: company and product names, tickers, citations, trademarks and internal acronyms.

    • Do-not-translate entries for protected names
    • Approved translations for company-specific language
    • Separate terminology by team or workspace
    • One glossary across every Bluente surface
    Talk to sales
    Do not translateProtected
    SourceNorthstar™
    Translated fileNorthstar™
    Name preserved exactlySpelling and capitalisation unchanged

    Every correction makes future work easier

    The terminology your reviewers have already approved becomes reusable knowledge. Instead of correcting the same phrase in every new translation, your team decides once and applies it everywhere.

    • Reuse decisions your reviewers already made
    • Reduce repetitive terminology corrections
    • Keep each team’s language separate
    • Your terminology is never used to train a shared model
    Translate with your terminology
    Reviewer correctionSaved
    BeforeService contract
    ApprovedServices Agreement
    Added to glossaryServices Agreement
    Next documentServices Agreement

    What changes for your reviewers

    01

    Fewer repeated corrections

    The terms your team fixes in every document are already applied before review begins.

    02

    Faster review of long document sets

    Reviewers spend less time searching for terminology drift across hundreds of pages and related files.

    03

    More confidence in every deliverable

    Approved language remains consistent wherever the document is translated — in the web app, Microsoft 365, browser extension or API.

    Glossary or model training?

    Choose based on what your reviewers are changing.

    If reviewers sayWhat you needWhy
    “This term is wrong” or “this term keeps changing”Custom glossaryIt applies approved terminology and protects words that must not be translated.
    “It is correct, but it does not sound like us”Model trainingIt adapts register, sentence construction and house style using work your team has already approved.

    Frequently asked questions

    Can you build the glossary for us?
    Yes. Most teams take the assisted route: we extract candidate terms from documents you have already approved, bring you a draft with sources noted, and you accept or reject line by line. You keep every decision; we do the assembly.
    How many entries can we have?
    No limit, on any tier. Most vendors cap glossary size by plan; we do not. Worth knowing that focused beats exhaustive — the constraint is editorial, not commercial.
    Can it differ by team and by language pair?
    Both. Terminology is scoped per workspace, so litigation and marketing keep separate lists, and an entry can differ by pair — the right term in Traditional Chinese for Taiwan is frequently not the right term in Simplified Chinese.
    What about words that change form?
    This is the real limit of terminology enforcement in every system, ours included. A term locked rigidly into German, Polish, Russian, Finnish or Arabic can produce a grammatically wrong sentence — which is why strictness is per entry. Enforce defined terms and entity names exactly; leave preferences loose enough for the sentence to work.
    Does it apply to scanned documents and through the API?
    Yes to both. Terms are enforced on text recovered by OCR exactly as on native files, and the API uses the same list as the web app — so a pipeline you built yourself and a document translated by hand agree.
    Can we export the glossary?
    Not self-serve today. Keep your master list in the spreadsheet you uploaded from and treat the version in Bluente as the copy applied at translation time. If you need current state back, ask your account contact.

    Your terminology should not change halfway through the document

    Translate with the language your team has already approved — consistently, across every page and every file.