The file infrastructure behind your product
Every file your users upload, scanned, processed, and delivered, without servers of your own.

Text found with OCR 
Profile avatar 
Cropped for mobile - PDFpurchase-order.pdfJPGpurchase-order-scan.jpg

Converted to PDF shared-folder.zipMalware detected
Scanned for viruses - 1080p5.0 Mb/s720p2.8 Mb/s480p1.2 Mb/s360p0.6 Mb/s
Video ready to stream
Trusted since 2009 by
the world’s most ambitious platforms.
One pipeline for every
file in your product
Prepare video, check every upload, and send each file through the processing it needs.
User videos, ready to play
Every video your users upload streams smoothly on any connection, with a poster frame ready.
Every customer upload checked first
Virus-scan every file, flag explicit images, and refuse the types your product does not accept, before anything reaches another user.
Each file type gets the processing it needs
Documents, images, recordings, and archives are sorted by type and feature, then processed automatically.
- File
onboarding-deck.pptx
- Source
- Shared workspace
- Routed through
- /document/convert
- →/document/thumbs
- File
scanned-contract.pdf
- Source
- E-signature
- Routed through
- /document/autorotate
- →/document/ocr
- File
customer-call.mp4
- Source
- Call recorder
- Routed through
- /video/encode
- →/speech/transcribe
- File
bug-repro.mov
- Source
- Support widget
- Routed through
- /video/encode
- →/video/thumbs
- File
profile-photo.jpg
- Source
- Account settings
- Routed through
- /image/facedetect
- →/image/resize
- File
product-shot.png
- Source
- Shared workspace
- Routed through
- /image/optimize
- →/s3/store
- File
q3-forecast.xlsx
- Source
- Shared workspace
- Routed through
- /file/virusscan
- →/document/convert
- File
project-files.zip
- Source
- Import tool
- Routed through
- /file/decompress
- →/file/filter
- File
signed-contract.pdf
- Source
- E-signature
- Routed through
- /file/hash
- →/document/thumbs
- File
avatar-upload.png
- Source
- Account settings
- Routed through
- /file/virusscan
- →/image/describe
- File
podcast-episode.mov
- Source
- Creator studio
- Routed through
- /audio/encode
- →/audio/waveform
- File
whiteboard-photo.jpg
- Source
- Shared workspace
- Routed through
- /image/ocr
- →/s3/store
- File
webinar.mp4
- Source
- Creator studio
- Routed through
- /video/encode
- →/video/adaptive
- File
onboarding-deck.pptx
- Source
- Shared workspace
- Routed through
- /document/convert
- →/document/thumbs
- File
scanned-contract.pdf
- Source
- E-signature
- Routed through
- /document/autorotate
- →/document/ocr
- File
customer-call.mp4
- Source
- Call recorder
- Routed through
- /video/encode
- →/speech/transcribe
- File
bug-repro.mov
- Source
- Support widget
- Routed through
- /video/encode
- →/video/thumbs
- File
profile-photo.jpg
- Source
- Account settings
- Routed through
- /image/facedetect
- →/image/resize
- File
product-shot.png
- Source
- Shared workspace
- Routed through
- /image/optimize
- →/s3/store
- File
q3-forecast.xlsx
- Source
- Shared workspace
- Routed through
- /file/virusscan
- →/document/convert
- File
project-files.zip
- Source
- Import tool
- Routed through
- /file/decompress
- →/file/filter
- File
signed-contract.pdf
- Source
- E-signature
- Routed through
- /file/hash
- →/document/thumbs
- File
avatar-upload.png
- Source
- Account settings
- Routed through
- /file/virusscan
- →/image/describe
- File
podcast-episode.mov
- Source
- Creator studio
- Routed through
- /audio/encode
- →/audio/waveform
- File
whiteboard-photo.jpg
- Source
- Shared workspace
- Routed through
- /image/ocr
- →/s3/store
- File
webinar.mp4
- Source
- Creator studio
- Routed through
- /video/encode
- →/video/adaptive
What your users notice
The infrastructure stays out of sight. What your users see is decks that preview in place, images they can find by what is in them, imports that finish on the first try, and calls with a transcript.
Slide decks preview page by page
PowerPoint uploads become page images, so your users flip through a deck without downloading it.
Three slides of a sample deck, shown one at a time beside a filmstrip 


Images arrive with suggested tags
AI labels what is in each photo, so your search finds an image by what it shows, not its file name.

