What can the Clipdrop API do?

Clipdrop, owned by Stability AI, exposes image-editing endpoints including background removal, object cleanup with a mask, super-resolution upscaling, and reimagine variations. Each is a separate REST endpoint that takes multipart form-data and returns an image.

How does authentication work?

Every request needs an x-api-key header containing your Clipdrop API key. You generate the key in the Clipdrop API dashboard; this tool never sees or stores it beyond sending it to Clipdrop's servers.

Why do cleanup and upscaling not run in the browser demo?

Cleanup needs a second same-size mask image and upscaling needs explicit target dimensions, so they require extra inputs. The guide shows the full cURL structure for those calls so you can build them in your own code.

Is my image uploaded anywhere besides Clipdrop?

No. The live test posts your file directly to clipdrop-api.co. Nothing routes through this page's servers, and the result is returned straight to your browser.

Clipdrop / Stability AI API Guide

Clipdrop / Stability AI API guide

Clipdrop — now part of Stability AI — packages a set of practical image-editing operations behind a simple REST API: background removal, object cleanup, super-resolution upscaling, and reimagine variations. Each is its own endpoint that accepts a multipart upload and an x-api-key header, then returns a finished image. This guide documents the request shape for each and lets you fire the single-file operations live with your own key.

How it works

Pick an operation and the tool shows the matching endpoint URL and the form fields it expects. For remove-background and reimagine — which take only an image_file — you can upload an image and run the call directly from your browser; the result image renders inline with a download link. For cleanup (which needs a mask_file) and upscaling (which needs target_width / target_height), the tool prints the exact cURL command so you can wire the extra inputs into your own backend. Your key travels only to clipdrop-api.co.

Notes and tips

Keep the key server-side in production. Browser calls are fine for testing, but a public site should proxy Clipdrop through your own backend so the key never reaches users.
Masks must match dimensions. For cleanup, the mask_file has to be the same width and height as the source; white marks the area to erase.
Upscaling caps. The upscaler targets a maximum output resolution — request target_width and target_height within the documented limit or the call returns an error.
Watch your credits. Each call consumes Stability credits; pair this with the Stability AI credit calculator to budget a batch before you run it.