Fileschool Guides to File Uploads
One file per guide, recorded on Filestack and taken apart step by step.
-
Convert HEIC to JPG Automatically on Upload
An iPhone photo arrives as HEIC and leaves as JPG, converted inside the upload path so every browser gets an image it renders.
- In
- classic-car.heic, image/heic, 1,960,764 bytes
- Browser
- Could not render this file
- Out
- classic-car.jpg, image/jpeg, 1,681,309 bytes
-
Chunked File Uploads With Resume Support
A file uploads as independent parts. A failure costs one part, and the transfer continues from the last part the server confirmed.
- File
- 8K_Thetestdata.mp4, 48.8 MB
- Settings
- intelligent: fallback, concurrency 3, retry 10
- Result
- Complete, with a CDN URL
No guide matches. Clear the search or pick another stage.
Frequently Asked Questions
What is Fileschool?
Fileschool is the Filestack library of file upload guides. Each guide takes one file, runs it through Filestack, and gives the settings, the code and the result the call returned.
Who are the guides written for?
Developers adding file upload, processing or delivery to an application. A guide gives the parameters of the call rather than a summary of what it does.
Do I need a Filestack account to follow a guide?
A free API key covers the calls in a guide. Sign up at filestack.com/signup-free and use the key in place of YOUR_API_KEY in the examples.
What do the stage filters mean?
The five stages a file passes through on Filestack: select, upload, process, store and deliver. Each guide is filed under the stage its call belongs to, so the filter narrows the library to one part of the path.
Is the code in a guide ready to run?
Yes, with your own API key and file handle in place of the ones in the example. The calls are the ones that produced the output shown next to them.
Where do I ask a question about a guide?
Filestack support takes questions through filestack.com/contact-us, and the Filestack docs carry the full reference for every task a guide uses.