Migrating Images from Filestack
Even though our Migro utility does a good job migrating your files from Filestack to Uploadcare, image transformations are a bit more complicated to transfer. This article holds a mapping of Filestack image transformation operations to the Uploadcare ones. We also provide some migration practices and visual examples. The following list is based on the names of Filestack operations:
Resize
Filestack image resizing operation has several input parameters that map to
the three Image Transformations: resize
,
preview
, and
scale_crop
.
Here’s what those three do:
resize
— resizes an image to fit into the specified dimensions.preview
— scales an input image to fit into the specified dimensions while preserving its original aspect ratio.scale_crop
— scales an image until one of the dimensions gets equal to the specified size, the rest of image is cropped.
Migrating operation parameters
width
->width
height
->height
fit
,align
->preview
,scale_crop
, andresize
. See below for more info.
When migrating images with the clip
and max
values for fit
: use preview
.
A crop
value for fit
can be migrated by using scale_crop
. When looking to
migrate scale
, resize
can be used. The two supported align
values are:
center
and no value, which defaults to left
.
Examples
Scale image to fit 750 px in width,
Filestack | Uploadcare |
Scale image to fit 500x500 px container,
Filestack | Uploadcare |
Crop image using 500x500 px box, use image center as anchor point,
Original image | Filestack | Uploadcare |
Migrating clip
fit
value, fit image into 500x500 px container,
Filestack | Uploadcare |
Migrating scale
fit
value, fit image into 1500x300 px container,
Filestack | Uploadcare |
Migrating max
fit
value, resize image to fit maximum allowed dimensions.
Note, Filestack and Uploadcare allow different maximum image dimensions.
For instance, the example below deals with the maximum of 3000x3000 pixels for Uploadcare,
that can be increased to 5000x5000 by using /format/jpeg/
,
learn more.
Filestack | Uploadcare |
Migrating align:left
and crop
fit
values, crop image using 200x400 px box,
top-left as anchor point,
Original image | Filestack | Uploadcare |
Migrating align:center
and crop
fit
values, crop image using 200x400 px
box, center as anchor point,
Original image | Filestack | Uploadcare |
Note, the following Filestack align
values are not supported by scale_crop
:
Crop
Filestack image cropping maps to the Uploadcare image crop operation. There’s a difference, though. When setting the crop coordinates that create an area that extends outside the original image dimensions, Filestack will give you the part of an input image that fits into the original dimensions. With Uploadcare, you can choose whichever coordinates, but an area beyond the original image dimensions will be filled with white.
Here’s the difference,
Filestack | Uploadcare |
Migrating operation parameters
x
,y
->two_coords
width
,height
->two_dimensions
Examples
A couple of crop examples,
Original image | Filestack | Uploadcare |
Original image | Filestack | Uploadcare |
Original image | Filestack | Uploadcare |
Rotate
Filestack image rotation well maps to the Uploadcare
rotate operation. It’s for right-angle
counterclockwise image rotation. In order to map the exif
Filestack parameter,
you can use the autorotate
operation that deals with the EXIF Orientation
tag.
Note, with Uploadcare, when you’re applying any transformations to your images,
they’re automatically aligned according to their EXIF. However, you can choose to
use /-/autorotate/no/
to change this behavior.
Migrating operation parameters
deg
or exif
-> angle
Examples (Filestack vs Uploadcare)
Rotate image 180 degrees counterclockwise,
Filestack | Filestack | Uploadcare |
Rotate image according to EXIF,
Filestack | Uploadcare |
Rotate image, discard EXIF info,
Filestack | Uploadcare |
Flip, Flop
The Filestack Flip
and Flop
operations map to the
flip and
mirror Image Processing operations respectively.
The operations require no parameters.
Examples (Filestack vs Uploadcare)
Flipping image,
Original image | Filestack | Uploadcare |
Mirroring image,
Original image | Filestack | Uploadcare |
Piping the two operations,
Original image | Filestack | Uploadcare |
Watermark
Filestack watermarks map to the Image Processing overlay operation. Watermarks, in this regard, are any images layered over your image content.
Migrating operation parameters
file
->uuid
size
->relative_dimensions
position
->relative_coordinates
Examples (Filestack vs Uploadcare)
Add overlay, align: center,
Filestack | Uploadcare |
Add overlay, define dimensions,
Filestack | Uploadcare |
Add overlay, define dimensions and position,
Filestack | Uploadcare |
Face detection
With Uploadcare, the detect_faces operation
is used to get a JSON holding coordinates of faces found in an image. Filestack
face detection well maps to the operation with the export
parameter set to
true
.
The Uploadcare version outputs data similar to the
json operation and requires no input
parameters.
Examples (Filestack vs Uploadcare)
Detect faces and return their coordinates as JSON,
Acquire JSON from Filestack
Acquire JSON from Uploadcare
Filters — blur
The blur
Filestack operation under the Filters
section maps to the
blur Image Processing operation.
Migrating operation parameters
amount
-> strength
Examples
Some blur,
Original image | Filestack | Uploadcare |
More blur,
Original image | Filestack | Uploadcare |
Monochrome
Desaturating images with Uploadcare is done via the
grayscale operation. The Filestack
analog is called monochrome
. Both operations require no input parameters.
Examples
Getting grayscale image,
Original image | Filestack | Uploadcare |
Sharpen
The Filestack image sharpening well maps to the sharp Image Processing operation.
Migrating operation parameters
amount
-> strength
Examples
Sharpen image,
Original image | Filestack | Uploadcare |
Enhance
While the Filestack and Uploadcare image enhancement operations share the same
title: Enhance, the latter also
takes the strength
parameters allowing you to adjust the degree of applied
enhancements.
Examples
Enhance image,
Original image | Filestack | Uploadcare |
Format conversions
Image conversions under the Filestack Filetype conversion
section map to the
format Image Processing operation.
In addition, the Uploadcare version supports the auto
setting that adjusts the
output image format according to the client preferences.
Examples
Set output format to PNG,
Filestack | Uploadcare |
Set output format to JPG,
Filestack | Uploadcare |
Set output format to WebP,
Filestack | Uploadcare |
Image quality
Both Filestack and Uploadcare allow you to change image quality. Filestack allows to change the parameter value explicitly, while Uploadcare has a set of five quality presets. See quality for details.
Migrating operation parameters
value
-> quality
Examples
Reducing image size via quality,
Original image | Filestack | Uploadcare |
Archives
The Filestack Zip
operation maps to the archive
processing operation. However, the latter only works with Group API.