What is a URL Transformation?
A URL transformation expresses media-processing instructions in a request URL so a derived asset can be generated or retrieved during delivery. Signatures and parameter validation can restrict permitted operations.
How URL Transformations work
A URL transformation service parses an asset identifier and an ordered set of operations, validates them, then resolves a cached derivative or runs the corresponding media pipeline. The URL consequently acts as both a request description and a cache key. Implementations may encode operations in path segments or query parameters, with signatures binding the approved representation. This pattern belongs at delivery time for image, video, or document variants requested by applications and devices.
Key facts
- 1Equivalent operations written in different orders or parameter forms can fragment caches unless the service canonicalizes requests, because CDNs normally distinguish different URL strings as separate objects.
- 2A signature should cover every transformation parameter and the source identifier; leaving dimensions, format, or origin outside the signed value can permit unauthorized processing changes.
- 3Source replacement requires explicit cache invalidation or a versioned asset identifier, otherwise a previously generated derivative may remain fresh after the underlying master has changed.
When URL Transformations matter
Use URL transformations when responsive sizes or variants cannot all be predicted and generated in advance. Unbounded dimensions or unsigned parameters can enable abusive processing, cache fragmentation, and unexpected cost.
Common use cases for delivery
These examples cover delivery broadly, not specifically URL Transformations.
- Serving image, audio, video, and document derivatives to a geographically distributed audience.
- Protecting private assets worldwide with expiring or signed requests.
- Reducing repeated processing and origin traffic by caching deterministic results.
Working with delivery
This guidance covers delivery broadly, not just URL Transformations.
A client requests an asset using a URL or playback manifest. A delivery layer evaluates authorization and cache state, serves a cached response when possible, or retrieves the asset from its origin before forwarding and optionally caching it.
Delivery choices determine more than download speed. Cache keys, origin behavior, authorization, geographic routing, invalidation, and egress cost decide whether an asset is fast, current, and available to the right audience.
What you gain
- Edge caching places frequently requested assets closer to viewers.
- Explicit cache and authorization rules reduce avoidable origin work.
- Multiple delivery variants let clients request an asset suited to their context.
What it costs
- Long cache lifetimes improve hit ratio but make replacement and invalidation more difficult.
- Signed access protects private media but adds key management, clock, and cache-partitioning concerns.
- More variants improve client fit while increasing storage, cache fragmentation, and operational complexity.
Before production
- 1Define cache keys, cache lifetime, invalidation, and authorization behavior explicitly.
- 2Measure time to first byte, cache-hit ratio, egress, and behavior after an origin failure.
- 3Test signed and unsigned requests at the CDN edge, not only against the origin.