The /file/filter Robot
We let you reject, or direct files against different encoding Steps.
The /file/filter Robot directs files to different encoding Steps based on your conditions.
||(required) String / Array of Strings / Object||
GeneralSpecifies which Step(s) to use as our input.
Special Step namesA special Step name is
Providing several Steps as inputYou can add arrays to
That's likely all you need to know about
› Advanced use cases
Step bundlingSome Robots can gather several Step results for a single invocation. For example, the /file/compress Robot would normally create one archive for each file passed to it. If you'd set
This is also a crucial parameter for the /video/adaptive Robot, otherwise you'll generate 1 playlist for each viewing quality.
Keep in mind that all input Steps must be present in your Template. If one of them is missing (for instance it is rejected by a filter), no result is generated because the Robot waits indefinitely for all input Steps to be finished. Here's a demo that showcases Step bundling.
Group by originalSticking with the /file/compress Robot example, you can set
FieldsYou can be more discriminatory by only using files that match a field name by setting the
Use AsSometimes Robots take several inputs. For instance, the /video/merge Robot can create a slideshow from audio and images. You can map different Steps to the appropriate inputs. Example:
Sometimes the ordering is important, for instance, with our concat Robots. In these cases, you can add an index that starts at 1. You can also optionally filter by the multipart field name. Like in this example, where all files are coming from the same source (end-user uploads), but with different
For times when it is not apparent where we should put the file, you can use Assembly Variables to be specific. For instance, you may want to pass a text file to the /image/resize Robot to burn the text in an image, but you are burning multiple texts, so where do we put the text file? We use specify it via
||Array of Arrays||
||Files that match at least one requirement will be accepted, or declined otherwise. Example:
||Array of Arrays||
||Files that match at least one requirement will be declined, or accepted otherwise. Example:
||Specifies the condition type according to which the members of the
||If this is set to
||This is the error message shown to your users (such as by Uppy) when a file is declined and
Our /file/filter Robot can be used in combination with other Robots, to create powerful workflows unique to your use case. Here are a few example scenarios that you can try live on our website:
- Automatically decompress uploaded archives
- Burn subtitles into a video
- Extract audio from video files
- Filter out all audio files with a bit rate lower than 64K
- Filter out anything other than image files
- Filter out anything other than video or image files
- Filter out files that are smaller than 1KB
- Filter out videos that are larger than 20MB or longer than 5 minutes
- Import your Dropbox files to Transloadit for encoding
- Only resize larger images when resizing files
- Properly preserve transparency across image types
- Reject videos that do not have an audio track
- Resize and apply transparency, based on a clipping path inside an image
Transloadit is a SaaS with a subscription model.
Our /file/filter Robot does not count toward your plan's data. It charges at minimum 0MB whenever it is used. For $49/month you run as many files through our /file/filter Robot as you like.
Just like with your mobile plan, pricing goes down considerably when you commit to larger monthly volumes. You can adjust this every month. More info and available plans on our Pricing page.
Blog posts about the /file/filter Robot
We wrote the following posts about the /file/filter Robot on our blog: