Choose Smart CDN when
Your application owns the originals, derivative demand is hard to predict, and a Template that accepts a constrained set of URL variables can create the exact image, video, document, or preview that a user requests.
Your images, videos, and files delivered fast to every user, anywhere on the planet.
Skip the upfront work and transform files only when your users actually need them, saving time and resources.
Process and deliver files at lightning speed with optimized infrastructure designed for high-performance transformations.
Transform images, videos, and documents on demand through URL parameters, cached worldwide for fast repeat delivery.
Add parameters to your file URLs to apply and layer multiple effects.

Loading preview…
Here are a few examples that show how you can take advantage of our Smart CDN

Generate meaningful previews for virtually any file type. Smart processing for images, videos, documents, and archives without downloading entire files.

Use AI to intelligently crop images around faces or important subjects.

Require expiring URL signatures and add visible watermarks as part of a controlled delivery workflow.

Dynamically resize images based on device type, screen size, or user preferences. Optimal files for every device.
A conventional CDN caches files that already exist. Transloadit Smart CDN can import an original from your storage, run a saved transformation Template on a cache miss, and deliver the result through the same URL. Subsequent requests reuse the cached derivative until its cache lifetime ends.
Your application owns the originals, derivative demand is hard to predict, and a Template that accepts a constrained set of URL variables can create the exact image, video, document, or preview that a user requests.
Every output is known before publication, a human must approve it, or one workflow must export several persistently stored output files. In those cases, run an asynchronous Assembly first and serve the saved Assembly outputs.
You only need to cache and deliver immutable files that are already prepared. A transformation layer adds little value when the origin contains every required variant.
A Smart CDN Template is still an Assembly workflow. On a cache miss, /file/serve selects the output returned by the URL. As soon as that output is ready, independent Smart-CDN-compatible branches can continue working without holding up the response.
The response path ends at /file/serve. That selected image, document, audio file, or video output can start streaming to the requester and enter the edge cache as soon as it is available.
Other compatible branches in the same Template can power richer experiences or prepare secondary assets. For example:
This additional work runs only on cache misses and every Step must use a Smart-CDN-compatible Robot. Warm cache hits are delivered from the edge without running the Template again.
Smart CDN is a transformation and delivery layer. It does not replace object storage, a digital asset management (DAM) system, a video player, live-streaming infrastructure, or an application’s authorization policy. Read an implementation guide for responsive images or review Smart CDN authentication.
In this image benchmark, a cache miss includes the source import and image transformation. A warm hit reuses the finished derivative at the edge. The difference is why both paths need separate measurements.
| Request region | Cold cache miss p50 | Cold cache miss p95 | Cold cache miss p99 | Warm edge hit p50 | Warm edge hit p95 | Warm edge hit p99 |
|---|---|---|---|---|---|---|
| US East (AWS us-east-1) | 341 | 452 | 496 | 88 | 96 | 106 |
| Europe (AWS eu-west-1) | 356 | 407 | 457 | 28 | 35 | 38 |
| Asia Pacific (AWS ap-southeast-1) | 430 | 485 | 505 | 18 | 27 | 34 |
These results are a dated measurement snapshot—not a latency SLO, availability SLO, or SLA. Internet routing, edge selection, file size, Template complexity, and origin performance all affect production results.
All 300 measured warm responses reported CDN-Cache: HIT. The tested Template advertised public, max-age=259200, s-maxage=86400: up to three days in a browser cache and one day in a shared cache.
A Template can set a different cache duration on /file/serve. For signed URLs, the remaining signature lifetime also limits how long a newly generated response may be cached. Review signing and cache lifetime.
A warm cache hit serves the finished derivative without importing the original or rerunning the Template. A derivative that is not available in cache still depends on the origin and transformation path.
In the same test, a deliberately missing source object returned HTTP 404 with S3_IMPORT_NOT_FOUND and Cache-Control: no-store. Do not rely on stale serving after cache expiry or eviction: this benchmark did not exercise that behavior, and no stale-if-error guarantee is offered here.
Warm responses are served from the delivery network instead of running the transformation again.
Distributed CDN architecture minimizes downtime risk and network congestion for consistent worldwide content delivery.
Require signed URLs and constrain the variables accepted by each saved Template.
CDN infrastructure handles high traffic volumes without compromising performance or user experience.
Cache hits avoid repeated origin imports and transformations, reducing repeat processing and origin transfer.
Transform media files only when requested, eliminating preprocessing needs and saving storage resources.
The guides, Robot reference, and working demos teams reach for when Smart CDN has to run reliably at scale.
Martijn Vermaat, Engineering Manager at WeTransfer
Every plan runs every Robot, so nothing about this service is held back for a bigger one. You are paying for the volume you put through it.
Perfect for trying out Transloadit
For lower-volume workloads
$54 per month. Billed annually · save 22%
For growing workloads and more capacity
For teams with advanced needs