
A corrected event poster can be uploaded under the same local filename yet leave the website showing the old date. Trace the stored identity before diagnosing cache behavior. This guide prepares an offline intake decision; it does not perform an upload, overwrite or production reference change.
Decide whether this is a revision or another candidate
Cloudinary's upload documentation describes random public IDs by default. Using the source filename can retain readability while adding a unique suffix. Removing uniqueness or supplying a custom public ID changes the identity convention; intentional replacement also uses the documented overwrite behavior.
A similarly named file is not evidence that it should replace the approved one. First record whether the new image corrects the same deliverable or represents an alternative crop, product or campaign.
Trace one source to its stored identity
- Preserve the current approved file and its library record.
- Record its full public ID, resource type and delivery type.
- Upload a harmless sample through the intended intake route.
- Inspect the returned identifier rather than only its display label.
- Compare whether the route generated a random ID, a suffixed filename or the intended existing public ID.
- Have the authorized implementation owner align the naming and overwrite contract with the revision policy.
- Verify the correct asset and website reference after the controlled change.
Do not remove unique suffixes globally merely to fix one replacement. Uniqueness can prevent different clients' files named portrait.jpg from colliding.
Keep organizational labels out of the inference
Cloudinary's dynamic-folder documentation says display names need not be unique and are separate from delivery identity. A folder full of matching labels therefore cannot prove that an overwrite occurred.
The approved-version handoff guide supplies the editorial record. Add the returned delivery identity so the implementation can follow the same choice.
When an authorized implementation is later performed, accept only after the intended asset and delivered correction have been verified. If this is an alternative rather than a replacement, give it a separate identity and approval state. No upload, overwrite or live-site change is claimed here.
A filled fictitious poster intake
Every identifier below is invented. Both records use resource type image and delivery type upload; those fields are recorded rather than inferred from a thumbnail. The local name poster.jpg is the same, but the returned IDs differ.
| Record | Public ID | Intended role | Reference implication |
|---|---|---|---|
| Approved wall poster v1 | events/harbor-evening-wall | Existing date edition | Website currently references this asset identity |
| Uploaded date correction | events/poster_q7m2 | Same composition with corrected date | New identity alone does not replace the existing reference |
| Proposed phone crop | events/harbor-evening-phone | Genuine alternative layout | Keep separate from the wall poster |
For the date correction, the authorized implementation owner must decide on the documented replacement contract or an explicit reference update. Do not overwrite the wall poster with the phone crop because both depict the same event. Preserve the old approved edition and distinguish a correction from a new deliverable.
If the eventual correction deliberately targets the existing public ID, record the relevant overwrite behavior and returned result. If the route instead retains a new ID, the reference that would need changing is the wall-poster delivery reference, not an arbitrary similarly labeled asset. Verify the actual delivered image only after that authorized change is made.
The intake note should include exact copy approval, public ID, resource/delivery type, intended role and pending action. A successful association check does not establish that the artwork's new date is factually correct or that every cache is refreshed. Investigate those separately using the confirmed asset identity.
Sources and review limits
- Cloudinary customizing uploads — Public IDs, unique filenames and deliberate overwrite behavior.
Reviewed November 13, 2026. All worked records are constructed examples, not observed generation, application, printing or measurement results. Imagild provides visual artwork; the named external application and supplier control the finishing task. This manuscript remains offline.