FakerAPI vs LibreTranslate

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

Uptime · 30d
Uptime · 90d1.0%100%
Uptime · 30d0.0%100%
P50 · ms860619
P95 · ms8601474
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (software is AGPL-3.0)
Free tierFree — no keyFree — /languages is keyless; hosted /translate may require a key or donation
Rate limit60 req/window · 59 remainingUnpublished (per hosted instance)
In directory since2026-07-052026-07-05
operationalpartialdownno data

FakerAPI vs LibreTranslate: common questions

Which is more reliable, FakerAPI or LibreTranslate?

On our scheduled checks, LibreTranslate leads on measured uptime — FakerAPI at 1.0% versus LibreTranslate at 100% 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, FakerAPI or LibreTranslate?

LibreTranslate has the lower median latency in our checks — FakerAPI responds in 860 ms versus LibreTranslate at 619 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 FakerAPI and LibreTranslate need an API key?

Neither needs a paid key — FakerAPI is callable with no signup, and LibreTranslate is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call FakerAPI and LibreTranslate from the browser?

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

Are FakerAPI and LibreTranslate free for commercial use?

FakerAPI has unclear commercial terms, and LibreTranslate 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.