Softwr

Translation · head to head

wxrks vs OmegaT

wxrks logo

wxrks

Translation

Translation platform formerly called Bureau Works, priced by processed words per year with unlimited seats and a real free tier

From
Free
Rated
-
OmegaT logo

OmegaT

Translation

Free, open source desktop CAT tool under the GPLv3, maintained by a volunteer community rather than a company

From
Free
Rated
-

The short version

  • Each has a real cost: wxrks connectors are marked as billed separately on the pricing page with no rate published anywhere, so the integration that justifies buying the platform carries a cost you cannot discover until you ask.; OmegaT there is no commercial support contract available, so a business relying on it for critical work has only community forums to fall back on when something breaks.
  • They diverge on capability: wxrks covers Published price ladder, OmegaT covers Translation memory.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which wxrks and OmegaT actually diverge.

Attributes where wxrks and OmegaT differ
AttributewxrksOmegaT
Pricing modelPer year by processed word volumeOpen source, no licence fee
PlatformsWeb, APIWindows, macOS, Linux

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Translation).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in wxrks

  • Published price ladder
  • Unlimited user seats
  • Four parallel meters
  • Published overage rates
  • Marketplace
  • Repository and design connectors

Only in OmegaT

  • Translation memory
  • Glossary support
  • Wide format support
  • Project-based workflow
  • Machine translation plugin support
  • Cross-platform desktop app

What people use each for

The jobs each tool is most often brought in to do.

wxrks

  • A team that needs to model localisation cost from published numbers rather than sit through a sales cycle to get a figurenot OmegaT
  • Content operations with many occasional reviewers, since seats are unlimited and only analytics users are chargednot OmegaT
  • Developer-led localisation pulling strings from GitHub, GitLab or Bitbucket rather than a content management systemnot OmegaT
  • Small teams and side projects that can live inside 60,000 words a year on the permanent free tiernot OmegaT

OmegaT

  • A freelance translator who wants translation memory and fuzzy matching without paying for a Trados or memoQ licencenot wxrks
  • A small language service provider standardising on a free tool for individual translators before investing in a shared TMSnot wxrks
  • A translator working with files from clients using commercial CAT tools, leveraging Okapi’s format support for compatibilitynot wxrks
  • A developer or power user who wants to inspect, modify or extend the tool since it is open source under the GPLv3not wxrks

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

wxrks

  • Connectors are marked as billed separately on the pricing page with no rate published anywhere, so the integration that justifies buying the platform carries a cost you cannot discover until you ask.
  • Four separate meters run in parallel and any one of them can be exhausted while the others have headroom, so a workload heavy on API calls or AI tokens can force a plan upgrade long before the word allowance is touched.
  • Word allowances are annual rather than monthly, so a single large launch early in the term can consume most of the year and leave the remaining months on overage rates.
  • The marketplace is promoted as a way to reach agencies and translators, but whether the vendor takes a commission and how linguists are paid is not disclosed anywhere on the public site.
  • The company rebranded from Bureau Works in March 2026, so existing documentation, third-party guides, integration listings and internal references still carry the old name, and the vendor is small with no disclosed funding behind it.

OmegaT

  • There is no commercial support contract available, so a business relying on it for critical work has only community forums to fall back on when something breaks.
  • It lacks the cloud-hosted, real-time collaborative project management features of commercial TMS platforms like memoQ or Smartling.
  • The interface is a Java desktop application with a dated look and feel compared with modern web-based CAT tools, which affects onboarding speed for new users.
  • Release cadence and feature development depend on volunteer contributor availability rather than a company roadmap, so some requested features take a long time to arrive, if ever.
  • Machine translation integration requires configuring third-party API keys (Google, DeepL) separately, adding setup steps a commercial all-in-one tool would handle natively.

Pricing, plan by plan

wxrks

Free
  • FreeFree
    • 60,000 processed words per year
    • 2,300 API calls
    • 300,000 stateless AI tokens
  • Starter$38/month
    • Billed yearly
    • 1 million words per year
    • 38,000 API calls, 5 million AI tokens, 330,000 MT words
  • Boutique$180/month
    • Billed yearly
    • 3.2 million words per year
    • 122,000 API calls, 16 million AI tokens, 1 million MT words
  • Clockwork$470/month
    • Billed yearly
    • 9.6 million words per year
    • Overage at 0.0005 USD per word

OmegaT

Free
  • OmegaTFree
    • Full CAT tool functionality, GPLv3 licensed
    • No paid tier, no vendor support contract available

Which should you pick?

Choose wxrks if

  • You need published price ladder.
  • You want to start without paying.
  • You work on Web, API.
  • You also want unlimited user seats.

Choose OmegaT if

  • You need translation memory.
  • You want to start without paying.
  • You work on Windows, macOS, Linux.
  • You also want glossary support.

Questions people ask

Is wxrks or OmegaT better?
Neither clearly leads. wxrks starts at Free and OmegaT at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, wxrks or OmegaT?
wxrks starts at Free and OmegaT at Free.
Does wxrks or OmegaT run on more platforms?
wxrks runs on Web, API. OmegaT runs on Windows, macOS, Linux.
Can I use wxrks for free?
Both have a free tier, so you can try either at no cost before committing.
What is wxrks best used for?
wxrks is most often used for a team that needs to model localisation cost from published numbers rather than sit through a sales cycle to get a figure, content operations with many occasional reviewers, since seats are unlimited and only analytics users are charged, developer-led localisation pulling strings from github, gitlab or bitbucket rather than a content management system, small teams and side projects that can live inside 60,000 words a year on the permanent free tier. Of those, a team that needs to model localisation cost from published numbers rather than sit through a sales cycle to get a figure and content operations with many occasional reviewers, since seats are unlimited and only analytics users are charged are not what OmegaT is typically brought in for.
What can wxrks do that OmegaT cannot?
wxrks covers Published price ladder, Unlimited user seats, Four parallel meters, Published overage rates. OmegaT covers Translation memory, Glossary support, Wide format support, Project-based workflow.

Answered from the vendors’ own pages

wxrks: Is this still Bureau Works?

Yes. The company rebranded to wxrks on 23 March 2026 and bureauworks.com redirects to wxrks.com. The legal entity is Bureau Translations Inc.

OmegaT: Is OmegaT really free, with no paid version?

Yes, it is fully free and open source under the GPLv3, with no commercial edition or vendor support contract sold alongside it.

wxrks: Is the free plan permanent?

Yes. It allows 60,000 processed words a year along with API call, AI token and machine translation allowances, and unlimited user seats. A fourteen day trial of paid features is offered separately.

OmegaT: Who maintains OmegaT?

A volunteer open source community, not a company; this differs from MateCat, which is developed and hosted by the company Translated.

wxrks: What happens when I exceed the word allowance?

You pay a published per-word overage rate, from 0.0009 USD on Starter falling to 0.0003 USD on the largest plans, rather than being cut off.

OmegaT: Can it open files from Trados or Wordfast?

Yes, via the bundled Okapi Filters plugin, which supports SDLXLIFF, TTX, TXML and many other commercial CAT tool formats.

wxrks: Do connectors cost extra?

The pricing page states connectors are billed separately but publishes no rate. Get the figure in writing before signing, because it is the one unbounded item in an otherwise transparent price list.

Share

Related pages

Other head to heads