
A Cloudinary archive-download URL does not necessarily create a stored archive asset. The documented dynamic download methods produce a signed URL that expires after one hour; the archive they generate is not cached or stored in the product environment. create_zip and create_archive instead create and upload an archive asset. Choose the mode before promising a lasting campaign download.
Key Takeaways
- A dynamic archive link and a stored ZIP are different outputs.
- A successful download does not prove that an archive now exists in the media library.
- Stored media still needs an access policy, retention plan and receiving-file check.
Find out what the integration generated
Read the method used to prepare the client handoff, rather than guessing from a URL ending or the ZIP filename. The official archive guide distinguishes stored archive creation from on-demand signed downloads.
Use this distinction in the production note:
| Preparation mode | Documented output | Evidence to retain |
|---|---|---|
create_zip or create_archive | Archive uploaded to the product environment | The actual created asset and its approved membership |
| Dynamic archive download URL | Time-limited request that creates the download | The intended selection and delivery window; no stored-archive assumption |
A downloaded copy on a recipient's computer is also separate from a server-side stored asset. Neither a browser bookmark nor a successful download establishes the other location's retention policy.
Choose temporary distribution or a stored deliverable deliberately
For a short-lived review, a dynamic download can be the intended choice. Send it only through an appropriate authorized route and explain the delivery window. Do not paste signed addresses into public production notes.
For an ongoing campaign handoff, determine whether the requirement is a stored archive asset, an independently retained downloaded file, or both. If the integration only creates a dynamic URL, do not relabel that URL as a permanent media-library ZIP. Use the supported stored-archive method when that is the agreed requirement, then verify its actual result.
The source also documents blocked archive delivery on Free accounts. A delivery failure can therefore need a separate account-policy investigation. This guide does not recommend changing a security setting, promise that a stored archive is automatically public, or claim that choosing another mode bypasses the policy.
Check membership separately from link lifetime
Before creating the deliverable, identify the approved assets and intended revisions. The archive API can select by tags, public identifiers or prefixes; that does not make a broad selection equivalent to the client's approved list.
Use the manual approved-version record to compare the expected selection with the actual contents. Keep working alternatives outside the agreed delivery scope. If the collection changes later, repeat the membership check rather than treating an older archive name as evidence of current contents.
Verify the receiving file and record the actual storage location
For a proposed campaign test, download the intended archive during its valid delivery window and open it in an appropriate local tool. Check required filenames, file counts, revisions and a representative image or video. Record an actual failure if the response cannot be opened; this guide does not report a successful archive test.
If offline access matters, use the real-file availability check on the receiving device. Keep archival responsibilities separate from link generation; Imagild's own asset storage guidance does not set Cloudinary's retention policy.
Accept the handoff when the selected mode meets the delivery window, the actual archive contains the approved files, and the agreed keeper knows where the real bytes are retained. Do not infer indefinite availability from a stored asset, or a stored asset from a one-time download.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- How to Archive Imagild Assets Before the 90-Day Storage Window Ends
- My Archive Shows Every Photo. Why Are Some Unavailable Offline?
Sources and scope
- Cloudinary: Generate archives: create_zip and create_archive upload generated archives to the product environment. Dynamic archive download URLs expire after one hour and their resulting archives are not cached or stored there.
Documentation-based comparison of two archive-generation modes. No archive was generated, no client data transferred, and no expiry or recovery test executed. Selection and receiving checks are proposed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.