Recording applications
Offer a transparent version of a presenter’s clip alongside the original. Your application handles the recording and playback; the API handles the background removal task.
For applications and scripts
Video background removal API
Build transparent video into your application. Upload a recording, track the task and retrieve a WebM with the original audio.
Existing account credits. No separate API subscription.
Import a video · cURL
curl 'https://videobgremover.net/api/v1/uploads/import' \
-H "Authorization: Bearer $API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: import-example-001' \
-d '{"url":"https://example.com/video.mp4"}'Replace the example URL and API key. This request prepares your video; processing starts only after you submit a job with an approved credit cap.
Actual processed output
A recording in. A reusable layer out.
The transparent export separates the presenter from the room. Put it over your own scene, slide or product footage without including the original backdrop.
Five-second direct-upload example with a test audio track. Fine hair and moving edges can be softer; review your export before use.
Download exampleIntegration workflow
Keep the video task in your workflow.
Background removal is asynchronous. Keep your interface responsive while the task runs, then retrieve the result when it is ready. A saved task ID lets your application pick up where it left off.
Explore endpoints and request fields →- Import or upload a clip
Send a public HTTPS URL, or upload your own file with a signed PUT plan. Poll the upload until it is ready; server validation returns the estimated credit cost.
- Approve the cost and submit
Create a job with upload_id and max_credits. Use a stable Idempotency-Key for retries. Save the returned job_id so your application can resume checking it.
- Track progress and download
Poll the task at its suggested interval. Once it succeeds, request the download link and store the transparent WebM in your application. Polling adds no processing charge.
Where it fits
Bring recorded footage into your product.
Content production
Prepare a subject layer for a tutorial, product demo or presentation. Save the completed WebM with your project assets, then place it over the scene you are assembling.
Repeatable scripts
Connect a supported file source, persist task IDs and download completed outputs. Process clips in sequence and keep your own archive of the files you want to reuse.
Credits and access
Use the credits you already have.
The video background removal API shares your website balance. Processing uses one credit per second, rounded up, and each job requires max_credits. Inspect the upload estimate before submitting; checking progress and retrieving a download do not add processing credits.
Trial accounts can process up to 30 seconds. Paid access uses your account’s entitlement, capped at five minutes for API tasks. There is one unfinished task per account across the website, REST and MCP.
Compare plans and credit packs →Supported video contract
| Input files | MP4, MOV or WebM |
|---|---|
| Video codecs | H.264, HEVC or VP9 |
| Resolution | Up to 1080p, portrait supported |
| Frame rate | Up to 30 fps |
| Clip duration | Trial: 30 seconds; paid: up to 5 minutes, subject to entitlement |
| Transparent output | VP9 WebM, with source audio when present |
These are API/MCP limits. The website editor has its own upload and export choices.
Before you connect
API questions, answered.
Can I use a file from my own storage?
Yes. Import a public HTTPS URL, or create a signed upload plan and PUT your file directly. HTTPS imports accept up to 200 MiB and direct uploads up to 500 MiB. The import URL must be reachable without cookies or extra headers and must not redirect. Private storage works with the direct-upload path; your API key belongs on API requests, not on the signed storage PUT.
How should my application handle a timeout?
Keep the same Idempotency-Key and identical request body when retrying a submission. You receive the existing task rather than a second paid task. A different body needs a new key. Save job_id and poll GET /jobs/{id}; a browser or client disconnect does not cancel accepted processing. A task waiting for review should be checked rather than repeatedly resubmitted.
Can I cancel a task or process several videos at once?
You can cancel a queued task before processing starts. Once it is running, cancellation is unavailable. Each account has one unfinished task shared with the website and MCP, so wait for that task to finish before submitting the next video. You can prepare up to three pending uploads. This API does not offer parallel batch processing on one account.
How long can I retrieve my files?
A completed result stays available for seven days. The download endpoint returns a signed link valid for ten minutes; request another link while the result is retained. Unused uploads expire after 24 hours. Consumed input files are cleaned up 24 hours after their task finishes. Download the completed WebM into your own storage for a longer-lived archive.
Does this API replace the website editor?
It provides background removal and transparent WebM downloads. For interactive background colors, still-image backdrops or additional export choices, use the website editor. The account balance is shared, but API input and output are not a promise of automatic file transfer into another editing session.
Start with one short clip.
Create a key and connect your first video task.