Video Background Remover
Isolate the foreground of an existing clip and choose transparency or a solid background. Transparent WebM VP9 with original audio is the default request.
View model details →Model comparisons
Video Background Remover vs Video Eraser
Video Background Remover or Video Eraser, tier by tier: matched prices, request fields, limits and the content policy measured on each.
Video Eraser
Erase a fixed region throughout a video using a white-on-black image mask. An optional instruction describes the local removal; the same mask applies to the whole clip.
View model details →Compare
The short answer
Start with the input you have, the result you want and your budget. These are the differences that affect that choice.
- These tools produce different results. Choose the operation you need first; a lower price does not make one a substitute for the other.
These tools produce different results. Choose the operation you need first; a lower price does not make one a substitute for the other.
Current price
Price at the same setting
A start price answers a different question than the one you have. These are the tiers both models publish, matched setting for setting, in US dollars per billed unit with no conversion step in between.
These two bill on different tiers, so there is no row to line up. Each one's own published tiers are listed here instead.
Video Background Remover: $0.06 / output seconds
Video Eraser: $0.024 / output seconds
About this comparison
Controls and limits
Every row here is read from the JSON Schema the endpoint validates against, so it matches what the API will really accept rather than a feature list written by hand.
Swipe horizontally to compare all fields.
| Controls and limits | Video Background Remover | Video Eraser |
|---|---|---|
| Supported tasks | video-edit | video-edit |
| Execution | Submit, then poll or take the callback | Submit, then poll or take the callback |
| Request timeout | 120 minutes | 120 minutes |
| Availability | Live | Live |
Can I swap the model ID without changing the request body?
Request body, field by field
The task lifecycle is shared; the body is not. Each endpoint publishes its own JSON Schema and the API validates against that, so this is the list to reconcile before a switch.
- 1 fields appear in both request bodies under the same names. video_url
- Only Video Background Remover accepts: background, keep_original_audio, output_format.
- Only Video Eraser accepts: mask_url, prompt.
- Video Background Remover requires video_url.
- Video Eraser requires mask_url, video_url.
- Both reject unknown fields outright, so a parameter left over from the other model comes back as a validation error instead of being quietly ignored.
Compare
Moving from one to the other
The model identifiers are spicyapi/background-remover-video-v1/video-edit and spicyapi/video-eraser-v1/video-edit, and both go in the same field of the same request.
Both run the same way: submit the task, then poll it or take the callback. Queueing and retry logic carry over unchanged.
Both use the same submit-and-track flow, but their required inputs may differ. Check each model page before switching.
One key, one balance, one set of spend caps. Both bill to the same account in US dollars, and the per-key daily, monthly and lifetime limits apply to whichever one you call.
Questions developers ask
Which is cheaper, Video Background Remover or Video Eraser?
Which is cheaper, Video Background Remover or Video Eraser?
These tools produce different results. Choose the operation you need first; a lower price does not make one a substitute for the other. Prices may change; check the estimate shown for your actual settings before submitting.
How long can a single request run?
Video Background Remover allows 120 minutes per task and Video Eraser allows 120. Those are ceilings rather than typical times — most requests finish far sooner — but they are what your own client timeout has to survive.
Prices and capabilities shown here come from the current public model catalogue. Check each model page for its latest inputs and examples.