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
- Builtin 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. - An
@latestreference is intentionally movable, so identical client code can resolve to a later maintained graph; a pinned version provides a stable workflow dependency. - The 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.