shipapis
StarSubmit an APISubmit API

IFTTT vs LibreTranslate

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

APIIFTTTNEW—LibreTranslateNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (software is AGPL-3.0)
Free tierFree — limits not publishedFree — /languages is keyless; hosted /translate may require a key or donation
Rate limitUnpublishedUnpublished (per hosted instance)
In directory since2026-07-052026-07-05
operationalpartialdownno data

IFTTT vs LibreTranslate: common questions

Which is more reliable, IFTTT or LibreTranslate?

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

Do IFTTT and LibreTranslate need an API key?

Neither needs a paid key — IFTTT 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 IFTTT and LibreTranslate from the browser?

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

Are IFTTT and LibreTranslate free for commercial use?

IFTTT 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.