CartVisualCreate account

How should I configure Claid Image to Video input, cost, and output handling before generating a product clip?

Make four decisions before submitting: validate the single source image, reserve credits for each requested duration, choose a submission schedule, and decide whether Claid should return a temporary URL or write to connected storage. A connected-storage destination controls where Claid writes the result; it does not, by itself, document how long that storage provider will retain the file.

Published · By CartVisual editorial team

1. Validate one source image

Start with the exact file or storage object that will be submitted. Claid accepts one input image per request, and only one video can be generated per request. Each image side must be at least 300px, and the documented formats are JPG, PNG, WEBP, HEIC, and HEIF.

The input can be an image URL or a connected-storage reference. For a URL, check both the documented length boundary and whether Claid can access the image. Record the source revision before generating so each candidate can be traced to the same reviewed product image.

  • One reviewed image per request.
  • Both image dimensions are at least 300px.
  • The actual file format is supported.
  • The submitted URL or storage reference identifies the reviewed image.

2. Reserve credits and schedule requests

Choose duration and candidate count together. The planning formula is: total credits = (5-second requests × 35) + (10-second requests × 70). This gives you a reservation amount, not a promise that every request will produce a usable clip.

Keep rate limits separate from the credit calculation. A conservative schedule for a small batch is one request at time 0 seconds, another at 60 seconds, and another at 120 seconds. That spacing stays below both listed ceilings, although it may be slower than necessary. If your workflow uses a tighter schedule, record the planned timestamps and check both the per-second and per-minute limits.

  • 5-second request: 35 credits.
  • 10-second request: 70 credits.
  • Plan no more than one generation in any one-second interval.
  • Plan no more than 15 generations in any one-minute interval.
  • Count each candidate as a separate request.

3. Choose delivery before approval

Output is optional. Without an output setting, Claid places the result in a temporary bucket, provides a public video URL, and documents a 24-hour lifespan. Use this branch only when your workflow can retrieve the result and apply its own retention policy within that window; the documentation does not promise successful generation or permanent access.

For a production handoff, configure connected Cloud Storage and provide a destination path or folder. That selects Claid's delivery location, but retention, permissions, lifecycle rules, and later availability remain matters for the connected storage configuration. Treat a returned file as a candidate until it has been inspected against the product source.

CartVisual can be used for product-video preparation or review through its available workflow. It does not submit Claid requests or manage Claid credit, rate-limit, or storage settings, so keep those controls in the Claid workflow.

  • Short review: omit output and plan retrieval before the 24-hour lifespan ends.
  • Storage handoff: specify a connected-storage path or folder.
  • After a response, record the actual result location and inspect the video before approval.

Worked example: schedule a three-clip plan

Hypothetical seller case. A merchant has one reviewed 1200 × 1200 PNG and wants two 5-second candidates plus one 10-second candidate. The image clears the documented minimum dimensions. The merchant wants to compare the candidates tomorrow, so the plan uses connected storage rather than relying on a temporary public URL; this choice does not establish how long the storage provider will retain the files.

The reservation is 2 × 35 + 1 × 70 = 140 credits. A conservative submission schedule is request A at 0:00, request B at 1:00, and request C at 2:00. If generation succeeds, the merchant inspects each returned video and retains the approved file under the storage provider's policy. This is a planning example, not an executed Claid job.

DecisionHypothetical choiceNext evidence
InputOne 1200 × 1200 PNGConfirm the submitted object is the reviewed source
BudgetTwo 5-second and one 10-second requestReserve 140 credits
ScheduleSubmit at 0:00, 1:00, and 2:00Record actual submission times
OutputConnected-storage folderConfirm the configured destination path
ReviewReturned videos, if generation succeedsInspect each actual response and retain the approved file under the storage policy

Where CartVisual fits

Use CartVisual's product-video workflow for preparation or review, while keeping Claid-specific submission, credit, rate-limit, and connected-storage decisions in the vendor workflow.

See the current CartVisual workflow and its limitations

Source and evidence scope

Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.

Claid: Image to Video I/O

Official source snapshot checked .

The supplied Claid Image to Video I/O documentation establishes input count, input formats, minimum dimensions, URL length and accessibility, listed credits, rate limits, temporary output behavior, and connected-storage options. It does not establish motion quality, product fidelity, generation success, storage retention duration, approval guarantees, or CartVisual integration behavior.

Related decisions

Browse ecommerce creative workflows