Treat transparency as a two-field compatibility requirement
Pixelcut's Remove Video Background endpoint separates the replacement background from the delivered encoding. The background_color parameter accepts transparent or a three- or six-digit hexadecimal color. Its documented default is #000000. The output_format parameter independently defaults to mp4_h264.
Those defaults matter together. Omitting background_color does not request transparency, and selecting a video container merely because it can display the clip does not establish alpha support.
For a transparent result, Pixelcut identifies four compatible output values: webm_vp9, mov_h265, mov_proresks and gif. Choose among them according to the receiving editor's actual import contract. The documentation describes supported output combinations; it does not establish that every marketplace, advertising platform or editing application accepts them.
For a finished opaque result, choose an approved hex background instead. This changes the deliverable from a reusable foreground layer to a video with its replacement background already included.
Reject incompatible requests before submission
A useful preflight is to examine background_color and output_format as one pair. If the destination requires transparency but output_format remains mp4_h264, revise the configuration before submission. Do not assume Pixelcut will automatically change the format or preserve alpha through an unsupported combination.
The request also requires a publicly accessible video_url. The documented input boundaries are 100 MB maximum, 60 seconds maximum, supported MP4, MOV, WebM, MKV or GIF input, and a resolution range of 64 × 64 through 4096 × 4096 pixels.
The following JSON illustrates one transparent-output request. Its URL is deliberately invalid and it contains no authorization data.
{
"video_url": "https://assets.example.invalid/product-demo.mp4",
"background_color": "transparent",
"output_format": "webm_vp9"
}Hand off the job state separately from the video
This endpoint processes video asynchronously. The documented acceptance response uses HTTP 202 and includes a job_id and Location header for subsequent status inspection.
Store the source revision, requested background_color, requested output_format and returned job reference together. Acceptance does not mean that a transparent file has been delivered, that its edges are correct, or that the receiving application has successfully imported it.
The separate Pixelcut job-status guide handles the later pending, running, completed and failed states. The source-preflight guide addresses whether the footage is suitable for segmentation. Neither decision replaces the format-pair check before submission.
Illustrative decision: one demo, two incompatible delivery requests
A seller has a 12-second, 48 MB MP4 showing a countertop appliance. An editor needs to composite the appliance over several seasonal backgrounds and has confirmed that the editing application accepts transparent WebM VP9.
The proposed request sets background_color to transparent and output_format to webm_vp9. Leaving the output format at its mp4_h264 default would not satisfy the documented transparent-output combination.
A second campaign requires a finished black-background MP4 instead. For that separate deliverable, the seller chooses #000000 and mp4_h264. The first request is a reusable layer; the second is an opaque composition.
Next action: confirm the receiving application's codec and alpha requirements, select the matching two-field combination, and preserve the asynchronous job reference if a request is subsequently authorized.
Source and evidence scope
Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.
Pixelcut: Remove Video Background
Official source snapshot checked .
The supplied Pixelcut API reference establishes background and format values, defaults, input limits and asynchronous acceptance. The pairing method is editorial preflight guidance. It does not establish destination-editor compatibility, exact alpha quality, successful segmentation, job completion or CartVisual integration.