Comparison
Dialecto vs Weblate
Weblate works from its own clone of your repository and commits translations back to it. Dialecto reads only your translation files, and rewrites your code when a key or a text changes.
Advantages over Weblate
- Reads only your translation files, never a clone of your whole repository.
- Rewrites your code when you rename a key or change a gettext text.
- Lets you edit a translation by clicking it on your running Phoenix or Astro app.
- Costs far less than Hosted Weblate, with a free tier that does real work.
We make Dialecto, so we're biased. Every claim links to its source, checked 6 October 2026.
Feature comparison
Security and source of truth
Repository accessWeblateWhole repository clonedDialectoTranslation files only
Manual file editsWeblateLock Weblate firstDialectoRepository version wins
Weblate's docs warn of merge conflicts when a file changes both in Weblate and outside it, and advise locking Weblate first. Dialecto treats your repository as the source, so an edit made there simply wins. 3
EU hostingWeblateIn the EU, mainly GermanyDialectoIn the EU
Hosted Weblate runs mainly in Germany and keeps customer data in the EU. Dialecto runs in the EU too, and text leaves it only through a model provider you pick. 4
Self-hostingWeblateFree softwareDialectoAvailable
Both run on your own servers. Weblate is free software under the GPL, so self-hosting it costs only the upkeep. 5
AI context
Curated contextWeblateGlossary, persona, styleDialectoDomain, voice, audience, glossary
Both give the model more than the bare string: Weblate sends the key, its explanation, glossary terms and your style notes. Dialecto adds the domain each key belongs to, your brand voice and the audience you're writing for. 6
Model choiceWeblateMany, local includedDialectoLocal or hosted
Both take your provider, and both can draft with a local model: Weblate through Ollama, Dialecto when you host it yourself. 6
ValidationWeblateMany, some enforcedDialectoChecked on every change
Weblate runs a wide set of checks and can enforce some, holding a string back until it's fixed. Dialecto checks placeholders, plurals and glossary terms on every change, and its merge gate holds back new untranslated strings. 7
Key renames
Batch key renamesWeblateOne key at a timeDialectoWhole families at once
Rename every basket.* key to cart.* in every language in one step. Weblate renames one key at a time, keeping its translations. 8
Call-site rewritesWeblateBy handDialectoIn the same pull request
Dialecto rewrites every place your code uses a renamed key or a changed gettext text, and lists anything it can't rewrite safely. Weblate's docs leave your code to you. 8
Changes
Changes as pull requestsWeblateBatched, through a forkDialectoOne line of diff each
Editing
In-context editing in developmentWeblateNone foundDialectoPhoenix and Astro
Click a translation on your running app and change it there, while you develop. We found no on-page editor in Weblate's docs; it shows screenshots beside each string instead. 8
Try the editorScreenshotsWeblateBeside each stringDialectoNot offered
Weblate shows translators a screenshot of where each string appears, which helps when the text alone is ambiguous. 8
Reach
Formats beyond gettext and JSONWeblateDozens, mobile includedDialectogettext and JSON
Weblate reads dozens of formats, from Android and iOS resources to XLIFF and Qt. For a mobile app today, Weblate covers more. 12
Runtime deliveryWeblateA JavaScript CDN add-onDialectoIn the build
Weblate can publish translations to a CDN for your JavaScript to load at runtime. With Dialecto, translations ship in your build, and your site never calls us. 13
Price
Price for 10,000 stringsWeblate€47 a monthDialecto€XX a month
Hosted Weblate counts each string once per language, the source included, and charges €47 a month for 10,000, or €470 a year; public libre projects are free. Dialecto charges €XX a month for the same 10,000. 14
Example
Changing the English wording
Your product says “cart” now, but checkout still says “Your basket is empty”, and in gettext that English text is also the key every translation hangs on.
Change “Your basket is empty” to “Your cart is empty” and ship it.
With Weblate
Find every
gettext("Your basket is empty")in your code and change it by hand; Weblate leaves code to you. 8Extract and merge, which marks the translation in every language as fuzzy. 13
Clear “Needs editing” on the translation in each language. 8
Review the commit Weblate pushes back. 3
Effort
8 edits by hand: 5 places in your code, then clearing “Needs editing” in each of 3 languages.
With Dialecto
Change the text in the editor; every catalog and every call follows, and each translation stays.
Review the pull request Dialecto opens; the checks have already run.
Effort
One edit: Dialecto changes the text in every catalog and the 5 places in your code, in one pull request.
Done by hand, changing a word in gettext means editing every call and approving every language again, so teams keep the old wording. Dialecto makes it one edit, so your words can change as often as your product does.
Moving from Weblate
- In Weblate, commit and push any pending changes, then lock the component. 3
- Remove Weblate's GitHub App or deploy key and its webhook, so only one tool writes your translation files. 9
- Connect Dialecto and confirm the paths of your translation files.
- Done. Your translations were in your repository all along, and Dialecto opens the next pull request.
Leaving Dialecto
Your translations already live in your repository, exactly as you approved them, so there's nothing to export. Disconnect Dialecto and keep working.
Change your wording in one edit, on your own repository.
Create your account, connect your repository, and your first change arrives as a pull request your team reviews.
Sources, checked 6 October 2026
- 1Weblate: version control integrationdocs.weblate.org/
en/ read 6 October 2026latest/ vcs.html - 2Weblate's FAQ (shallow clones, a translations-only repository)docs.weblate.org/
en/ read 6 October 2026latest/ faq.html - 3Weblate: continuous localizationdocs.weblate.org/
en/ read 6 October 2026latest/ admin/ continuous.html - 4Hosted Weblate: data residencydocs.weblate.org/
en/ read 6 October 2026latest/ security/ data-residency.html - 5Weblate 2026.10's licence (pyproject.toml)github.com/
WeblateOrg/ read 6 October 2026weblate/ blob/ weblate-2026.10/ pyproject.toml - 6Weblate: machine translation and AIdocs.weblate.org/
en/ read 6 October 2026latest/ admin/ machine.html - 7Weblate: enforced checksdocs.weblate.org/
en/ read 6 October 2026latest/ admin/ checks.html - 8Weblate: translating (editing keys, screenshots)docs.weblate.org/
en/ read 6 October 2026latest/ user/ translating.html - 9Weblate: code hosting (pull requests through a fork, the GitHub App)docs.weblate.org/
en/ read 6 October 2026latest/ admin/ code-hosting.html - 10Weblate: the gettext formatdocs.weblate.org/
en/ read 6 October 2026latest/ formats/ gettext.html - 11translate-toolkit 3.20.0's PO writer, which Weblate 2026.10 usesgithub.com/
translate/ read 6 October 2026translate/ blob/ 3.20.0/ translate/ storage/ pypo.py - 12Weblate: supported file formatsdocs.weblate.org/
en/ read 6 October 2026latest/ formats.html - 13Weblate: add-ons (msgmerge, the JavaScript CDN)docs.weblate.org/
en/ read 6 October 2026latest/ admin/ addons.html - 14Hosted Weblate pricingweblate.org/
en/ read 6 October 2026hosting/