CartVisualCreate account

How should I retain Pixelcut result URLs before they expire?

Treat Pixelcut’s result_url as temporary delivery, not permanent asset storage. Download the completed file immediately, save it in storage you control, and deliver that retained copy to customers or downstream systems. Keep the original input and request parameters when reprocessing may be necessary. Record the downloaded artifact separately from the temporary URL.

Published · By CartVisual editorial team

Make the URL a delivery step

Pixelcut documents that many endpoints return a result_url whose file is retained for at most 24 hours and then permanently deleted. The URL should therefore be handled as a short-lived handoff between generation and your asset workflow, not as the canonical image address.

The useful seller decision is timing: does the result need to be retained, reviewed, transformed, or delivered later? If any answer is yes, download it during the completion workflow. Do not place the result_url into a queue whose first processing step may occur after the link has expired.

  • Download the completed result immediately.
  • Store the file in storage controlled by your team.
  • Use your own stable delivery or CDN URL for later consumers.
  • Keep the original input and request parameters if reprocessing is possible.

Separate four kinds of evidence

A reliable record distinguishes the generation request from the file that was actually retained. This prevents a successful generation response from being mistaken for a permanently available asset.

Use a small lifecycle record with four values: request details, temporary delivery URL, retained file, and publication status. The URL is evidence of where the provider offered the result; the retained file is evidence that your system took custody; publication is a later business decision. These states should not be collapsed into one “ready” flag.

This is an original planning aid, not a Pixelcut-defined schema. The important control is that a result is not marked deliverable merely because a URL was returned.

  • Request record: input reference, parameters, timestamp, and job identifier if available.
  • Delivery record: result_url and download status.
  • Asset record: retained file location, file type, and integrity check.
  • Publishing record: destination, approval state, and public URL.

Plan for reprocessing without the old link

If a retained file needs a new crop, format, or campaign variant, the expired result_url is not a recovery plan. Preserve the original input and the request parameters so the job can be evaluated or submitted again under the current workflow.

Keep the provider result and your own derivative visibly separate. A derivative created after download should reference the retained source asset, not depend on the temporary provider URL. This makes a later replacement auditable and avoids confusing a new creative with the original generation.

Before handing an asset to a storefront, catalog, or campaign system, confirm that the file exists in your storage and that the receiving system uses the retained location. The final outcome should be a controlled asset reference, not an unverified temporary link.

Worked example: a retained product image

The following is a hypothetical workflow for a seller generating one product image for a campaign. The seller wants the image reviewed tomorrow, so the result cannot remain dependent on Pixelcut’s temporary URL.

The seller downloads the result as soon as the job completes, stores it under an internal asset ID, and records the original request details. A reviewer approves the retained file, after which the campaign system receives the seller’s controlled delivery URL. The temporary result_url remains in the audit record but is not used for customer delivery.

StateRecorded valueDecision
RequestInput reference plus generation parametersKeep for possible reprocessing
Provider deliveryPixelcut result_urlDownload immediately; do not publish it
Retained assetInternal storage key and downloaded fileUse as the review source
Campaign deliverySeller-controlled public or CDN URLPublish only after approval

Where CartVisual fits

After retaining the approved file, sellers can use CartVisual’s product-image workflow for additional product creative. CartVisual does not implement Pixelcut result-URL storage or automatic publishing.

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.

Pixelcut: Handling Results

Official source snapshot checked .

The vendor-specific facts are limited to Pixelcut’s official documentation on result_url lifetime, immediate download, storage, CDN delivery, and reprocessing records. The lifecycle record and approval distinctions are original workflow guidance. This article does not claim a CartVisual API integration or automatic publishing.

Related decisions

Browse ecommerce creative workflows