Compare
Transept vs Lokalise for content work
Lokalise is one of the strongest enterprise localization platforms — built for product strings, continuous localization, and developer workflows. Transept is built for the rest of localization: documents, marketing copy, content, the things that don’t fit a string-key model. Many teams use both.
Free to begin · No card required
Featured on
Lokalise is the localization platform engineering teams pick when they ship multilingual software. It treats translation as string-key data — `LOGIN_BUTTON_TEXT` in `en.json`, `de.json`, `fr.json` — with branches, CI/CD hooks, and the developer rituals product teams already use. That model is excellent for software UI. It’s the wrong shape for everything else: a 50-page report, a marketing email, a knowledge-base article, a launch announcement. Transept fills that gap. Most teams that adopt both use Lokalise for product strings and Transept for the document-heavy content that doesn’t fit a translation file. Here’s how to tell which surface is which.
Where each tool is the right pick
| Feature | Lokalise | Transept |
|---|---|---|
| Product string localization (i18n) | Yes | NoNot the surface |
| CI/CD integration | Yes | No |
| Developer workflows (branches, MRs) | Yes | No |
| DOCX / PDF document translation | Partial | Yes |
| HTML email & landing pages | Partial | Yes |
| Notion & Google Drive | No | Yes |
| Sentence-level alternatives | No | Yes |
| Translation memory | YesStrong for product strings | YesReuses past work, finds reworded matches |
| Decision-context memory | No | YesRemembers the reasoning, not just the segment |
| Model quality tiers (per doc/sentence) | Partial | Yes |
| Self-serve onboarding (no sales call) | No | Yes |
| Free tier with full feature set | NoFree trial only | Yes |
| Starting price (paid) | From ~$144/mo, billed annually | €29/mo, excl. VAT |
Lokalise pricing checked July 17, 2026 against Lokalise’s published pricing. Plans and prices are set by Lokalise and may have changed since. View Lokalise pricing
Lokalise is for continuous product localization. Transept is for high-quality document and content translation workflows. They overlap on glossary and translation memory, but they’re solving different problems. If you’re localizing iOS strings, you want Lokalise. If you’re localizing a launch kit, a Notion workspace, or a 200-page book, you want Transept.
When Transept is the better fit
Document-heavy content
Books, articles, FAQs, knowledge bases, contracts. Lokalise is string-key-shaped; these aren’t.
Marketing & launch work
Emails, landing pages, social, press kits, blog posts. The stuff that doesn’t live in a developer’s repo.
Small teams without procurement budgets
Lokalise starts around $140/mo and scales up. Transept starts free and Starter is €29. Self-serve, no sales call.
Memory that finds rewordings
Reuse a sentence even when it’s been reworded, not just an exact match — every translation you approve is remembered automatically and offered back the next time something close comes up. It’s free on every plan, feeds the AI as it works, and imports and exports TMX and XLIFF so nothing’s locked in.
Memory that remembers the why
Lokalise remembers the string you shipped. Transept also remembers the reasoning around it — the alternatives you rejected, the review comments left on a sentence — and feeds that context back to the model on the next run. The AI repeats the decision behind your wording, not just the wording, so it stops re-suggesting phrasings you already turned down.
10 languages, one weekend
We translated Transept itself into ten languages over three days, running our own pages through the editor, glossary, and memory on this site. If you are reading this in German or Ukrainian, it came through the same workflow you are looking at.
Field notes from the weekend— Don’t take our word for it —
The editor, in miniature
A working slice of the real thing — Literess, glossary, styleguide, workflows, and the translation memory are all live. Click around.
Here to help you translate
A key turned in the lock and the door swung open.
У замку повернувся ключ, і двері розчахнулися.
The knock came just before midnight.
Стукіт пролунав перед самою північчю.
FAQ
- Many teams do. Lokalise runs the product-string side; Transept runs the document and marketing side. Share the same glossary between the two by exporting from one and importing into the other.
- API access for document translation is on the roadmap. For now, the workflow is interactive — upload, translate, export. Most document workflows are interactive anyway.
- Both remember what you’ve translated and reuse it. Lokalise builds its memory from accepted product strings and is genuinely strong for continuous software localization — a saved entry surfaces as a suggestion above a 50% match, keyed to the message IDs your engineers ship. Transept builds its memory automatically from every translation you approve and matches by meaning as well as exact text, so a reworded sentence surfaces alongside a near-duplicate — and it searches past comments, chat, and whole documents, not just segment pairs. For software strings, Lokalise is the right pick; for documents and content, Transept is.
- No on both counts. Transept’s memory builds itself from the translations you approve — there’s no separate database to curate and no concordance to manage. Reuse never costs words and it’s included on every plan, free tier included. If you already have a memory elsewhere, import it over TMX or XLIFF, and you can export the same way whenever you want to move.
- Are you localizing strings in a JSON file your engineers ship with the product? Lokalise. Are you localizing a document, an email, a FAQ, or a blog post? Transept. Both? Both.
- Lokalise focuses on string keys and developer workflows. Document uploads exist but are not the primary surface; DOCX/PDF round-trip is friction-heavy compared to a tool built for it. Transept is the dedicated document-first workspace.
- If you ship software with localized UI strings, yes — Lokalise is hard to replace for that. Transept doesn’t target string-key localization workflows. If you’re only translating documents and marketing content, Transept on its own is enough.
- Both have AI translation. Lokalise routes through their own AI for string-level translation with TM integration. Transept runs on frontier models (currently Google Gemini) on a provider-agnostic engine, with sentence-level alternatives, glossary enforcement, and a multi-stage QA workflow tuned for documents.
- Yes — export from Lokalise as CSV and import into Transept (and vice versa). Glossary format is compatible; keep the master in one tool and re-import periodically.
- Transept by a wide margin at small team sizes. Lokalise Explorer starts at ~$140/month/seat; with Transept, creating a team and inviting your translators is free, a Starter plan is €29/month with every feature unlocked, and a shared word pool is optional — €29 per seat, each adding 100,000 words the whole team draws from. Lokalise prices for the value it delivers on continuous product localization, which is a different problem.
Keep reading around this comparison
- FeatureDocument translation that holds together→DOCX, PDF, Markdown — uploaded, parsed into blocks, translated with the rest of the document for context. Page 1 reads like page 300; the…
- FeatureBatch translation without the spreadsheet→A 30-file launch kit into 12 languages used to mean a spreadsheet, a project manager, and a week. With batch translation, it’s a queue you…
- FeatureTeam review, on the sentence→Inline threads on any sentence. Real-time presence so two reviewers don’t step on each other. An activity feed of who changed what.…
- Use caseLocalize the help center without breaking product terms→Help articles need a clear support voice, exact product UI strings, and zero drift across a hundred pages. Build a product glossary once,…
- CompareTransept vs Phrase self-serve vs enterprise→Phrase is a powerful enterprise localization platform — TMS depth, vendor management, integrations, LQA. Transept is a different shape:…