Connect Transloadit to the tools you already use

These are real integration paths backed by dedicated Robots or maintained SDKs. Every guide includes runnable code, authentication boundaries, operational limitations, and primary documentation.

Bring your own storage

Cloud storage

Import originals, process them, and export results without proxying file bytes through your application.

Amazon S3

Import from and export to Amazon S3 with dedicated Robots.

Cloudflare R2

Process R2 objects with dedicated import and store Robots.

Supabase

Connect Supabase Storage through its S3-compatible endpoint.

Tigris

Import and export Tigris objects with first-class Robots.

Azure Blob Storage

Connect Azure Blob Storage containers to Assembly pipelines.

Google Cloud Storage

Import and store Google Cloud objects with a service account.

Dropbox

Process files from a connected Dropbox app and return results.

Backblaze B2

Import from and export to Backblaze B2 buckets.

Box

Move files in and out of Box folders from an Assembly.

DigitalOcean Spaces

Read and write DigitalOcean Spaces objects.

MEGA S4 Object Storage

Import from and export to MEGA S4 Object Storage buckets.

MinIO

Connect a self-hosted MinIO cluster over its S3-compatible API.

OpenStack Swift

Import from and export to OpenStack Swift containers.

Rackspace Cloud Files

Import from and export to Rackspace Cloud Files containers.

Wasabi

Import from and export to Wasabi hot cloud storage.

Move files anywhere

Transfer protocols and publishing platforms

Import through standard transfer protocols, or send processed files directly to media platforms and tus-compatible servers.

FTP

Import from and export to FTP servers.

SFTP

Import from and export to SFTP servers over SSH.

HTTP

Import files from web URLs, including requests with custom headers.

Vimeo

Import videos from Vimeo and export processed videos back.

YouTube

Export processed videos directly to YouTube.

tus

Export results to any tus-compatible upload server.

Ship in your stack

Frameworks and application platforms

Use a maintained SDK or signed browser upload flow while keeping secrets on a trusted server.

Next.js

Signed Uppy uploads for the Next.js App Router.

Laravel

Create Assemblies from Laravel with the official PHP SDK.

Python

Run signed Assembly jobs with the maintained Python SDK.

Ruby

Create and monitor signed Assemblies from Ruby.

iOS

Secure iOS uploads with TransloaditKit and backend signing.

Node.js

Create Assemblies and await results from Node.js.

PHP

Sign uploads and run Assemblies from a PHP application.

Java

Drive Assemblies from JVM services with the maintained Java SDK.

Go

Start and poll Assemblies from Go services.

Android

Upload from Android apps against a signature from your backend.

More official connections

Automation, browser uploads, and infrastructure

Maintained tooling that sits alongside the recipes above, for teams that reach Transloadit through a workflow builder, a browser uploader, or their infrastructure code.

Uppy

Browser uploads with resumability, rich UI, and direct Transloadit support.

Zapier

Trigger media workflows and connect their results to no-code automations.

Convex

Create signed uploads and react to completed Assemblies from Convex functions.

Terraform

Provision and version Transloadit Templates as infrastructure code.

Connect your stack, keep your infrastructure

Every recipe here runs on the same platform your customers’ uploads already depend on.
Upload pipelines you have to maintain
Maintained Robots and SDKs
Credentials scattered through app code
Credentials saved once, referenced by name
File bytes proxied through your servers
Storage-to-storage transfers
Glue code that drifts from the docs
Versioned Templates as the source of truth
GDPR
HIPAA
ISO 27001ISO27001
AES-256
SOC 2 Type II
No credit card needed ·