Transloadit
Pricing
  • File Uploads
  • File Importing
  • Batch Processing
  • Video Encoding
  • Audio Encoding
  • Image Processing
  • Document Processing
  • Artificial Intelligence
  • File Filtering & Security
  • Media Cataloging
  • File Compression
  • Code Evaluation
  • File Exporting
  • Smart CDN
  • View all services
  • Explore integrations
  • Explore live demos
  • Uppy
  • TransloaditKit
  • Android SDK
  • Node.js SDK
  • Python SDK
  • Ruby SDK
  • Go SDK
  • Java SDK
  • PHP SDK
  • Zapier
  • MCP Server
  • Transloadit CLI
  • Terraform
  • Essentials
  • Best Practices
  • FAQ
  • Robots
  • API
  • Formats
  • Build your first app
  • About
  • Comparisons
  • Open Source
  • Testimonials
  • Jobs
  • Security
  • Posts
  • DevTimes
  • DevTips
  • Press
  • Research
  • Case Studies
  • Solutions
  • Guides
  • Glossary
  • Legal
  • Tools
  • Helping Coursera bring education to millions around the world
  • Transloadit Support
  • Open Source Support
  • Service level agreement
EssentialsRobotsFAQAPIFormatsBest Practices

What if my imports or exports from Backblaze, S3, GCP, etc. are slow?

Transloadit operates on AWS in the regions us-east-1 (North Virginia), eu-west-1 (Ireland) and ap-southeast-1 (Singapore). Assemblies are geo-routed to these regions based on the location of your end user that is triggering the Assembly.

For example, if your end user uploads from Thailand and is thus routed to our ap-southeast-1 region, but your Backblaze bucket is in US-West, the Assembly will export files from Singapore to the US west coast and it will be very slow.

To work around this slowness you can create multiple buckets on Backblaze (or in S3, etc.) that are closer to our three regions. You can then create three sets of Template Credentials and name them:

  • my_credentials_us-east-1
  • my_credentials_eu-west-1
  • my_credentials_ap-southeast-1

Add buckets that are closest to the region in the name of these Credentials, and configure your backend to work with three different file storage locations.

Then in your Template you can reference them like so:

{
  "use": ":original",
  "robot": "/backblaze/store",
  "credentials": "my_credentials_${assembly.region}"
}

This will select the Template Credentials according to the region in which the Assembly was submitted, and will thus pick a Backblaze bucket that is much closer. As a result, exports should run much faster. The same applies to imports as well.

See also:

Will there ever be an encoding queue?
Are Assembly IDs secure?
What are Assemblies?
Contact support⁠

TransloaditChecking status…

Product

  • Services
  • Pricing
  • Demos
  • Tools
  • Security
  • Support

Company

  • About/Press
  • Blog/Jobs
  • Comparisons/Compliance matrix
  • Research
  • Open source
  • Solutions

Docs

  • Getting started
  • Transcoding
  • FAQ
  • API
  • Guides/DevTips
  • Supported formats

More

  • Platform status⁠
  • Community forum⁠
  • StackOverflow⁠
  • Uppy
  • tus⁠

© 2009–2026 Transloadit-II GmbH

PrivacyTermsImprint
EnglishDeutschEspañolPortuguês (Brasil)