
Cloudinary cannot apply browser-dependent format selection when f_auto is hidden inside a named transformation. Put it directly in the delivery URL, such as t_square/f_auto. If you also need Save-Data-aware quality, expose q_auto outside the named definition so the CDN can interpret that request.
Key Takeaways
- A reusable preset can hide parameters the CDN needs to see.
- Hidden
f_autois ineffective; hiddenq_autostill has limited behavior.- Verify actual requests and returned formats, not filename extensions.
Keep geometry reusable and negotiation visible
Cloudinary's named-transformation documentation says f_auto is not applied inside named transformations. The CDN selects a format for the requesting browser, so the parameter must appear in the delivery URL.
Quality has a narrower exception. A named transformation can use q_auto, but a request with Save-Data: on cannot trigger the CDN's translation to q_auto:eco when that parameter is hidden. The documented default in that case is q_auto:good. Explicit quality choices such as q_auto:best do not have the same CDN dependency.
Inspect and repair one delivery contract
- Record the named definition and the final URL emitted by the application.
- Keep crop and sizing operations in the named transformation if that suits the design.
- Remove reliance on hidden
f_auto; chain it visibly after the named component. - If Save-Data negotiation is required, also put
q_autovisibly in the URL. - With Strict Transformations enabled, ask the implementation owner to approve or sign the exact combined transformation.
- Compare requests with known browser support and, where the client can actually send it, the Save-Data header.
Do not infer a request header from a browser preference label. Record the header actually transmitted.
A hypothetical portfolio preset
An imagined portrait portfolio has one square-crop preset shared across cards. The developer expects automatic format selection from that preset alone. The proposed candidate retains the square geometry but uses visible delivery components for format and quality negotiation.
Compare the decoded picture, response Content-Type, dimensions and transmitted headers. Different requests may legitimately receive the same format; the procedure does not promise a particular codec or a smaller file every time.
Acceptance and boundaries
Accept when the URL exposes the required negotiation parameters, access policy permits it and representative delivered images remain visually suitable. Keep measurements if you want to claim a transfer or performance improvement.
The responsive-image delivery guide addresses browser resource selection and LCP. This issue occurs earlier in a different place: a CDN cannot act on a negotiation parameter hidden behind a named transformation. The same Cloudinary page also warns that automatic width and DPR must remain visible, so review those dependencies in the same implementation instead of creating isolated preset fixes.
Related tasks
- Why Is My Website Slow After I Upload Full-Size AI Images Everywhere?
- JPEG, PNG or WebP: Choose a Photo Export Format
- Why Does a Shared Link Still Show My Old Image After I Updated the Page?
Sources and scope
- Cloudinary: Named transformations: Named transformations cannot hide f_auto from CDN negotiation; hidden q_auto cannot receive Save-Data eco translation; automatic width and DPR also require visible URL parameters.
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.