Cobalt Alternative: A Hosted Media API You Can Build On
If you're looking for a cobalt alternative, you've probably already found cobalt - the open-source downloader with ~46k GitHub stars - and hit the same wall a lot of developers do: the public hosted API isn't meant for your project.
cobalt is genuinely great. If you want to save a video for yourself in the browser, or you're happy running and maintaining your own instance, cobalt is the honest answer and you may not need anything else. This page is for the other case: you want a hosted API you can call from your app or agent without standing up and babysitting a server.
TL;DR
- Use cobalt if you want a free, open-source downloader you self-host, or in-browser downloads for yourself. It's AGPL-3.0, so check that the license fits how you plan to ship.
- Use Importly when you want a hosted API that works from servers and agent sandboxes whose cloud IPs get blocked, delivers the file to your own S3/R2 bucket with a webhook, and can return a transcript in the same job. One API key covers the REST API and the hosted MCP server.
Why cobalt's hosted API isn't a drop-in for your app
cobalt's own API docs are clear about this. From the official api.md (imputnet/cobalt, last updated 2026-03-30):
hosted api instances (such as
api.cobalt.tools) use bot protection and are not intended to be used in other projects without explicit permission. if you want to use the cobalt api, you should host your own instance or ask an instance owner for access.
So the supported path for building on cobalt is running your own instance. That's completely reasonable for an open-source project - but it hands you the operational work, not just the code.
What self-hosting actually puts on your plate
Running your own cobalt instance is the real comparison, and it's more than docker run:
- Blocked cloud IPs. Your instance calls out from AWS, Google Cloud, Fly or a VPS address range, and large platforms treat those as bots. You end up managing that yourself.
- Keeping up with breakage. When a site changes how it serves media, downloads break until the extractor is updated. You own the "it worked yesterday" pages at 2am.
- The infra itself. A server (or container) to run, scale, monitor and patch, plus storage and egress for the files.
- License fit. cobalt is AGPL-3.0. For some commercial setups that's fine; for others the network-copyleft terms matter. Worth reading before you build a product on it.
None of this makes cobalt a bad choice - it's the price of self-hosting anything. The question is whether you want to own it.
What Importly offers
Importly downloads, transcribes and inspects video and audio from public URLs through one hosted API. You send a URL, you get the file - in hosted storage or copied straight into your own bucket - so you don't run the download stack or fight blocked IPs yourself.
| Need | Importly | Self-hosted cobalt |
|---|---|---|
| Hosted API you can build on | Yes, POST /import | You run the instance |
| Works from blocked cloud IPs | Yes, handled for you | Your server's problem |
| File to your own S3/R2/B2 bucket | Yes, store: true | You wire up storage |
| Webhook when the job finishes | Yes | You build it |
| Transcript in the same job | Yes, includeTranscript: true | No, download only |
| Metadata (title, duration, etc.) | Yes | Partial, per extractor |
| Stays working when sites change | We ship the fix | You update and redeploy |
| Free / open source | No, usage-based | Yes, AGPL-3.0 |
| Free start | $3.00 credit, no card | Free to self-host |
Pricing, honestly
Importly is usage-based: $0.01 per MB downloaded (rounded up, $0.03 minimum per import), plus $0.01 per transcript when captions exist or $0.02 per media minute for built-in speech-to-text. A 3-minute 720p video (~40 MB) is about $0.40; audio only is much less. New accounts get $3.00 in free credit, no card. See billing.
Self-hosting cobalt has no per-download fee - you pay for the server, storage, egress and your own time instead. If your volume is high and you enjoy running the infra, that math can favour self-hosting. If you'd rather make one API call and move on, Importly is the trade.
When Importly is the better alternative
- You want to call an API, not run and maintain a downloader instance.
- Your code runs on a server, serverless function or agent sandbox and cloud IPs get blocked. See serverless video downloads.
- You want the result pushed to your own bucket (Amazon S3, Cloudflare R2, Backblaze B2) with a webhook when it lands. See S3 storage and webhooks.
- You also need a transcript or metadata, not just the raw file.
- You want a coding agent to use the MCP server first, then build the same calls into your app with the same key.
When cobalt is still the better choice
- You want free, open-source software you control end to end.
- You're downloading for yourself in the browser, not inside an app.
- You're happy to run an instance and keep it updated, and AGPL-3.0 fits your use.
A low-risk way to test
- Keep cobalt (or your current downloader) where it already works.
- Point a representative set of URLs at Importly's
/importon the free $3 credit. - Compare success rate from your real server environment, delivery into your bucket, and how much glue code each path needs.
- Move only the jobs where the hosted API and delivery actually save you time.
bash1curl https://api.importly.io/import \2 -H "Authorization: Bearer $IMPORTLY_API_KEY" \3 -H "Content-Type: application/json" \4 -d '{5 "url": "https://www.youtube.com/watch?v=jNQXAC9IVRw",6 "store": true,7 "webhookUrl": "https://your.app/webhooks/import"8 }'
FAQ
Is Importly open source like cobalt?
No. cobalt is AGPL-3.0 and free to self-host; Importly is a hosted, usage-based API. They solve the same first step - getting media from a URL - but Importly is for teams who'd rather not run the downloader themselves.
Can Importly download the same sites cobalt does?
Importly handles YouTube, TikTok, podcasts and hundreds of other public media sites. Pass the page URL exactly as you'd paste it in a browser. If a URL you need isn't supported, it'll tell you rather than fail silently.
Does Importly have an MCP server?
Yes. Connect https://mcp.importly.io/mcp in Claude, ChatGPT, Cursor or Claude Code and it can import, transcribe and inspect media with the same API key you'd use from your app.
Should I just self-host cobalt instead?
If you want free and open source and you're comfortable owning the server, blocked IPs and updates, yes - self-host cobalt. Importly earns its keep when you'd rather make one API call and not maintain any of that.
Related: Video downloader API, YouTube downloader API, yt-dlp API vs self-hosting, Apify alternative, Importly docs.