Take the tour ×  I have an application where users upload an
image and it has to be available in three different sizes
(thumbnail, medium size, full size). The image does not need to
be modified by my users.  It seems there are two options:
Option 1: Use image conversion urls whenever I want to display a
thumbnail. Ex. https://www.filepicker.io/api/file/hFHUCB3iTxyMzs
euWOgG/convert?w=200&h=250  Option 2: Use convert() with store
to store the thumbnail in S3.  My question is can I use Option
1? How would this impact performance? Are the converted files
cached on filepicker.io's end or does filepicker convert the
image every time the user's browser hits the conversion url?
share|improve this question add comment  1 Answer  The converted
files are cached on our end, so using the conversion urls is
entirely supported. If you know the sizes that you want ahead of
time and don't think you'll need the variety, you can also use
the .convert() call to "precache" the conversions, but it's more
of a style preference t