
Moving an asset folder or changing its display name in Cloudinary's dynamic folder mode does not change its delivery URL. Delivery uses the public ID; the immutable asset ID identifies the object for supported management operations. Treat these as separate fields when organizing an approved photo library or repairing a broken website reference.
Key Takeaways
- Dynamic folders and display names organize assets without rewriting public IDs.
- An asset ID cannot replace a public ID in a delivery URL.
- Legacy fixed folder mode has different move behavior.
Identify the product environment's folder mode
Cloudinary's folder-mode guide distinguishes dynamic and legacy fixed folders. In dynamic mode, changing the asset folder or display name leaves the public ID and URL unchanged. In fixed mode, moving an asset changes its public-ID path and can break existing references.
Check the Folder mode indicator on the environment Dashboard before interpreting a move. Do not assume that behavior observed in one environment applies to another.
Record the three names separately
Cloudinary's identifier reference says the asset ID is immutable for the asset's lifetime. The public ID is used for delivery and needs resource type and delivery type for unambiguous identification. A dynamic-mode display name is a label and need not be unique.
- Locate the approved asset and record its display name and current asset folder.
- Read the public ID from the asset's Summary information.
- Obtain the asset ID from the upload response or a documented management lookup where your workflow needs stable object identity.
- Build delivery using the public ID, correct resource type and delivery type.
- Compare the actual delivered picture with the approval record.
- After an organizational move, check whether the public ID really changed before editing website URLs.
Do not paste an asset ID into the delivery path because it appears more permanent.
A hypothetical archive cleanup
A studio moves a portrait from an intake folder to an approved folder in a dynamic-mode environment. Its old public URL still works, and its display name now reads “Approved portrait.” Those observations are compatible: the organization changed, while the delivery identity did not.
If the studio instead deliberately renames the public ID, the website integration needs a separate coordinated update. A display-name edit should not be used as an assumed URL-renaming operation.
Acceptance and limitations
Retain a record joining stable object identity, current public delivery identity and approved file revision. Confirm that the website serves the right photograph; a successful lookup alone does not establish approval.
The approved-version handoff guide explains the editorial selection record. This procedure adds the provider-specific identifier mapping. Do not switch folder modes as an incidental repair: Cloudinary documents migration through support and says it cannot be reverted to fixed mode.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Can I Use a Temporary AI Download Link as My Product Feed Image URL?
Sources and scope
- Cloudinary: Folder modes: Dynamic asset folders and display names are decoupled from public IDs, while legacy fixed folder moves can change URLs; documented folder-mode inspection and migration boundaries.
- Cloudinary: Asset ID versus public ID: Immutable asset ID versus delivery public ID; display names are labels; delivery requires public ID with resource and delivery type.
Documentation-based editorial guidance. All scenarios, worksheets and acceptance checks are hypothetical or proposed. No hands-on test, account operation, benchmark, measured search demand, AI-citation rate or platform acceptance is claimed.
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.