shipapis
StarSubmit an APISubmit API

CloudConvert vs npm Registry

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

APICloudConvertHEALTHY96npm RegistryHEALTHY98
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms433243
P95 · ms10191246
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree (public registry)
Rate limitUnpublishedUnpublished (bulk scraping discouraged)
In directory since2026-07-052026-07-05
operationalpartialdownno data

CloudConvert vs npm Registry: common questions

Which is more reliable, CloudConvert or npm Registry?

Both are neck-and-neck — CloudConvert and npm Registry each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, CloudConvert or npm Registry?

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

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

Can I call CloudConvert and npm Registry from the browser?

Only npm Registry 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 npm Registry free for commercial use?

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