Introducing Turbo Mode for /document/ thumbs
We added a new Turbo mode for our 🤖 /document/thumbs Robot. It emits page thumbnails as soon as they are ready instead of batching them at the end, so downstream Steps can start work earlier. This can reduce end-to-end time for multi-page PDFs; the improvement depends on the document and workflow.
What is Turbo Mode?
Turbo mode lets Transloadit parallelize or stream work so results become available earlier. We first introduced it for our 🤖 /video/encode and 🤖 /video/concat Robots, and are now bringing similar benefits to document thumbnailing. See our Turbo mode FAQ to find out how it works.
How it works for documents
Turbo mode is enabled by default for document thumbnails. Turbo mode allows the
🤖 /document/thumbs Robot to emit a result for
each page as soon as that page is processed. If you prefer batched results, you can opt out per
Step by setting turbo to false.
Leaving Turbo mode enabled means:
- Faster pipelines: subsequent Steps (for example, image post-processing or storing) can begin while later pages are still being rendered.
- Parallel work: Turbo mode can extract pages in parallel for larger documents and distribute resizing across machines. The available concurrency and speedup depend on the workload; doubling the number of pages does not guarantee twice the speedup.
- Page indices: final results are sorted by page, but pages can be emitted out of order while
processing. Use
meta.thumb_indexrather than arrival order to identify a page's zero-based index: the first page has index0.
This streaming behavior is especially useful for document viewers that need to show page previews as soon as possible, or pipelines in which every second matters between ‘upload’ and ‘first usable preview’.
When to use it (and when not to)
✅ Time-sensitive workflows: choose Turbo mode if you want to reduce time-to-first-preview, or if downstream work can run per page.
❌ Cost-sensitive workflows: Turbo mode adds the input document's size for every extracted page
when calculating usage. For multi-page documents this can increase the charge substantially.
Compare the latency benefit with that cost and consider setting turbo to false when cost matters more.
Single-page documents have neither the Turbo performance benefit nor the extra charge. See the
turbo parameter and pricing docs.
Why is it enabled by default?
The default favors earlier results and faster multi-page workflows. That trade-off is not free:
evaluate both latency and usage with representative documents. Set turbo to false in the
Step when you prefer sequential processing and batched results.
Example Assembly
Below is a minimal example that converts a multi‑page PDF into 600‑px wide page thumbnails and
stores them with an index in the file path. Turbo mode is enabled by default; no additional
parameter is needed. The output's zero-based meta.thumb_index
is available as ${file.meta.thumb_index} in the storage path.
First create a stored Template Credential for your private S3 bucket
and replace YOUR_AWS_CREDENTIALS with its name. bucket-default avoids requesting a public
object ACL; keep the bucket policy private too. The path stays under the setup guide's uploads/
policy prefix; update the policy and path together if you change that prefix. The Assembly ID and
original file ID group pages from the same input together, while separating different inputs and runs.
{
"steps": {
"thumbs": {
"use": ":original",
"robot": "/document/thumbs",
"width": 600,
"resize_strategy": "fit"
},
"store": {
"use": "thumbs",
"robot": "/s3/store",
"credentials": "YOUR_AWS_CREDENTIALS",
"acl": "bucket-default",
"path": "uploads/docs/${assembly.id}/${file.original_id}/page-${file.meta.thumb_index}.${file.ext}"
}
}
}
Availability
Turbo mode for document thumbnails is enabled by default. Contact support for help reviewing your workflow.
Learn more and try it
- Read the 🤖 /document/thumbs Robot docs.
- Review the Turbo mode FAQ.
- New to Transloadit? Sign up and start processing in minutes.
Enjoy, and use responsibly!
