What is a Template?
A Template securely stores Transloadit Assembly Instructions and is referenced in API requests through a `template_id`. It lets clients invoke a predefined processing workflow without sending its full instructions.
How Templates work
A Transloadit Template is an account-managed workflow definition that clients invoke indirectly, allowing processing logic to be governed outside the submitting application. Its JSON describes named Assembly steps, their parameters, and how outputs from earlier steps flow into later ones. Referencing a server-side definition reduces payload duplication and keeps sensitive workflow details away from untrusted clients. Templates sit between application requests and Assembly execution, so their change management is part of the integration contract.
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.
Key facts
- 1Step names form references within Assembly Instructions, so renaming a step can break downstream `use` relationships even when every individual operation remains syntactically valid.
- 2A `template_id` selects stored instructions but does not by itself authenticate an API request; account authentication and any request-signing requirements remain separate controls.
- 3Because multiple applications can invoke one Template, a backward-incompatible edit has a wider blast radius than a per-request change; versioned Templates provide a clean migration boundary.
When Templates matter
Use a Template to centralize workflow changes and avoid exposing complete Assembly Instructions in clients. Updating a shared Template can affect every caller, so incompatible changes may require a new Template.
- Running repeatable upload, import, processing, AI, storage, and notification pipelines.
- Tracking long-running media work independently from an application request.
- Applying credentials, quotas, retries, and error policies consistently across integrations.
Working with platform at scale
Guidance that holds across every platform term in this glossary, not just Templates.
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.
Answer these 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.
How Transloadit helps with Templates
When Templates are relevant to your workflow, you can hand the surrounding platform work to Transloadit instead of maintaining the processing stack yourself. Transloadit models file workflows as reusable Assembly Instructions. Upload, import, processing, AI, storage, delivery, status updates, and error handling can be composed without operating the underlying media tools yourself.
Support for a specific codec, container, parameter, or combination can vary by Robot and processing stack. Check the linked documentation for the exact inputs and outputs available for your use case.