Choose the motion from the source-image context
Pixelcut's motion parameter supports subtle and spin. Subtle is the documented default and produces gentle movement returning to the starting pose. Spin describes a full 360-degree revolution ending at the starting view.
The important distinction is inside the spin definition. For people and isolated products on a plain background, the schema says the subject turns in place while the camera remains fixed. For an object photographed in a real setting, it says the object stays still and the camera orbits around it.
The documentation also contains a broader statement that the camera stays fixed with no pans, zooms, tilts, or reframing. That statement conflicts with the real-setting orbit description. Do not resolve the conflict by inventing a precedence rule. If a locked camera is mandatory for a real-setting spin, clarify the intended behavior before committing to the request.
Prompt text cannot substitute for this decision. Pixelcut says directions requesting camera movement, cuts, new objects, or scene changes are ignored. Use the documented motion setting rather than attempting to force a different camera path through the prompt.
Specify duration, resolution, audio and source independently
Pixelcut accepts whole-second durations from 5 through 15, with 5 seconds as the default. Its documented output choices are 480p, 768p and 1080p, priced at 8, 16 and 32 credits per second respectively. Calculate planned credits as duration multiplied by the selected rate; subtle versus spin does not change that price.
The include_audio default is true. Setting it to false removes the audio stream, without changing the documented credit rate. This is an output contract, not a motion-quality setting.
Provide exactly one image source: a supported image field or image_url. The overview says requests with multiple sources are rejected, although the multipart schema separately says the image field wins when both are supplied. Because those statements conflict, use one source rather than depending on undocumented practical precedence.
The documented source limits are JPEG or PNG, at most 25 MB, from 64 × 64 through 6000 × 6000 pixels. These are input restrictions; they do not establish the generated MP4's fidelity to unseen product geometry.
{
"image_url": "https://assets.example.invalid/isolated-product.png",
"motion": "spin",
"duration": 6,
"resolution": "768p",
"include_audio": false
}Treat submission as a job, not a finished video
The illustrative request object uses an intentionally invalid image address and contains no credentials. The endpoint returns an asynchronous job rather than an immediate completed MP4. A successful submission can return HTTP 202, pending status, a job_id, and a Location header for status polling.
Keep the submitted source, motion choice, duration, resolution, audio selection, estimated credits, and returned job information together. Do not invent an automatic polling interval, retry policy, or result-retention period from this page. The separate looping-video job-status guide addresses subsequent pending, running, completed and failed states.
A complete 360-degree generated clip is still not proof of the physical product's rear or side construction. If those views affect a merchandise claim, retain genuine references for review.
Illustrative decision: an isolated bottle versus a bottle in a café
A seller wants a six-second repeating clip of a bottled product. One available source isolates the bottle on a plain background. Another shows the same product on a café table. The seller also has genuine photographs of the bottle's side and rear for later comparison, but sends only one image to the API.
For a product-turn concept, the isolated source matches Pixelcut's documented in-place spin description. The café image instead falls under the real-setting description, which specifies a stationary object and orbiting camera. Because the overview contradicts that camera behavior, the café version cannot be promised as a locked-camera spin.
The seller plans 6 seconds at 768p: 6 × 16 = 96 credits. Setting include_audio to false does not change that estimate. The next action is to choose the source and resolve any mandatory camera requirement before an authorized submission, then retain the returned job reference for retrieval.
Where CartVisual fits
CartVisual offers a separate approved-first-frame product-video workflow. It does not implement Pixelcut motion modes, its asynchronous API, or automatic publishing.
Source and evidence scope
Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.
Official source snapshot checked .
The supplied Pixelcut specification documents motion, input, pricing, audio, and asynchronous submission. Its general fixed-camera statement conflicts with the real-setting orbit description; its one-source rule conflicts with a multipart precedence note. The example is a plan, not an observed result or paid request.