
Turning on Cloudinary automatic backup protects newly uploaded assets, but existing assets need the separate Back Up Existing Assets job. Check both scopes before describing an older campaign as covered. A visible media-library thumbnail is not evidence that its earlier file versions are recoverable.
Key Takeaways
- Automatic backup is off by default in the documented workflow.
- Enabling it and covering assets already present are separate steps.
- Backup scope includes originals, not every generated rendition or external source.
Separate the coverage dates
Cloudinary's backup documentation describes enabling automatic backup for new uploads and running a one-time job for assets uploaded earlier. The Existing assets section exposes Back Up Existing Assets and records the job's identifier, creation time and status.
Do not infer that switching the setting on recreates versions already lost before backup existed. The documentation offers support-assisted recovery on a case-by-case basis when automatic backup was not enabled; it does not guarantee that recovery.
Build an asset-coverage receipt
- Record the product environment and when backup was enabled.
- List a few representative older originals and a newly uploaded sample.
- Ask the authorized owner to confirm the configured backup destination.
- If earlier existing assets need coverage, use the documented existing-assets backup workflow.
- Inspect the job's status and confirmation details.
- Check available backup/version information for the representative originals.
- Keep the independent approved deliveries and their source records.
The page notes that large initial inventories may require support assistance. A job request is not the same evidence as a completed job.
A hypothetical older portrait campaign
Suppose a studio enables backup after months of approved portraits are already stored. Its proposed audit distinguishes the older archive from files uploaded afterward.
The useful record says which population was covered by the initial job, which later uploads follow automatic backup and which items remain unverified. “Backup enabled” alone cannot answer those separate questions.
Cloudinary states that repeated existing-assets jobs process assets without a backup copy rather than creating duplicate backups. That behavior helps fill a coverage gap; it is not a claim that the job preserves every historical state that ever existed.
Keep the scope realistic
The documented backups contain original assets. Derived and remotely fetched assets are excluded because the service can regenerate or retrieve them. If a final published rendition or an outside source matters as a fixed record, retain the actual approved file independently.
The independent asset-archive guide explains why a production library should not be your sole archive. This guide addresses a separate provider's explicit new-versus-existing backup population.
Accept coverage only to the extent supported by settings, completed jobs and inspected version records. This article reports no backup operation, storage purchase or recovery test.
Related tasks
- How to Archive Imagild Assets Before the 90-Day Storage Window Ends
- Does a Lightroom Classic Catalog Backup Include My Original Photos?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- Cloudinary: Backups and version management: New-upload versus existing-asset backup setup, job scope and original-only coverage; tag-only changes do not create a backup; own-storage availability, migration guidance and restrictions on managed backup objects and policies.
Documentation-based editorial synthesis with AI-assisted research and drafting. Scenarios, ledgers and acceptance checks are hypothetical or proposed. No hands-on test, account change, measured demand, AI-citation rate, benchmark or client acceptance is claimed. Availability and plan limits remain within each cited source's scope.
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.