Is a generated download link ready for a public campaign?

Identify what the address actually grants

A result can open in your signed-in browser and still be inaccessible elsewhere. Current Itemlume result routes require authentication and resolve files within the requesting user’s workspace. They are served as private material, rather than as a general public asset endpoint. Copying the address does not convert that account boundary into publication permission.

In an illustrative handbag launch, the designer pastes a result address into a spreadsheet and can open it. A colleague in another session sees a sign-in requirement or cannot retrieve the same file. That is not sufficient evidence of a failed generation. The intended retrieval context differs from the account context in which the preview worked.

Choose a delivery route for the real audience

Frame.io documents explicit external sharing with its own visibility and permission settings. That illustrates the distinction between review access and publication access; this is not a statement that Itemlume has the same share-link controls. Frame.io’s sharing guide. Select the service deliberately rather than treating every working preview as public hosting.

Move the file, not the account session

Obtain the approved image or video through the available signed-in download route. Check the saved file’s content, dimensions and format before uploading it elsewhere. Never solve a sharing problem by giving a colleague your password, session cookie or private API credential. The recipient needs the intended media, not your ability to operate the whole account.

For the handbag, download the current reviewed hero image and upload it to the correct product listing. Then inspect the listing preview. If your destination requires a media URL, use a host you intentionally control and configure for that purpose. Account-specific result paths should not become catalog-feed addresses merely because they resemble ordinary image URLs.

Keep publication permission separate from technical access

A file that is technically reachable is not necessarily approved for marketing. Product accuracy, reference rights, model-use permissions and the final message still require review. Conversely, a private generated result can be approved for publication without being publicly accessible at its original address. Access and approval answer different questions and should have different records.

Retain the clean approved file and label its publication derivative. A later storefront crop or caption may need a separate review even when the source image is accurate. Do not replace a published file silently with an unreviewed new generation under an unchanged external filename. Consider how the destination manages cached versions and confirm what visitors actually see.

Test the destination as its intended viewer

After upload, use the destination’s public or placement preview and confirm the actual image or video shown. A successful Itemlume preview does not test a store’s crop, an ad platform’s transcode or its surrounding interface. The review should establish both that the intended audience can reach the delivered media and that it is the approved version.

If an external link fails, record which service owns that link before reporting the issue. A private Itemlume result, a reviewer-controlled link and a storefront media address have different access rules. This guide does not promise permanent public result URLs, an automatic media feed or a new Itemlume sharing button. Use a deliberate publication route for each destination.