- Sticky notes
- Notebook
- Meeting
- Laptop
Suggested tagsSticky notes, Notebook, Meeting, Laptop Imports arrive on the first try
Resumable uploads of up to 200 GB per file, depending on plan, pick up where they left off after a dropped connection.
workspace-export.zip6.2 GBUploading part 1 of 8Calls arrive with a draft transcript
Recorded calls play beside a draft transcript, so your users skim what was said instead of rewatching.
- We moved the launch to the second week.
- Then the import tool ships first.
- I’ll share the deck after the call.
Using Transloadit saves development and maintenance. Being able to focus on our product instead of reinventing the wheel cannot be understated.What can Transloadit help with?
Six pieces of file infrastructure SaaS teams usually build, scale, and patch themselves. Each one already runs in production on Transloadit.
A resumable upload service
Uploads from browsers and mobile apps, up to 200 GB per file depending on plan, that resume where they left off when a connection drops.
A document conversion fleet
Office files become PDFs and page thumbnails without LibreOffice workers of your own to size, restart, and keep patched.
An OCR pipeline
Text from PDFs, scans, and screenshots comes back with the results, ready for your search index, without an OCR stack to run.
An image service
Resizing, face-aware cropping, and format conversion, HEIC from iPhones included, plus on-request sizes from Smart CDN.
A video encoding cluster
Screen recordings, demos, and calls encoded for playback, with thumbnails and transcripts, without FFmpeg servers to scale.
Upload security
Signed upload requests, virus scanning with daily signature updates, and type and size filters, before a file reaches storage.
You keep the product.
We run the file infrastructure.
Transloadit is the processing layer, not a replacement for your app, your storage, or your CDN. Here is exactly where the line sits, so nobody discovers it during integration.
What stays with your product
- 01Accounts, permissions, and who can see each file
- 02Your data model and which output belongs to which record
- 03Retention, deletion, and your customers’ data requests
- 04The interface your customers upload from and view files in
What Transloadit handles
- 01Upload endpoints, resumable transfers, and imports from your buckets
- 02Converters, encoders, and virus scanners, scaled and kept patched
- 03Job status and retried notifications to your back end
- 04On-demand transformation and Smart CDN delivery, when enabled
Ship file features, not file servers
Documents, images, audio, and video share one API, so the next file feature needs no new service.
Stuck queues, crashed converters, and encoder upkeep are ours to fix. Parallel processing keeps up as uploads land.
ISO 27001 and SOC 2 Type II, a DPA, signed uploads, and processing in the US, EU, or Asia Pacific.
Workers scale for launches and bulk imports. Work beyond your plan’s job slots queues instead of failing.
Files export to your own S3, GCS, Azure, or R2. Temporary copies are purged after 24 hours by default.
Maintained SDKs for Node.js, Python, Go, and more, and workflows you version like code.
Questions from engineering leads
The answers we would give on an evaluation call, including the cases where another tool is the better choice.
Why not build this ourselves?
You can: FFmpeg, LibreOffice, ImageMagick, and ClamAV are open source. The cost is everything around them: queues, retries, capacity for spikes, security patches, and every format edge case your customers find. Transloadit runs that layer, so your engineers work on the product instead.
What if we move off Transloadit later?
Your files never live only with us: originals and outputs are exported to the storage you configure, and your workflows are JSON you keep in your repository. Leaving means replacing the processing, not migrating your data.
Where does an integration start?
Most teams start with one recurring file task, such as document previews or video encoding, called from your back end or the browser. The next workflow is a few lines of config, not new infrastructure.
How does our product learn that a file is ready?
Each job reports its status and results, and can notify your back end at a URL you choose. Notifications are retried, so a short outage or deploy does not lose a result.
What happens when a launch or a bulk import spikes the volume?
Workers autoscale with demand, so there is nothing to provision ahead of a peak. Your plan’s Priority Job Slots set how many jobs run at once; additional work queues instead of failing, and you can reserve extra slots ahead of a planned peak.
How do we stop abuse of our upload endpoint?
Sign every upload request on your backend with an expiry, so only the parameters you approved can run. Filter Steps reject files by type, size, or duration before processing, and virus scanning stops malware before a file reaches your storage. Read about Signature Authentication
Does Transloadit keep copies of our customers’ files?
Only briefly. Temporary processing copies are deleted after 24 hours by default, and you can turn off temporary result storage per workflow. Job status, which includes file names, is kept for 90 days by default. Originals and results are exported to the storage you configure, and retention and deletion happen in your own systems.
Is Transloadit file storage or a CDN?
Neither, by default. Transloadit is the processing layer between your customers’ uploads and the storage you already use. Smart CDN can deliver right-sized variants on demand when you enable it. See how Transloadit Smart CDN works
Stop building file infrastructure.
Move one recurring file task from your servers to Transloadit, and see the results land in your own storage.