CloudConvert vs Keyvalue

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

Uptime · 30d
Uptime · 90d100%86.3%
Uptime · 30d100%80.0%
P50 · ms433855
P95 · ms10192051
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CloudConvert vs Keyvalue: common questions

Which is more reliable, CloudConvert or Keyvalue?

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

CloudConvert has the lower median latency in our checks — CloudConvert responds in 433 ms versus Keyvalue at 855 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 CloudConvert and Keyvalue need an API key?

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

Can I call CloudConvert and Keyvalue from the browser?

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

Are CloudConvert and Keyvalue free for commercial use?

CloudConvert has unclear commercial terms, and Keyvalue 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.