Skip to content

Translate the words. Preserve the work.

Lab Forge is a production translation workbench for 82 languages. Trados and memoQ packages go back as packages, client terminology is enforced rather than suggested, and 47 deterministic checks run over the finished file before you download it.

View pricing
Already have an account? Sign in →
Specimen workbench · not a live job

How a file moves through Lab Forge

  1. Open a project

    Set the client, source language, and target languages.

  2. Upload and estimate

    Drop the file. Billable words, locked rows, and cost show before anything runs.

  3. Translate against the glossary

    The job uses document context and locked terms. Pause or cancel from the pipeline page.

  4. Review, export, certify

    Edit in the QA panel, download the file, and export or share the delivery certificate.

What you can run

These are the surfaces that exist in the product today. None of them are billed as a live demo on this page.

  1. Translation tasks

    Run memoQ and Trados bilingual RTF, XLIFF and SDL packages, Word, PDF, subtitles, and other source files. Locked segments stay locked. QA findings are listed before you download.

  2. Glossary and terminology

    Attach project glossaries and passthrough terms. The pipeline is required to keep those strings, not invent near-matches.

  3. Certificate export

    A finished task can issue a delivery certificate. Anyone with the link can check it on the public verify page.

  4. Legal document verdicts

    Legal Review reads a contract, scores clause risk, and returns Word comments plus tracked changes. It is analysis, not legal advice.

  5. Image Studio and official documents

    Image Studio confirms token cost before it generates a private image bundle. Official Document overlay translates text on a scan while photos, stamps, signatures, and the MRZ stay on the original pixels.

What makes the output defensible

Anything can produce a draft. These are the parts a language-services buyer audits: enforced terminology, deterministic checks, an MQM typology, and file formats that return in the shape they arrived.

  1. Terminology

    Glossary terms are enforced, not suggested

    Locked client terms are injected into the translation prompt and then checked again on the finished text, so a term that came back as a near-synonym is reported as a glossary finding instead of shipping quietly. Terminology is scored as its own dimension.

  2. Quality assurance

    47 deterministic checks, with no model in the QA path

    Numbers, units, currencies, dates, placeholders, inline tags, brackets, truncation and CJK passthrough are verified in pure code — the same input always produces the same findings, and the QA gate reports them before you download. Nothing here asks a model whether the translation is good.

  3. MQM scorecard

    Quality reported on the MQM framework buyers already audit against

    Findings are classified on the MQM CORE dimensions — terminology, accuracy, linguistic conventions, style, locale conventions, audience appropriateness, design and markup — and weighted by severity into a scorecard you can read per task, export, or share. Your reviewers argue with a typology, not with a single opaque number.

  4. CAT interop

    SDLXLIFF, memoQ and Trados packages go back as packages

    34 file extensions route to 20 purpose-built processors. Trados and memoQ project packages are unpacked, translated through a native XLIFF 1.2 reader that understands bpt/ept/ph inline tags, then rebuilt so every non-payload entry is preserved byte for byte. Locked segments, segment IDs and status columns survive the trip.

  5. Subtitles

    SRT and WebVTT keep their timing

    WebVTT has its own processor rather than an SRT alias, because cue identifiers, cue settings, NOTE and STYLE blocks and speaker markup are not SRT and quietly corrupt when treated as such. Timings and line counts are preserved on both.

  6. Translation memory

    Translation memory with CAT-standard match bands

    Fuzzy matching combines token edit distance with semantic similarity and reports the match band a CAT tool would report, including in-context exact matches. TMX imports and exports round-trip, and Trados .sdltm memories are read directly, so an existing memory arrives with you.

  7. Tracked changes

    Word deliverables carry real tracked changes

    Review output is written as genuine Word insertions and deletions with comments anchored on the change, so a client opens the file in Word and accepts or rejects edit by edit. Run-level styling is preserved and the source is copied before any write.

Request a workspace

Registration uses an invite key from your account manager, unless the operator has opened signup. Rates are on the Pricing page. Open Translate is available after you sign in.

Sign in to Open Translate