
Cloudinary does not use one universal “request wins” rule for upload presets. Signed upload requests generally override matching preset parameters, while supported parameters in unsigned requests generally lose to the preset, with documented exceptions. Inspect the upload mode and the specific parameter before changing the browser code.
Key Takeaways
- Signed and unsigned uploads have different precedence.
- Unsigned calls accept only a limited request-parameter set.
- Some parameters merge rather than replace each other.
Make a parameter-by-parameter comparison
Cloudinary's upload-preset documentation says signed request parameters take precedence except for eager and incoming transformation parameters, where values from both preset and request are applied.
For unsigned uploads, the preset takes precedence for supported matching parameters, except that context and metadata merge. The request takes precedence for filename_override and public_id, although disallow_public_id:true in the preset prevents that public-ID exception.
Do not extrapolate these rules to a parameter that unsigned uploads cannot supply directly.
Trace the actual upload
- Record whether the implementation makes a signed or unsigned upload.
- Identify the exact preset name used by that request.
- Compare only the affected parameters in the request and preset.
- Mark each one as request precedence, preset precedence, merged or unavailable in unsigned requests.
- Have the authorized owner adjust the correct configuration in a non-production sample workflow.
- Inspect the upload response and the stored asset rather than only the browser form.
If the symptom involves transformations, inspect both the preset and request definitions. Under the signed-upload rule, replacing a value in browser code may still leave the preset's transformation participating in processing.
A hypothetical portrait intake
A team expects a browser-supplied naming choice to replace its unsigned preset's configuration. The proposed diagnostic first identifies which naming parameter was actually sent. It then checks whether that parameter is permitted directly and whether a documented exception applies.
This avoids a broad rewrite based on an assumption that all request values win. A different setting in the same request can legitimately follow another rule.
Keep preset names and the request example in a private implementation note if they reveal internal workflow details. Never expose a signing secret to make an unsigned flow behave like a signed backend flow.
Acceptance and scope
Accept when the stored asset's naming, metadata and transformations match the explicitly documented parameter matrix. Check another supported input type if the preset is shared between images and videos; Cloudinary notes that irrelevant asset-type options can be silently ignored.
The approved-file handoff record helps record resulting files and their use. It does not define provider upload precedence. This guide reports no upload test and recommends no incidental change to an organization's default preset.
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: Upload presets: Signed and unsigned request/preset precedence and merged exceptions; asynchronous eager configuration and notifications; asset-type relevance and exact eager transformation representation.
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.