What is Turbo Mode?
Turbo Mode is a Transloadit setting that parallelizes supported Robot work to return results sooner. `/video/encode` and `/video/concat` can complete up to 22x faster, while `/document/thumbs` streams page results.
How Turbo Mode works
Turbo Mode changes how supported Transloadit processing is scheduled by distributing work that would otherwise proceed more serially. The media instructions and requested output remain the governing recipe; the acceleration comes from concurrency and earlier emission of eligible results. Its benefit depends on the Robot and workload, so it is not a universal speed switch. It belongs in latency-sensitive Assembly design where capacity use, result ordering, and downstream readiness are planned together.
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
- 1The documented acceleration applies specifically to supported Robots: `/video/encode` and `/video/concat` can finish up to 22 times faster, rather than every Assembly Step receiving that gain.
- 2For `/document/thumbs`, pages can be processed and made available individually, allowing downstream work to begin before the complete document has produced all thumbnails.
- 3Parallel work can consume Priority Job Slots or incur per-page processing costs more quickly, so concurrency limits and consumers of early results must be sized for burstier execution.
When Turbo Mode matters
Enable Turbo Mode when lower completion latency justifies additional Priority Job Slot or per-page processing costs. Parallel execution can consume capacity faster, so confirm that downstream Steps handle early results correctly.
- 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 Turbo Mode.
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 Turbo Mode
When Turbo Mode is 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.