The ImgBB API, end to end.

Uploading

One endpoint — https://api.imgbb.com/1/upload — taking POST or GET. The image parameter is refreshingly flexible: the same field accepts a binary file, a base64 string, or a remote URL, so you don't need to learn three call shapes.

What comes back

A JSON envelope with success, status, and a data object holding the image metadata, pre-generated thumb and medium variants, and a delete_url.

The part that catches people out: deletion

The delete_url in that response looks like an API affordance. It isn't. It's a web page — https://ibb.co/[ID]/[deletekey] — that a human opens in a browser and confirms. There is no documented DELETE endpoint.

For a one-off share that's fine. For anything programmatic it's a real constraint: your service can upload an image but cannot take it back down. If a user deletes their account, or you upload something by mistake, or a customer asks you to remove an image, the only path is to persist every delete_url somewhere and have a person visit each one. Worth knowing before it's load-bearing.

Expiry is set once, at upload

The expiration parameter takes 60 to 15,552,000 seconds — one minute to 180 days — and the image self-deletes at the end of it. It's a genuinely useful escape hatch given there's no delete API, and it's the right tool for ephemeral previews. The catch is that it's decided at upload time: nothing in the docs lets you extend, shorten or cancel it afterwards, so you have to know an image's lifetime before you've uploaded it.

A note on the key

The key travels in the query string. That's the documented design, and it works — but query strings are the part of a URL most likely to be written down by something you don't control: server access logs, proxy logs, browser history, a Referer header. If you use ImgBB from a backend, keep the key server-side and treat log redaction as your problem to solve rather than assuming it's handled.

When ImgBB is the right call

Genuinely: when you want an image on the internet with minimal ceremony. No account modelling, no project structure, no SDK — sign up, grab a key, POST a file. For a personal script, a hobby project, a forum image, or a quick prototype, the simplicity is a feature and the missing pieces never come up.

When you've outgrown it

The line is roughly where other people's images start passing through your code. At that point you tend to need things the upload-only design doesn't cover: deleting an image from code, keeping one customer's uploads separable from another's, and an auth model where the credential isn't in the URL.

Here's how the two APIs line up. We build PixelVault, so read the right-hand column with that in mind — the rows where ImgBB wins are in there too.

Where ImgBB is still ahead

Two rows above are worth calling out because they go the other way. ImgBB accepts 32 MB per image against PixelVault's 5 MB — if you're hosting high-resolution photography or large scans, that difference decides it, and no amount of API surface makes up for a file you can't upload. ImgBB also lets you set an expiry up to 180 days, where PixelVault's ephemeral uploads cap at 30. And base64 works on ImgBB's single upload endpoint, while on PixelVault it's the batch endpoint that takes base64 items.

Hosting an image without an account at all

The one row with no ImgBB equivalent: PixelVault takes an upload with no API key and no signup. That matters most for coding agents and scripts, where the account-creation step is the part that can't be automated — an agent can go from "I have a PNG" to "I have a URL" in one call, with nothing to provision first.

The honest catch: keyless uploads are kept about 30 days, not forever. They live under a shared anonymous prefix and are cleared by a storage lifecycle rule. It's the right tool for a CI screenshot, a scratch diagram, or an agent sharing a render mid-conversation — not for a README image that has to survive. For permanence you register (which the API does support programmatically), verify an email, and upload with a key.

What it costs

ImgBB's API is free and has no published paid tier — which also means no published rate limit or uptime commitment to hold it to. PixelVault's free tier is 200 MB of storage and 500 uploads a month with no credit card; paid plans are on the way but aren't purchasable yet, so today the free tier is the offer. Full detail on the pricing page, the equivalent calls in the API docs, and a broader feature comparison on the ImgBB alternative page.