Built for Bulk
We built Convert.FAST from day one to handle bulk workloads—hundreds of photos from a camera roll, a folder full of screenshots, or an entire archive of documents. Drop them all at once and let our dedicated servers do the rest.
Batch Limits by Tier
Your tier determines how many files you can upload per batch and how many process simultaneously:
| Tier | Files per Batch | Concurrent |
|---|---|---|
| Free | 50 | 3 |
| Pro | 200 | 6 |
| Business | 1000 | 10 |
Why concurrent limits? Our fair scheduler prevents any single user from monopolising workers so everyone gets fast processing. Upload 200 files on Pro, but only 6 process at once—the rest queue automatically.
See our Limits page for the complete breakdown including file size limits and total batch size limits per converter.
How Long Does a Batch Take?
Your upload speed is the biggest factor. Our servers process images in milliseconds—the time you're waiting is mostly spent uploading your files. A 20 Mbps upload connection will feel very different from a 100 Mbps one.
Real-world example (images): 1,000 iPhone 14 HEIC photos converted to JPG via HEIC → JPG took 5 minutes flat on a 500/20 Mbps Australian connection—drop to download. Most of that time was the upload.
Real-world example (audio): Audio conversion is remarkably fast. At ~250ms per minute of content, a 3-hour M4B audiobook converts to OGG in under a minute of server time. A podcast library with 10 hours of content processes in about 2-3 minutes. The bottleneck is usually your upload speed, not our processing.
Once files reach our servers, processing is fast. Typical server-side times by tier:
- Free (incl. guests): 50 files in 1–2 minutes
- Pro: 200 files in 3–4 minutes
- Business: 1000 files in 5–10 minutes
During peak load, times may extend slightly as our fair scheduler rotates between users. Paid tiers get priority, but no one can block the queue.