Treat Imagild's Library as temporary production storage, not as your only permanent archive. The published asset policy provides a 90-day storage window for source and generated files. Download important material early, keep an independent backup and verify that the files open. A remembered task entry or a saved result URL is not a substitute for the actual media file.
Decide what belongs in the archive
Keep the authorized source, accepted result, approval notes and any final external edit that you need to reproduce or deliver the project. You do not have to retain every failed experiment indefinitely. Separate discarded candidates from accepted files so a future collaborator does not choose the wrong portrait or film clip.
The asset policy is different from account, payment and operational record retention. Do not assume all task or transaction records disappear at the same time as media. Conversely, a task record may remain while its linked file is no longer available. Review the current privacy and storage information for the scope that applies to your project.
Use a small, understandable archive
Hypothetical project: a creator makes an approved portrait and three film clips from an authorized reference. Their archive contains the source, accepted media, a text note listing the approved versions and a separate folder for the final edited teaser. This is a suggested organization, not an automated Imagild export feature.
Name files by project, purpose and version rather than only by the download date. A filename such as “couple-entrance-approved-v03” is more useful than several files all called “final.” Keep any identifying information in filenames limited to what your collaborators actually need.
A practical download sequence
- Open the completed item and confirm that it is the accepted version.
- Download the actual image or video, not a screenshot of its preview.
- Open the local file and check dimensions, playback and audio where relevant.
- Copy it to an independent backup destination under your control.
- Record which file is approved and which public or private use it covers.
A cloud sync folder can be convenient, but verify that it contains the actual media rather than a shortcut or partial download. If you depend on another storage provider, its own retention, sharing and account rules also matter.
Do not wait for the deadline
Make archival part of approval, not a task postponed until day 89. Production can finish at different times for different items, and an old reference reused in a new project may have its own lifecycle. Do not assume every object in a film project receives a new 90-day window merely because one clip was regenerated.
The exact expiration mechanism can depend on the storage backend. This guide does not promise recovery after deletion or describe a grace period. If a file is no longer available, contact support with the task identifier, but keep expectations realistic and do not expose private references in a public support thread.
Keep access and permission records separate
Downloading a file does not expand your right to publish it. Preserve the subject's approval and the reference authorization where appropriate. A private reception export and a public promotional cut should have separate labels so an archive does not become a source of accidental disclosure.
Protect the backup according to the sensitivity of the source material. Use an appropriate private destination, limit collaborator access and review the archive when the project ends. Long-term storage is a responsibility you choose, not an automatic benefit of generating more versions.
Will a saved Library link work forever?
No permanent availability is promised. Store the file itself if it matters. A browser bookmark cannot preserve content that has expired from its storage location.
Does generating a new version preserve all earlier files?
Do not assume it does. Download the specific accepted versions while available and keep your own version list. A new job and an older source object can have different storage histories.