What is a Builtin Template?
A Builtin Template is a versioned, Transloadit-maintained Template stored in API2. It is referenced by a builtin/ slug such as builtin/encode-hls-video@latest.
How Builtin Templates work
An Assembly request can point to a platform-supplied processing graph instead of carrying or owning an equivalent custom Template. The service resolves the Builtin Template identifier and its version, then executes the maintained sequence with the caller’s inputs and supported parameters. This places workflow maintenance at the platform boundary while leaving version selection important for testing, repeatability, and controlled rollout in production integrations.
Key facts
- 1Builtin Template identifiers occupy the
builtin/namespace, and a suffix following@selects a release alias or version rather than forming part of an uploaded file name. - 2An
@latestreference is intentionally movable, so identical client code can resolve to a later maintained graph; a pinned version provides a stable workflow dependency. - 3The built-in graph defines processing steps, not the caller’s media itself. Assembly creation must still provide valid inputs and any parameters required by that particular workflow.
When Builtin Templates matter
Reference a Builtin Template when its maintained workflow matches the required processing steps. Pin a specific version when reproducibility matters, because @latest may adopt later changes.
Common use cases for platform workflows
These examples cover platform workflows broadly, not specifically Builtin Templates.
- Running repeatable upload, import, processing, AI, storage, and notification pipelines.
- Tracking long-running media work independently from an application request.
- Referencing centrally stored credentials by name instead of sending storage secrets with each request.
Working with platform workflows
This guidance covers platform workflows broadly, not just Builtin Templates.
A client authenticates and submits files or references together with workflow instructions. The platform validates the request, schedules dependent operations, records state transitions, and exposes results through a response, polling endpoint, or notification.
Platform concepts become reliable only when their lifecycle is explicit. Authentication, idempotency, retries, timeouts, observability, quotas, and terminal states should be designed together rather than added after failures occur.
What you gain
- Reusable workflows separate application intent from processing infrastructure.
- Stable job identifiers and lifecycle events improve observability and recovery.
- Managed queues and workers let products scale without embedding every media tool.
What it costs
- Synchronous responses are simple but keep connections open while long work executes.
- Aggressive retries improve recovery from transient faults but can duplicate work or overload a dependency.
- Higher concurrency reduces queue time until resource contention or a downstream limit becomes the bottleneck.
Before production
- 1Define authentication, authorization, idempotency, retries, and terminal error behavior.
- 2Observe queue time, execution time, callbacks, and partial results with stable identifiers.
- 3Exercise malformed, duplicate, interrupted, and unauthorized requests before launch.