LibreTranslate vs UrlBae

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%1.0%
Uptime · 30d100%0.0%
P50 · ms6191158
P95 · ms14741158
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (software is AGPL-3.0)Unverified
Free tierFree — /languages is keyless; hosted /translate may require a key or donationFree tier — API key required
Rate limitUnpublished (per hosted instance)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LibreTranslate vs UrlBae: common questions

Which is more reliable, LibreTranslate or UrlBae?

On our scheduled checks, LibreTranslate leads on measured uptime — LibreTranslate at 100% versus UrlBae at 1.0% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, LibreTranslate or UrlBae?

LibreTranslate has the lower median latency in our checks — LibreTranslate responds in 619 ms versus UrlBae at 1158 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do LibreTranslate and UrlBae need an API key?

LibreTranslate needs no key, while UrlBae requires a free API key. If you want to start calling without signup, reach for LibreTranslate first.

Can I call LibreTranslate and UrlBae from the browser?

Only LibreTranslate is browser-friendly — it returns CORS headers over HTTPS. UrlBae needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are LibreTranslate and UrlBae free for commercial use?

LibreTranslate has unclear commercial terms, and UrlBae has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.